PO.2.1 Roles and Responsibilities for Secure Development
Define and assign roles and responsibilities for secure software development across product, engineering, security, and operations. Make the responsibilities measurable so that ownership for security work is clear.
4
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
- Annual review of role definitions · Identity provider / directory
governing documentDocuments that govern the control
- RACI for SSDF practices · Policy repository / GRC workspace
- Security champion programme charter · Policy repository / GRC workspace
- Individual security objectives in performance management · 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
- security is responsible and accountable for everything in the RACI
- no security champions assigned in product teams
- performance objectives do not reflect security work
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 sheetPO.1.3 Communicate Requirements to Third-Party Providers · PO.2.2 Training and Skills Maintenance