Skip to content
Work smarter with our new enhanced navigation!
See how IO makes compliance easier.
Read the blog

What is Control 5.4 Management Responsibilities

What is an information security policy?

An information security policy is a formal document that provides management direction, goals and principles for protecting an organisation’s information. An effective information security policy should be tailored to the specific needs of an organisation and supported by senior management to ensure appropriate allocation of resources.

The policy communicates the overarching principles on how management would like employees to handle sensitive data and how the company will protect its information assets.

The policy is often derived from laws, regulations and best practices that must be adhered to by the organisation. Information security policies are usually created by an organisation’s senior management, with input from its IT security staff.

Policies should also include a framework for defining roles and responsibilities and a timeline for periodic review.

Attributes Table

Attributes are a way to categorise different types of controls. These attributes allow you to align your controls with industry standards. In control 5.4 they are:

Control Type Information Security Properties Cybersecurity Concepts Operational Capabilities Security Domains
#Preventive #Confidentiality #Identify #Governance #Governance and Ecosystem
#Integrity
#Availability



ISMS.online gives you an 81% Headstart from the moment you log on

ISO 27001 made easy

We’ve done the hard work for you, giving you an 81% Headstart from the moment you log on. All you have to do is fill in the blanks.




What Is The Purpose of Control 5.4?

Control 5.4 was designed to ensure that management understands their responsibility in information security and that they take steps to ensure that all employees are aware of and fulfil their information security obligations.

Control 5.4 Explained

Information is a valuable asset and must be protected from loss, damage or misuse. The organisation shall ensure that appropriate measures are taken to protect this asset. For this to happen, management must ensure that all personnel apply all the information security policy, topic-specific policies and procedures of the organisation.

Control 5.4 covers the purpose and implementation guidance for defining management responsibility with regards to information security in an organisation in line with the framework of ISO 27001.

This control is all about making sure that management is on board with the information security programme and that all employees and contractors are aware of and follow the organisation’s information security policy. No one should ever be exempt from mandatory compliance with the organisation’s security policies, topics-specific policies and procedures.

What Is Involved and How to Meet the Requirements

The key to meeting the requirements of this control is in ensuring that management is able to compel all relevant personnel to adhere to the organisation’s information security policies, standards, and procedures.

The first step is management buy-in and support. Management must demonstrate its commitment by following through on all policies and procedures it puts in place. For example, if you require workers to take annual security awareness training courses, managers should lead by example and complete those courses first.

Next comes communicating the importance of information security to everyone in the company, regardless of their role. This includes the board of directors, executives and management, as well as employees. Everyone must understand their role in maintaining the security of sensitive data as covered in the company’s ISMS programme.




climbing

Embed, expand and scale your compliance, without the mess. IO gives you the resilience and confidence to grow securely.




Differences between ISO 27002:2013 and ISO 27002:2022

ISO 27002:2022 control 5.4 Management Responsibilities was formerly known as control 7.2.1 Management Responsibilities in ISO 27002:2013. This is not a new control but a more robust interpretation of the 2013 version.

While control 5.4 and control 7.2.1 broadly covers the same thing, there are few differences that organisations and business managers should note. These differences are covered in the implementation guidance of the control.

Control 5.4 ISO 27002:2013-2022 Implementation Guidelines Compared

In ISO 27002: 2013, management responsibilities covers ensuring that employees and contractors:

a) are properly briefed on their information security roles and responsibilities prior to being granted access to confidential information or information systems;

b) are provided with guidelines to state information security expectations of their role within the
Organisation;

c) are motivated to fulfil the information security policies of the organisation;

d) achieve a level of awareness on information security relevant to their roles and responsibilities within the organisation;

e) conform to the terms and conditions of employment, which includes the organisation’s information security policy and appropriate methods of working;

f) continue to have the appropriate skills and qualifications and are educated on a regular basis;

g) are provided with an anonymous reporting channel to report violations of information security policies or procedures (“whistle blowing”).

Management should demonstrate support of information security policies, procedures and controls, and act as a role model.

Control 5.4 is a more user-friendly version and requires that management responsibilities ensures that employees and contractors:

a) Are properly briefed on their information security roles and responsibilities prior to being granted access to the organisation’s information and other associated assets;

b) Are provided with guidelines which state the information security expectations of their role within the organisation;

c) Are mandated to fulfil the information security policy and topic-specific policies of the organisation;

d) Achieve a level of awareness of information security relevant to their roles and responsibilities within the organisation;

e) Compliance with the terms and conditions of employment, contract or agreement, including the organisation’s information security policy and appropriate methods of working;

f) Continue to have the appropriate information security skills and qualifications through ongoing professional education;

g) Where practicable, are provided with a confidential channel for reporting violations of information security policy, topic-specific policies or procedures for information security (“whistleblowing”). This can allow for anonymous reporting, or have provisions to ensure that knowledge of the identity of the reporter is known only to those who need to deal with such reports;

h) Are provided with adequate resources and project planning time for implementing the organisation’s security-related processes and controls.

As you can see, ISO 27002:2022 specifically requires that in order to execute the organisation’s security-related procedures and controls, workers and contractors are supplied with necessary resources as well as project planning time.

The wordings in some of the implementation guidelines of ISO 27002:2013 vs ISO 27002:2020 were also affected. Where guideline C of the 2013 version states that employees and contractors be ‘motivated’ to adopt the company’s ISMS policies, 2022 uses the word ‘mandated’




ISMS.online supports over 100 standards and regulations, giving you a single platform for all your compliance needs.

ISMS.online supports over 100 standards and regulations, giving you a single platform for all your compliance needs.




Who Is In Charge Of This Process?

The answer to this question is pretty simple: the management! It is the responsibility of the management to ensure that a proper ISMS (Information Security Management System) is implemented.

This is normally supported by the appointment of a suitably qualified and experienced information security manager, who will be accountable to senior management for developing, implementing, managing and continually improving the ISMS.

New ISO 27002 Controls

New Controls
ISO/IEC 27002:2022 Control Identifier ISO/IEC 27002:2013 Control Identifier Control Name
5.7 NEW Threat intelligence
5.23 NEW Information security for use of cloud services
5.30 NEW ICT readiness for business continuity
7.4 NEW Physical security monitoring
8.9 NEW Configuration management
8.10 NEW Information deletion
8.11 NEW Data masking
8.12 NEW Data leakage prevention
8.16 NEW Monitoring activities
8.23 NEW Web filtering
8.28 NEW Secure coding
Organisational Controls
ISO/IEC 27002:2022 Control Identifier ISO/IEC 27002:2013 Control Identifier Control Name
5.1 05.1.1, 05.1.2 Policies for information security
5.2 06.1.1 Information security roles and responsibilities
5.3 06.1.2 Segregation of duties
5.4 07.2.1 Management responsibilities
5.5 06.1.3 Contact with authorities
5.6 06.1.4 Contact with special interest groups
5.7 NEW Threat intelligence
5.8 06.1.5, 14.1.1 Information security in project management
5.9 08.1.1, 08.1.2 Inventory of information and other associated assets
5.10 08.1.3, 08.2.3 Acceptable use of information and other associated assets
5.11 08.1.4 Return of assets
5.12 08.2.1 Classification of information
5.13 08.2.2 Labelling of information
5.14 13.2.1, 13.2.2, 13.2.3 Information transfer
5.15 09.1.1, 09.1.2 Access control
5.16 09.2.1 Identity management
5.17 09.2.4, 09.3.1, 09.4.3 Authentication information
5.18 09.2.2, 09.2.5, 09.2.6 Access rights
5.19 15.1.1 Information security in supplier relationships
5.20 15.1.2 Addressing information security within supplier agreements
5.21 15.1.3 Managing information security in the ICT supply chain
5.22 15.2.1, 15.2.2 Monitoring, review and change management of supplier services
5.23 NEW Information security for use of cloud services
5.24 16.1.1 Information security incident management planning and preparation
5.25 16.1.4 Assessment and decision on information security events
5.26 16.1.5 Response to information security incidents
5.27 16.1.6 Learning from information security incidents
5.28 16.1.7 Collection of evidence
5.29 17.1.1, 17.1.2, 17.1.3 Information security during disruption
5.30 5.30 ICT readiness for business continuity
5.31 18.1.1, 18.1.5 Legal, statutory, regulatory and contractual requirements
5.32 18.1.2 Intellectual property rights
5.33 18.1.3 Protection of records
5.34 18.1.4 Privacy and protection of PII
5.35 18.2.1 Independent review of information security
5.36 18.2.2, 18.2.3 Compliance with policies, rules and standards for information security
5.37 12.1.1 Documented operating procedures
People Controls
ISO/IEC 27002:2022 Control Identifier ISO/IEC 27002:2013 Control Identifier Control Name
6.1 07.1.1 Screening
6.2 07.1.2 Terms and conditions of employment
6.3 07.2.2 Information security awareness, education and training
6.4 07.2.3 Disciplinary process
6.5 07.3.1 Responsibilities after termination or change of employment
6.6 13.2.4 Confidentiality or non-disclosure agreements
6.7 06.2.2 Remote working
6.8 16.1.2, 16.1.3 Information security event reporting
Physical Controls
ISO/IEC 27002:2022 Control Identifier ISO/IEC 27002:2013 Control Identifier Control Name
7.1 11.1.1 Physical security perimeters
7.2 11.1.2, 11.1.6 Physical entry
7.3 11.1.3 Securing offices, rooms and facilities
7.4 NEW Physical security monitoring
7.5 11.1.4 Protecting against physical and environmental threats
7.6 11.1.5 Working in secure areas
7.7 11.2.9 Clear desk and clear screen
7.8 11.2.1 Equipment siting and protection
7.9 11.2.6 Security of assets off-premises
7.10 08.3.1, 08.3.2, 08.3.3, 11.2.5 Storage media
7.11 11.2.2 Supporting utilities
7.12 11.2.3 Cabling security
7.13 11.2.4 Equipment maintenance
7.14 11.2.7 Secure disposal or re-use of equipment
Technological Controls
ISO/IEC 27002:2022 Control Identifier ISO/IEC 27002:2013 Control Identifier Control Name
8.1 06.2.1, 11.2.8 User endpoint devices
8.2 09.2.3 Privileged access rights
8.3 09.4.1 Information access restriction
8.4 09.4.5 Access to source code
8.5 09.4.2 Secure authentication
8.6 12.1.3 Capacity management
8.7 12.2.1 Protection against malware
8.8 12.6.1, 18.2.3 Management of technical vulnerabilities
8.9 NEW Configuration management
8.10 NEW Information deletion
8.11 NEW Data masking
8.12 NEW Data leakage prevention
8.13 12.3.1 Information backup
8.14 17.2.1 Redundancy of information processing facilities
8.15 12.4.1, 12.4.2, 12.4.3 Logging
8.16 NEW Monitoring activities
8.17 12.4.4 Clock synchronization
8.18 09.4.4 Use of privileged utility programs
8.19 12.5.1, 12.6.2 Installation of software on operational systems
8.20 13.1.1 Networks security
8.21 13.1.2 Security of network services
8.22 13.1.3 Segregation of networks
8.23 NEW Web filtering
8.24 10.1.1, 10.1.2 Use of cryptography
8.25 14.2.1 Secure development life cycle
8.26 14.1.2, 14.1.3 Application security requirements
8.27 14.2.5 Secure system architecture and engineering principles
8.28 NEW Secure coding
8.29 14.2.8, 14.2.9 Security testing in development and acceptance
8.30 14.2.7 Outsourced development
8.31 12.1.4, 14.2.6 Separation of development, test and production environments
8.32 12.1.2, 14.2.2, 14.2.3, 14.2.4 Change management
8.33 14.3.1 Test information
8.34 12.7.1 Protection of information systems during audit testing

How ISMS.online Helps

One of the biggest challenges in implementing an ISO 27001-aligned ISMS is keeping on top of your information security controls. Our system makes this easy.

We understand the importance of protecting your organisation’s data and reputation. That’s why our cloud-based platform is designed to simplify the implementation of ISO 27001, provide you with a robust framework of information security controls and help you achieve certification with minimal resources and time.

We’ve included a variety of user-friendly features and toolkits into our platform to save you time and guarantee you’re creating a really robust ISMS. With ISMS.online, you can easily obtain ISO 27001 certification and afterwards easily manage it.

Book a demo today.


Sam Peters

Sam is Chief Product Officer at ISMS.online and leads the development on all product features and functionality. Sam is an expert in many areas of compliance and works with clients on any bespoke or large-scale projects.

Take a virtual tour

Start your free 2-minute interactive demo now and see
ISMS.online in action!

platform dashboard full on mint

We’re a Leader in our Field

4/5 Stars
Users Love Us
Leader - Winter 2026
Regional Leader - Winter 2026 UK
Regional Leader - Winter 2026 EU
Regional Leader- Winter 2026 Mid-market EU
Regional Leader - Winter 2026 EMEA
Regional Leader - Winter 2026 Mid-market EMEA

"ISMS.Online, Outstanding tool for Regulatory Compliance"

— Jim M.

"Makes external audits a breeze and links all aspects of your ISMS together seamlessly"

— Karen C.

"Innovative solution to managing ISO and other accreditations"

— Ben H.