Purpose of Control 5.37
Control 5.37 deals with the concept of information security as an operational activity, with its constituent elements being carried out and/or managed by one or more individuals.
Control 5.37 outlines a series of operational procedures that ensure an organisation’s information security facility remains efficient and secure, and in line with their documented requirements.
Attributes Table
Control 5.37 is a preventive and corrective control that maintains risk through the creation of a bank of procedures associated with an organisation’s information security activities.
| Control Type | Information Security Properties | Cybersecurity Concepts | Operational Capabilities | Security Domains |
|---|---|---|---|---|
| #Preventive | #Confidentiality | #Protect | #Asset Management | #Governance and Ecosystem |
| #Corrective | #Integrity | #Recover | #Physical Security | #Protection |
| #Availability | #System and Network Security | #Defence | ||
| #Application Security | ||||
| #Secure Configuration | ||||
| #Identity and Access Management | ||||
| #Threat and Vulnerability Management | ||||
| #Continuity | ||||
| #Information Security Event Management |
Ownership of Control 5.37
Control 5.37 deals with a diverse set of circumstances that have the potential to include multiple departments and job roles under the remit of documented operating procedures. That being said, it can safely be assumed that most of the procedures will affect ICT staff, equipment and systems.
Where this occurs, ownership should reside with a senior member of the management team responsible for all ICT-related activities, such as a Head of IT.
Compliance doesn't have to be complicated.
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.
General Guidance on Control 5.37
Procedures should be created for information security-related activities in accordance with 5 key operational considerations:
- Any instance of an activity that is performed by one or more people, in the same way.
- When an activity is not often carried out.
- When a procedure carries the risk of being forgotten.
- Any new activities that are unfamiliar to staff, and are therefore subject to a higher degree of risk.
- When the responsibility for carrying out an activity is transferred to a different employee or group of employees.
Where these instances occur, documented operating procedures should clearly outline:
- Any individuals responsible – both incumbents and new operators.
- A set of guidelines that maintain security during the installation and subsequent configuration of any related business systems.
- How information is processed throughout the activity.
- BUDR plans and implications, in the event of data loss or a major event (see Control 8.13).
- Linked dependencies with any other systems, including scheduling.
- A clear procedure for dealing with “handling errors” or miscellaneous events that have the potential to occur (see Control 8.18).
- A full list of personnel to be contacted in the event of any disruption, including clear escalation procedures.
- How to operate any relevant storage media associated with the activity (see Controls 7.10 and 7.14).
- How to reboot and recover from a system failure.
- Audit trail logging, including all associated event and system logs (see Controls 8.15 and 8.17).
- Video monitoring systems that monitor onsite activities (see Control 7.4).
- A robust set of monitoring procedures that cater to the operational capacity, performance potential and security of said activity.
- How the activity should be maintained, in order to be kept at optimal performance levels.
All of the above procedures should be subject to periodic and/or ad-hoc reviews, as and when required, with all changes being ratified by Management in a timely manner to safeguard information security activity across the organisation.
Manage all your compliance in one place
ISMS.online supports over 100 standards
and regulations, giving you a single
platform for all your compliance needs.
Changes and Differences From ISO 27002:2013
27002:2022-5.37 replaces 27002:2013-12.1.1 (Documented operating procedures).
27002:2022-5.37 expands on 27002:2013-12.1.1 by offering a much broader set of circumstances that would warrant adherence to a document procedure.
27002:2013-12.1.1 lists information processing activities such as computer start-up and close-down procedures, backup, equipment maintenance, media handling, whereas 27002:2022-5.37 expands the remit of the control to generalised activities not limited to specific technical functions.
Aside from a few minor additions – such as categorising the individuals responsible for an activity – 27002:2022-5.37 contains the same general guidance points as 27002:2013-12.1.1
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
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
How ISMS.online Helps
ISO 27002 implementation is simpler with our step-by-step checklist that guides you through the whole process, from defining the scope of your ISMS through risk identification and control implementation.
- Users can complete tasks and submit evidence to demonstrate compliance with the standard.
- It’s easy to delegate responsibilities and monitor progress towards compliance.
- The extensive risk assessment toolset saves time and effort throughout the process.
- We have a dedicated team of consultants on hand to support you throughout your journey to compliance.
Get in touch today to book a demo.
Jump to topic
