PR.PS-06 Secure software development practices are integrated, and their performance is monitored throughout the software development life cycle
Secure software development practices are integrated, and their performance is monitored throughout the software development life cycle.
5
artefacts
1
held by a system
1
at each review
hard
to go live
Document repository
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- Static and dynamic analysis pipeline configuration · Source control / CI pipeline
periodic reviewEvidence produced at each review
- Pre release security sign off records · Source control / CI pipeline
governing documentDocuments that govern the control
- Secure SDLC standard with control gates · Policy repository / GRC workspace
- Threat modeling outputs per project · Document repository
- Software composition analysis findings · Document repository
First move
Mostly documents and reviews. Pull the 1 system-held artefact from your Source control / CI pipeline on a schedule; put the documents under version control with an owner and review date, and log each review as a dated record with a named reviewer.
Common gaps auditors find
- Threat modeling skipped for fast track projects
- Pipeline analysis breaks but does not block
- Composition analysis findings unprioritized
- Sign off absent for emergency releases
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 sheetPR.PS-05 Installation and execution of unauthorized software are prevented · RC.CO-03 Recovery activities and progress in restoring operational capabilities are communicated to designated internal and external stakeholders