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

A permissive security policy is characterized by allowing all activities except those that are explicitly blocked. This approach starts with a default state of allowing access and functionality, with restrictions applied only to known dangerous services, attacks, or behaviors. Such a policy can lead to a wider attack surface because it assumes services and behaviors are safe unless proven otherwise.

A prudent policy would typically involve more conservative security measures, applying necessary restrictions to protect against identified and potential threats.

A paranoic policy would be at the extreme end of security measures, possibly blocking more than necessary to ensure the highest level of security, often at the expense of usability or functionality.

A promiscuous policy, in contrast, would be even more open than a permissive policy, essentially allowing nearly all traffic or actions with minimal restrictions, which is not what Rica observed.

Email Dossier is a tool designed to perform detailed investigations on email messages to verify their authenticity and trace their origin. It can analyze email headers and provide information about the route an email has taken, the servers it passed through, and potentially malicious links or origins. For an incident handler like Stenley, tasked with verifying the validity of emails and containing malicious email threats, Email Dossier serves as a practical tool for analyzing and validating emails received by employees. By using this tool, Stenley can identify fraudulent or suspicious emails, thereby helping to protect the organization from phishing attacks, malware distribution, and other email-based threats.

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.

This scenario demonstrates manual phishing email verification, which is a foundational detection technique taught in the ECIH Email Security module. Manual verification involves human inspection of email characteristics such as sender address anomalies, mismatched URLs, unusual tone, urgency, and contextual inconsistencies.

Option D is correct because Ethan manually inspects the email by hovering over links, reviewing sender formatting, and evaluating message tone. These actions are key indicators used to identify phishing without relying on automated tools.

Option A relates to encoding analysis, which is not described. Option B involves automated network-based detection. Option C focuses on shortened URLs, which are not present here.

ECIH emphasizes that while automated defenses are important, human verification remains critical, especially for targeted phishing attacks that bypass technical controls. Therefore, Option D correctly identifies the detection approach used.

The team implemented out-of-band communication by establishing communication mechanisms independent of the potentially affected email infrastructure. ECIH preparation activities stress the importance of reliable incident reporting and alternate communication channels because primary communication systems may become unavailable, compromised, filtered, or monitored during an incident. A dedicated VoIP line and SMS-based reporting mechanism allow employees to notify the incident response team even when organizational email cannot be trusted or is experiencing disruption. Backup archives protect information but do not solve the communication problem. Phishing-awareness training improves employee recognition of malicious messages but does not provide an alternative reporting path. Email content filtering can reduce malicious email delivery, but it still relies on the same email infrastructure. Therefore, establishing out-of-band communication directly addresses the reporting weakness described.

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

Liam is establishing and maintaining the chain of custody for digital evidence. ECIH forensic-readiness procedures require responders to document evidence from the moment it is identified and collected through every subsequent transfer, examination, storage, and presentation. Exhibit numbers, collector identification, seizure date and time, device descriptions, original locations, photographs, and transfer records provide traceability and demonstrate that evidence has remained controlled. Recording who receives each item next is particularly important because every change in possession must be documented. These procedures protect evidence integrity and support its admissibility during disciplinary, civil, or criminal proceedings. Imaging volatile memory concerns acquisition from active systems, while malware removal would modify the evidence. Endpoint detection software is unrelated to evidence documentation. Liam ' s systematic labeling and transfer recording therefore constitute creation of a chain-of-custody record.

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

Explanation (aligned to IH & R lifecycle):

This question is about triage/validation—determining whether what you see is truly an incident and establishing priority. The most appropriate first move is to use endpoint telemetry and behavioral analytics (A) to validate maliciousness (e.g., suspicious parent/child process chains, token manipulation, credential dumping patterns, anomalous privilege escalation, and data transfer behaviors). This supports fast, evidence-based classification and reduces unnecessary disruption. Option (C) is containment and may be required after validation or for clearly high-confidence cases, but immediately disconnecting multiple endpoints can destroy volatile evidence, break business operations, and reduce your ability to trace lateral movement patterns across hosts. Option (B) is a broad preventive change that can create outage risk and is not a validation method. Option (D) can be helpful, but it is slower and not the primary “detect and validate” action for an internal team facing active anomalies.

A disciplined approach is: validate via behavioral tooling + logs, scope affected endpoints, determine severity, then execute containment proportional to confirmed risk. That sequencing mirrors standard incident handling flow (identify → validate/triage → contain → eradicate → recover → lessons learned). When time matters, the highest-value action is the one that converts ambiguous signals into confident incident classification quickly—behavioral validation does that best.

This incident involves active data exfiltration, which ECIH malware handling guidance identifies as a critical containment priority. When malware is actively transmitting sensitive data, stopping the leak takes precedence over deep analysis.

Option B is correct because using the network traffic analyzer to identify and halt outbound malicious communication immediately prevents further data loss. ECIH stresses that containment actions must first stop harm before eradication and recovery.

Option A supports eradication but does not immediately stop exfiltration. Option C is premature. Option D is unreliable and risks reinfection.

Therefore, halting malicious transmissions is the ideal first step.

By classifying and encrypting customer Personally Identifiable Information (PHI), you are specifically guarding against the risk of Sensitive Data Exposure. This OWASP security risk involves the accidental or unlawful exposure of protected data to unauthorized individuals. Encryption serves as a critical defense mechanism by ensuring that, even if data is accessed without authorization, it remains unintelligible and useless to the attacker without the decryption keys. Data classification further supports this by identifying which data is sensitive and requires such protections, ensuring that appropriate security controls are applied to prevent exposure.