Pass the ECCouncil ECIH 212-89 Questions and answers with CertsForce

The correct sequence of steps involved in forensic readiness planning, based on the activities described, is as follows:

Identify the potential evidence required for an incident.

Determine the source of the evidence.

Define a policy that determines the pathway to legally extract electronic evidence with minimal disruption.

Establish a policy for securely handling and storing the collected evidence.

Identify if the incident requires full or formal investigation.

Train the staff to handle the incident and preserve the evidence.

Create a special process for documenting the procedure.

In the context of incident handling, the "point of contact" list is essential for ensuring that Sheila, the incident handler working at night, can quickly notify the responsible personnel within the organization about the cyberattack. This list typically includes the contact information of key stakeholders and decision-makers who need to be informed about security incidents, allowing for timely communication, decision-making, and response coordination.

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.

In the context of an incident response team, the role of an internal auditor like David includes identifying, evaluating, and reporting on information security risks and vulnerabilities within the organization. His responsibility is to ensure that the organization's security controls are effective and to identify any security loopholes that could be exploited by attackers. Once identified, he reports these vulnerabilities to management so that they can take the necessary actions to mitigate the risks. This role is critical in maintaining theorganization's overall security posture and ensuring compliance with relevant laws, regulations, and policies.

The scenario described is characteristic of a Trojan. A Trojan is a type of malware that disguises itself as legitimate software but performs malicious actions once installed. Unlike viruses, which can replicate themselves, or worms, which can spread across networks on their own, Trojans rely on the guise of legitimacy to trick users into initiating their execution. In this case, the user believed they were downloading and installing genuine software, but the reality was that the application contained a Trojan. The malicious code executed upon installation provided unauthorized remote access to the user's computer, which could be used by an attacker to control the system, steal data, install additional malware, or carry out other malicious activities.

Trojans can come in many forms and can be used to achieve a wide range of malicious objectives, making them a versatile and dangerous type of cyber threat. The deceptive nature of Trojans, exploiting the trust users have in what appears to be legitimate software, is what makes them particularly effective and widespread.

Process memory, or volatile memory (RAM), is digital evidence that requires a constant power supply to retain data and is deleted or lost when the power supply is interrupted. It contains information about the system's ongoing processes and operations. This type of evidence can be crucial for forensic investigations as it may hold information about user actions, system events, and the state of applications and services at the time of an incident. Unlike swap files, event logs, and slack space, which can retain information without a constant power supply, process memory is inherently volatile and its contents are lost when a device is powered off or restarts.

The most effective eradication and prevention control in this scenario is the implementation of the Principle of Least Privilege (PoLP) through strict access controls. According to the EC-Council Incident Handler (ECIH) curriculum under Insider Threat Management and Incident Prevention, organizations must ensure that users are granted only the minimum level of access required to perform their job functions. Excessive privileges significantly increase the risk of intentional or accidental misuse of critical systems and data.

In this case, employees were granted administrative access to sensitive systems without a business justification. Administrative privileges typically allow access to restricted financial data and the ability to modify audit logs. ECIH emphasizes that improper privilege management is a primary enabling factor in insider threats. If role-based access control (RBAC) aligned with PoLP had been properly enforced, these employees would not have had the capability to access restricted financial records or alter audit logs.

While User and Entity Behavior Analytics (UEBA) can detect anomalous behavior, it is primarily a detective control rather than a preventive eradication measure. Enhanced password policies strengthen authentication but do not address excessive authorization rights. Network segmentation limits lateral movement but does not directly prevent misuse of over-privileged accounts within authorized segments.

ECIH guidelines strongly recommend periodic access reviews, separation of duties, privilege auditing, and strict RBAC enforcement as part of insider threat mitigation and eradication strategies. By implementing PoLP and continuously reviewing administrative privileges, organizations can significantly reduce the attack surface and prevent privilege abuse before an insider can exploit sensitive systems.

The EC-Council Incident Handler (ECIH) curriculum classifies social engineering as a human-based attack technique that manipulates individuals into disclosing confidential information without exploiting technical vulnerabilities. In this scenario, the attackers first gathered publicly available information—also known as Open-Source Intelligence (OSINT)—by mining executive digital footprints, analyzing online publications, and reviewing external mentions. This reconnaissance phase aligns directly with OSINT-based profiling.

The adversaries then conducted scripted interviews under fabricated personas to extract additional identifiers. This behavior is characteristic of pretexting, a specific social engineering technique where attackers create a false scenario to persuade victims to provide sensitive information. ECIH explains that pretexting often involves impersonation and carefully constructed narratives to build credibility and trust.

The absence of malware infection or system-level compromise further confirms that this was not a technical exploit such as phishing with malicious macros (Option A) or pharming (Option C). Additionally, skimming (Option D) is a physical data theft technique unrelated to executive impersonation or digital profiling.

ECIH emphasizes that insider threat and financial fraud investigations frequently reveal social engineering campaigns leveraging OSINT, impersonation, and psychological manipulation rather than malware. Preventive controls include executive awareness training, strict identity verification for financial change requests, multi-factor authentication, and callback verification procedures.

Therefore, the technique that best aligns with the adversary’s method is social engineering using open-source intelligence followed by pretexting.

This scenario is a clear example of a deceptive phishing attack, which is extensively covered in the ECIH Email Security Incident module. Deceptive phishing involves impersonating a trusted internal entity—such as HR—to trick recipients into disclosing sensitive information like credentials or personal data.

Option D is correct because the email impersonates HR, uses social engineering, and directs users to a visually identical but fraudulent login page hosted on an unfamiliar domain. These characteristics are classic indicators of deceptive phishing.

Option A refers to DNS manipulation and is not evidenced here. Option B involves overwhelming email volume rather than deception. Option C refers to unsolicited bulk email without impersonation.

Elena’s actions align with ECIH best practices: preserving headers for forensic validation, capturing screenshots to document fraudulent infrastructure, and blocking malicious domains to prevent further exposure. Correctly categorizing the incident as deceptive phishing ensures appropriate eradication, awareness, and reporting measures.