SOC 2 · CC9 Risk mitigation
CC9.1
Mitigating risks from business disruptions
frameworkSOC 2 (Trust Services Criteria)
sectionCC9 Risk mitigation
csf 2.0GV.OC-04 GV.RM-01 GV.RM-02 GV.RM-03 GV.RM-06 PR.IR-03 RC.RP-04
topicsRisk Management, Business Continuity
frameworks0 10 1
Official text · not licensableSummary (ControlMapping's wording): Mitigating risks from business disruptions. The criterion text is AICPA's copyright.
Wrong or missing mapping? Report it
| Framework | Requirement | Title | Link | Source / reason |
|---|---|---|---|---|
| NIST CSF 2.0 | GV.OC-04GV.RM-01GV.RM-02GV.RM-03GV.RM-06PR.IR-03RC.RP-04 | Critical objectives, capabilities, and services that external stakeholders depend on or expect from the organization are understood and communicated; Risk management objectives are established and agreed to by organizational stakeholders… | Editorial | Same topic: Business Continuity, Risk Management (editorial pick) |
| ISO 27001 | A.5.29A.5.30A.8.14Clause 6.1.1Clause 6.1.3 | Information security during disruption; ICT readiness for business continuity… | Editorial | Same topic: Business Continuity, Risk Management (editorial pick)8 loosely related (not mappings)A.5.1 Policies for information security Only shares CSF GV.RM-01, GV.RM-02, GV.RM-03, GV.RM-06: related, not a mapping Clause 6.1.2 Information security risk assessment Only shares CSF GV.RM-01, GV.RM-02, GV.RM-06: 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.8.27 Secure system architecture and engineering principles Only shares CSF PR.IR-03: related, not a mapping |
| CIS v8.1 | CIS 11.1 | Establish and Maintain a Data Recovery Process | No mapping. Only shares CSF PR.IR-03: related, not a mapping | |
| PCI DSS | 12.3.112.10.1 | Targeted risk analysis for flexible-frequency requirements; Incident response plan ready to activate | Editorial | Same topic: Risk Management, Business Continuity (editorial pick)26 loosely related (not mappings)5.2.3.1 Re-evaluation frequency set by targeted risk analysis Only shares CSF GV.RM-03, GV.RM-06: related, not a mapping 5.3.2.1 Scan frequency set by targeted risk analysis Only shares CSF GV.RM-03, GV.RM-06: related, not a mapping 6.3.1 Vulnerabilities identified and risk-ranked Only shares CSF GV.RM-03, GV.RM-06: related, not a mapping 6.3.3 Security patches installed promptly Only shares CSF GV.RM-03, GV.RM-06: related, not a mapping 7.2.5.1 System and application account access periodically reviewed Only shares CSF GV.RM-03, GV.RM-06: related, not a mapping 8.6.3 System account passwords protected and changed Only shares CSF GV.RM-03, GV.RM-06: related, not a mapping 9.5.1.2.1 Inspection frequency set by targeted risk analysis Only shares CSF GV.RM-03, GV.RM-06: related, not a mapping 10.4.2.1 Review frequency set by targeted risk analysis Only shares CSF GV.RM-03, GV.RM-06: related, not a mapping …and 18 more in the downloads |
| CMMC | RA.L2-3.11.1 | Risk Assessments | Editorial | Same topic: Risk Management (editorial pick)1 loosely related (not mappings) |
| 800-53 | CP-2(8)CP-7PM-9PM-28RA-7 | Identify Critical Assets; Alternate Processing Site… | Editorial | Same topic: Business Continuity, Risk Management (editorial pick) |
| HIPAA | §164.308(a)(1)(ii)(B)§164.308(a)(7)(ii)(C) | Risk Management; Emergency Mode Operation Plan | Editorial | Same topic: Risk Management, Business Continuity (editorial pick)12 loosely related (not mappings)§164.308(a)(7)(ii)(D) Testing and Revision Procedure Only shares CSF GV.OC-04, PR.IR-03: related, not a mapping §164.308(a)(7)(ii)(E) Applications and Data Criticality Analysis Only shares CSF GV.OC-04: related, not a mapping …and 4 more in the downloads |
| GDPR | Art.24(1)Art.32(1)(b)Art.32(2) | Responsibility of the controller; Security of processing… | Editorial | Same topic: Risk Management, Business Continuity (editorial pick)1 loosely related (not mappings) |
| NIS2 | 2.14.14.37.1 | Risk management framework; Business continuity and disaster recovery plan… | Editorial | Same topic: Risk Management, Business Continuity (editorial pick)1 loosely related (not mappings)1.1 Policy on the security of network and information systems Only shares CSF GV.RM-03: related, not a mapping |
| Essential Eight | ISM-1515 | Restoration of data, applications and settings from backups to a common point in time… | No mapping. Only shares CSF PR.IR-03: related, not a mapping | |
| DORA | Art.5(2)(a)Art.6(1)Art.6(8)Art.11(1)Art.11(4)Art.11(6)Art.16(1)Art.24(1) | Governance and organisation; ICT risk management framework… | Editorial | Same topic: Risk Management, Business Continuity (editorial pick)3 loosely related (not mappings)Art.12(4) Backup policies and procedures, restoration and recovery procedures and methods Only shares CSF PR.IR-03: related, not a mapping |
| CPS 234 | Para 13Para 15Para 27Para 31 | Board ultimately responsible for information security; Maintain a capability commensurate with threats… | Editorial | Same topic: Risk Management (editorial pick) |
| 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.