212-89 Exam Dumps - ECCouncil ECIH Questions and Answers

System characterization is the process of defining the boundaries of an IT system, which includes identifying the resources, information, and functionality that constitute the system. This process is crucial for understanding the scope of the system, the data it processes, and the technology it employs. By characterizing a system, incident handlers can better understand the system ' s normal operations and behaviors, which is essential for identifying anomalies that may indicate a security incident. System characterization involves documenting the hardware, software, network configuration, data flows, and other critical elements of the IT environment. This foundational knowledge supports effective incident handling by providing a baseline against which suspicious activities can be compared.

Nation-state attribution involves identifying a specific country or government as the sponsor behind a cyber-attack or intrusion. This type of threat attribution is focused on determining the involvement of state actors in cyber operations against specific targets, which often involves sophisticated, well-planned, and executed cyber campaigns. Alexis ' s efforts to identify and attribute the actors behind the attack to a specific nation-state fall under this category, as she seeks to uncover the geopolitical motives and the extent of state sponsorship behind the incident. Nation-state attribution requires analyzing a variety of indicators, including technical evidence, tactics, techniques, and procedures (TTPs), and contextual intelligence. This is distinct from campaign attribution, which focuses on linking attacks to a specific campaign or operation, true attribution, which aims at identifying the actual individuals behind an attack, and intrusion set attribution, which involves attributing a set of malicious activities to a particular threat actor or group.

The incident involves an active cloud-based malware compromise rather than merely an operational scheduling issue. ECIH v3 cloud incident handling emphasizes using cloud-aware security capabilities to identify compromised resources, determine attack scope, detect malicious workloads or processes, and support containment and eradication. Deploying the available cloud security tool directly addresses the active threat and can help identify how the malware is spreading through the cloud environment. Monitoring flight schedules provides operational visibility but does not stop malicious activity. Halting all flights would be a severe business and safety decision that should not be taken without evidence that such disruption is necessary. Passenger notification may eventually be required depending on operational impact but does not remediate the security incident. Therefore, targeted technical investigation and containment using the cloud-specific security tool is the appropriate primary action.

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

In Wireshark, the filtericmp.type==8is used to detect ping sweep attempts. ICMP type 8 messages are echo requests, which are used in ping operations to check the availability of a network device. A ping sweep involves sending ICMP echo requests to multiple addresses to discover active devices on a network. By filtering for ICMP type 8 messages in Wireshark, Bran can identify these echo requests, helping to pinpoint ping sweep activities on the network.

Michael’s actions reflect crime scene control, a foundational first-response principle in the ECIH forensic readiness module. Securing the area, preventing unauthorized access, and avoiding system changes preserve evidence integrity.

Option C is correct because his primary objective is to secure and evaluate the digital crime scene before evidence collection begins. ECIH stresses that scene control prevents contamination, tampering, and accidental evidence destruction.

Options A, B, and D may follow but are not the immediate objective.

The EC-Council Incident Handler (ECIH) curriculum stresses that preparation is the most critical phase of incident response. Organizations must establish clearly defined roles, communication channels, escalation procedures, and documented response workflows before an incident occurs. The scenario highlights confusion during a resilience drill—specifically unclear stakeholder responsibilities, communication breakdowns, and uncertainty in vendor coordination and log retrieval.

ECIH emphasizes that conducting realistic simu-lations, tabletop exercises, and red/blue team drills strengthens organizational readiness. These exercises help validate escalation paths, clarify third-party engagement protocols, and ensure that evidence collection procedures—such as retrieving diagnostic logs—are well understood by operational teams.

Option A (automated alerts) improves detection but does not solve role ambiguity. Option B (firmware patching) addresses vulnerability management but not communication gaps. Option D (manual fallback mode) supports business continuity but does not resolve the confusion in responsibilities and escalation paths identified in the drill.

ECIH guidance clearly states that effective first response depends on documented playbooks, defined stakeholder responsibilities, vendor coordination procedures, and continuous testing of incident response plans. simu-lation-based training exposes procedural weaknesses and ensures each department understands its operational and communication duties.

Therefore, conducting realistic simu-lations and clearly documenting responsibilities for each stakeholder is the most appropriate corrective action to close the preparedness gaps identified during the exercise.

In healthcare environments, ransomware threatens more than information confidentiality; it can directly disrupt clinical and operational services required for patient care. ECIH incident handling emphasizes availability, business continuity, and rapid restoration when malware affects mission-critical systems. An effective response framework allows the organization to detect affected endpoints, contain ransomware propagation, eradicate malicious components, restore trusted systems, and maintain essential healthcare operations. Regulatory reporting and reputational effects are significant considerations, but they are secondary to protecting service continuity where outages may delay diagnosis, treatment, access to medical records, or other patient-support functions. Completely overhauling the IT infrastructure is not automatically required after every ransomware incident. The strongest justification for a robust endpoint incident-handling capability in this scenario is therefore the need to maintain operational continuity and protect the delivery of patient care.

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

ECIH recognizes that containment strategies must consider operational impact, evidence preservation, and attacker behavior. In this OT environment, the organization specifically needs to restrict lateral movement without revealing that defenders have detected the attacker. Selectively disabling services associated with the attack while continuing passive monitoring provides controlled, low-profile containment. It can restrict the adversary ' s movement while allowing responders to observe persistence mechanisms, communications, and attempted exfiltration and preserve valuable forensic evidence. A system-wide shutdown would be highly disruptive to production and immediately alert the attacker. Restoring from backup is a recovery action and could destroy evidence or reintroduce compromise before the threat is understood. An organization-wide credential-change announcement would likewise expose the response effort. Therefore, selective service restriction combined with passive monitoring best satisfies the required stealth-containment objective.

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

Netstat (network statistics) is a command-line tool that displays network connections (both incoming and outgoing), routing tables, and a number of network interface (and network protocol) statistics. It is considered a volatile evidence collecting tool because it gathers information that exists in the system ' s memory, which is lost upon shutdown or reboot. This makes it invaluable for collecting evidence of active connections and processes that are present at the time of the incident response but does not persistently store data that can be recovered later. This contrasts with tools like FTK Imager or ProDiscover Forensics, which are used for acquiring digital evidence in a non-volatile manner, such as disk imaging, and HashTool, which is used for validating the integrity of collected digital evidence through hashing.

Static analysis involves examining the malware ' s memory dumps or binary codes without executing the code. This technique is used to find traces of malware by analyzing the code to understand its purpose, functionality, and potential impact. Static analysis allows for the identification of malicious signatures, strings, or other indicators of compromise within the malware ' s code. This method is contrasted with dynamic analysis, which studies the malware ' s behavior during execution, live system analysis, which examines running systems, and intrusion analysis, which focuses on detecting and analyzing breaches.