ISO/IEC 27035 Lead Incident Manager Training — Lesson 3: Containment, Eradication, Recovery, Communication, and Coordination

Learning Objectives

• Interpret the principles, requirements, roles, and dependencies shaping containment, eradication, recovery, communication, and coordination.
• Apply the workflow and produce incident response and recovery runbook that another practitioner can review.
• Analyze “systems return to service before the intrusion path is removed” and recommend a proportionate, supported response.

Detailed Topics

• containment strategy
• eradication
• service recovery
• stakeholder communication
• legal coordination
• supplier coordination
• regulatory notification
• business validation
• Competence, communication, governance, documented information, risk, validation, and follow-up considerations

Instructor Demonstration

The instructor demonstrates the containment, eradication, recovery, communication, and coordination workflow, identifies the applicable inputs and responsibilities, records checkpoints in incident response and recovery runbook, and contrasts the accepted state with a condition where systems return to service before the intrusion path is removed.

Hands-On Exercise

Complete a controlled implementation, audit, assessment, or foundation exercise for Containment, Eradication, Recovery, Communication, and Coordination. Establish scope and criteria, collect or create evidence, examine “systems return to service before the intrusion path is removed,” reach a supported conclusion, and preserve the result in incident response and recovery runbook.

1. Confirm objectives, scope, roles, criteria, stakeholders, and expected outputs.
2. Perform the planned activities while recording assumptions, evidence, and decisions.
3. Test a normal case, an exception, and a follow-up or improvement condition.
4. Document conclusions, owners, due dates, escalation, and verification requirements.

Scenario Analysis

• Identify the requirement or principle with the strongest influence on containment, eradication, recovery, communication, and coordination.
• Compare two defensible responses and explain their governance, risk, and evidence trade-offs.
• Determine how incident response and recovery runbook should be approved, retained, reviewed, and updated.

Troubleshooting Guidance

Separate missing evidence from ineffective practice, and distinguish a documentation issue from a control, process, governance, or competence failure. Use incident response and recovery runbook to trace the earliest divergence. Treat “systems return to service before the intrusion path is removed” as a hypothesis until the response is validated against the applicable requirement and intended outcome.

Validation Checklist

• The scope, criteria, stakeholders, and intended outcome for containment, eradication, recovery, communication, and coordination are explicit.
• The incident response and recovery runbook links statements and decisions to objective, reviewable support.
• Responsibilities, competence, communication, risk, legal duties, and change impact were considered where relevant.
• Findings, corrective actions, monitoring, review triggers, and improvement ownership are clear.

Lesson Outcome

Learners can apply Containment, Eradication, Recovery, Communication, and Coordination, explain the reasoning used, and defend the result through incident response and recovery runbook.