Free ECCouncil 212-89 Practice Exam with Questions & Answers | Set: 7

James is ensuring network monitoring readiness, an important component of the incident-response preparation phase. ECIH emphasizes establishing sufficient visibility before an incident occurs by configuring security devices to generate appropriate logs and alerts, centralizing event information, and ensuring incident responders understand their monitoring and escalation responsibilities. Reviewing firewall and IDS/IPS logging directly improves the organization ' s ability to recognize abnormal traffic patterns associated with DoS attacks. Centralized logging also allows responders to correlate events from different network devices and determine the scope of suspicious activity more rapidly. Vulnerability scanning focuses on identifying weaknesses rather than establishing monitoring capability. Backup hardening supports recovery, while law-enforcement coordination concerns external escalation. James ' s activities are therefore specifically aimed at preparing the organization ' s network monitoring and detection infrastructure for efficient incident identification and response.

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

This scenario indicates identity compromise in a cloud environment, reflected by unusual API activity. The ECIH Cloud Security Incident Handling module emphasizes that in cloud platforms, identity and access management (IAM) is the primary security boundary. When API misuse is detected, the most urgent action is to invalidate potentially compromised credentials.

Option D is correct because rotating all IAM access keys immediately cuts off the attacker’s ability to continue abusing API access. Reviewing IAM policies for excessive permissions further reduces the attack surface and prevents privilege misuse. ECIH explicitly states that compromised credentials must be revoked before implementing additional detective or preventive controls.

Option A may help limit access but does not address stolen credentials that could still be abused elsewhere. Option B improves future visibility but does not mitigate the active incident. Option C is unrelated, as there is no indication of a DDoS attack.

ECIH guidance prioritizes containment through credential revocation in cloud incidents involving unauthorized API usage. Therefore, rotating IAM keys and reviewing permissions is the most critical immediate mitigation 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.

The vulnerable advanced-search feature has been identified as the active attack vector, so immediate containment requires removing that functionality from exposure. Disabling the feature and reverting to the previously stable version prevents continued exploitation while responders investigate the vulnerability, preserve relevant logs, determine the scope of compromise, and develop a validated remediation. Multi-factor authentication strengthens account security but does not correct a vulnerability in backend search processing. Re-authentication similarly does not prevent exploitation by an already authenticated user or malicious request. Stronger database encryption protects stored information but does not stop application-layer abuse that occurs through vulnerable business logic. ECIH incident handling emphasizes containing the exploited component before eradication and recovery. Therefore, temporarily disabling the vulnerable feature is the most direct and appropriate immediate response.

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

In the described attack, where attackers pose as legitimate access points (APs) by beaconing the WLAN ' s SSID to lure users, the attack is known as an Evil twin AP attack. This type of attack involves setting up a rogue AP with the same SSID as a legitimate wireless access point, making it appear as an authorized network to users. Unsuspecting users may connect to this malicious AP, allowing attackers to intercept sensitive information, conduct man-in-the-middle attacks, or distribute malware. The Evil twin AP attack exploits the trust users have in known SSIDs to compromise their security.

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.

Ping sweeping is a technique used in network reconnaissance to identify which IP addresses in a range are active or live. By sending ICMP echo requests ( " ping " ) to multiple hosts and observing which ones respond, an attacker or, in this case, a red team member like Allan, can determine which systems are up and potentially vulnerable to further exploration or attack. This method is foundational for mapping the network before deploying more targeted exploits or scans.

ISO/IEC 27001 Annex A.16 focuses on information security incident management, including reporting, assessment, response, and learning. The ECIH curriculum aligns closely with these requirements, emphasizing structured procedures and continuous improvement.

Option C is correct because it directly addresses the identified gaps: clear escalation channels, consistent outcome tracking, and incorporation of lessons learned. ECIH stresses that post-incident activities—often overlooked—are essential for improving readiness and preventing recurrence.

Option A supports preparedness but does not address systemic process gaps. Option B improves visibility but not governance. Option D is a technical control unrelated to incident learning and escalation.

Thus, implementing structured incident escalation and post-incident knowledge integration is the priority action for compliance and resilience.

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.

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

Repeated antivirus failures combined with continuing malicious traffic indicate that the malware may have persistent components that cannot be reliably removed through standard cleanup. ECIH eradication principles require restoring a compromised device to a known trusted state when the responder cannot guarantee that malicious components have been eliminated. A factory reset or clean reinstallation of the mobile operating system removes applications, configurations, and persistence mechanisms that may continue surviving conventional antivirus scans. Switching to airplane mode is useful as an immediate containment measure because it interrupts communications, but it does not eradicate malware. Disabling the SIM card similarly affects cellular connectivity while leaving the infection intact, and restricting background refresh has no meaningful effect on deeply embedded malicious software. Therefore, reimaging or reinstalling the mobile operating system is the appropriate eradication step.

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