CA.L2-3.12.2 Plan of Action
Develop and carry out plans of action that correct identified deficiencies and reduce or eliminate vulnerabilities.
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 of progress and closure for completed items · Document repository
governing documentDocuments that govern the control
- Plan of action and milestones with owners and target dates · Policy repository / GRC workspace
- Linkage from assessment findings to plan entries · 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 maintained as a static list with no progress
- Findings closed without evidence of correction
- Deficiencies identified but never entered into the plan
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.1 Security Control Assessment · CA.L2-3.12.3 Security Control Monitoring