ISO 27002:2022
Organizational controls – ISO 27002:2022

ISO 27002:2022 5.4: Management responsibilities

Managers are to insist that everyone working for the organization applies information security as the organization's policy, topic-specific policies and procedures lay down. Purpose: make sure managers grasp their own part in information security and act so that all staff know and carry out their security duties. Guidance: management shows visible backing for the policies, procedures and controls. Its duties include making sure people are briefed on their security role before they receive access to information and assets; are given written expectations for their role; are required to follow the policies; reach a level of awareness that matches their role (see 6.3); keep to the security terms of their employment contract or agreement and the expected ways of working; maintain the right security skills and qualifications through continuing education; have, where practical, a confidential route for reporting breaches of policy or procedure (whistleblowing), which may be anonymous or restrict knowledge of the reporter's identity to those handling the report; and are given enough resources and planning time to implement the security processes and controls.

Maintained by Gerard BlokdykControl text last updated

What else in your programme already covers this

This control maps to 67 controls across 27 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.

  • NIST-CSF-GV.PO-01 Policy for managing cybersecurity risks is established based on organizational context, cybersecurity strategy, and priorities and is communicated and enforced
  • NIST-CSF-GV.PO-02 Policy for managing cybersecurity risks is reviewed, updated, communicated, and enforced to reflect changes in requirements, threats, technology, and organizational mission
  • NIST-CSF-GV.RM-01 Risk management objectives are established and agreed to by organizational stakeholders
  • NIST-CSF-GV.RM-03 Cybersecurity risk management activities and outcomes are included in enterprise risk management processes
  • NIST-CSF-GV.RM-04 Strategic direction that describes appropriate risk response options is established and communicated
  • NIST-CSF-GV.RR-01 Organizational leadership is responsible and accountable for cybersecurity risk and fosters a culture that is risk-aware, ethical, and continually improving
  • NIST-CSF-GV.RR-02 Roles, responsibilities, and authorities related to cybersecurity risk management are established, communicated, understood, and enforced
  • NIST-CSF-GV.RR-03 Adequate resources are allocated commensurate with the cybersecurity risk strategy, roles, responsibilities, and policies

NIST SP 800-53 Rev 5 · 7 controls

PCI DSS 4.0 · 5 controls

  • 12.1.1 12.1.1 Overall information security policy established and disseminated
  • 12.1.2 12.1.2 Security policy reviewed annually and updated as needed
  • 12.4.2 12.4.2 Quarterly reviews that personnel follow security procedures
  • 12.6.3 12.6.3 Security awareness training on hire and annually with acknowledgment
  • 2.1.1 2.1.1 Requirement 2 policies and procedures governed

SOC 2 · 5 controls

  • SOC2-CC1.3 CC1.3 Structures, reporting lines, authorities and responsibilities (COSO principle 3)
  • SOC2-CC1.5 CC1.5 Accountability for internal control responsibilities (COSO principle 5)
  • SOC2-CC2.2 CC2.2 Internal communication of objectives and control responsibilities (COSO principle 14)
  • SOC2-CC4.2 CC4.2 Evaluating and communicating control deficiencies (COSO principle 17)
  • SOC2-CC5.3 CC5.3 Deploying controls through policies and procedures (COSO principle 12)

ISO/IEC 42001:2023 · 4 controls

  • 5.1 Leadership and commitment
  • 5.3 Roles, responsibilities and authorities
  • 7.3 Awareness
  • A.3 Internal organization
  • ISM-0725 Cyber security steering committee
  • ISM-1865 Agreement to system usage policies before access
  • ISM-2001 Championing a positive cyber security culture

HIPAA Security Rule · 3 controls

ISO 22301:2019 · 3 controls

  • 5.1 Leadership and commitment
  • 5.3 Roles, responsibilities and authorities
  • 9.3 Management review

ISO 27701:2019 · 3 controls

  • 5.3.1 Leadership and commitment
  • 5.3.3 Organizational roles, responsibilities and authorities
  • 6.2.1 Management direction for information security
  • CPS230-13 Board Accountability for Operational Risk Management
  • CPS230-9 Management of the Full Range of Operational Risks

C5 (Germany) · 2 controls

FedRAMP High · 2 controls

  • PL-4 Rules of Behavior
  • PS-8 Personnel Sanctions

FedRAMP Moderate · 2 controls

  • PL-4 Rules of Behavior
  • PS-8 Personnel Sanctions

ISO 27001:2022 · 2 controls

  • 5.36 Compliance with policies, rules and standards for information security
  • 5.4 Management responsibilities

NIST SP 800-181 · 2 controls

NIST SP 800-66 Rev 2 · 2 controls

APRA CPS 234 · 1 control

  • CPS234-P19 Policy Direction to All Responsible Parties
  • AUCDR-IS-STEP1 Step 1 - Define and implement security governance for CDR data

DORA · 1 control

ISO 10005:2005 · 1 control

  • 5.5 Management responsibilities

ISO 27018:2019 · 1 control

  • 7.2.1 Management responsibilities

ISO/IEC 38500:2024 · 1 control

  • 5.11 Social responsibility

NIS2 Directive · 1 control

  • Art.20.1 Management body approves the cybersecurity risk-management measures and oversees their implementation

NIST SP 800-218 · 1 control

Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.

Other controls in Organizational controls – ISO 27002:2022

You are reading one control. How much of ISO 27002:2022 have you already done?

ISO 27002:2022 5.4 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of ISO 27002:2022 your existing evidence covers. Hold NIST SP 800-53 Rev 5 and 79 of 93 ISO 27002:2022 controls already carry evidence.

Each report names every control your existing framework evidences, every one it does not, the reasoning behind each claim, and the claims that were argued against and rejected. 180 were rejected on the NIST SP 800-53 Rev 5 pair alone.

Query this from an agent

The graph holds this control, the 67 it maps to, and the evidence behind each claim, over MCP and REST.