SEC11-BP06 Deploy software programmatically
Deploy through automated pipelines with separation of duties, approvals and audit so no human pushes code or infrastructure directly to production.
Source: AWS Well-Architected Security Pillar, SEC11-BP06. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open AWS Well-Architected Security Pillar in the compliance library.
These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.
system holds itEvidence a system already holds
- Approval gate configuration · Cloud console / configuration management
- Production deploy audit log · SIEM / log platform
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- Pipeline definitions · Policy repository / GRC workspace
- Human deploy exception register · Policy repository / GRC workspace
First move
Common gaps auditors find
- manual deployments to production
- no separation between build and deploy roles
- no audit of deployments
Do this for your whole sheet
Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.
Build my evidence sheetSEC11-BP05 Centralize services for packages and dependencies · SEC11-BP07 Regularly assess security properties of the pipelines