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

The port scanning technique that involves resetting the TCP connection between the client and server abruptly before the completion of the three-way handshake, thereby leaving the connection half-open, is known as a Stealth scan (also referred to as a SYN scan). This technique allows the scanner to inquire about the status of a port without establishing a full TCP connection, making the scan less detectible to intrusion detection systems and less likely to be logged by the target. It ' s a method used to discreetly discover open ports on a target machine without establishing a full connection that would be visible in logs.

This incident demonstrates a document-based web malware delivery mechanism, specifically leveraging remotely hosted Rich Text Format (RTF) injection, which is explicitly discussed in ECIH web and malware handling modules. RTF documents can reference external objects or templates, allowing malicious payloads to be fetched dynamically when the document is opened—without requiring macros or user interaction.

Option A is correct because the behavior described aligns precisely with remote template injection. The absence of macros, the silent external connections, and the use of structural document elements are classic indicators of RTF-based malware delivery. ECIH highlights this as a high-risk technique because it bypasses traditional macro-based detection and user warning mechanisms.

Option B is incorrect because the payload was delivered via downloaded documents, not email impersonation of social contacts. Option C references browser extensions and PDFs, which are not involved. Option D describes lateral spread, not initial delivery.

ECIH emphasizes that modern web-based attacks increasingly abuse trusted document formats and remote object references to evade controls. Understanding these techniques enables responders to improve document sanitization, outbound traffic monitoring, and content disarm and reconstruction (CDR) controls.

Centralized logging and monitoring is a core best practice in cloud incident detection and response under ECIH. Cloud environments are distributed and dynamic, making visibility a major challenge.

Option C is correct because aggregating logs from multiple cloud platforms enables correlation, faster detection, and effective incident triage. ECIH emphasizes centralized visibility as essential for identifying cross-platform threats.

Options A and D are limited in scope. Option B does not address cloud-specific risks.

Centralized logging and monitoring provide the visibility required to detect, correlate, investigate, and respond to incidents spanning multiple cloud environments. ECIH cloud incident handling emphasizes that distributed infrastructure creates fragmented telemetry across identity services, workloads, storage, applications, APIs, and network controls. Aggregating those logs into a centralized monitoring or SIEM platform enables responders to identify anomalies that might otherwise appear unrelated when viewed within individual services. Penetration testing only selected critical assets provides useful assurance but leaves other components outside continuous visibility. Physical office security does not address most cloud-specific attack vectors. Moving to a single cloud provider is also not inherently a security best practice and does not eliminate configuration, identity, or monitoring risks. Centralized visibility therefore provides the strongest foundation for detecting cross-cloud incidents and coordinating an effective response.

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

Rate limiting is the most appropriate response because the attack specifically abuses the application ' s search functionality by generating excessive requests. Application-layer DoS attacks consume server-side resources through apparently legitimate HTTP requests rather than simply overwhelming network bandwidth. Applying rate limits to the affected search endpoint restricts how frequently individual clients or sessions can invoke the resource-intensive function, directly reducing the attack ' s effectiveness while allowing legitimate users to continue accessing the application. Moving to a higher-bandwidth host does not address exhaustion of application resources. Clearing the cache is unrelated to controlling malicious request volume. IP-based blocking can help in limited situations, but distributed attackers can rotate or spoof sources, making static blocking less effective. Rate limiting therefore provides targeted containment of the abused application functionality.

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

Michael ' s activities, which involve analyzing file systems, slack spaces, and metadata of storage units to find hidden malware and evidence of malice, indicate that he is handling a storage-related cloud security incident. This type of incident pertains to unauthorized access, alteration, or exfiltration of data stored in cloud environments. By focusing on the storage aspects such as file systems and metadata, Michael is looking for signs of compromise that specifically affect the storage of data, which is indicative of a storage-related security incident in the cloud.

Reducing the success rate of SQL injection attacks is focused on minimizing vulnerabilities within the application ' s database interactions, rather than the broader server or network services. SQL injection prevention techniques typically involve input validation, parameterized queries, and the use of stored procedures, rather than changes to the network or server configuration.

A) Closing unnecessary application services and ports on the server is a general security best practice to reduce the attack surface but does not directly impact the success rate of SQL injection attacks. This action limits access to potential vulnerabilities across the network and server but doesn ' t address the specific ways SQL injection exploits input handling within web applications.

B) Automatically locking a user account after a predefined number of invalid login attempts within a predefined interval can help mitigate brute force attacks but has no direct effect on preventing SQL injection, which exploits code vulnerabilities to manipulate database queries.

C) Constraining legitimate characters to exclude special characters and D) Limiting the length of the input field are both direct methods to reduce the risk of SQL injection. They focus on controlling user input, which is the vector through which SQL injection attacks are launched. By restricting special characters that could be used in SQL commands and limiting input lengths, an application can reduce the potential for malicious input to form a part of SQL queries executed by the backend database.

The organization is addressing legal escalation and investigation support. After technical containment and initial notification, the incident response team compiles evidence describing the timeline, malicious infrastructure, email artifacts, fraud details, and financial impact and provides it to a government cybercrime agency. ECIH post-incident and recovery activities include maintaining documentation, preserving evidence, coordinating with legal personnel, and cooperating with appropriate law-enforcement or regulatory authorities when incidents involve fraud or other criminal activity. Data redundancy concerns backup and availability planning, while server reconfiguration and endpoint protection are technical remediation measures. Neither explains forwarding a structured evidentiary report to investigators. The purpose of this action is to facilitate criminal investigation, evidence correlation, possible attribution, and potential recovery of losses. Therefore, legal escalation and investigation support is the correct recovery-process component.

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

Obfuscation is a technique used to make data or code difficult to understand. It is often employed by attackers to conceal the true intent of their code or communications, making it harder for security professionals, automated tools, and others to analyze or detect malicious activity. Obfuscation can involve the use of ambiguous or misleading language, as well as more technical methods such as encoding, encryption, or the use of nonsensical variable names in source code to hide its true functionality.

The EC-Council Incident Handler (ECIH) curriculum emphasizes Identity and Access Management (IAM) as a foundational control in cloud security. In cloud environments, shared credentials and lack of role-based restrictions significantly increase the risk of misuse, unauthorized access, and privilege abuse.

The scenario clearly identifies two major violations: credential reuse across departments and absence of role-specific restrictions. ECIH highlights that cloud best practices require enforcing strict user access control using the Principle of Least Privilege (PoLP) and role-based access control (RBAC). Each user—including third-party contractors—must have unique credentials with clearly defined permissions aligned strictly with their job responsibilities.

Credential isolation ensures accountability and traceability, enabling effective logging, auditing, and forensic investigation. Without unique user tracking, organizations cannot accurately attribute actions, which weakens incident response and compliance efforts.

Option B (data anonymization) relates to data privacy but does not address access misuse. Option C (vulnerability scanning of mobile apps) addresses application security, not identity misuse. Option D (SSL encryption) protects data in transit but does not prevent unauthorized credential reuse or excessive access rights.

ECIH strongly recommends implementing multi-factor authentication (MFA), enforcing strong IAM policies, restricting third-party access, and continuously monitoring privileged accounts in cloud environments. Therefore, enforcement of strict user access control and credential isolation is the most appropriate preventive measure.