PR.IR-03 Mechanisms are implemented to achieve resilience requirements in normal and adverse situations
Mechanisms are implemented to achieve resilience requirements in normal and adverse situations. Control from NIST Cybersecurity Framework 2.0 framework, domain: PR - Protect.
5
artefacts
0
held by a system
2
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
- Failover and failback tested with evidence · Backup / DR tooling
- Chaos engineering exercise outcomes · Document repository
governing documentDocuments that govern the control
- Resilience architecture patterns for critical services · Policy repository / GRC workspace
- Capacity planning and load testing reports · Policy repository / GRC workspace
- Resilience targets traced to business outcomes · 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
- Failback never tested
- Resilience patterns inconsistent across teams
- Chaos engineering absent in production
- Targets not refreshed against business change
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 sheetPR.IR-02 The organization's technology assets are protected from environmental threats · PR.IR-04 Adequate resource capacity to ensure availability is maintained