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

This scenario reflects inappropriate resource usage, a category of network and system misuse defined in the ECIH Network Security Incident module. Excessive outbound traffic during non-business hours combined with high CPU and memory utilization indicates unauthorized or improper use of system resources.

Option A is correct because the behavior suggests activities such as cryptomining, data exfiltration, or unauthorized processing. These activities strain system resources and often occur outside normal working hours to avoid detection.

Option B would not necessarily cause sustained resource strain. Option C focuses on physical changes. Option D relates to permission enforcement, not usage behavior.

ECIH categorizes inappropriate usage as a security incident when system resources are misused in ways that violate policy or threaten availability, making Option A correct.

In the context of collecting physical evidence during a cyber forensic investigation, Patrick must consider items like removable media, cables, and publications. These items can contain crucial information related to the crime, such as data storage devices (USB drives, external hard drives), cables connected to potentially relevant devices, and any printed materials that might have information or clues about the incident. Open ports, services, and OS vulnerabilities, DNS information, and published name servers and web application source code, while important in digital forensics, do not constitute physical evidence in the traditional sense.

Explanation (aligned to IH&R best practice):

Insider threats are most effectively reduced by combining least privilege with continuous detection of abnormal behavior. Regular access reviews ensure that users only retain permissions needed for their roles (reducing “privilege creep”), while behavior analytics help detect misuse that still occurs within “legitimate” access. Password rotation (A) is largely hygiene and does not prevent a determined insider who already has authorized access; frequent forced changes can also push unsafe behaviors (writing passwords down, predictable patterns). A strict hierarchy (B) is not practical and does not map to “need-to-know”—seniority is not the right control boundary, job function is. Biometrics (C) strengthens authentication, but the scenario’s problem is not identity uncertainty; it is misuse by a valid insider. The most effective approach is therefore governance + monitoring: (1) define data access baselines, (2) review permissions routinely, (3) alert on suspicious actions such as unusual repository cloning, bulk downloads, access outside normal hours, or atypical branches, and (4) investigate quickly with HR/legal processes. These measures directly address motive-driven misuse by enabling early detection and limiting the blast radius. This aligns with the broader incident handling emphasis on identifying affected systems/data, understanding scope, and improving controls post-incident to prevent recurrence.