SC.L2-3.13.2 Security Engineering
Apply architectural design, software development techniques and systems engineering principles that promote effective information security.
3
artefacts
0
held by a system
1
at each review
hard
to go live
Policy repository / GRC workspace
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 principles are applied in design reviews · Document repository
governing documentDocuments that govern the control
- Documented security architecture and design principles · Policy repository / GRC workspace
- Secure development standards applied to in house software · Policy repository / GRC workspace
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
- Principles documented but absent from actual design decisions
- Secure development standards not applied to acquired or outsourced code
- No design review step in the development process
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 sheetSC.L2-3.13.1 Boundary Protection · SC.L2-3.13.3 Role Separation