CPS 234 para 15 Information Security Capability
The entity must maintain an information security capability sized to the threats facing its information assets and sufficient to keep the entity operating soundly.
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
- Capability assessment covering resources, skills and controls · Document repository
- Resourcing and budget records for the security function · Document repository
governing documentDocuments that govern the control
- Skills matrix for security personnel · 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
- Capability asserted but never assessed
- No link between assessed threat level and resourcing
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 14 Definition of Information Security Roles and Responsibilities · CPS 234 para 16 Assessment of Related Party and Third Party Capability