Frameworks / SANS Incident Handler's Handbook and PICERL Methodology / PICERL-R1 What else in your programme already covers this This control maps to 85 controls across 42 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.
ASD37-34 Regular backups (Essential) ASD37-35 Business continuity and disaster recovery plans (Very Good) ASD37-36 System recovery capabilities (Very Good) NIST-CSF-RC.RP-01 The recovery portion of the incident response plan is executed once initiated from the incident response process NIST-CSF-RC.RP-06 The end of incident recovery is declared based on criteria, and incident-related documentation is completed NIST-CSF-RS.MA-05 The criteria for initiating incident recovery are applied SOC2-A1.2 Environmental protections, data backups, and recovery infrastructure support availability SOC2-A1.3 Recovery plan procedures support system recovery from failures 4.4.8 Business Continuity and Recovery DIQ-1 Data Integration and Interoperability OWASPSAMM-5 Operations: Incident Management, Environment Management, Operational Management PSDTWO-2 SCA Exemptions and Risk-Based Authentication SHAREASSESS-4 Vulnerability Management, Patching, Application Security SUPCHAIN-2 Source Integrity - Branch Protection, Code Review, Two-Person Rule TSAPIPE-2 OT/IT Network Segmentation and Access Control CYB-5 Cyber Incident Response Plan Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected .
Other controls in Phase 5 - Recovery Query this from an agent The graph holds this control, the 85 it maps to, and the evidence behind each claim, over MCP and REST.