CPS 230 para 13 Identification, Assessment and Management of Operational Risk
The entity must identify, assess and manage the operational risks arising from inadequate or failed internal processes and systems, from the actions or inactions of people, and from external drivers and events, recognisi
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
- Risk and control self assessment records · Document repository
- Coverage evidence across all products, activities, processes and systems · Document repository
governing documentDocuments that govern the control
- Operational risk taxonomy and register · 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 technology risk only
- Externally driven risks omitted
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 12 Key Principles for Operational Risk, Resilience and Service Providers · CPS 230 para 14 Prevention, Adaptation and Return to Normal Operations