cm/controlmapping
Sources
ISO 27001 · ISMS clauses 4–10
Clause 8.3

Information security risk treatment

frameworkISO/IEC 27001:2022 sectionISMS clauses 4–10 csf 2.0GV.OC-01 GV.OC-02 topics— frameworks2 2 4 5
Official text · not licensableTitle: Information security risk treatment. The control text is ISO's copyright; see ISO/IEC 27001:2022.

Wrong or missing mapping? Report it

Equivalents of Clause 8.3 in other frameworks
FrameworkRequirementTitleLinkSource / reason
NIST CSF 2.0GV.OC-01GV.OC-02The organizational mission is understood and informs cybersecurity risk management; Internal and external stakeholders are understood, and their needs and expectations regarding cybersecurity risk management are understood and consideredLoosely relatedNo mapping. Only shares CSF GV.OC-01, GV.OC-02: related, not a mapping
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).
SOC 2CC5.1Control activities that mitigate risksEditorialControlMapping editorial: Selecting control activities that reduce risk: ISO's risk treatment, planned (6.1.3) and carried out (8.3).
1 loosely related (not mappings)
CC3.1 Objectives specified clearly enough to identify risks Loosely related
Only shares CSF GV.OC-01: related, not a mapping
PCI DSS12.1.112.1.412.8.112.8.5Information security policy established and published; Executive responsibility for information security assigned…Loosely relatedNo mapping. Only shares CSF GV.OC-01, GV.OC-02: related, not a mapping
+2 more loosely related (not mappings)
12.9.1 Service providers acknowledge responsibilities to customers Loosely related
Only shares CSF GV.OC-02: related, not a mapping
12.9.2 Service providers support customer compliance requests Loosely related
Only shares CSF GV.OC-02: related, not a mapping
CMMCRA.L2-3.11.1Risk AssessmentsLoosely relatedNo mapping. Only shares CSF GV.OC-02: related, not a mapping
800-53CA-5PM-4RA-7Plan of Action and Milestones; Plan of Action and Milestones Process…CrosswalkNIST SP 800-53 → ISO 27001 mapping
8 loosely related (not mappings)
PM-9 Risk Management Strategy Loosely related
Only shares CSF GV.OC-02: related, not a mapping
PM-11 Mission and Business Process Definition Loosely related
Only shares CSF GV.OC-01: related, not a mapping
PM-18 Privacy Program Plan Loosely related
Only shares CSF GV.OC-02: related, not a mapping
PM-30 Supply Chain Risk Management Strategy Loosely related
Only shares CSF GV.OC-02: related, not a mapping
SR-3 Supply Chain Controls and Processes Loosely related
Only shares CSF GV.OC-02: related, not a mapping
SR-5 Acquisition Strategies, Tools, and Methods Loosely related
Only shares CSF GV.OC-02: related, not a mapping
SR-6 Supplier Assessments and Reviews Loosely related
Only shares CSF GV.OC-02: related, not a mapping
SR-8 Notification Agreements Loosely related
Only shares CSF GV.OC-02: related, not a mapping
HIPAA§164.308(a)(1)(ii)(B)Risk ManagementEditorialControlMapping editorial: HIPAA's risk management (reduce risk to a reasonable level) is ISO 27001 risk treatment (6.1.3, 8.3).
GDPR—No requirementNo mapping in our dataNo mapping in our data (only GDPR's security articles are mapped, editorially).
NIS22.1Risk management frameworkCrosswalkENISA NIS2 → ISO 27001 mapping
1 loosely related (not mappings)
1.1 Policy on the security of network and information systems Loosely related
Only shares CSF GV.OC-02: related, not a mapping
Essential Eight—No requirementNo mapping in our dataNo mapping in our data (Essential Eight links are editorial only).
DORAArt.8(1)Art.11(5)Identification; Response and recoveryLoosely relatedNo mapping. Only shares CSF GV.OC-01: related, not a mapping
CPS 234—No requirementNo mapping in our dataNo mapping in our data (CPS 234 is principles-based and its links are editorial).
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.