CPS 234 para 17 Active Maintenance of Capability Against Change
The entity must actively maintain its information security capability as vulnerabilities and threats change, including changes driven by its information assets or business environment.
3
artefacts
1
held by a system
2
at each review
moderate
to go live
Vulnerability scanner / patch tooling
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- Threat and vulnerability monitoring inputs · Vulnerability scanner / patch tooling
periodic reviewEvidence produced at each review
- Records of capability adjustments following change · Document repository
- Change triggers linking asset or environment change to capability review · Cloud console / configuration management
governing documentDocuments that govern the control
none for this control
First move
Start with the 1 of 3 artefacts that already live in a system (Vulnerability scanner / patch tooling); keep the periodic reviews but log each one as a dated record with a named reviewer.
Common gaps auditors find
- Capability set once at implementation and not revisited
- No trigger connecting business change to capability review
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 sheetCPS 234 para 16 Assessment of Related Party and Third Party Capability · CPS 234 para 18 Information Security Policy Framework