312-39 Exam Dumps : Certified SOC Analyst (CSA v2)

MITRE D3FEND is specifically designed to map defensive techniques to offensive adversary behaviors and tactics. In SOC and detection engineering, it provides a structured defensive ontology: you can identify an adversary technique (credential access, privilege escalation, defense evasion) and then select defensive countermeasures such as credential hardening, process isolation, monitoring/behavior analytics, and access control enforcement. The scenario describes a framework that “systematically maps defensive techniques to known adversarial tactics,” which aligns directly with D3FEND’s purpose. The other options are broader governance or maturity models rather than a defensive technique-mapping framework. Systems Security Engineering CMM and Cybersecurity Capability Maturity Models focus on process maturity and organizational capability development, not on mapping defensive controls to adversary behavior at a technique level. NIST CSF 2.0 is a high-level cybersecurity risk management framework organized around functions (govern, identify, protect, detect, respond, recover); it guides program structure but does not provide the same granular defensive technique taxonomy. Therefore, MITRE D3FEND is the correct choice for a structured, technique-to-defense mapping approach.

This activity is Recovery because it focuses on restoring systems and business operations to a normal, trusted state after the threat has been contained and eradicated. Restoring encrypted data from backups, rebuilding compromised workstations, and re-enabling network access are all recovery tasks. The key objective in recovery is to return services safely while ensuring the environment is clean and stable—hence validation steps before reconnecting systems to production networks. Containment would have occurred earlier and would include isolating affected VLANs/hosts and stopping spread. Eradication would include removing ransomware artifacts, closing persistence, patching vulnerabilities (which the scenario says has already been done), and ensuring the attacker cannot regain access. Post-incident activities occur after recovery and include lessons learned, reporting, process improvements, and control updates. From a SOC operational standpoint, recovery is often the most resource-intensive phase because it requires coordination between security, IT operations, application owners, and business units to restore systems, verify integrity, and monitor for reinfection. Because the scenario is explicitly about restore/rebuild and safe return-to-service, the correct phase is recovery.

SIEM use case management is the process of defining, implementing, tuning, and governing detection scenarios (use cases) so that alerts align with the organization’s real risks and operating environment. High false positives often result from generic rules not tuned to local baselines, missing context, or unclear detection objectives. Use case management addresses this by documenting what threat is being detected, what data sources are required, what “good” vs “bad” looks like, expected false positives, severity mapping, and response actions. It includes iterative tuning: refining thresholds, adding allowlists, improving parsing/normalization, and validating detections against real activity and test cases. “Security analytics” is a broad term that includes detections and analysis, but the question emphasizes a structured process of defining scenarios aligned to risk—use case management. IT compliance is focused on meeting regulatory requirements, not reducing alert noise through scenario design. Log forensics is deep investigation of events after the fact, not the proactive engineering process of improving detection quality. From a SOC viewpoint, mature use case management is a primary lever for reducing alert fatigue while increasing true-positive detection.