“"I practiced with full-length exams after completing each incident response module. It helped me connect the entire response lifecycle instead of treating each phase as a separate topic."”
Jordan Ellis
Cyber Defense Analyst
The 212-89 exam gives you 100 multiple-choice questions and a three-hour window, delivered through EC-Council’s own ECC Exam Portal rather than Pearson VUE or PSI — you can sit it remotely proctored or at an authorized testing center. There’s no single published passing percentage; EC-Council uses a form-dependent cut score, and the figure most commonly cited sits somewhere in the 60–78% range depending on which exam form you draw.
Don’t expect straight definition recall. ECIH leans heavily on scenario questions: you’re handed a situation — a phishing email with a suspicious attachment, a server showing signs of lateral movement, a departing employee who copied files before resigning — and asked what the next correct step is. A lot of wrong answers aren’t factually wrong, they’re just out of sequence. Eradicating malware before you’ve imaged the affected disk, or containing a host before you’ve captured volatile memory, will cost you points even if the action itself is defensible in isolation.
EC-Council has not published official per-domain weighting percentages for the 212-89 blueprint, so treat the table below as relative emphasis rather than a precise scoring formula. Based on the depth of content EC-Council allocates to each module in the official courseware, two areas clearly carry more weight than the rest.
Domain | Relative Emphasis | What It Covers |
|---|---|---|
Incident Handling and Response Process | Heavy | The 9-step IH&R lifecycle: preparation through post-incident activity |
Handling and Responding to Malware Incidents | Heavy | Static/dynamic analysis basics, containment and eradication of malware |
Handling and Responding to Network Security Incidents | Medium-high | DoS/DDoS, man-in-the-middle, unauthorized access incidents |
Handling and Responding to Cloud Security Incidents | Medium | AWS, Azure, and GCP incident response and native logging tools |
Handling and Responding to Endpoint Security Incidents | Medium | Mobile, IoT, and OT/ICS incidents — new in v3 |
Introduction to Incident Handling and Response | Medium | Threat landscape, IR frameworks, team roles, SOAR basics |
Forensic Readiness and First Response | Medium | Order of volatility, write-blockers, chain of custody |
Handling and Responding to Email Security Incidents | Medium | Phishing, BEC, spoofing, mailbox compromise |
Handling and Responding to Web Application Security Incidents | Medium | Injection, defacement, and web-layer incident response |
Handling and Responding to Insider Threats | Medium | Investigation discretion, HR/legal coordination, evidence handling |
Order of volatility. People study “collect evidence” as a single step and move on. The exam wants you to know the actual sequence — RAM and running processes before disk, disk before archived logs — and it’ll test this with a scenario rather than a direct question, so you have to recognize it in context.
Chain of custody mechanics. Not just “document who touched the evidence,” but the specific details: hashing with MD5/SHA-256 to prove integrity, using a write-blocker before imaging, and what breaks a chain of custody versus what merely weakens it. Candidates who’ve never done forensics hands-on tend to miss the nuance here.
Cloud incident response across three platforms. ECIH v3 expects you to recognize equivalent tools across AWS, Azure, and GCP — CloudTrail next to Microsoft Sentinel next to Cloud Audit Logs. If you’ve only worked in one cloud environment, this section will expose the gap fast.
The new endpoint module. Mobile, IoT, and OT/ICS incident handling was added in the v3 update, and it’s thinner in most third-party study material than the legacy modules. Underestimating it because it’s “new” is a common mistake.
Insider threat investigation discipline. The correct answer often isn’t the most aggressive one. Quietly preserving evidence and looping in HR/legal before confronting a suspected insider is frequently the right move, and test-takers who default to “lock the account immediately” in every scenario lose points here.
Because ECIH is scenario-heavy, don’t just drill isolated facts — work through full incident narratives and force yourself to sequence the response from detection to post-incident review. When you get a practice question wrong, check whether you missed a fact or missed the order of operations; they require different fixes.
Run timed sets that mix incident types. The exam won’t group all the malware questions together, and candidates who only practiced one module at a time are often slower to context-switch under conditions. If you consistently nail network and malware questions but stumble on cloud or insider-threat scenarios, that’s your signal to go back to the courseware for those specific modules rather than re-running the whole bank.
Memorizing the IH&R process as a list of names instead of understanding why each step has to happen before the next — the exam tests the “why,” not just the “what”
Treating containment, eradication, and recovery as interchangeable when a question’s wording signals a specific phase
Skipping the forensics fundamentals because they feel like a CHFI topic rather than an ECIH one — they’re squarely in scope here
Under-preparing for the cloud module because home-lab practice tends to focus on one provider
Running out of time because scenario questions take longer to read than straight recall questions, and candidates haven’t paced a full 100-question mock under the 3-hour clock
New to incident response: Budget 8–10 weeks. Spend the first few weeks building a working knowledge of networking and OS fundamentals if those are shaky, then move through the IH&R process and forensics readiness modules before tackling the incident-type-specific sections.
Has related security experience (SOC analyst, sysadmin, network security): 4–6 weeks is usually . Your gap is more likely to be the formal IH&R sequence and the forensics/chain-of-custody specifics than the general security concepts.
Retaking the exam: 2–3 weeks, focused entirely on whichever modules you missed on the score report. Retakers who fail a second time usually failed the same category twice — go back to that specific module rather than re-reviewing everything.
The jump from ECIH v2 to v3 added a dedicated Endpoint Security Incidents module covering mobile, IoT, and OT/ICS — ground the earlier version didn’t address directly. Cloud incident response also expanded to treat AWS, Azure, and GCP as three distinct environments rather than a single generic “cloud” topic. If you’re studying from older material or a v2-era course, these two areas are where you’re most likely to have gaps Try a Salesforce Certified Marketing Cloud Email Specialist practice exam for free.
Last updated on Oct, 30 2026