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 Type | Information Security Properties | Cybersecurity Concepts | Operational Capabilities | Security Domains |
|---|---|---|---|---|
| #Preventive | #Confidentiality | #Identify | #Legal and Compliance | #Governance and Ecosystem |
| #Integrity | #Protect | #Information Security Assurance | ||
| #Availability |
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).
Get an 81% headstart
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.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:
- Establish the underlying cause for the non-compliance.
- Decide whether corrective action is required.
- If necessary, plan and implement said corrective action to ensure ongoing compliance.
- 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
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.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.
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.
Get in touch today to book a demo.
Jump to topic
