Frameworks / ASD Strategies to Mitigate Cyber Security Incidents / ASD37-36 ASD Strategies to Mitigate Cyber Security Incidents
Recovering Data and System Availability
ASD Strategies to Mitigate Cyber Security Incidents ASD37-36: System recovery capabilities (Very Good) System recovery capabilities including standard operating environment images to restore computers to a known good state.
Maintained by Gerard Blokdyk · Verified against the published standard 31 May 2026 · Control text last updated 21 May 2026 What else in your programme already covers this This control maps to 169 controls across 95 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.
NIST-CSF-PR.IR-03 Mechanisms are implemented to achieve resilience requirements in normal and adverse situations 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-02 Recovery actions are selected, scoped, prioritized, and performed NIST-CSF-RC.RP-04 Critical mission functions and cybersecurity risk management are considered to establish post-incident operational norms NIST-CSF-RC.RP-05 The integrity of restored assets is verified, systems and services are restored, and normal operating status is confirmed 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 NIST-CSF-RS.MI-02 Incidents are eradicated API1164-17 Wireless and Field Communications API1164-18 Field Device Security API1164-19 Safety Instrumented Systems Interface ASBv3-IR-6 Containment, eradication and recovery - automate the incident handling ASBv3-PV-3 Define and establish secure configurations for compute resources BR-1 Ensure regular automated backups CIS-11.1 Establish and Maintain a Data Recovery Process CIS-11.2 Perform Automated Backups CIS-4.1 Establish and Maintain a Secure Configuration Process CM-2 Baseline Configuration CM-2(3) Retention of Previous Configurations CP-10 System Recovery and Reconstitution CM-2 Baseline Configuration CM-2(3) Retention of Previous Configurations CP-10 System Recovery and Reconstitution FEDRAMP-CP-9 System Backup FedRAMP-Boundary Authorization Boundary, SSP, SAR, POA&M documentation FedRAMP-IncidentReporting FedRAMP incident reporting to PMO and US-CERT IEC62443-16 Incident response plan for operational disruptions IEC62443-17 Recovery plan for critical systems IEC62443-20 Exercises and drills for OT incidents 8.3.2 Identification of strategies and solutions 8.3.5 Implementation of solutions 8.4.5 Recovery ISO27019-16 Incident response plan for operational disruptions ISO27019-18 Reporting obligations to authorities ISO27019-20 Exercises and drills for OT incidents 27031-8.1 Exercising and Testing 27031-8.2 Maintaining IRBC 27031-9.3 Management Review PICERL-C2 System Backup PICERL-R1 System Restoration PICERL-R2 Security Verification SOC2-A1.2 A1.2 Environmental protection, backup and recovery infrastructure SOC2-A1.3 A1.3 Testing recovery plan procedures SOC2-CC7.5 CC7.5 Recovering from security incidents SSAE18-A1.2 A1.2 - Environmental Protections and Recovery SSAE18-A1.3 A1.3 - Recovery Plan Testing SSAE18-CC7.5 CC7.5 - Incident Recovery C5-OPS-08 Data Backup and Recovery - Regular Testing C5-PSS-11 Images for Virtual Machines and Containers IMO-MSC-FAL-Recover-BackupRestore-ContinuityOfNavigation-LessonsLearned-Drills IMO MSC-FAL Recover Function - Backup and Restore + Continuity of Navigation + Continuity of Cargo Operations + Continuity of Propulsion + Lessons Learned + Drills + Resilience IMO-MSC-FAL-Respond-IncidentResponse-Communication-FlagState-PortAuthority-CIRT-USCGNVIC IMO MSC-FAL Respond Function - Incident Response Plan + Containment + Communication + Flag State + Port Authority + USCG NVIC + Class Society Notification + CIRT ISO22316-08 Recovery time and point objectives ISO22316-12 Recovery strategy for critical activities 5.30 ICT readiness for business continuity 8.13 Information backup 5.30 ICT readiness for business continuity 8.13 Information backup ISO22317-08 Recovery time and point objectives ISO22317-12 Recovery strategy for critical activities ISO22318-08 Recovery time and point objectives ISO22318-12 Recovery strategy for critical activities NFPA1600-5.3 Resource Needs Assessment NFPA1600-6.4 Continuity and Recovery NISTSP34-2 Business Impact Analysis (BIA): Critical Resources, Recovery Priorities NISTSP34-4 Information System Contingency Plan (ISCP) Development IM8-RES.2 Disaster Recovery IM8-RES.4 Resilience Testing ISMSP-PI-06 Personal Information Destruction ISMSP-SYS-06 Business Continuity and Disaster Recovery E8-BACKUP-ML1 Regular Backups (ML1) ANSSI-HYG-37 Define and Apply a Backup Policy for Critical Components 4.4.8 Business Continuity and Recovery DIQ-1 Data Integration and Interoperability FFIEC-12 Disaster recovery procedures FIRST-CSIRTF-SA2-ISIM Service Area 2 - Information Security Incident Management (Intake, Analysis, Containment, Recovery, Coordination, Crisis) GAMP5-Supplier-Operations-Change-Periodic Supplier Assessment, Operational Phase, Change Control and Periodic Review GLBA-Subordinate-Rules-Operationalisation GLBA Operationalisation through FTC Safeguards Rule, Privacy Rule, SEC Reg S-P and Banking-Agency Guidelines HKMA-CRAF-Domain5-6-Response-Recovery-SitAwareness HKMA C-RAF Domain 5 (Response and Recovery) + Domain 6 (Situational Awareness) - Incident Response, Recovery, Threat Landscape, Information Sharing HKMA-SPM-OR-RR-SA-OperationalResilience HKMA SPM Operational Risk (OR-1), Operational Resilience (OR-2), Recovery Planning (RR-1), Outsourcing (SA-2) IACS-UR-E26-Respond-Recover-IncidentResponse-Recovery-Backup-Lessons IACS UR E26 Respond + Recover Goals - Incident Response + Communication + Recovery + Backup + Lessons Learned IEEE1686-IR-Recovery-Reporting-Exercises-Drills-RECOV IEEE 1686 - Incident Response + Recovery from Failed Update + Reporting to Authorities + Coordination with Sector-Specific Agencies + Exercises and Drills ISO-22320-5.2 Incident management process 27011-8.6 Data protection and backup ISO27043-23 Backup and recovery procedures ISO21434-23 Backup and recovery procedures JP-FSA-CYB-Incident-Response-Playbooks-Containment-Eradication-Recovery-Post-Mortem-Tabletop-CSIRT Japan FSA Cybersecurity Incident Response + Playbooks + Containment + Eradication + Recovery + Post-Mortem + Tabletop Exercises + CSIRT + FSA Notification + Customer Communication + Forensics + Lessons Learned MTCS-Acquisition-Development-Maintenance-Supplier-Vulnerability-DevSecOps-SBOM-SDLC-SCA-API-Container MTCS Acquisition + Development + Maintenance + Supplier + Vulnerability + DevSecOps + SBOM + SDLC + SCA MAS-TRM-Reliability-Data-Centre-Chapters-7-8-RTO-RPO-BCP-DR-System-Availability-4-Hours-12-Months MAS TRM Reliability + Data Centre + Chapters 7-8 + RTO + RPO + BCP + DR + System Availability 4 Hours 12 Months NABERS-3 NABERS Water Performance Rating NAIC-5 Third Party Service Provider Oversight - Section 4(F)(3) and Section 5 NERCCIP-6 Incident Reporting and Response Planning + Recovery Plans (CIP-008 + CIP-009) NISTPF-8 Protect-P Information Protection Processes (PR.PO-P) NISTSP115-8 Operational Considerations - Tools, Reporting Templates, ISMS Integration, Annex Material NISTSP123-5 Server Operations - Patching, Malware, Logging, Backup NISTSP137-7 Incident Response Integration and Ongoing Authorization NISTSP144-6 Availability, Resilience, BCP/DR, and SLA Management NISTSP145-3 Rapid Elasticity Characteristic and Capacity Management NISTSP146-7 Service Level, Performance, Reliability, Interoperability, and Portability NISTSP61-5 Containment, Eradication, and Recovery NISTSP63R4-4 Authenticator Lifecycle: Binding, Recovery, Replacement, Suspension, Revocation NISTSP82-7 OT Incident Response, Forensics, Recovery, and Continuity NISTSP88-5 Media Inventory, Tracking, Chain of Custody, and Sanitization Records NISTSP92-6 Log Retention: Policy, Tiered Storage, Backup, Secure Disposal, Legal Hold NGCB-6 Incident Response, 72-Hour NGCB Notification, and Independent Investigation OSFIB13-3 Cyber Security: Identification, Protection, Detection, Response, Recovery OWASPMASVS-7 MASVS-RESILIENCE: Resilience Against Reverse Engineering OWASPSAMM-5 Operations: Incident Management, Environment Management, Operational Management OMANCS-7 Business Continuity, Disaster Recovery, and Resilience OPENBANK-8 Incident Detection, Response, Customer Notification, Post-Incident Review, BCM OSSFSC-8 Project Maintenance, Sustainability, Integration with Supply Chain Security PCI-P2PE-12 Disaster recovery procedures PCI-PIN-12 Disaster recovery procedures PCI-SSF-12 Disaster recovery procedures PSDTWO-2 SCA Exemptions and Risk-Based Authentication PTESPHASE-3 Threat Modeling SHAREASSESS-4 Vulnerability Management, Patching, Application Security SUPCHAIN-2 Source Integrity - Branch Protection, Code Review, Two-Person Rule SOC-CY-A2 Disaster Recovery TSAPIPE-2 OT/IT Network Segmentation and Access Control SEMD-CS-3 Cyber Resilience 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 Recovering Data and System Availability You are reading one control. How much of ASD Strategies to Mitigate Cyber Security Incidents have you already done? ASD Strategies to Mitigate Cyber Security Incidents ASD37-36 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of ASD Strategies to Mitigate Cyber Security Incidents your existing evidence covers. Hold NIST SP 800-53 Rev 5 and 32 of 37 ASD Strategies to Mitigate Cyber Security Incidents controls already carry evidence.
Each report names every control your existing framework evidences, every one it does not, the reasoning behind each claim, and the claims that were argued against and rejected. 0 were rejected on the NIST SP 800-53 Rev 5 pair alone.
Query this from an agent The graph holds this control, the 169 it maps to, and the evidence behind each claim, over MCP and REST.