ISO 27002:2022, Control 5.37 – Documented Operating Procedures

ISO 27002:2022 Revised Controls

Book a demo

young,female,entrepreneur,freelancer,working,using,a,laptop,in,coworking

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 TypeInformation Security PropertiesCybersecurity ConceptsOperational CapabilitiesSecurity Domains
#Preventive
#Corrective
#Confidentiality
#Integrity
#Availability
#Protect
#Recover
#Asset Management
#Physical Security
#System and Network Security
#Application Security
#Secure Configuration
#Identity and Access Management
#Threat and Vulnerability Management
#Continuity
#Information Security Event Management
#Governance and Ecosystem
#Protection
#Defence

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.

We’re cost-effective and quick

Discover how that will boost your ROI
Get your quote

General Guidance on Control 5.37

Procedures should be created for information security-related activities in accordance with 5 key operational considerations:

  1. Any instance of an activity that is performed by one or more people, in the same way.
  2. When an activity is not often carried out.
  3. When a procedure carries the risk of being forgotten.
  4. Any new activities that are unfamiliar to staff, and are therefore subject to a higher degree of risk.
  5. 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:

  1. Any individuals responsible – both incumbents and new operators.
  2. A set of guidelines that maintain security during the installation and subsequent configuration of any related business systems.
  3. How information is processed throughout the activity.
  4. BUDR plans and implications, in the event of data loss or a major event (see Control 8.13).
  5. Linked dependencies with any other systems, including scheduling.
  6. A clear procedure for dealing with “handling errors” or miscellaneous events that have the potential to occur (see Control 8.18).
  7. A full list of personnel to be contacted in the event of any disruption, including clear escalation procedures.
  8. How to operate any relevant storage media associated with the activity (see Controls 7.10 and 7.14).
  9. How to reboot and recover from a system failure.
  10. Audit trail logging, including all associated event and system logs (see Controls 8.15 and 8.17).
  11. Video monitoring systems that monitor onsite activities (see Control 7.4).
  12. A robust set of monitoring procedures that cater to the operational capacity, performance potential and security of said activity.
  13. 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.

Discover our platform

Book a tailored hands-on session
based on your needs and goals
Book your demo

Updated for ISO 27001 2022
  • 81% of the work done for you
  • Assured Results Method for certification success
  • Save time, money and hassle
Book your demo
img

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

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.

Get in touch today to book a demo.

It helps drive our behaviour in a positive way that works for us
& our culture.

Emmie Cooney
Operations Manager, Amigo

Book your demo

New Controls

ISO/IEC 27002:2022 Control IdentifierISO/IEC 27002:2013 Control IdentifierControl Name
5.7NewThreat intelligence
5.23NewInformation security for use of cloud services
5.30NewICT readiness for business continuity
7.4NewPhysical security monitoring
8.9NewConfiguration management
8.10NewInformation deletion
8.11NewData masking
8.12NewData leakage prevention
8.16NewMonitoring activities
8.23NewWeb filtering
8.28NewSecure coding

Organisational Controls

ISO/IEC 27002:2022 Control IdentifierISO/IEC 27002:2013 Control IdentifierControl Name
5.105.1.1, 05.1.2Policies for information security
5.206.1.1Information security roles and responsibilities
5.306.1.2Segregation of duties
5.407.2.1Management responsibilities
5.506.1.3Contact with authorities
5.606.1.4Contact with special interest groups
5.7NewThreat intelligence
5.806.1.5, 14.1.1Information security in project management
5.908.1.1, 08.1.2Inventory of information and other associated assets
5.1008.1.3, 08.2.3Acceptable use of information and other associated assets
5.1108.1.4Return of assets
5.12 08.2.1Classification of information
5.1308.2.2Labelling of information
5.1413.2.1, 13.2.2, 13.2.3Information transfer
5.1509.1.1, 09.1.2Access control
5.1609.2.1Identity management
5.17 09.2.4, 09.3.1, 09.4.3Authentication information
5.1809.2.2, 09.2.5, 09.2.6Access rights
5.1915.1.1Information security in supplier relationships
5.2015.1.2Addressing information security within supplier agreements
5.2115.1.3Managing information security in the ICT supply chain
5.2215.2.1, 15.2.2Monitoring, review and change management of supplier services
5.23NewInformation security for use of cloud services
5.2416.1.1Information security incident management planning and preparation
5.2516.1.4Assessment and decision on information security events
5.2616.1.5Response to information security incidents
5.2716.1.6Learning from information security incidents
5.2816.1.7Collection of evidence
5.2917.1.1, 17.1.2, 17.1.3Information security during disruption
5.30NewICT readiness for business continuity
5.3118.1.1, 18.1.5Legal, statutory, regulatory and contractual requirements
5.3218.1.2Intellectual property rights
5.3318.1.3Protection of records
5.3418.1.4Privacy and protection of PII
5.3518.2.1Independent review of information security
5.3618.2.2, 18.2.3Compliance with policies, rules and standards for information security
5.3712.1.1Documented operating procedures

People Controls

ISO/IEC 27002:2022 Control IdentifierISO/IEC 27002:2013 Control IdentifierControl Name
6.107.1.1Screening
6.207.1.2Terms and conditions of employment
6.307.2.2Information security awareness, education and training
6.407.2.3Disciplinary process
6.507.3.1Responsibilities after termination or change of employment
6.613.2.4Confidentiality or non-disclosure agreements
6.706.2.2Remote working
6.816.1.2, 16.1.3Information security event reporting

Physical Controls

ISO/IEC 27002:2022 Control IdentifierISO/IEC 27002:2013 Control IdentifierControl Name
7.111.1.1Physical security perimeters
7.211.1.2, 11.1.6Physical entry
7.311.1.3Securing offices, rooms and facilities
7.4NewPhysical security monitoring
7.511.1.4Protecting against physical and environmental threats
7.611.1.5Working in secure areas
7.711.2.9Clear desk and clear screen
7.811.2.1Equipment siting and protection
7.911.2.6Security of assets off-premises
7.1008.3.1, 08.3.2, 08.3.3, 11.2.5Storage media
7.1111.2.2Supporting utilities
7.1211.2.3Cabling security
7.1311.2.4Equipment maintenance
7.1411.2.7Secure disposal or re-use of equipment

Technological Controls

ISO/IEC 27002:2022 Control IdentifierISO/IEC 27002:2013 Control IdentifierControl Name
8.106.2.1, 11.2.8User endpoint devices
8.209.2.3Privileged access rights
8.309.4.1Information access restriction
8.409.4.5Access to source code
8.509.4.2Secure authentication
8.612.1.3Capacity management
8.712.2.1Protection against malware
8.812.6.1, 18.2.3Management of technical vulnerabilities
8.9NewConfiguration management
8.10NewInformation deletion
8.11NewData masking
8.12NewData leakage prevention
8.1312.3.1Information backup
8.1417.2.1Redundancy of information processing facilities
8.1512.4.1, 12.4.2, 12.4.3Logging
8.16NewMonitoring activities
8.1712.4.4Clock synchronization
8.1809.4.4Use of privileged utility programs
8.1912.5.1, 12.6.2Installation of software on operational systems
8.2013.1.1Networks security
8.2113.1.2Security of network services
8.2213.1.3Segregation of networks
8.23NewWeb filtering
8.2410.1.1, 10.1.2Use of cryptography
8.2514.2.1Secure development life cycle
8.2614.1.2, 14.1.3Application security requirements
8.2714.2.5Secure system architecture and engineering principles
8.28NewSecure coding
8.2914.2.8, 14.2.9Security testing in development and acceptance
8.3014.2.7Outsourced development
8.3112.1.4, 14.2.6Separation of development, test and production environments
8.3212.1.2, 14.2.2, 14.2.3, 14.2.4Change management
8.3314.3.1Test information
8.3412.7.1Protection of information systems during audit testing
Get a Headstart on ISO 27001
  • All updated with the 2022 control set
  • Make 81% progress from the minute you log in
  • Simple and easy to use
Book your demo
img

Explore ISMS.online's platform with a self-guided tour - Start Now