Secure Software Delivery Architecture¶
Security controls only matter if teams keep them on when a release is late.
What you will learn¶
- Build, sign, and verify artefact provenance
- Policy gates versus advisory scanners
- Secrets management across pipelines and runtime
- Break-glass procedures that still leave an audit trail
Production scenarios¶
- Container image promotion across environments
- Blocking known-critical CVEs without freezing all delivery
- Separating build identities from deploy identities