Cookies on this site. Help us understand what works and improve your experience. Essential cookies keep the site working. With your permission, our visit insights and Google Analytics measure usage, and Google Ads measures advertising. Optional cookies are not required to use the free kit. Change your choice anytime in Cookie settings. Privacy policyCookie policy
Respond to incidents according to your documented procedures – contain, eradicate, recover and communicate.
Is it mandatory? Not automatically. You must consider this control in your Statement of Applicability (6.1.3 d). Include it if your risk assessment, laws, contracts or business needs require it; if you exclude it, write down a justification an auditor will accept.
Why this control matters
Response guidance is most useful when teams know how the organization moves from triage to decisive action without losing control of systems, evidence, or communication. Teams should align the Incident Response Policy, Incident Response Procedure, and Data Breach Notification Procedure so containment, eradication, recovery, and external notices follow a single approved path. It also supports practical role clarity for technical, legal, and business responders.
Common auditor findings to check for
Potential gaps to test in your own environment, not a claim about observed audit frequency.
Containment steps are described broadly, but no playbook shows who can isolate endpoints, disable accounts, or block traffic when hours matter.
External notification duties are referenced, yet deadlines, decision approvals, and draft-message ownership are not linked to legal or privacy review, creating avoidable delay.
Recovery activities start without criteria for restoring services, validating cleanliness, or recording residual risk, which can leave the incident technically unresolved despite service resumption.
How you can implement it
Tools and review intervals are examples; choose them according to risk, obligations and your operating environment.
Write incident playbooks for ransomware, phishing, account takeover, lost device, and supplier compromise. Each playbook should state initial containment actions, the owning role, the tool used, the evidence to preserve, and the criteria for moving from containment to eradication and recovery. Keep the steps short enough to use under pressure.
Define who may execute urgent actions such as disabling a privileged account, quarantining an endpoint, or blocking a domain. Pair each action with an approval rule and fallback route if the primary approver is unavailable. This avoids hesitation and prevents unauthorized response changes during the incident.
Link recovery to validation. Before returning systems to service, require checks such as malware scan results, patch status, account review, backup restore verification, and business owner sign-off. Record the recovery decision, any temporary workaround, and remaining risks so leadership understands what was restored and what remains monitored.
Specify notification workflow for customers, authorities, suppliers, and internal leadership where legal or contractual duties apply. The procedure should identify the reviewer, the message owner, the source of facts, and the record set that proves timing, content, and approval. Use date-stamped templates to reduce drafting time without replacing judgment.
What an auditor will ask to see
Incident playbooks with containment, eradication, recovery, and communication steps for key scenarios.
Data Breach Notification Procedure with approval chain, notification criteria, and draft template references.
Incident log showing actions taken, evidence preserved, recovery validation, and final closure decision.
Baseline documents in the kit
These free kit documents help you document or evidence A.5.26. Each one is tailored to your organization when you build your kit.
Use the SIG and CAIQ questionnaire accelerator to find supporting documents. A mapping is a starting point: verify your actual operating evidence before answering a buyer.
For help adapting this to your environment, explore ISO/IEC 27001 consulting, starting with a free one-hour consultation.
Get these documents tailored to your organization
109 ready-to-edit documents, including all 19 mandatory ones, tailored from a short scoping questionnaire and linked to your risk register and SoA.