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

Operational planning and control

frameworkISO/IEC 27001:2022 sectionISMS clauses 4–10 csf 2.0GV.OC-01 GV.OC-02 GV.SC-01 GV.SC-03 RC.RP-04 topics— frameworks2 0 9 2
Official text · not licensableTitle: Operational planning and control. The control text is ISO's copyright; see ISO/IEC 27001:2022.

Wrong or missing mapping? Report it

Equivalents of Clause 8.1 in other frameworks
FrameworkRequirementTitleLinkSource / reason
NIST CSF 2.0GV.OC-01GV.OC-02GV.SC-01GV.SC-03The 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 considered…Loosely relatedNo mapping. Only shares CSF GV.OC-01, GV.OC-02, GV.SC-01, GV.SC-03: related, not a mapping
+1 more loosely related (not mappings)
RC.RP-04 Critical mission functions and cybersecurity risk management are considered to establish post-incident operational norms Loosely related
Only shares CSF RC.RP-04: related, not a mapping
CIS v8.1CIS 15.2Establish and Maintain a Service Provider Management PolicyLoosely relatedNo mapping. Only shares CSF GV.SC-01: related, not a mapping
SOC 2CC9.2A1.1A1.2CC3.1Managing vendor and business partner risk; Capacity management to meet availability commitments…Loosely relatedNo mapping. Only shares CSF GV.SC-01, GV.SC-03, RC.RP-04, GV.OC-01: related, not a mapping
+1 more loosely related (not mappings)
CC9.1 Mitigating risks from business disruptions Loosely related
Only shares CSF RC.RP-04: related, not a mapping
PCI DSS1.2.31.2.46.3.16.3.2Accurate network diagram maintained; Accurate account-data flow diagram maintained…Loosely relatedNo mapping. Only shares CSF GV.SC-01, RC.RP-04, GV.SC-03: related, not a mapping
+15 more loosely related (not mappings)
6.4.3 Payment page scripts authorised and integrity-checked Loosely related
Only shares CSF GV.SC-01, GV.SC-03: related, not a mapping
11.6.1 Payment page changes and tampering detected Loosely related
Only shares CSF GV.SC-01, GV.SC-03: related, not a mapping
12.1.4 Executive responsibility for information security assigned Loosely related
Only shares CSF GV.OC-02, GV.SC-01: related, not a mapping
12.8.1 List of third-party service providers kept Loosely related
Only shares CSF GV.OC-02, GV.SC-01: related, not a mapping
…and 11 more in the downloads
CMMCRA.L2-3.11.1Risk AssessmentsLoosely relatedNo mapping. Only shares CSF GV.OC-02, GV.SC-03: related, not a mapping
800-53CM-3PL-7PM-1SA-1SA-4Configuration Change Control; Concept of Operations…CrosswalkNIST SP 800-53 → ISO 27001 mapping
15 loosely related (not mappings)
PM-9 Risk Management Strategy Loosely related
Only shares CSF GV.OC-02, GV.SC-03, RC.RP-04: related, not a mapping
PM-30 Supply Chain Risk Management Strategy Loosely related
Only shares CSF GV.OC-02, GV.SC-01, GV.SC-03: related, not a mapping
SR-3 Supply Chain Controls and Processes Loosely related
Only shares CSF GV.OC-02, GV.SC-01, GV.SC-03: related, not a mapping
PM-11 Mission and Business Process Definition Loosely related
Only shares CSF GV.OC-01, RC.RP-04: related, not a mapping
PM-18 Privacy Program Plan Loosely related
Only shares CSF GV.OC-02, GV.SC-03: related, not a mapping
SR-2 Supply Chain Risk Management Plan Loosely related
Only shares CSF GV.SC-01, GV.SC-03: related, not a mapping
IR-8 Incident Response Plan Loosely related
Only shares CSF RC.RP-04: related, not a mapping
PM-8 Critical Infrastructure Plan Loosely related
Only shares CSF RC.RP-04: related, not a mapping
…and 7 more in the downloads
HIPAA§164.308(a)(6)§164.316(b)(2)(ii)§164.316(b)(2)(iii)§164.308(a)(1)Security Incident Procedures; Availability…Loosely relatedNo mapping. Only shares CSF GV.SC-03, RC.RP-04: related, not a mapping
+22 more loosely related (not mappings)
§164.308(a)(1)(ii)(A) Risk Analysis Loosely related
Only shares CSF GV.SC-03: related, not a mapping
§164.308(a)(1)(ii)(B) Risk Management Loosely related
Only shares CSF GV.SC-03: related, not a mapping
§164.308(a)(3) Workforce Security Loosely related
Only shares CSF GV.SC-03: related, not a mapping
§164.308(a)(3)(ii)(A) Authorization and/or Supervision Loosely related
Only shares CSF GV.SC-03: related, not a mapping
…and 18 more in the downloads
GDPRArt.28(1)Art.32(1)(b)Processor; Security of processingLoosely relatedNo mapping. Only shares CSF GV.SC-01, GV.SC-03, RC.RP-04: related, not a mapping
NIS26.4Change management, repairs and maintenanceCrosswalkENISA NIS2 → ISO 27001 mapping
2 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
5.1 Supply chain security policy Loosely related
Only shares CSF GV.SC-01: related, not a mapping
Essential Eight—No requirementNo mapping in our dataNo mapping in our data (Essential Eight links are editorial only).
DORAArt.28(2)Art.29(1)Art.29(2)Art.8(1)General principles; Preliminary assessment of ICT concentration risk at entity level…Loosely relatedNo mapping. Only shares CSF GV.SC-01, GV.SC-03, GV.OC-01: related, not a mapping
+4 more loosely related (not mappings)
Art.11(1) Response and recovery Loosely related
Only shares CSF RC.RP-04: related, not a mapping
Art.11(4) Response and recovery Loosely related
Only shares CSF RC.RP-04: related, not a mapping
Art.11(5) Response and recovery Loosely related
Only shares CSF GV.OC-01: related, not a mapping
Art.11(6) Response and recovery Loosely related
Only shares CSF RC.RP-04: related, not a mapping
CPS 234Para 16Para 22Assess third parties' information security capability; Evaluate the design of third parties' controlsLoosely relatedNo mapping. Only shares CSF GV.SC-01, GV.SC-03: related, not a mapping
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.