SA-15 Development Process, Standards, and Tools
Sets expectations on the developer's own process, standards and tooling, since delivered security depends on them.
3
artefacts
0
held by a system
2
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
none for this control
periodic reviewEvidence produced at each review
- Evidence of the developer's process and tool use · Document repository
- Review of the developer's own supply chain for tooling · Document repository
governing documentDocuments that govern the control
- Required development standards in contract · Vendor register / contract repository
First move
This control is evidenced by people and documents, not systems. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date. Do not try to automate it.
Common gaps auditors find
- process requirements unverified
- developer tool chain never considered as a risk
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 sheetSA-11 Developer Testing and Evaluation · SA-16 Developer-Provided Training