CA.L2-3.12.4 System Security Plan
Develop, document and periodically update a system security plan describing system boundaries, the operating environment, how each requirement is implemented, and connections to other systems.
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
- Version history showing periodic update · Document repository
- Approval record for the current version · Document repository
governing documentDocuments that govern the control
- Current system security plan covering boundary, environment, implementation and interconnections · 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
- Plan describes intent rather than actual implementation
- Boundary and interconnections omitted or stale
- No defined update trigger or cadence
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 sheetCA.L2-3.12.3 Security Control Monitoring · CM.L2-3.4.1 System Baselining