MITRE ATT&CK is a threat intelligence framework that helps security teams map attack techniques to detection rules.
#1. Develop Custom Detection Rules Based on Attack Techniques (A)
Maps Splunk correlation searches to MITRE ATT&CK techniques to detect adversary behaviors.
Example:
To detect T1078 (Valid Accounts):
index=auth_logs action=failed | stats count by user, src_ip
If an account logs in from anomalous locations, trigger an alert.
#Incorrect Answers:
B: Use it only for reporting after incidents # MITRE ATT&CK should be used proactively for threat detection.
C: Rely solely on vendor-provided threat intelligence # Custom rules tailored to an organization's threat landscape are more effective.
D: Deploy it as a replacement for current detection systems # MITRE ATT&CK complements existing SIEM
/EDR tools, not replaces them.
#Additional Resources:
MITRE ATT&CK & Splunk
Using MITRE ATT&CK in SIEMs

The Risk Framework can be enriched through the Assets & Identities Framework, Risk Factoring, and Annotations , making option A the correct combination.
The Assets & Identities Framework contributes organizational context about entities represented by risk objects. For example, a destination system may be identified as highly critical, or a user may belong to a privileged identity category. That context allows the same underlying behavior to be interpreted differently depending on the entity involved.
Risk Factors provide a mechanism for modifying risk according to contextual conditions. A detection may assign a baseline risk score, while a Risk Factor increases or otherwise adjusts the effective risk when characteristics of the affected user or asset justify higher concern.
Annotations provide structured metadata describing the detection and its security meaning, such as mappings to relevant adversary techniques or other analytical context. This makes accumulated risk more understandable and useful to analysts.
A risk object is the entity receiving risk rather than an enrichment mechanism. Data models provide normalized data structures, and the notable framework concerns analyst-facing security events rather than the complete enrichment set requested here.
Study Guide topics: Risk Framework; Assets & Identities; Risk Factors; annotations; contextual enrichment; risk objects; RBA.

Additional context should be incorporated by adding enriched fields during search execution . A correlation search should return not merely evidence that a detection condition occurred, but sufficient contextual fields for an analyst to understand and triage the resulting finding efficiently.
For example, a detection can enrich results with normalized entity fields such as user, src, dest, asset priority, identity information, process details, authentication attributes, threat-intelligence context, or other fields relevant to the analytic. Those values can then be carried into the notable/finding and used for investigation, drilldowns, risk analysis, and downstream automation.
The dedup command addresses duplicate search results; it does not inherently enrich the notable. Adding indexers improves ingestion and search scalability rather than investigative context. Search-head memory optimization is an infrastructure-performance activity and likewise does not add meaningful fields to a finding.
This principle aligns directly with the supplied course material ' s guidance that, once a detection is known to fire, engineers should ensure that the fields analysts need are present in the detection output .
Study Guide topics: correlation searches, analyst context, field enrichment, actionable findings, CIM fields, Assets & Identities, drilldowns.

Splunk Security Essentials (SSE) is the best fit because it is specifically designed to help security teams explore, organize, and assess security use cases and detection content. A threat-informed defense workflow requires engineers to relate candidate detections to adversary behaviors, and SSE provides security-content views that map detections to the MITRE ATT & CK framework , enabling analysts to identify relevant tactics, techniques, and coverage gaps.
This capability supports a structured use-case development process: determine the adversary behaviors relevant to the organization, review available detections aligned to those behaviors, identify required data sources, and determine where additional detection coverage is needed. The supplied Cybersecurity Defense Engineer material reinforces this use of Splunk Security Essentials by associating it with MITRE ATT & CK analysis and industry-focused ATT & CK visualization.
Enterprise Security is the operational SIEM platform where detections execute, while the Enterprise Security Content Update app distributes security content. A "Supporting add-on for MITRE ATT & CK" is not the primary use-case development application described here.
Study Guide topics: threat-informed defense, Splunk Security Essentials, MITRE ATT & CK mapping, detection coverage, use-case development, security-content analysis.

Effective documentation ensures that security teams canstandardize response procedures, reduce incident response time, and improve compliance.
#1. Visual Workflow Diagrams (B)
Helpsmap out security processesin an easy-to-understand format.
Useful for SOC analysts, engineers, and auditors to understandincident escalation procedures.
Example:
Incident flow diagramsshowing escalation fromTier 1 SOC analysts # Threat hunters # Incident response teams.
#2. Incident Response Playbooks (C)
Definesstep-by-step response actionsfor security incidents.
Standardizes how teams shoulddetect, analyze, contain, and remediate threats.
Example:
ASOAR playbookfor handlingphishing emails(e.g., extract indicators, check sandbox results, quarantine email).
#Incorrect Answers:
A: Detailed event logs# Logs areessential for investigationsbut do not constituteprocess documentation.
D: Customer satisfaction surveys# Not relevant tosecurity process documentation.
#Additional Resources:
NIST Cybersecurity Framework - Incident Response
Splunk SOAR Playbook Documentation