CPS 230 para 36 Mandatory Minimum Classification of Critical Operations
Unless it can justify otherwise the entity must classify as critical operations at least payments, deposit taking and management, custody, settlements and clearing for an ADI, claims processing for an insurer, investment
3
artefacts
0
held by a system
0
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
none for this control
governing documentDocuments that govern the control
- Classification decisions against the mandatory minimum list · Policy repository / GRC workspace
- Documented justification for any listed operation excluded · Document repository
- Mapping of supporting systems and infrastructure · 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
- Mandatory list not applied to the entity type
- Exclusions taken without a documented justification
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 230 para 34 Critical Operations Register, Continuity Plan and Activation · CPS 230 para 38 Tolerance Levels for Each Critical Operation