CA.L2-3.12.1 Security Control Assessment
Assess the security controls in place periodically to determine whether they are effective as implemented.
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
- Completed assessment results per control · Document repository
- Evidence assessments cover effectiveness and not just presence · Document repository
governing documentDocuments that govern the control
- Assessment plan defining scope, method and frequency · 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
- Assessment confirms a control exists without testing whether it works
- Scope excludes parts of the CUI environment
- No defined periodicity so assessments lapse
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