ISO 27001 Annex A 5.26 Response to Information Security Incidents Explained

ISO 27001 Response to Information Security Incidents

ISO 27001 Annex A 5.26 Response to information security incidents is an ISO 27001 control that requires an organisation to respond to information security incidents based on documented procedures.

It is about your response to information security incidents which means you need a documented process for what you will do.

Key Takeaways

ISO 27001 Annex A 5.26 requires organisations to respond to information security incidents in accordance with documented procedures. While previous controls (A.5.24 and A.5.25) cover the planning and assessment, this control is about the operational execution of your response. It is a corrective control designed to ensure that once an incident is confirmed, your team acts efficiently to contain the threat, recover services, and meet legal obligations (such as the 72-hour GDPR notification rule).

Purpose

The purpose of ISO 2701 Annex A 5.26 is a corrective control that ensures efficient and effective response to information security incidents.

Definition

ISO 27001 defines Annex A 5.26 as:

Information security incidents should be responded to in accordance with the documented procedures.

ISO 27001:2022 Annex A 5.26 Response to information security incidents

Explanation

ISO 27001 Annex A 5.26 Response to Information Security Incidents is a security control that mandates the operational execution of documented response procedures. Implementing this ensures that organisations can efficiently contain threats and recover services, thereby maintaining legal compliance and protecting reputation during a critical cybersecurity breach.

Requirement

• Documented Response Procedures: You must have clear, step-by-step instructions (often called Playbooks) for different types of incidents, such as ransomware, lost devices, or unauthorized data access.
• Team Competency: The designated response team must have the technical skills and authority to act. This includes the power to take systems offline or disconnect networks during a crisis.
• Containment & Eradication: The immediate goal of the response is to stop the incident from spreading (Containment) and then remove the root cause, such as malware or an exploited vulnerability (Eradication).
• Evidence Collection: During the response, you must collect and preserve evidence (logs, memory dumps, or physical hardware). This is critical if the incident leads to legal action or insurance claims.
• Legal & Regulatory Communication: You must have a process for notifying external parties. For data breaches involving personal data, this often requires notifying a regulator (like the ICO) within a strict legal timeframe.
• Formal Closure: Every incident must be officially “Closed” only after the recovery is complete and a summary report has been created.

Audit Focus

1. Response Timestamps: “Show me the logs for your last major incident. How much time passed between the ‘Decision’ to categorize it (A.5.25) and the start of ‘Containment’?”
2. Playbook Accuracy: “Show me your ransomware playbook. Can you prove that the team followed these specific steps during your last malware event?”
3. Communication Logs: “If you had a data breach last year, show me the record of your notification to the regulator. Did you meet the mandatory deadline?”

FREE Training Video

Implementation Guide

This guide provides a framework for responding to an information security incident. The guide should be used in conjunction with your information security incident management plan.

The standard that relates to information security management for further reading if required is ISO/IEC 27035

To implement ISO 27001 Annex A 5.26 is straightforward. You are going to document processes and procedures for information security incident response and then communicate to those people that need to know about it.

The team that does the response is going to be designated which means you know and have recorded who they are and they are going to have the required competence to do the job.

What the incident response process should include

The information security incident response process is going to include

• Containment: stopping the incident from spreading or getting worse
• Evidence Collection: collecting evidence of what happened
• Escalation: considering and acting on escalation as required which may mean invoking business continuity
• Logging: recording the response activities and what you did so you can analyse it later
• Communicating: telling people about the processes so they know what is expected and what to do
• Sharing: sharing knowledge with people that would be interested to improve responsiveness and reduce wider impact
• Closing: once the incident ends formally closing the incident and recording it
• Root cause: identifying why it happened and acting on that root cause conclusion.

The 3 steps of Information Security Incident Response

The 3 steps in information security incident response are:

1. Identification: identifying the information security incident
2. Assessment: assessing and prioritising the information security incident
3. Response: responding to the information security incident incident

How to implement ISO 27001 Annex A 5.26

Implementing a robust incident response capability is not merely a compliance checkbox: it is the difference between a minor disruption and a catastrophic business failure. Following these ten steps will ensure your organisation meets the rigorous requirements of ISO 27001 Annex A 5.26 while protecting your digital assets and reputation.

1. Formalise the Incident Management Plan and Policy

Define the governance framework and specific procedures for handling security breaches. Result: Provides a structured, legally defensible roadmap for the IRT to follow during high-pressure events.

• Document clear definitions for events versus incidents based on your Asset Register.
• Specify legal and regulatory reporting triggers for GDPR, NIS2, and DORA.
• Ensure the policy is signed off by senior leadership to guarantee resource availability.

2. Provision the Incident Response Team and IAM Roles

Identify internal stakeholders and external specialists required to execute the plan. Result: Ensures that the right people have the necessary authorities and technical access before an incident occurs.

• Define clear IAM roles and “Break Glass” accounts for emergency system access.
• Establish Rules of Engagement (ROE) documents for third-party digital forensics providers.
• Mandate MFA for all accounts with administrative or incident response privileges.

3. Establish Internal and External Reporting Channels

Create dedicated pathways for employees and automated systems to flag suspicious activity. Result: Reduces the “Mean Time to Detect” (MTTD) and ensures compliance with 72-hour notification windows.

• Configure SIEM alerts to trigger notifications to the SOC and IRT immediately.
• Set up an anonymous reporting line or internal portal for staff to report anomalies.
• Maintain an offline contact list for regulators, law enforcement, and key clients.

4. Classify Incidents Using a Severity Matrix

Develop a technical criteria for triaging events based on impact and urgency. Result: Enables the organisation to prioritise resources effectively and avoid “alert fatigue” on low-risk events.

• Map incident severity to the criticality of assets defined in your Asset Register.
• Define escalation triggers that move an incident from “Technical” to “Crisis Management.”
• Include quantitative metrics: such as volume of data compromised or duration of downtime.

5. Execute Technical Containment Playbooks

Develop step-by-step technical guides for specific incident types like ransomware or DDoS. Result: Stops the lateral movement of threats and prevents further data exfiltration.

• Draft network isolation procedures to quarantine infected segments or VLANs.
• Identify specific “Kill Switches” for high-risk cloud services or API integrations.
• Test these playbooks quarterly via tabletop exercises to ensure they remain current.

6. Capture and Preserve Forensic Evidence

Standardise the collection of logs, disk images, and memory dumps. Result: Maintains the integrity of evidence for legal proceedings, insurance claims, and root cause analysis.

• Utilise write-blockers and hash-sum verification for all captured digital evidence.
• Maintain a strict Chain of Custody (CoC) log for all physical and digital media.
• Ensure logs are stored in a central, tamper-proof repository.

7. Restore Systems via Eradication and Recovery Steps

Remove the root cause of the incident and return services to a “Known Good” state. Result: Minimises business downtime while ensuring that the threat does not immediately recur.

• Restore data only from verified, immutable backups to avoid reinfection.
• Perform vulnerability scans on all restored systems before they are reconnected to the network.
• Revoke and reissue compromised credentials, certificates, and API keys.

8. Orchestrate Stakeholder and Regulatory Communications

Manage the flow of information to employees, customers, and authorities. Result: Protects the organisation’s brand equity and ensures adherence to global data protection laws.

• Prepare pre-approved communication templates for various incident scenarios.
• Utilise out-of-band communication channels if primary email or Slack is compromised.
• Designate a single spokesperson to prevent conflicting messages.

9. Conduct a Formal Post-Incident Review (PIR)

Analyse the timeline and effectiveness of the response after the threat is neutralised. Result: Identifies specific control gaps and drives continuous improvement in your security posture.

• Document “Lessons Learnt” and identify why the initial security controls failed.
• Assess the performance of the IRT against established Key Performance Indicators (KPIs).
• Quantify the total financial and operational cost of the incident.

10. Update the Risk Register and Statement of Applicability

Integrate the findings from the PIR back into the organisational risk management cycle. Result: Closes the compliance loop by ensuring future risk assessments are based on real-world data.

• Adjust risk likelihood and impact scores based on the actual incident data.
• Update Annex A controls and technical configurations to mitigate the discovered root cause.
• Verify that the updated controls are audited in the next internal audit cycle.

ISO 27001 Templates

Response Lifecycle Table

Phase	Action	Goal
1. Containment	Isolate infected server (disconnect network).	Stop the bleeding.
2. Eradication	Remove malware / Close vulnerability.	Clean the wound.
3. Recovery	Restore from backup / Restart services.	Get back to work.
4. Communication	Notify Data Subject / Regulator (72h rule).	Legal compliance.

How to comply

To comply with ISO 27001 Annex A 5.26 you are going to implement the ‘how’ to the ‘what’ the control is expecting. In short measure you are going to:

1. Document your information security incident response process
2. Assign and document the roles and responsibilities involved in the information response process
3. Communicate the incident response processes that those that need to know about it
4. Implement appropriate controls to mitigate, monitor and report on information security incidents
5. Monitor and review the information security incident response effectiveness

How to audit ISO 27001 Annex A 5.26

Auditing your incident response capability is a critical safeguard for business continuity: it ensures that when a breach occurs, your team acts with precision rather than panic. This guide provides a technical roadmap for Lead Auditors to verify that Annex A 5.26 is fully operational within the organisation.

1. Formalise the Information Security Incident Management Policy

Review the overarching policy to ensure it defines what constitutes an incident versus an event. Result: Establishes a clear legal and operational baseline for all security activities.

• Verify the document version control and senior management approval.
• Check for alignment with the internal Risk Management Framework.
• Ensure the policy is accessible to all employees via the company intranet.

2. Provision Incident Management Roles and IAM Permissions

Audit the Incident Response Team (IRT) structure and verify that specific IAM roles are pre-configured for emergency access. Result: Enables immediate action without administrative delays during a crisis.

• Inspect the “Rules of Engagement” (ROE) documents for third-party responders.
• Confirm that MFA is mandated for all privileged incident response accounts.
• Review the skills matrix to ensure technical staff are trained in forensic preservation.

3. Deploy Automated Detection and Reporting Channels

Examine the technical integration between your SIEM, SOC, and internal reporting tools. Result: Reduces the “Mean Time to Detect” (MTTD) by automating the initial alert phase.

• Test the “Report Phishing” or “Report Incident” buttons within the mail client.
• Audit log aggregation settings to ensure critical assets are sending telemetry.
• Verify that out-of-band communication channels (e.g., encrypted messaging) are established.

4. Classify Incident Severity and Triage Procedures

Evaluate the criteria used to categorise incidents by impact and urgency. Result: Ensures resources are allocated proportionally to the level of risk.

• Review the “Incident Classification Matrix” for consistency across different departments.
• Check that “High” severity triggers an automatic escalation to the CISO.
• Verify that the triage process accounts for data sensitivity as defined in the Asset Register.

5. Execute Technical Containment Playbooks

Sample recent incident logs to verify that containment steps were followed according to pre-defined playbooks. Result: Prevents the lateral movement of threats and limits data exfiltration.

• Inspect playbooks for specific scenarios: Ransomware, DDoS, and Model Poisoning for AI.
• Verify that network isolation procedures (VLAN tagging or port shutdown) are tested.
• Confirm that “Forensic Integrity” is maintained before systems are wiped or restored.

6. Trigger Mandatory Regulatory and Legal Notifications

Audit the workflow for notifying authorities such as the ICO (UK) or relevant EU regulators within 72 hours. Result: Maintains legal compliance and avoids heavy statutory fines.

• Check the reporting templates for GDPR, NIS2, and DORA requirements.
• Verify that “CIRCIA” timelines are understood if operating in US critical sectors.
• Ensure the Legal and PR departments are integrated into the escalation path.

7. Conduct Eradication and Forensic System Recovery

Verify that systems are only returned to production after a confirmed “clean” state is achieved. Result: Eliminates the risk of reinfection from dormant backdoors.

• Audit the backup restoration logs to ensure “Immutable Backups” were utilised.
• Confirm that vulnerability scans are performed on recovered assets before they go live.
• Check that local admin passwords and service account keys were rotated post-incident.

8. Review Post-Incident Lessons Learnt and Root Causes

Inspect the “Post-Incident Report” (PIR) for the most recent major incident to identify systemic failures. Result: Drives continuous improvement and prevents incident recurrence.

• Ensure the “Root Cause Analysis” (RCA) led to a specific change in technical controls.
• Verify that the PIR was shared with relevant stakeholders within 30 days.
• Check for a “No-Blame” culture that encourages honest reporting of human error.

9. Synchronise the Asset Register and Risk Assessment

Ensure that incident data is used to update the organisational risk profile and asset criticality. Result: Provides an accurate, data-driven view of the current threat landscape.

• Cross-reference the incident log with the Asset Register to see if new “Shadow IT” was discovered.
• Verify that risk scores for compromised assets were recalculated.
• Check that technical debt identified during the response is added to the remediation backlog.

10. Audit Response Effectiveness via Simulation and Testing

Verify the frequency and quality of “Tabletop Exercises” or “Red Team” simulations. Result: Confirms that response procedures work in practice, not just on paper.

• Review the results of the most recent annual “Simulated Breach” exercise.
• Verify that third-party vendors (MSPs) participated in the joint response testing.
• Check that the “Incident Management Plan” was updated based on simulation findings.

How to pass the audit

To pass an audit of ISO 27001 Annex A 5.26 Information security incidents should be responded to in accordance with the documented procedures you are going to make sure that you have followed the steps above in how to comply.

1. Have a documented information security incident management plan.
2. Implement the information security incident management plan.
3. Monitor the effectiveness of the information security incident management plan.
4. Review and update the information security incident management plan as needed.

What the audit will check

The audit is going to check a number of areas. Lets go through the main ones

1. That you have documented your roles, responsibilities and process

The audit will check the documentation, that you have reviewed it and signed and it off and that it represents what you actually do not what you think they want to hear.

2. That you can demonstrate the process working

They are going to ask you for evidence to the incident response process and take one example. For this example you are going to show them and walk them through the process and prove that you followed it and that the process worked.

3. That you can learn your lesson

Documenting your lessons learnt and following this through to continual improvements or incident and corrective actions will be checked. They want to see that not only did you respond but that you learnt from it and did something to improve that reduced or eliminated the possibility of it happening again.

Top 3 Mistakes People Make and How to Avoid Them

The top 3 Mistakes People Make For ISO 27001 Annex A 5.26 are

1. Not having a documented information security incident response plan.

This is the most common mistake made by organisations. A documented information security incident response plan is essential for effective incident response. It should include the following:

• A process for identifying information security incidents.
• A process for assessing the impact of information security incidents.
• A process for prioritising information security incidents.
• A process for responding to information security incidents.
• A process for recording information security incidents.

2. Not implementing the information security incident response plan.

Even if you have a documented information security incident response plan, it is not enough to simply have the plan. The plan must be implemented in order to be effective. This means assigning responsibility for implementing the plan, providing training on the plan, and testing the plan.

3. Not monitoring the effectiveness of the information security incident response plan.

Once the information security incident response plan is implemented, it is important to monitor its effectiveness. This means reviewing reports of information security incidents, conducting audits of the plan, and taking corrective action as needed.

By avoiding these mistakes, you can ensure that you have an effective information security incident management plan in place.

Why It Is Important

As the saying goes, shit happens. It is facts of life. No system or security is 100% We cannot be on the back foot when the inevitable happens and effective incident management can eliminate or reduce the impact of information security incidents.

ISO 27001 Annex A 5.26 Response to information security incidents is important because it provides guidance on how to manage information security incidents. Information security incidents can have a significant impact on an organisation, so it is important to have a plan in place for how to respond to them. The guidance in ISO 27001 Annex A 5.26 can help you to develop and implement an effective information security incident response plan.

The following are some of the benefits of having an effective information security incident response plan:

• It can help to reduce the impact of information security incidents.
• It can help to protect the organisations reputation.
• It can help to comply with legal and regulatory requirements.
• It can help to improve the organisations overall information security posture.

Applicability across different business models

Business Type	Applicability	Examples of Control Implementation
Small Businesses	Highly applicable for ensuring that the team acts effectively during a crisis. The focus is on clear, simple instructions that guide the small staff through containment and recovery without needing a dedicated security department.	Using a basic Lost Device Playbook that guides the office manager through remotely wiping a laptop via Microsoft Intune or Google Admin. Storing a physical “Incident Response Cheat Sheet” in the office safe that lists emergency contacts for legal counsel and the insurance provider. Documenting a manual process for notifying customers via email if a data breach involving personal information is confirmed.
Tech Startups	Critical for startups with complex cloud infrastructures and strict customer SLAs. Compliance involves technical playbooks that automate containment and ensure that “Eradication” doesn’t destroy forensic evidence.	Implementing Automated Incident Response (AIR) scripts that can isolate a compromised AWS instance or revoke a specific user’s API keys in seconds. Maintaining a “Ransomware Playbook” that specifically details how to restore the production database from an “Air-Gapped” backup. Establishing a 24/7 on-call rotation for the engineering team to ensure rapid containment of high-severity technical incidents.
AI Companies	Vital for protecting unique AI assets and proprietary research data. Focus is on specialized response protocols for adversarial attacks on models or unauthorized exfiltration of large training datasets.	Developing an Adversarial Attack Playbook that outlines the steps to take if a model begins producing biased or unauthorized outputs during inference. Implementing a forensic “Snapshoting” procedure for GPU cluster environments to preserve the system state for investigation before remediation starts. Formalizing a communication protocol for notifying research partners and academic collaborators of an incident involving shared sensitive datasets.

Applicable Laws and Related Standards

Standard / Law	Relevant Control / Article	Mapping & Requirements
NIST CSF v2.0	PR.IR-P1, PR.IR-P2, RS.MA-01	Focuses on the creation and execution of incident response playbooks and maintaining response integrity.
NIST SP 800-61	Incident Response Life Cycle	Provides the operational framework for detection, containment, and eradication required by ISO 5.26.
SOC 2 (Trust Services Criteria)	CC7.3, CC7.4, CC7.5	Requires procedures to identify and respond to incidents, including technical containment and system recovery.
EU GDPR	Articles 33 & 34	ISO 5.26 triggers the 72-hour regulatory notification and communication to affected data subjects.
UK Data (Use and Access) Act 2025	Complaints & Emergency Interest	Maintains 72h rule; adds 30-day mandatory response to security complaints and allows processing for “emergency interest.”
NIS2 Directive (EU)	Articles 21 & 23	Mandates incident handling for essential/important entities with a 24-hour “Early Warning” requirement.
UK Cyber Security and Resilience Bill	MSPs & 24h Reporting	Extends reporting duties to Managed Service Providers (MSPs) with a 24-hour initial notification window.
DORA (Digital Operational Resilience Act)	Articles 17, 18, 19	Specific to finance; requires same-day initial reporting for “Major ICT-related incidents.”
CIRCIA (USA)	72h / 24h Reporting	Mandatory 72-hour reporting for critical infrastructure; 24-hour reporting if a ransom is paid.
EU AI Act	Article 62	Requires immediate reporting (max 15 days) of “serious incidents” caused by high-risk AI systems.
ISO/IEC 42001 (AI Management)	Annex A.10.3	Maps incident response to AI-specific risks like model poisoning and prompt injection.
HIPAA (USA)	164.308(a)(6)	Requires documented procedures to identify, respond to, and mitigate security incidents involving ePHI.
CCPA / CPRA (California)	1798.82 & 1798.150	Incident response effectiveness is used as evidence of “reasonable security” to mitigate statutory damages.
EU Product Liability Directive (PLD)	Article 4	Classifies software as a product; failure to effectively respond to known flaws establishes “strict liability.”
ECCF (European Cybersecurity Cert)	Assurance Levels	Compliance with ISO 5.26 is a prerequisite for “Substantial” and “High” security labels for ICT products.

FAQ

Related ISO 27001 Controls

• ISO 27001 Clause 8.1 Operational Planning and Control
• ISO 27001 Annex A 5.25 Assessment And Decision On Information Security Events
• ISO 27001 Annex A 5.24 Information Security Incident Management Planning and Preparation

Further Reading

• The complete guide to ISO/IEC 27002:2022
• The Top 5 Ways AI is Changing ISO 27001

ISO 27001 controls and attribute values

Control type	Information security properties	Cybersecurity concepts	Operational capabilities	Security domains
Corrective	Confidentiality	Respond	Information Security Event Management	Defence
	Integrity	Recover
	Availability

About the author