cm/controlmapping
Sources
NIST CSF 2.0 · Govern (GV)
GV.RR-02

Roles, responsibilities, and authorities related to cybersecurity risk management are established, communicated, understood, and enforced

frameworkNIST Cybersecurity Framework 2.0 sectionGovern (GV) topicsRoles & Responsibilities frameworks5 4 1 3

Wrong or missing mapping? Report it

Equivalents of GV.RR-02 in other frameworks
FrameworkRequirementTitleLinkSource / reason
ISO 27001A.5.2A.5.4Information security roles and responsibilities; Management responsibilitiesCrosswalkSame topic: Roles & Responsibilities
2 loosely related (not mappings)
A.5.3 Segregation of duties Loosely related
Only shares CSF GV.RR-02: related, not a mapping
Clause 7.2 Competence Loosely related
Only shares CSF GV.RR-02: related, not a mapping
CIS v8.1CIS 14.9Conduct Role-Specific Security Awareness and Skills TrainingLoosely relatedNo mapping. Only shares CSF GV.RR-02: related, not a mapping
SOC 2CC1.2CC1.3CC1.5Board independence and oversight of internal control; Structures, reporting lines, authorities and responsibilities…EditorialSame topic: Roles & Responsibilities (editorial pick)
PCI DSS12.1.312.1.4Security roles and responsibilities defined; Executive responsibility for information security assignedCrosswalkSame topic: Roles & Responsibilities
11 loosely related (not mappings)
1.1.2 Roles for network security controls assigned Loosely related
Only shares CSF GV.RR-02: related, not a mapping
2.1.2 Roles for secure configuration assigned Loosely related
Only shares CSF GV.RR-02: related, not a mapping
3.1.2 Roles for protecting stored account data assigned Loosely related
Only shares CSF GV.RR-02: related, not a mapping
4.1.2 Roles for protecting data in transit assigned Loosely related
Only shares CSF GV.RR-02: related, not a mapping
5.1.2 Roles for malware protection assigned Loosely related
Only shares CSF GV.RR-02: related, not a mapping
6.1.2 Roles for secure systems and software assigned Loosely related
Only shares CSF GV.RR-02: related, not a mapping
7.1.2 Roles for access restriction assigned Loosely related
Only shares CSF GV.RR-02: related, not a mapping
8.1.2 Roles for identification and authentication assigned Loosely related
Only shares CSF GV.RR-02: related, not a mapping
…and 3 more in the downloads
CMMC—No requirementNo mapping in our dataNo mapping in our data.
800-53PM-2PM-29PS-9Information Security Program Leadership Role; Risk Management Program Leadership Roles…CrosswalkSame topic: Roles & Responsibilities
4 loosely related (not mappings)
PM-13 Security and Privacy Workforce Loosely related
Only shares CSF GV.RR-02: related, not a mapping
PM-19 Privacy Program Leadership Role Loosely related
Only shares CSF GV.RR-02: related, not a mapping
PM-23 Data Governance Body Loosely related
Only shares CSF GV.RR-02: related, not a mapping
PM-24 Data Integrity Board Loosely related
Only shares CSF GV.RR-02: related, not a mapping
HIPAA§164.308(a)(2)Assigned Security ResponsibilityCrosswalkSame topic: Roles & Responsibilities
GDPRArt.37(1)Art.39(1)Designation of the data protection officer; Tasks of the data protection officerEditorialSame topic: Roles & Responsibilities (editorial pick)
NIS21.2Roles, responsibilities and authoritiesCrosswalkSame topic: Roles & Responsibilities
Essential Eight—No requirementNo mapping in our dataNo mapping in our data (Essential Eight links are editorial only).
DORAArt.5(2)(c)Art.5(3)Art.6(4)Governance and organisation; Governance and organisation…EditorialSame topic: Roles & Responsibilities (editorial pick)
CPS 234Para 13Para 14Board ultimately responsible for information security; Define information security roles and responsibilitiesEditorialSame topic: Roles & Responsibilities (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.