Eccouncil 312-39 Dumps - Pass Certified SOC Analyst v2 Exam in First Attempt 2026

This scenario aligns with requirement analysis because the team is defining what intelligence is needed and how it should be collected and used. The analyst has observed a problem (possible DGA-based malware activity) and recognizes gaps in current detection. The next step in a CTI lifecycle is to translate that concern into actionable intelligence requirements: which telemetry sources are necessary (DNS logs, proxy logs, endpoint telemetry, threat intel on DGA families), what questions must be answered (which hosts, what domains, what patterns, what time windows), and what success criteria look like (detection thresholds, false positive tolerance, enrichment needs). This is the ''direction'' phase of CTI, where priorities are set and collection needs are specified to ensure intelligence efforts align to threats that matter. ''Filtering CTI'' would be about reducing noise in collected intelligence or refining feeds after collection. ''Intelligence buy-in'' is stakeholder alignment and program support, not the analytic definition of requirements. ''Automated tool'' is not a CTI lifecycle stage. From a SOC perspective, requirement analysis is critical to turn observations into structured detection and hunting objectives that can be measured and improved.

''Actions on objectives'' is the Cyber Kill Chain phase where the attacker achieves their mission goals---such as data theft, disruption, or destruction. In the scenario, the attacker accessed sensitive client records and exfiltrated them over time, which directly represents the adversary achieving the objective of obtaining confidential data. Delivery and exploitation occur earlier (initial delivery of a payload or credential capture and then exploiting access). Command and control is the stage where compromised systems communicate with attacker infrastructure to receive instructions, which may occur during lateral movement and persistence but is not the final objective. The scenario emphasizes that the breach was discovered after the attacker had already accessed the sensitive repository and exfiltrated data, meaning detection happened at or after the mission impact stage. From a SOC improvement perspective, the lesson is that detections should shift ''left'' in the kill chain: detect credential abuse, anomalous authentication, lateral movement, and suspicious access to file shares before exfiltration. But given where the investigation found the attacker's success, the correct phase is actions on objectives.

Human Intelligence (HUMINT) involves information gathered from people, relationships, and human behavior rather than purely technical artifacts. The scenario describes adversaries using social engineering and pretexting---building trust through conversations and manipulating employees to reveal sensitive information. The analyst is focusing on deception detection and psychological profiling, which are rooted in understanding human intent, influence tactics, and interpersonal manipulation patterns. That aligns with HUMINT, where insights may come from interviews, insider reporting, investigative findings, or controlled engagements that reveal motivations and methods that logs will not show. Threat intelligence feeds and technical threat intelligence primarily provide machine-consumable indicators, malware signatures, infrastructure data, and observed TTPs; they are valuable but not the main lens here because these attackers ''rarely leave digital footprints.'' OSINT is derived from publicly available sources, which can help identify personas or prior campaigns, but the core described intelligence method is interpreting human behavior and social manipulation. From a SOC standpoint, HUMINT-driven insights inform security awareness training, executive protection protocols, identity verification procedures, and ''out-of-band'' validation processes that reduce success of pretexting and business email compromise.

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.

If critical logs are not reaching the SIEM, the most direct root cause is an architectural or configuration failure in the SIEM deployment. A SIEM's detection capability depends on ingesting the right telemetry from key control points (network, endpoint, identity, cloud). Missing firewall, IDS, and endpoint logs creates blind spots that will prevent detections from firing, even for well-known attacks, because the SIEM simply lacks the required evidence. This commonly happens due to misconfigured collectors/agents, incorrect forwarding rules, blocked network paths, wrong ports/protocols, parsing failures, certificate/auth issues, or incomplete onboarding of data sources. While lack of SIEM knowledge can affect tuning and interpretation, it does not explain missing log delivery. Volume-handling issues typically show up as ingestion throttling, dropped events, or delayed indexing after logs are onboarded---not as a complete absence of critical sources. Performance delays can degrade detection timeliness, but again the scenario states the logs are not reaching the SIEM at all. From a SOC engineering standpoint, the first troubleshooting steps are data pipeline validation (connectivity, agent health, message counts), ingestion dashboards, and source-side forwarding verification. Therefore, improper configuration or deployment architecture is the correct reason.