cm/controlmapping
Sources
SOC 2 · CC3 Risk assessment
CC3.1

Objectives specified clearly enough to identify risks

Official text · not licensableSummary (ControlMapping's wording): Objectives specified clearly enough to identify risks. The criterion text is AICPA's copyright.

Wrong or missing mapping? Report it

Equivalents of CC3.1 in other frameworks
FrameworkRequirementTitleLinkSource / reason
NIST CSF 2.0GV.OC-01GV.OC-04GV.OC-05GV.RM-01GV.RM-02GV.RM-03GV.RM-06The organizational mission is understood and informs cybersecurity risk management; Critical objectives, capabilities, and services that external stakeholders depend on or expect from the organization are understood and communicated…EditorialSame topic: Business Environment, Risk Management (editorial pick)
ISO 27001Clause 4.1Clause 4.2Clause 6.1.1Clause 6.1.3Clause 4.3Clause 6.2Understanding the organization and its context; Understanding the needs and expectations of interested parties…EditorialSame topic: Business Environment, Risk Management (editorial pick)
ControlMapping editorial: Objectives specified clearly enough to identify risk: ISO's security objectives (6.2) within a defined ISMS scope (4.3).
10 loosely related (not mappings)
A.5.1 Policies for information security Loosely related
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 Loosely related
Only shares CSF GV.RM-01, GV.RM-02, GV.RM-06: related, not a mapping
A.5.3 Segregation of duties Loosely related
Only shares CSF GV.OC-05: related, not a mapping
A.5.8 Information security in project management Loosely related
Only shares CSF GV.OC-05: related, not a mapping
A.5.20 Addressing information security within supplier agreements Loosely related
Only shares CSF GV.OC-04: related, not a mapping
A.5.31 Legal, statutory, regulatory and contractual requirements Loosely related
Only shares CSF GV.OC-04: related, not a mapping
Clause 6.1 Actions to address risks and opportunities Loosely related
Only shares CSF GV.OC-01: related, not a mapping
Clause 8.1 Operational planning and control Loosely related
Only shares CSF GV.OC-01: related, not a mapping
…and 2 more in the downloads
CIS v8.1—No requirementNo mapping in our dataNo mapping in our data (most CIS links are editorial: CIS's published crosswalk covers 49 of 153 safeguards).
PCI DSS12.3.112.5.2Targeted risk analysis for flexible-frequency requirements; PCI DSS scope confirmed annually and on changeEditorialSame topic: Risk Management, Business Environment (editorial pick)
27 loosely related (not mappings)
5.2.3.1 Re-evaluation frequency set by targeted risk analysis Loosely related
Only shares CSF GV.RM-03, GV.RM-06: related, not a mapping
5.3.2.1 Scan frequency set by targeted risk analysis Loosely related
Only shares CSF GV.RM-03, GV.RM-06: related, not a mapping
6.3.1 Vulnerabilities identified and risk-ranked Loosely related
Only shares CSF GV.RM-03, GV.RM-06: related, not a mapping
6.3.3 Security patches installed promptly Loosely related
Only shares CSF GV.RM-03, GV.RM-06: related, not a mapping
7.2.5.1 System and application account access periodically reviewed Loosely related
Only shares CSF GV.RM-03, GV.RM-06: related, not a mapping
8.6.3 System account passwords protected and changed Loosely related
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 Loosely related
Only shares CSF GV.RM-03, GV.RM-06: related, not a mapping
10.4.2.1 Review frequency set by targeted risk analysis Loosely related
Only shares CSF GV.RM-03, GV.RM-06: related, not a mapping
…and 19 more in the downloads
CMMCRA.L2-3.11.1Risk AssessmentsEditorialSame topic: Risk Management (editorial pick)
800-53PM-9PM-11PM-28RA-7RA-9Risk Management Strategy; Mission and Business Process Definition…EditorialSame topic: Risk Management, Business Environment (editorial pick)
11 loosely related (not mappings)
PM-30 Supply Chain Risk Management Strategy Loosely related
Only shares CSF GV.OC-04, GV.OC-05, GV.RM-03, GV.RM-06: related, not a mapping
SR-2 Supply Chain Risk Management Plan Loosely related
Only shares CSF GV.RM-01, GV.RM-03: related, not a mapping
CP-2(8) Identify Critical Assets Loosely related
Only shares CSF GV.OC-04: related, not a mapping
CP-7 Alternate Processing Site Loosely related
Only shares CSF GV.OC-04: related, not a mapping
PM-3 Information Security and Privacy Resources Loosely related
Only shares CSF GV.RM-03: related, not a mapping
PM-8 Critical Infrastructure Plan Loosely related
Only shares CSF GV.OC-04: related, not a mapping
PM-18 Privacy Program Plan Loosely related
Only shares CSF GV.RM-06: related, not a mapping
RA-3 Risk Assessment Loosely related
Only shares CSF GV.RM-06: related, not a mapping
…and 3 more in the downloads
HIPAA§164.308(a)(1)(ii)(B)Risk ManagementEditorialSame topic: Risk Management (editorial pick)
16 loosely related (not mappings)
§164.308(a)(1)(ii)(A) Risk Analysis Loosely related
Only shares CSF GV.RM-06: related, not a mapping
§164.308(a)(7) Contingency Plan Loosely related
Only shares CSF GV.OC-04: related, not a mapping
§164.308(a)(7)(ii)(B) Disaster Recovery Plan Loosely related
Only shares CSF GV.OC-04: related, not a mapping
§164.308(a)(7)(ii)(C) Emergency Mode Operation Plan Loosely related
Only shares CSF GV.OC-04: related, not a mapping
§164.308(a)(7)(ii)(D) Testing and Revision Procedure Loosely related
Only shares CSF GV.OC-04: related, not a mapping
§164.308(a)(7)(ii)(E) Applications and Data Criticality Analysis Loosely related
Only shares CSF GV.OC-04: related, not a mapping
§164.308(b)(1) Business Associate Contracts and Other Arrangements Loosely related
Only shares CSF GV.OC-05: related, not a mapping
§164.308(b)(4) Written Contract or Other Arrangement Loosely related
Only shares CSF GV.OC-05: related, not a mapping
…and 8 more in the downloads
GDPRArt.24(1)Art.32(2)Responsibility of the controller; Security of processingEditorialSame topic: Risk Management (editorial pick)
1 loosely related (not mappings)
Art.32(1)(b) Security of processing Loosely related
Only shares CSF GV.OC-04: related, not a mapping
NIS22.17.1Risk management framework; Policies and procedures to assess the effectiveness of cybersecurity risk-management measuresEditorialSame topic: Risk Management (editorial pick)
5 loosely related (not mappings)
1.1 Policy on the security of network and information systems Loosely related
Only shares CSF GV.RM-03: related, not a mapping
4.1 Business continuity and disaster recovery plan Loosely related
Only shares CSF GV.OC-04: related, not a mapping
5.1 Supply chain security policy Loosely related
Only shares CSF GV.OC-05: related, not a mapping
5.2 Directory of suppliers and service providers Loosely related
Only shares CSF GV.OC-05: related, not a mapping
13.1 Supporting utilities Loosely related
Only shares CSF GV.OC-05: related, not a mapping
Essential Eight—No requirementNo mapping in our dataNo mapping in our data (Essential Eight links are editorial only).
DORAArt.5(2)(a)Art.6(1)Art.6(8)Art.8(1)Art.11(5)Art.16(1)Art.24(1)Governance and organisation; ICT risk management framework…EditorialSame topic: Risk Management, Business Environment (editorial pick)
3 loosely related (not mappings)
Art.11(1) Response and recovery Loosely related
Only shares CSF GV.OC-04: related, not a mapping
Art.11(4) Response and recovery Loosely related
Only shares CSF GV.OC-04: related, not a mapping
Art.11(6) Response and recovery Loosely related
Only shares CSF GV.OC-04: related, not a mapping
CPS 234Para 13Para 15Para 27Para 31Board ultimately responsible for information security; Maintain a capability commensurate with threats…EditorialSame topic: Risk Management (editorial pick)
Cyber Essentials—No requirementNo mapping in our dataNo 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 · Loosely related 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.