{
  "uid": "cogitave.learn.secure-sdlc",
  "kind": "module",
  "href": "/modules/secure-sdlc/",
  "title": "Build with the secure SDLC",
  "summary": "State the security baseline - threat modeling, least privilege, and IAM - and follow the secure development lifecycle that shifts security left, so each stage of a change carries its own security gate instead of a check bolted on at the end.",
  "type": null,
  "products": [
    "cogitave-core"
  ],
  "roles": [
    "developer"
  ],
  "levels": [
    "intermediate"
  ],
  "subjects": [
    "software-engineering"
  ],
  "headings": [],
  "source": "By the end of this module, you'll be able to:\n- Distinguish the security controls the Security Standard owns (IAM, secrets, PKI, security operations) from the process the Secure Development Lifecycle Standard owns.\n- Explain the security baseline: STRIDE-style threat modeling, least privilege, and identity and access management for humans, workloads, and agents.\n- Map security as a gate onto each stage of the request lifecycle - from a threat model at the design gate to remediation SLAs after release - rather than treating it as an afterthought.\n- Say when a threat model is mandatory and what enforces the no-new-high-or-critical gate, and follow each rule to the standard that owns the detail.\n",
  "units": [
    "cogitave.learn.secure-sdlc.introduction",
    "cogitave.learn.secure-sdlc.the-security-baseline",
    "cogitave.learn.secure-sdlc.the-secure-development-lifecycle",
    "cogitave.learn.secure-sdlc.knowledge-check",
    "cogitave.learn.secure-sdlc.summary"
  ],
  "durationInMinutes": 27,
  "badge": "cogitave.learn.secure-sdlc.badge",
  "partOf": "cogitave.learn.paths.engineering-standards"
}