The ECIH Introduction to Incident Handling module identifies social engineering as a primary method attackers use to gain unauthorized access without exploiting technical vulnerabilities.
Option C is correct because the attack relied on deception-spoofed notifications and lookalike domains-to trick users into disclosing credentials. This is a classic social engineering technique, often used as the initial access vector.
Options A, B, and D are technical reconnaissance or network attacks, not human-focused deception.
Recognizing social engineering as the root cause is essential for selecting appropriate remediation actions such as user awareness training, phishing defenses, and MFA, all emphasized in ECIH guidance.

The EC-Council Incident Handler (ECIH) curriculum clearly defines the Preparation Phase as the foundation of an effective Incident Handling and Response (IH&R) program. This phase focuses on establishing readiness before incidents occur. Activities include defining roles and responsibilities, forming and training the incident response team, conducting simulation and tabletop exercises, auditing assets, reviewing response tools, and developing formal policies and playbooks.
The scenario explicitly describes forward-looking corrective and preventive measures such as simulation exercises, stakeholder training, asset auditing, and policy development. These are hallmark activities of the Preparation phase. ECIH emphasizes that organizations lacking structured preparation often experience delayed response, unclear accountability, and increased operational impact during cyber incidents.
Option A (Recovery) focuses on restoring systems after containment and eradication. Option C (Eradication) involves removing threats after containment. Option D (Triage) falls under detection and analysis. None of these address proactive readiness and organizational resilience.
Therefore, initiating the Preparation phase is the correct approach to strengthen long-term cybersecurity resilience in alignment with ECIH standards.

This incident represents an application-layer DoS attack, which targets specific functions rather than bandwidth. ECIH emphasizes function-level protection in such scenarios.
Option C is correct because rate limiting restricts abusive request frequency while allowing legitimate usage.
It directly addresses the exploited feature without disrupting service availability.
Option D may block legitimate users behind shared IPs. Options A and B do not mitigate the attack vector.
Rate limiting aligns with ECIH guidance for preserving availability during Layer 7 attacks.

The GPG18 and Forensic readiness planning (SPF) principles outline various guidelines to enhance an organization's readiness for forensic investigation and response. Principle 5, which suggests that organizations should adopt a scenario-based Forensic Readiness Planning approach that learns from experience gained within the business, emphasizes the importance of being prepared for a wide range of potential incidents by leveraging lessons learned from past experiences. This approach helps in continuously improving forensic readiness and response capabilities by adapting to the evolving threat landscape and organizational changes.
References:While specific documentation from GPG18 and SPF might detail these principles, the ECIH v3 program by EC-Council covers the concept of forensic readiness planning, including adopting scenario-based approaches and learning from past incidents as a fundamental aspect of enhancing an organization's incident response and forensic capabilities.

This incident is a textbook example of whaling, a specialized form of phishing that targets senior executives or impersonates them to exploit authority and trust. According to the ECIH Email Security module, whaling attacks often focus on financial fraud, such as wire transfer requests or invoice manipulation, and are designed to bypass normal controls through urgency and executive impersonation.
Option A is correct because the attacker impersonated the CEO and targeted employees responsible for financial actions. The minor domain alteration and authoritative language are classic whaling indicators.
Option B refers to overwhelming inboxes with large volumes of mail. Option C involves automated credential testing. Option D targets mobile messaging platforms.
Jason's response-header analysis, identity verification, firewall blocking, financial alerting, and organization- wide notification-aligns with ECIH best practices for handling executive impersonation attacks.
Recognizing the attack type correctly is critical for appropriate escalation and mitigation, making Option A the correct answer.