What problem does it solve?
Manually triaging reported phishing emails is slow and inconsistent. This Skill automates the full incident response workflow: parsing a suspicious .eml file, creating a SOAR container, attaching IOC artifacts, and triggering an investigation playbook through the Splunk SOAR REST API.
Core Features & Use Cases
- Email Parsing: Extracts headers (From, To, Subject, Return-Path, Message-ID), authentication results (SPF, DKIM, DMARC), URLs, and IP addresses from .eml files.
- SOAR Container & Artifact Creation: POSTs to /rest/container and /rest/artifact with CEF fields such as fromAddress, sourceAddress, and requestURL, controlling run_automation timing.
- Playbook Orchestration & Monitoring: Triggers playbooks via /rest/playbook_run and polls /rest/action_run until all actions reach a terminal state, then compiles a verdict report.
- Use Case: A security analyst receives a reported phishing email, hands the .eml file to the agent, and receives a container ID, playbook run status, and a malicious/benign verdict with flagged indicators.
Quick Start
Parse the attached suspicious-email.eml file, create a Splunk SOAR container with its indicators as artifacts, trigger the phishing_investigate playbook, and report the final verdict.