CPS 234 para 21 Implementation of Information Security Controls
Controls protecting information assets must be implemented in a timely way and sized to the vulnerabilities and threats, the criticality and sensitivity of the assets, the asset life cycle stage and the potential consequ
3
artefacts
0
held by a system
1
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
- Evidence of timeliness of control implementation · Document repository
governing documentDocuments that govern the control
- Control set mapped to classified assets · Document repository
- Life cycle coverage from design through to disposal · 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
- Controls applied uniformly with no reference to classification
- Decommissioning and disposal stages uncontrolled
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 20 Information Asset Classification · CPS 234 para 22 Evaluation of Third Party Control Design