EC-Council Certified Incident Handler v3 (ECIH) — Lesson 3: Containment, Eradication, Recovery, Verification, and Stakeholder Decisions

Learning Objectives

• Explain the structures, services, data, settings, roles, and dependencies governing Containment Options and Eradication.
• Implement and validate Service Recovery, Security Validation, and Business Decisions and Status Reporting using reviewable evidence.
• Evaluate the condition where analysts reach the wrong conclusion because Business Decisions and Status Reporting evidence is incomplete and Eradication context was not preserved and select a proportionate corrective response.

Detailed Topics

• Containment Options applied to the course scenario, expected behavior, dependencies, controls, and evidence.
• Eradication applied to the course scenario, expected behavior, dependencies, controls, and evidence.
• Service Recovery applied to the course scenario, expected behavior, dependencies, controls, and evidence.
• Security Validation applied to the course scenario, expected behavior, dependencies, controls, and evidence.
• Business Decisions and Status Reporting applied to the course scenario, expected behavior, dependencies, controls, and evidence.

Instructor Demonstration

The instructor traces an incident team must control a fast-moving cyber event, preserve evidence, coordinate stakeholders, restore services, and convert lessons into stronger defenses. The walkthrough connects tools, configuration or analysis logic, system messages, decisions, and evidence captured in the incident plan, case timeline, containment record, and lessons-learned report. It also tests the exception where analysts reach the wrong conclusion because Business Decisions and Status Reporting evidence is incomplete and Eradication context was not preserved.

Hands-On Exercise

Complete a controlled, authorized EC-Council exercise covering Containment, Eradication, Recovery, Verification, and Stakeholder Decisions and preserve the verified result in the incident plan, case timeline, containment record, and lessons-learned report.

1. Confirm scope, authorization, prerequisites, versions, identities, dependencies, and acceptance criteria.
2. Execute the workflow while recording settings, outputs, events, decisions, and system messages.
3. Test normal behavior, one boundary condition, and the stated exception without targeting real third-party systems.
4. Document corrections, evidence, ownership, retest criteria, rollback or recovery, and handover actions.

Scenario Analysis

• Identify which object, service, policy, setting, or sequence most strongly influences Containment Options.
• Compare two defensible responses and explain technical, security, operational, legal, and support trade-offs.
• Determine how the incident plan, case timeline, containment record, and lessons-learned report should be approved, retained, retested, and updated.

Troubleshooting Guidance

Start where expected behavior first differs from the observed result. Check authorization, prerequisites, identity, configuration order, data quality, version compatibility, connectivity, status, resource limits, and evidence separately. Treat “analysts reach the wrong conclusion because Business Decisions and Status Reporting evidence is incomplete and Eradication context was not preserved” as a hypothesis until logs, settings, captured outputs, and retest outcomes confirm the cause.

Validation Checklist

• Required components, identities, permissions, settings, safety controls, and dependencies are present.
• The incident plan, case timeline, containment record, and lessons-learned report connects each conclusion to objective, reviewable evidence.
• Normal processing, a boundary condition, dependency behavior, and the stated exception were tested.
• Corrections, ownership, retest criteria, rollback or recovery, documentation, and operational handover are complete.

Lesson Outcome

Learners can apply Containment, Eradication, Recovery, Verification, and Stakeholder Decisions, explain the resulting security or operational behavior, and defend the outcome through the incident plan, case timeline, containment record, and lessons-learned report.