CPS 234 para 20 Information Asset Classification
Information assets, including those held by related parties and third parties, must be classified by criticality and sensitivity reflecting the potential impact of an incident on the entity or on depositors, policyholder
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
- Coverage evidence for third party held assets · Vendor register / contract repository
governing documentDocuments that govern the control
- Information asset register with criticality and sensitivity ratings · Policy repository / GRC workspace
- Classification scheme and rating rationale · 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
- Register covers internally hosted assets only
- Classification not tied to impact on customers or the entity
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 19 Policy Direction to All Responsible Parties · CPS 234 para 21 Implementation of Information Security Controls