Important Eccouncil 312-39 Exam Questions

Answer: D

Explanation:

Capturing and comparing system snapshots before and after suspected compromise is a core method of host integrity monitoring. The goal is to detect unauthorized changes to critical system components such as registry keys, scheduled tasks, services, binaries, configuration files, and security settings. By comparing a known-good baseline snapshot to a suspected-compromised state, analysts can identify what changed, when it changed (with supporting timestamps), and which changes are anomalous relative to expected patching or administrative activity. While this activity can occur within a broader digital forensics investigation, the specific technique described---baseline comparison to detect unauthorized modification---is integrity monitoring. Signature-based detection focuses on matching known indicators (hashes, strings, known patterns) and does not rely on before/after snapshot comparison. Threat intelligence gathering is about collecting and analyzing information on external threats, not directly comparing host states. From a SOC standpoint, integrity monitoring supports rapid scoping and eradication because it highlights persistence and tampering mechanisms that must be removed and can reveal stealth modifications that evade signature scanners. It also supports compliance requirements by demonstrating configuration control and unauthorized-change detection capabilities.

Answer: D

Explanation:

In the context of log storage, a circular buffer is a data structure that uses a single, fixed-size buffer as if it were connected end-to-end. This structure lends itself to buffering streams of data, where the data is written to the buffer and read from it in a potentially non-sequential manner. When the buffer is full, new data is written starting at the beginning of the buffer, and thus 'wraps' around. This is why the method is referred to as 'wrapping'. FIFO (First In, First Out) and LIFO (Last In, First Out) are queueing methods, and non-wrapping implies that the buffer does not overwrite existing data when full.

References:The answer can be verified through EC-Council's SOC Analyst study materials and official courseware, which detail various log storage methods and their characteristics. Additionally, the concept of a circular buffer is a well-known data structure in computer science, often discussed in the context of system design and memory management.

Answer: B

Explanation:

Azure Monitor is the Azure-native platform for collecting, analyzing, and visualizing telemetry across Azure resources, including metrics and logs from infrastructure, applications, and services. For SOC needs, it provides centralized observability: resource metrics, activity logs, diagnostic logs, and integration with log analytics for query and alerting. This supports both performance monitoring and security monitoring by enabling detection of unusual behaviors (unexpected spikes, anomalous access patterns) and providing dashboards and alerting to support rapid response. Azure Firewall is a network security control focused on traffic filtering and policy enforcement; it does not serve as the comprehensive telemetry collection and visualization layer for all Azure resources. Azure Policy focuses on governance and compliance enforcement by evaluating and enforcing resource configuration rules; it's important but not the main telemetry analysis solution. Azure Active Directory is the identity service (now commonly referred to as Entra ID) and is essential for authentication/authorization, but it is not the cross-resource monitoring platform. Since the question emphasizes broad telemetry collection, analysis, and visualization across Azure resources for continuous monitoring, Azure Monitor is the correct service.

Answer: B

Explanation:

This rule is signature-based because it matches a known malicious pattern (a specific string payload) within network traffic. Snort's content keyword searches for an exact sequence of bytes/characters in the packet payload---in this case, a classic SQL injection tautology pattern intended to manipulate application logic. Signature detection is high-confidence when the signature is precise and the payload is strongly associated with malicious intent. In SOC operations, signature-based rules are commonly used for well-known exploit strings, malware beacons, and protocol abuse patterns. The tradeoff is that signatures can be bypassed with encoding, obfuscation, payload variations, or different injection strategies that avoid the exact string. Behavioral/anomaly/statistical methods, by contrast, focus on deviations from baseline or broader behavioral patterns (for example, unusual login rates, uncommon HTTP methods, or atypical data transfer volumes). Here, the detection trigger is explicitly the presence of a known SQL injection payload string, which is the defining characteristic of signature-based detection. The SIEM correlation with failed logins adds context and confidence, but the rule itself is still signature-driven.

Answer: D

Explanation:

This scenario best aligns with Persistence because the attacker established mechanisms to maintain access over time after the initial compromise. The defining evidence is ''unauthorized scheduled tasks executed during off-peak hours'' running obfuscated scripts and connecting to a C2 server. Scheduled tasks and startup mechanisms are classic persistence techniques that allow an adversary to survive reboots, re-establish footholds, and perform recurring actions (beaconing, payload retrieval, credential harvesting) without continuous interactive access. The scenario explicitly states the adversary gained access months ago via compromised VPN credentials (initial intrusion), but what you are observing now is the long-lived foothold and automated re-entry capability. Cleanup would involve covering tracks and removing evidence; while obfuscation and potential log manipulation can be related, the core described behavior is recurring execution and ongoing C2 communication. Search and exfiltration would focus on data discovery and transfer; while network slowdowns could be related to exfiltration, the most direct indicators here are persistence mechanisms enabling continued control. For SOC response, this phase emphasizes removing persistence artifacts, rotating credentials, and validating no alternate footholds remain.