SA-17 Developer Security and Privacy Architecture and Design
Requires the developer to produce architecture and design evidence sufficient for the organization to judge the security of what it is buying.
3
artefacts
0
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
none for this control
periodic reviewEvidence produced at each review
- Review records of those deliverables · Document repository
governing documentDocuments that govern the control
- Architecture and design deliverables required and received · Policy repository / GRC workspace
- Traceability from requirement to design · Document 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
- design evidence withheld as proprietary and the risk unaccepted
- deliverables received but never reviewed
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-16 Developer-Provided Training · SA-20 Customized Development of Critical Components