ISO 27002:2022, Control 5.36 – Compliance With Policies, Rules and Standards for Information Security

ISO 27002:2022 Revised Controls

Book a demo

achieving,best,results.,two,confident,young,men,looking,at,laptop

Purpose of Control 5.36

A key part of operating with a robust, secure set of information security practices is the need to remain compliant with any published policies and procedures.

Control 5.36 requires organisations to gain a top-down view of information security compliance, relating to its various policies (both singular and topic-specific), rules and standards.

Attributes Table

Control 5.36 is a preventive and corrective control that modifies risk by maintaining adherence with pre-existing policies and procedures within the scope of information security.

Control TypeInformation Security PropertiesCybersecurity ConceptsOperational CapabilitiesSecurity Domains
#Preventive#Confidentiality
#Integrity
#Availability
#Identify
#Protect
#Legal and Compliance
#Information Security Assurance
#Governance and Ecosystem

Ownership of Control 5.36

Control 5.36 deals primarily with operational matters. As such, ownership should reside with the COO, or CISO (if present).

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

General Guidance on Control 5.36

Managers and information owners (including service and product owners) should be able to review compliance across an organisation’s entire bank of information security policies, rules and standards.

Managers should implement business-specific methods of reporting (incorporating any technical tools that are required) on information security compliance, with the overall aim of conducting periodic reviews – that are thoroughly recorded, stored and reported – which highlight areas for improvement.

If issues are discovered and instances of non-compliance are found, managers should be able to do the following:

  1. Establish the underlying cause for the non-compliance.
  2. Decide whether corrective action is required.
  3. If necessary, plan and implement said corrective action to ensure ongoing compliance.
  4. Once enacted, review any corrective action taken to explore its effectiveness and highlight any areas for further development.

Corrective actions should be taken in a “timely manner”, and ideally by the next review. If actions aren’t completed by the time the next review comes around, Managers should be able to evidence progress at the very least.

Supporting Controls

  • 5.35
  • 8.15
  • 8.16
  • 8.17

Changes and Differences From ISO 27002:2013

27002:2022-5.36 replaces two controls from 27002:2013, namely:

  • 18.2.2 – Compliance with security policies and standards
  • 18.2.3 – Technical compliance review

27002:2022-5.36 condenses all of the complex technical guidance offered in 27002:2013-18.2.3, by simply stating that Managers should be able to review compliance wherever it’s necessary to do so.

27002:2022-5.36 contains precisely the same set of guidance points as 27002:2013-18.2.2, relating to the actions that are required when a review flags up instances of non-compliance.

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.

Get a Headstart
on ISO 27002

The only compliance
solution you need
Book your demo

New Controls

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

Physical Controls

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

ISMS.online now supports ISO 42001 - the world's first AI Management System. Click to find out more