Despite the broad range of preventive measures available to organisations that are ISO 27002:2022 adherent, disruptions to business continuity and standard operations can and do occur.
Control 5.29 outlines the operational adjustments that organisations should adopt when experiencing disruption, to safeguard information and protect company assets.
5.22 is a dual-purpose preventative and corrective control that maintains risk by implementing a plan that enhances information security during periods of disruption, and mitigates damage across organisational assets.
| Control Type | Information Security Properties | Cybersecurity Concepts | Operational Capabilities | Security Domains |
|---|---|---|---|---|
| #Preventive #Corrective | #Confidentiality #Integrity #Availability | #Protect #Respond | #Continuity | #Protection #Resilience |
Control 5.29 refers to operational information security process and procedures that are activated once critical events or business disruption occurs.
As such, ownership of Control 5.29 should reside with a member of the senior management teams who oversees the organisation’s day-to-day operations and/or continuity planning contingencies, such as the Chief Operating Officer (COO).
Control 5.29 stipulates that information security should be a constituent part of an organisation’s broader business continuity management procedure.
Organisations should draw up plans that seek to maintain information security integrity, and subsequently restore it, should information be compromised in any way following operational interruption or systems failure.
Security levels should be restored to levels prior to interruption, and in a timely manner that mitigates any further damage.
In doing so, organisations should:
Control 5.29 acknowledges the highly variable nature of continuity planning, and gives organisations significant leeway to implement information security controls that are specific to the different kinds of business disruption that organisations may experience.
ISO asks organisation to focus on two key areas when formulating a business continuity plan:
a) loss of confidentiality
b) the integrity of information
Book a tailored hands-on session
based on your needs and goals
Book your demo
27002:2022-5.29 replaces the following three controls from 27002:2013:
In recognition of the complex nature of business continuity plans – and how they differ according to various different kinds of interruption – ISO have simplified their guidance by moving away from a granular approach and asking organisations to instead consider a few basic points when drafting subject-specific plans (see above).
For example, part of the guidance within 17.1.2 states that:
“incident response personnel with the necessary responsibility, authority and competence to manage an incident and maintain information security are nominated”.
Despite their importance in effective continuity planning, 5.29 makes no specific mention of incident response teams and trusts the organisation to consider them under all points in the guidance notes, more specifically:
A cloud-based platform for ISO 27002 implementation, ISMS.online, helps you manage your information security risk management processes easily and effectively.
The ISMS.online platform provides a range of powerful tools that simplify the way you can document, implement, maintain and improve your information security management system (ISMS) and achieve compliance with ISO 27002.
Get in touch today to book a demo.
We’ll give you an 81% headstart
from the moment you log in
Book your demo
| 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 |
| 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 |
| 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 |
