Control 5.24 deals with information security under the umbrella of Incident Management.
Control 5.24 outlines how organisations should manage information security incidents through adequate planning and preparation, by creating efficient processes and detailing how staff should respond to incidents based on clearly defined roles and responsibilities.
Throughout the guidance, an emphasis is placed on constructive communication and promoting a professional response to what are often high-pressure scenarios, especially when dealing with commercially sensitive data, or PII.
5.24 is a corrective control that maintains risk by establishing a common set of Incident Management procedures that mitigate any commercial or operational damage caused by critical information security events.
Control Type | Information Security Properties | Cybersecurity Concepts | Operational Capabilities | Security Domains |
---|---|---|---|---|
#Corrective | #Confidentiality #Integrity #Availability | #Respond #Recover | #Governance #Information Security Event Management | #Defence |
Incident Management, in broader terms, is usually applicable to service-related incidents. Given that Control 5.24 deals specifically with information security-related incidents and breaches, taking into account the highly sensitive nature of these events, ownership of Control 5.24 should ideally reside with a CISO, or organisational equivalent.
Given that CISOs are usually only seen within larger companies and enterprise-level organisations, ownership could also reside with the COO, or Service Manager, depending on the nature of the organisation.
Incident Management yields the best results when an organisation’s staff are working together to resolve a specific problem.
In order to achieve that, Control 5.24 specifics 5 main guidance points that help organisations to create a cohesive, efficient IM operation.
Organisations should:
The objective of an organisation’s incident management process should be to ensure that all those responsible for resolving information security incidents have a firm understanding of three main areas:
All processes should work in harmony to ensure these three variables remain a top priority.
Control 5.24 outlines 8 main activities that should be addressed when attempting to resolve information security-related incidents.
Book a tailored hands-on session
based on your needs and goals
Book your demo
We can’t think of any company whose service can hold a candle to ISMS.online.
Reporting is an essential element of any Incident Management policy that ensures information is accurately disseminated throughout an organisation. Reporting activities should be focused around 4 main areas:
It should be noted that Control 5.24 doesn’t contain any guidance on how to meet external requirements on how incidents are reported (e.g. regulatory guidelines and/or prevailing legislation), but organisations should take steps to share information concerning incidents with all relevant parties, and coordinate a response that meets all regulatory, sector-specific and legal requirements.
27002:2022-5.24 replaces 27002:2013-16.1.1 (Management of information security incidents and improvements – Responsibilities and procedures).
27002:2022-5.24 acknowledges the need for organisations to undergo thorough preparation, in order to remain resilient and compliant in the face of potential information security incidents.
As such, 27002:2022-5.24 offers a far more comprehensive breakdown of the steps that organisations need to take across role delegation, incident management and reporting functions, with specific reference given to other ISO controls that help organisations to gain a more rounded view of incident management as a whole, not merely related to information security events.
To help organisation compartmentalise their incident management operations, 27002:2022-5.24 deviates from 27002:2013-16.1.1 by focusing on three distinct areas for consideration:
When you use ISMS.online, you will be able to:
Get in touch today to book a demo.
Book a tailored hands-on session
based on your needs and goals
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 |