The scenario identifies inefficient manual enrichment and investigation workflows as the primary operational problem.
Analysts must repeatedly access Endpoint Detection and Response (EDR), remote-access, and Identity and Access Management (IAM) platforms to collect contextual information about security findings.
Automating initial triage directly addresses this inefficiency by gathering relevant evidence and presenting it within the associated finding.
A SOAR playbook can query integrated security platforms to retrieve endpoint details, account information, authentication activity, network context, and relevant threat-intelligence attributes.
These results can then support faster incident classification, prioritization, and investigation.
Splunk SOAR playbooks are designed to automate analyst workflows through integrated applications and predefined actions.
Splunk Enterprise Security also supports enrichment of findings using asset and identity information.
For example, an analyst investigating a suspicious login could receive the affected user ' s identity attributes, recent authentication history, endpoint status, and associated network observations without manually querying multiple consoles.
Option A introduces vulnerability scanning, which does not directly address the identified workflow bottleneck.
Option C may provide containment but is premature when the primary requirement is gathering context.
Option D improves reporting efficiency rather than initial investigation.
Therefore, automated triage with results presented in the relevant finding is the most effective solution.
Official reference / study topic: Splunk SOAR, Playbooks and Automation Rules for Enterprise Security Findings.
===============
Submit