HIPAA · §164.308 Administrative safeguards
§164.308(a)(7)(ii)(D)
Testing and Revision Procedure
frameworkHIPAA Security Rule
section§164.308 Administrative safeguards
statusAddressable
csf 2.0GV.OC-04 ID.IM-01 ID.IM-02 ID.IM-03 ID.IM-04 PR.IR-02 PR.IR-03 RC.CO-04 RC.RP-02 RC.RP-03 RC.RP-05
topicsDisaster Recovery
frameworks1 9 2
Official textImplement procedures for the periodic testing and revision of contingency plans.45 CFR Part 164 Subpart C, via NIST SP 800-66r2 (public domain)
Wrong or missing mapping? Report it
| Framework | Requirement | Title | Link | Source / reason |
|---|---|---|---|---|
| NIST CSF 2.0 | PR.IR-03RC.RP-02RC.RP-05 | Mechanisms are implemented to achieve resilience requirements in normal and adverse situations; Recovery actions are selected, scoped, prioritized, and performed… | Editorial | Same topic: Disaster Recovery (editorial pick)4 loosely related (not mappings)GV.OC-04 Critical objectives, capabilities, and services that external stakeholders depend on or expect from the organization are understood and communicated Only shares CSF GV.OC-04: related, not a mapping PR.IR-02 The organization's technology assets are protected from environmental threats Only shares CSF PR.IR-02: related, not a mapping RC.CO-04 Public updates on incident recovery are shared using approved methods and messaging Only shares CSF RC.CO-04: related, not a mapping RC.RP-03 The integrity of backups and other restoration assets is verified before using them for restoration Only shares CSF RC.RP-03: related, not a mapping |
| ISO 27001 | A.5.30A.8.14 | ICT readiness for business continuity; Redundancy of information processing facilities | Editorial | Same topic: Disaster Recovery (editorial pick)18 loosely related (not mappings)A.5.26 Response to information security incidents Only shares CSF ID.IM-04, RC.RP-02, RC.RP-05: related, not a mapping Clause 4.2 Understanding the needs and expectations of interested parties Only shares CSF GV.OC-04, PR.IR-03: related, not a mapping A.5.20 Addressing information security within supplier agreements Only shares CSF GV.OC-04: related, not a mapping A.5.31 Legal, statutory, regulatory and contractual requirements Only shares CSF GV.OC-04: related, not a mapping A.7.5 Protecting against physical and environmental threats Only shares CSF PR.IR-02: related, not a mapping …and 10 more in the downloads |
| CIS v8.1 | CIS 11.1 | Establish and Maintain a Data Recovery Process | Editorial | Same topic: Disaster Recovery (editorial pick)4 loosely related (not mappings)CIS 17.2 Establish and Maintain Contact Information for Reporting Security Incidents Only shares CSF RC.CO-04: related, not a mapping CIS 17.6 Define Mechanisms for Communicating During Incident Response Only shares CSF RC.CO-04: related, not a mapping CIS 11.4 Establish and Maintain an Isolated Instance of Recovery Data Only shares CSF RC.RP-03: related, not a mapping |
| SOC 2 | A1.2A1.3 | Environmental protections, backups and recovery infrastructure; Testing recovery plan procedures | Editorial | Same topic: Disaster Recovery (editorial pick)6 loosely related (not mappings)CC7.5 Recovering from identified security incidents Only shares CSF ID.IM-03, ID.IM-04, RC.CO-04, RC.RP-02…: related, not a mapping A1.1 Capacity management to meet availability commitments Only shares CSF GV.OC-04, PR.IR-03: related, not a mapping CC2.3 Communication with external parties Only shares CSF RC.CO-04, RC.RP-05: related, not a mapping CC9.1 Mitigating risks from business disruptions Only shares CSF GV.OC-04, PR.IR-03: related, not a mapping CC3.1 Objectives specified clearly enough to identify risks Only shares CSF GV.OC-04: related, not a mapping |
| PCI DSS | 12.10.1 | Incident response plan ready to activate | Editorial | Same topic: Disaster Recovery (editorial pick)19 loosely related (not mappings)12.10.2 Incident response plan reviewed and tested annually Only shares CSF ID.IM-02, ID.IM-04, PR.IR-03, RC.RP-02: related, not a mapping 12.10.6 Plan updated from lessons learned and industry changes Only shares CSF ID.IM-02, ID.IM-04, PR.IR-03, RC.RP-02: related, not a mapping 11.4.4 Penetration test findings corrected and retested Only shares CSF ID.IM-02, RC.RP-05: related, not a mapping 12.10.3 Incident response staff available around the clock Only shares CSF ID.IM-04, RC.CO-04: related, not a mapping 5.3.2 Periodic scans or continuous behavioural analysis Only shares CSF RC.RP-03: related, not a mapping 9.1.1 Physical security policies documented and kept current Only shares CSF PR.IR-02: related, not a mapping …and 11 more in the downloads |
| CMMC | IR.L2-3.6.1SC.L2-3.13.2MP.L2-3.8.9PE.L2-3.10.6 | Incident Handling; Security Engineering… | No mapping. Only shares CSF ID.IM-01, ID.IM-02, ID.IM-03, RC.CO-04…: related, not a mapping | |
| 800-53 | CP-7CP-10CP-2CP-3CP-4 | Alternate Processing Site; System Recovery and Reconstitution… | Crosswalk | Same topic: Disaster Recovery (editorial pick) NIST HIPAA → SP 800-53 crosswalk 24 loosely related (not mappings)IR-4 Incident Handling Only shares CSF ID.IM-01, ID.IM-02, ID.IM-03, RC.CO-04…: related, not a mapping IR-8 Incident Response Plan Only shares CSF ID.IM-01, ID.IM-02, ID.IM-03, ID.IM-04…: related, not a mapping SA-8 Security and Privacy Engineering Principles Only shares CSF ID.IM-01, ID.IM-02, ID.IM-03, PR.IR-03: related, not a mapping …and 16 more in the downloads |
| GDPR | Art.32(1)(c) | Security of processing | Editorial | Same topic: Disaster Recovery (editorial pick)2 loosely related (not mappings)Art.34(1) Communication of a personal data breach to the data subject Only shares CSF RC.CO-04, RC.RP-05: related, not a mapping |
| NIS2 | 4.14.2 | Business continuity and disaster recovery plan; Backup management | Editorial | Same topic: Disaster Recovery (editorial pick) |
| Essential Eight | ISM-1515 | Restoration of data, applications and settings from backups to a common point in time… | Editorial | Same topic: Disaster Recovery (editorial pick)10 loosely related (not mappings)ISM-1511 Backups of data, applications and settings are performed and retained in accordance… Only shares CSF RC.RP-03: related, not a mapping ISM-1705 Privileged user accounts (excluding backup administrator accounts) cannot access… Only shares CSF RC.RP-03: related, not a mapping ISM-1706 Privileged user accounts (excluding backup administrator accounts) cannot access their… Only shares CSF RC.RP-03: related, not a mapping ISM-1707 Privileged user accounts (excluding backup administrator accounts) are prevented from… Only shares CSF RC.RP-03: related, not a mapping ISM-1708 Backup administrator accounts are prevented from modifying and deleting backups during… Only shares CSF RC.RP-03: related, not a mapping ISM-1810 Backups of data, applications and settings are synchronised to enable restoration to a… Only shares CSF RC.RP-03: related, not a mapping ISM-1811 Backups of data, applications and settings are retained in a secure and resilient manner Only shares CSF RC.RP-03: related, not a mapping ISM-1812 Unprivileged user accounts cannot access backups belonging to other user accounts Only shares CSF RC.RP-03: related, not a mapping …and 2 more in the downloads |
| DORA | Art.11(6)Art.12(4) | Response and recovery; Backup policies and procedures, restoration and recovery procedures and methods | Editorial | Same topic: Disaster Recovery (editorial pick)13 loosely related (not mappings)Art.12(6) Backup policies and procedures, restoration and recovery procedures and methods Only shares CSF ID.IM-04, RC.RP-02: related, not a mapping …and 5 more in the downloads |
| CPS 234 | — | No requirement | No mapping in our data | No mapping in our data (CPS 234 is principles-based and its links are editorial). |
| Cyber Essentials | — | No requirement | No mapping in our data | No mapping in our data (Cyber Essentials covers five technical controls only). |
Crosswalk a published crosswalk (NIST, ENISA, CIS, PCI SSC) makes the link · Editorial ControlMapping's judgement where no crosswalk exists; the reason is shown · only shares a CSF 2.0 outcome: worth checking, not a mapping · No mapping in our data nothing mapped in our data; often new work, but check the coverage notes. How links are sourced.