212-89 Exam Dumps - EC Council Certified Incident Handler (ECIH v3)

A permissive security policy is one that allows employees broad freedoms in terms of internet access, application downloads, and remote access capabilities. In the scenario described, the incident response team identifies that the lack of restrictions is a significant security threat that could be exploited by attackers, indicating that the current policy is permissive. Modifying this policy would involve implementing more stringent controls on what sites can be visited, what applications can be downloaded, and how remote access is granted, moving towards a more controlled and secure environment. This approach contrasts with paranoic, prudent, and promiscuous policies, each of which has its own characteristics and applications in cybersecurity frameworks.

This incident indicates credential compromise, a common cloud security issue addressed in the ECIH Cloud Incident Handling module. When credentials are suspected to be compromised, the immediate priority is to stop unauthorized access and determine the scope of misuse.

Option B is correct because resetting the compromised credentials immediately cuts off the attacker’s access. Reviewing recent access logs allows responders to validate what actions were taken, which data was accessed, and whether additional accounts were affected. ECIH emphasizes immediate credential revocation as a first-response action in identity-based cloud incidents.

Option D (enabling MFA) is a critical hardening measure but does not immediately revoke compromised credentials. Option A is a recovery step that may not stop ongoing access. Option C may be necessary later but should not delay immediate containment.

Therefore, resetting credentials and reviewing logs is the most effective first action, fully aligned with ECIH guidance.

The DBCC LOG command is used in SQL Server environments to analyze the transaction log files of a database. It provides insights into the transactions that have occurred, which is crucial for forensic analysis in the event of an incident. The syntaxDBCC LOG( < database_name > , < output_level > )allows an incident handler to specify the level of detail they wish to retrieve from the log files. When an incident handler like Adam requires the full information on each operation along with the hex dump of the current transaction row, the output parameter should be set to 4. This level of output is the most verbose, providing comprehensive details about each transaction, including a hex dump which is essential for a deep forensic analysis. It helps in understanding the exact changes made by transactions, which can be pivotal in investigating incidents involving data manipulation or other unauthorized database activities.

Volatile data refers to information that is stored temporarily and is lost when a computer is turned off or restarted, such as RAM contents, including open sockets and open ports, the date and time of the system, and the state of the network interface. The creation dates of files, however, are considered non-volatile data because they are preserved on the hard drive and remain available after the system is restarted or turned off. Non-volatile data is stored on persistent storage mediums like hard drives, SSDs, and magnetic tapes, where it remains until it is deleted or overwritten.

Explanation (cloud triage at scale):

Cloud environments generate massive telemetry across services, accounts, regions, and tenants. The limiting factor is not “more logs,” but correlation and prioritization: connecting identity events, network flows, workload behaviors, API calls, and configuration changes into a coherent incident timeline and severity assessment. Automation/orchestration (A) supports rapid triage by correlating alerts, deduplicating noise, enriching with context (asset criticality, ownership, exposure), and driving consistent playbook actions (ticket creation, isolation steps, snapshotting, token revocation) with approvals.

(B) may be overbroad and can create major outages and contractual harm; it’s containment without validated scope. (C) is premature; customer communication should be accurate and proportional, usually after initial scoping and legal review. (D) is the opposite of best practice—third-party logs can be essential (EDR, CASB, SIEM, SaaS audit logs).

So (A) is the best first step because it makes triage fast, consistent, and scalable, which is exactly what you need when log volume is the main operational barrier.

A TCP Xmas scan is a type of network scanning technique used by attackers to identify open ports on a target machine. The name " Xmas " comes from the set of flags that are turned on within the packet, making it ' lit up like a Christmas tree ' . Specifically, the FIN, PSH, and URG flags are set, which corresponds to the hexadecimal value 0X029 in the TCP header ' s flags field. Wireshark, a popular network protocol analyzer, allows users to create custom filters to detect specific types of network traffic, including malicious scanning attempts. By using the filtertcp.flags==0X029, Rose can detect packets that have these specific flags set, indicating a potential TCP Xmas scan attempt.

In the context of using Wireshark, a popular network protocol analyzer, to detect ping sweep attempts on a network, the filtericmp.type==8is used. ICMP (Internet Control Message Protocol) is utilized for sending error messages and operational information indicating, for example, that a requested service is not available or that a host or router could not be reached. ICMP type 8 messages are echo requests, which are used by the ping command to test the reachability of a host on an IP network. A ping sweep consists of ICMP echo requests sent to multiple hosts to find which ones are alive. By applying theicmp.type==8filter in Wireshark, Bran can isolate and examine the echo request messages, helping to identify ping sweep attempts, which are characterized by a high volume of ICMP echo requests over a broad range of IP addresses in a short period.

This scenario demonstrates preservation of volatile evidence, a critical first-response principle in the ECIH forensic readiness module. Volatile evidence includes data that exists only while a system is powered on, such as active sessions, running processes, open files, and on-screen information.

Option B is correct because David documents the live system state without interacting in a way that would alter evidence. Photographing the screen, recording visible activity, and documenting connections are all recommended ECIH practices when dealing with powered-on systems.

Option A is unrelated. Option C alters system state. Option D applies only to inactive devices.

ECIH stresses that mishandling active systems can destroy crucial evidence. David’s actions align precisely with first responder best practices, making Option B correct.