SA-3 System Development Life Cycle
Runs C-SCRM activities at defined points across the development life cycle, including for acquired components.
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 activities occurred at those points · Source control / CI pipeline
governing documentDocuments that govern the control
- Life cycle definition with C-SCRM activities and gates · Policy repository / GRC workspace
- Roles assigned across the life cycle · 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
- C-SCRM activity concentrated at purchase with nothing during development or disposal
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 sheet