ISO 27002:2022, Control 5.24 – Information Security Incident Management Planning and Preparation

ISO 27002:2022 Revised Controls

Book a demo

young,business,people,group,have,meeting,and,working,in,modern

Purpose of Control 5.24

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.

Attributes Table

Control TypeInformation Security PropertiesCybersecurity ConceptsOperational CapabilitiesSecurity Domains
#Corrective#Confidentiality
#Integrity
#Availability
#Respond
#Recover
#Governance
#Information Security Event Management
#Defence

We’re cost-effective and quick

Discover how that will boost your ROI
Get your quote

Ownership of Control 5.24

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.

Guidance – Roles and Responsibilities

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:

  1. Agree upon and document a homogenous method for reporting information security events. This should also involve establishing a main point of contact for all such events to be reported to.
  2. Establish a series of Incident Management processes that manage information security related incidents within the sphere of various technical and administrative functions:

    a) Administration
    b) Documentation
    c) Detection
    d) Triage
    e) Prioritisation
    f) Analysis
    g) Communication
  3. Formulate an incident response procedure that enables the organisation to assess and respond to incidents. Organisations should also be mindful of the need to learn from incidents once they’re resolved, to mitigate any recurrence and provide staff with historical context in future scenarios.
  4. Limit the involvement in incidents to trained and competent personnel, who enjoy full access to procedural documentation and benefit from regular refresher training specifically relating to information security incidents.
  5. Establish a process that identifies the training needs of each member of staff involved in resolving information security-related incidents. This should include any vendor-specific or professional certifications, and provide staff with the opportunity to highlight any professional development needs, as related to information security.

Get a Headstart
on ISO 27002

The only compliance
solution you need
Book your demo

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

Guidance – Incident Management

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:

  • The time it takes to resolve an incident
  • Any potential consequences
  • The severity of the incident

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.

  1. Potential information security events should be assessed in accordance with a strict criteria that validates them as an approved incident.
  2. The management of information security events and incidents should be categorised into 5 main sub-topics, either manually or via process automation:

    a) Monitoring (see Controls 8.15 and 8.16)
    b) Detection (see Control 8.16)
    c) Classification ( see Control 5.25)
    d) Analysis
    e) Reporting (see Control 6.8)
  3. When attempting to bring information security incidents to a successful conclusion, organisations should implement procedures that enact the following:

    a) Response and escalation (see Control 5.26) in accordance with the type of incident
    b) Activation of crisis management plans or business continuity plans, on a case-by-case basis
    c) Managed recovery from an incident that mitigates any operational/financial damage caused
    d) Thorough communication of incident-related events to all internal and external parties
  4. Collaborative working with internal and external personnel (see Controls 5.5 and 5.6).
  5. Thorough, accessible and transparent logging of all incident managed-based activities.
  6. Responsible handling of evidence (including data and conversations), in accordance with internal and external guidelines and regulations (see Control 5.28).
  7. Root cause analysis, and a thorough review procedure, once the incident has been resolved.
  8. A comprehensive record of any improvements that are required to prevent the incident from reoccurring, including any amendments to the incident management process itself.

See ISMS.online
in action

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.
Vivian Kroner
ISO 27001, 27701 and GDPR lead implementer Aperian Global
100% of our users pass certification first time
Book your demo

Guidance – Reporting

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:

  1. Any actions that need to be taken once an information security event occurs.
  2. Incident forms that offer a clear and concise means of recording information and supporting personnel in carrying out their duties.
  3. Feedback processes to ensure that personnel are notified of the outcome of information security events, once the incident has been resolved.
  4. Incident reports that document all relevant information pertaining to an incident.

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.

Supporting controls

  • 5.25
  • 5.26
  • 5.5
  • 5.6
  • 6.8
  • 8.15
  • 8.16

Changes and Differences from ISO 27002:2013

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:

  • Roles and responsibilities
  • Incident management processes
  • Reporting

How ISMS.online Helps

When you use ISMS.online, you will be able to:

  • Create an ISMS that is compatible with ISO 27001 standards.
  • Perform tasks and submit proof to indicate that they have met the requirements of the standard.
  • Allocate tasks and track progress toward compliance with the law.
  • Get access to a specialised team of advisors that will assist you throughout your path towards compliance.

Get in touch today to book a demo.

See how we can help you

Book a tailored hands-on session
based on your needs and goals
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
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

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