CA-5 Plan of action and milestones
Requires a plan of action and milestones to record planned remediation for weaknesses found in control assessments and for known vulnerabilities, and requires that plan to be updated on a defined frequency using findings
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
- Closure evidence for completed items and re-test results · Source control / CI pipeline
governing documentDocuments that govern the control
- Current plan of action and milestones with owners, dates and resource estimates · Policy repository / GRC workspace
- Traceability from assessment and audit findings into plan entries · Policy repository / GRC workspace
- Update history evidencing the defined update frequency · Document repository
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 holds only assessment findings while vulnerability scan results are tracked elsewhere
- Milestone dates slip repeatedly with no re-approval or risk acceptance
- Items closed on assertion without evidence that the weakness was actually fixed
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