AIS-06 Automated Secure Application Deployment
Deploy applications through standardised, repeatable and policy-compliant release mechanisms, automating the deployment path wherever it is practical.
4
artefacts
1
held by a system
1
at each review
moderate
to go live
Source control / CI pipeline
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- Deployment pipeline definitions showing the compliant path · Source control / CI pipeline
periodic reviewEvidence produced at each review
- Approval records for any manual deployment · Source control / CI pipeline
governing documentDocuments that govern the control
- The documented deployment standard and the tooling that implements it · Policy repository / GRC workspace
- Records of deployments performed, showing the standard path was used · Policy repository / GRC workspace
First move
Start with the 1 of 4 artefacts that already live in a system (Source control / CI pipeline); keep the periodic reviews but log each one as a dated record with a named reviewer.
Common gaps auditors find
- A sanctioned pipeline exists but manual deployments bypass it routinely
- Deployment configuration itself is unmanaged and drifts between environments
- No record of who deployed what, so a release cannot be traced
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 sheetAIS-05 Automated Application Security Testing · AIS-07 Application Vulnerability Remediation