AIS-04 Secure Application Design and Development
Build applications through a secure development lifecycle so the organisation's security requirements are applied at design, build, deployment and operation.
4
artefacts
1
held by a system
2
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
- Records showing the lifecycle applied to a real project end to end · Source control / CI pipeline
periodic reviewEvidence produced at each review
- Design review or threat model records for recent applications · Source control / CI pipeline
- Evidence of security requirements being carried into build and deployment · Source control / CI pipeline
governing documentDocuments that govern the control
- The documented secure development lifecycle with security activities at each stage · 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
- Security activity concentrated at the end of the lifecycle only
- Threat modelling done for flagship projects and skipped elsewhere
- Operational stage excluded, so security requirements stop at go-live
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-03 Application Security Metrics · AIS-05 Automated Application Security Testing