212-89 Exam Dumps - ECCouncil ECIH Questions and Answers

This scenario describes a SYN flood attack, a classic protocol-level Denial-of-Service technique covered in the ECIH Network Security Incidents module. In a SYN flood, attackers send a large volume of TCP SYN packets but never complete the three-way handshake, leaving the server waiting for responses and exhausting connection resources.

Option D is correct because incomplete TCP handshakes, half-open connections, and resource exhaustion are defining characteristics of SYN flood attacks. The presence of multiple source IPs further suggests a distributed attack.

Option A involves taking over an existing session, not exhausting resources. Option B applies to UDP-based amplification attacks. Option C affects DNS resolution, not TCP handshakes.

ECIH stresses that early identification of SYN floods allows defenders to deploy SYN cookies, rate limiting, and upstream filtering. Recognizing handshake anomalies is therefore critical in protecting service availability.

According to the EC-Council Incident Handler (ECIH) curriculum, malware infections commonly originate from users downloading malicious executables from untrusted external sources. The scenario clearly indicates repeated access to suspicious URLs followed by the download of unsigned executable files outside business hours. ECIH classifies such behavior as high-risk web activity leading to malware compromise.

The endpoint protection system flagged the executables as malicious after execution, and outbound communication attempts suggest command-and-control (C2) beaconing behavior. ECIH explains that once malware executes, it frequently attempts outbound connections to attacker-controlled infrastructure for instructions, payload updates, or data exfiltration.

There is no evidence suggesting Wi-Fi spoofing (Option B), as logs trace activity to an internal workstation. Option C (SQL injection) relates to web application vulnerabilities, which are not described in this endpoint-based download scenario. Option D (privilege escalation) may occur after infection, but it is not presented as the initial cause.

ECIH emphasizes monitoring web proxy logs, correlating SIEM alerts, validating digital signatures, and analyzing firewall egress traffic to confirm malware incidents. Nina’s actions—log correlation, endpoint isolation, and lateral movement investigation—align precisely with recommended containment procedures.

Therefore, the most likely cause of the incident is inappropriate resource usage through malicious downloads.

Cross-site request forgery (CSRF or XSRF) is an attack that tricks the victim ' s browser into executing unauthorized actions on a website where they are currently authenticated. In this scenario, the attacker exploits the trust that a site has in the user ' s browser, effectively forcing the browser to perform actions without the user ' s knowledge or consent. For example, if the user is logged into their bank ' s website, an attacker could craft a malicious request to transfer funds without the user ' s direct interaction. CSRF attacks rely on authenticated sessions and typically target state-changing requests to compromise user or application data.

This scenario describes a persistent phishing campaign leveraging spoofed domains and variant-based delivery mechanisms. According to the EC-Council Incident Handler (ECIH) curriculum under Email Security Incident Handling and Eradication, once detection and containment measures (such as blocking malicious IP addresses and purging emails) have been implemented, the eradication phase must focus on eliminating root causes and recurring technical vectors.

The key phrase in the question is “eliminate recurring delivery mechanisms and close technical loopholes.” ECIH emphasizes that phishing campaigns frequently evolve by modifying URLs, sender domains, encoding techniques, and payload structures to bypass simple IP blocking controls. Therefore, security teams must analyze decoded message components, extract malicious URLs, and generate URL-based deny-lists at the secure email gateway, web proxy, and firewall layers.

Creating email-specific URL deny-lists directly disrupts the attack infrastructure and prevents repeated access to malicious domains—even when attackers use variant IP addresses or modified content. This is a technical eradication control aligned with eliminating delivery vectors.

Options B and C (training and simu-lations) are preventive awareness measures and fall under the preparation or post-incident improvement phase—not eradication. Option A (WHOIS masking) is unrelated to preventing phishing delivery.

ECIH guidance stresses strengthening email filtering rules, updating domain and URL blacklists, implementing SPF/DKIM/DMARC validation, and hardening secure email gateways as core eradication techniques. Therefore, option D best aligns with the eradication objective.

ECIH cloud incident handling guidance emphasizes that containment must be immediate and within the organization’s control. Modifying cloud security groups allows responders to restrict network access instantly, preventing further data exfiltration.

Option D is correct because it is actionable without CSP dependency and directly limits attacker movement. Option A may take time. Option B is investigative. Option C is regulatory and premature.

Containment through security group modification is therefore the most critical first step.

This scenario represents deceptive phishing because the attacker impersonates a trusted internal authority and directs employees to a fraudulent login page designed to harvest credentials. ECIH v3 email incident handling emphasizes examining sender information, URLs, domains, email headers, and landing pages when investigating suspected phishing. The fake HR message uses social engineering and a look-alike web page to persuade users to disclose payroll or authentication information. Email spamming refers broadly to unsolicited bulk messages and does not necessarily involve targeted credential theft. A mail storm is an abnormal flood of email traffic, while DNS cache poisoning manipulates DNS resolution rather than using a fraudulent link in an email. Elena ' s preservation of headers, screenshots, and malicious-domain information also follows appropriate evidence collection and containment practices for phishing incidents.

================

Public Key Infrastructure (PKI) is a framework used to manage digital certificates and public-key encryption. It enables secure electronic transfer of information for a range of network activities such as e-commerce, internet banking, and confidential email. PKI is fundamental to the management of encryption keys and digital certificates, ensuring the secure exchange of data over networks and verification of identity.

The collective symptoms are consistent with a distributed denial-of-service attack. ECIH network-incident handling requires responders to correlate traffic volume, resource consumption, connection patterns, and distributed source information when validating DoS/DDoS activity. Here, bandwidth saturation, elevated router CPU utilization, overloaded NAT tables, excessive connection attempts, and traffic originating from multiple geographic locations collectively indicate coordinated resource exhaustion. A vulnerability scan can generate connections to multiple ports, but it ordinarily does not produce the widespread bandwidth and infrastructure exhaustion described. Data exfiltration is associated primarily with unauthorized outbound transfer of information rather than massive incoming traffic. A rogue DHCP server affects address assignment and network configuration but does not explain geographically distributed request floods. The distributed sources and resource-exhaustion effects therefore make a DDoS incident the strongest diagnosis.

================

This incident involves malware actively impacting medical devices, posing patient safety risks. According to ECIH malware incident handling principles, the first priority is containment and eradication at the endpoint level.

Option D is correct because deploying endpoint protection directly detects and halts malware execution on the MRI machines, stopping both manipulation of results and further malicious activity. Endpoint containment is essential before network-level or recovery actions.

Option B addresses communication but does not stop local manipulation. Option C alters system state without containment. Option A is a regulatory step that follows validation.

ECIH emphasizes that in critical infrastructure and healthcare environments, immediate endpoint containment is essential to protect safety and data integrity.

In a Linux environment, email servers such as Sendmail log events, including details about sent and received emails, in a specific log file. The correct directory and file for examining email logs, particularly for Sendmail and using Syslog for logging, is /Var/log/maillog. This file contains vital information for forensic and incident response purposes, including source and destination IP addresses, email addresses, timestamps, and other data relevant to the email traffic handled by the server. By analyzing this log, incident responders can gather evidence related to email-based incidents, trace the source of malicious emails, and understand the scope of an incident. It ' s crucial for individuals like Khai, who are tasked with examining logs, to know the correct log file locations and their contents to effectively validate and analyze email header information and other relevant data.