CPS 230 para 38 Tolerance Levels for Each Critical Operation
For every critical operation the entity must set tolerance levels covering the maximum period of disruption it would tolerate, the maximum extent of data loss it would accept, and the minimum service levels it would main
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
- Board approval evidence · Policy repository / GRC workspace
governing documentDocuments that govern the control
- Tolerance level register covering all three dimensions per critical operation · Policy repository / GRC workspace
- Basis and rationale for each tolerance · Document repository
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
- Only a time based tolerance set
- Minimum service levels during alternative operation undefined
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 36 Mandatory Minimum Classification of Critical Operations · CPS 230 para 40 Required Content of the Business Continuity Plan