ECCouncil Updated 312-39 Exam Questions and Answers by lisa

Packet filters are a network security control that inspects packet headers (source/destination IP, ports, protocol flags) to allow or block traffic. Their known limitation is that they generally do not inspect encrypted payload content; they can see metadata but not the application-layer data inside TLS/SSL sessions. The scenario describes a solution that “inspects data packets in real time” but struggles with encrypted traffic, which aligns with packet filtering and other header-based inspection approaches. VPN, SSH, and IPsec are encryption technologies/protocols themselves, not the inspection control; they create encrypted tunnels that make payload inspection harder. From a SOC viewpoint, packet filtering is valuable for fast enforcement and reducing attack surface, but it is limited for detecting threats embedded in encrypted sessions. To improve visibility, SOC teams often complement packet filters with TLS termination at controlled points (proxies), endpoint telemetry (process initiating connection), and flow analytics (NetFlow/IPFIX) to detect anomalies in encrypted traffic based on behavior and metadata.

Black hole filtering is a network security measure used to prevent unwanted or malicious traffic from entering a network. It works by directing traffic to a null interface, a non-existent server, or a black hole IP address where the packets are dropped without acknowledgment. This process is typically used to protect against denial-of-service (DoS) attacks, where an overwhelming amount of traffic is sent to a network with the intent to disrupt service.

In the context of a security operations center (SOC), black hole filtering can be an effective strategy for mitigating threats. When a threat is identified, such as a DoS attack, the SOC analyst can configure the network to redirect the suspicious traffic to a black hole, effectively neutralizing the attack by preventing the malicious data packets from reaching their intended target.

 In a push-based log collection mechanism, the system or application actively sends (or “pushes”) log records to a designatedstorage location, which can be either on the local disk or over a network to a remote server. This is in contrast to a pull-based mechanism, where the log records are retrieved (or “pulled”) by the management server from the devices.

The push-based mechanism is often used for real-time monitoring and alerting because it allows for immediate transfer of log data as events occur. This method ensures that log records are consistently and reliably sent to a central repository without the need for a third-party service to request or retrieve them.

Host-based artifacts are the most direct evidence to confirm persistence and recurring execution on an endpoint. The scenario already describes classic host persistence mechanisms: scheduled tasks and registry autorun modifications. To confirm and mitigate, a threat hunter should focus on endpoint-resident artifacts such as: persistence entries (scheduled tasks, Run/RunOnce keys, services, WMI subscriptions), process ancestry (which parent launches the malicious script), file system changes (dropped scripts, DLLs, staged payloads), and security control tampering. These artifacts enable containment and eradication because they point to what must be removed and what must be prevented from re-creating itself after reboot. Network-based artifacts are important for identifying C2 destinations and potential lateral movement, but they won’t fully explain how the malware survives termination. Threat intelligence context can help attribute and match TTPs, but it’s not required to confirm persistence locally. Indicators of Attack are behavior patterns (like scheduled task creation, registry autoruns, process injection) and are valuable conceptually, but the option that best represents the concrete evidence you need to examine and remediate on the endpoint is “host-based artifacts.” In SOC response, you’d combine host artifact removal with credential resets and scoping for similar persistence across endpoints.