implementing-soar-playbook-for-phishing
Automate phishing incident response using Splunk SOAR REST API to create containers, add artifacts, and trigger playbooks
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-14
- Stars
- ★ 13
- Forks
- 2
01 前言 Front Matter
- name
- implementing-soar-playbook-for-phishing
- tags
- [ "soar", "splunk-phantom", "phishing", "incident-response" ]
- author
- mahipal
- domain
- cybersecurity
- source
- https://github.com/mukul975/Anthropic-Cybersecurity-Skills
- license
- Apache-2.0
- version
- 1.0
- nist_csf
- [ "DE.CM-01", "RS.MA-01", "GV.OV-01", "DE.AE-02" ]
- subdomain
- security-operations
- description
- Automate phishing incident response using Splunk SOAR REST API to create containers, add artifacts, and trigger playbooks
- mitre_attack
- [ "T1078", "T1190", "T1059", "T1566", "T1598" ]
- source_commit
- 04450304b12645cb2b974ab96d28c0664758a88d
02 资源文件 3
- 许可证LICENSE11.0 KB
- 参考文档references/api-reference.md2.5 KB
- 脚本scripts/agent.py8.6 KB
03 SKILL.md 正文
Implementing SOAR Playbook for Phishing
Overview
This skill implements a phishing incident response workflow using the Splunk SOAR (formerly Phantom) REST API. When a suspected phishing email is reported, the agent parses email headers and body, creates a SOAR container representing the incident, attaches artifacts containing indicators of compromise (sender address, URLs, IP addresses, file hashes), triggers an automated investigation playbook, and polls for action results.
Splunk SOAR orchestrates and automates security operations through playbooks that chain together investigative and response actions. The REST API at /rest/container, /rest/artifact, and /rest/playbook_run enables programmatic incident creation and automation triggering from external tools, email gateways, and SIEM alerts.
When to Use
- When deploying or configuring implementing soar playbook for phishing capabilities in your environment
- When establishing security controls aligned to compliance requirements
- When building or improving security architecture for this domain
- When conducting security assessments that require this implementation
Prerequisites
- Python 3.9 or later with
requestsandemailmodules - Splunk SOAR instance (Cloud or On-Premises) with REST API access
- SOAR API token with permissions to create containers and trigger playbooks
- Network connectivity to SOAR instance on port 443
- A configured phishing investigation playbook in SOAR
Steps
-
Parse the phishing email: Read the email file (.eml format) and extract headers including From, To, Subject, Reply-To, Return-Path, Received, Message-ID, X-Mailer, and authentication results (SPF, DKIM, DMARC). Extract URLs and IP addresses from the email body.
-
Authenticate to SOAR REST API: Use the API token in the
ph-auth-tokenheader to authenticate all REST API requests to the SOAR instance. -
Create a container: POST to
/rest/containerwith the incident label, name, description, severity, and status. The container represents the phishing incident and receives a container ID in the response. -
Add email header artifacts: POST to
/rest/artifactwithcontainer_idand CEF (Common Event Format) fields containing sender address (fromAddress), recipient (toAddress), subject, originating IP (sourceAddress), and Message-ID. Setrun_automationto False for all but the last artifact. -
Add URL artifacts: For each URL extracted from the email body, create an artifact with CEF field
requestURLand typeurl. These artifacts feed into URL reputation checks in the playbook. -
Trigger the playbook: POST to
/rest/playbook_runwith the playbook ID or name and the container ID. This initiates the automated investigation workflow. -
Poll action results: GET
/rest/action_runfiltered by container ID to monitor playbook progress. Poll until all actions reach a terminal state (success, failed, or cancelled). -
Compile response report: Aggregate playbook action results into a summary report with verdicts from URL reputation, domain reputation, IP geolocation, and email header analysis.
Expected Output
{
"incident": {
"container_id": 1542,
"status": "new",
"severity": "high",
"artifacts_created": 5
},
"playbook": {
"name": "phishing_investigate",
"run_id": 892,
"status": "success",
"actions_completed": 8
},
"verdict": "malicious",
"indicators": {
"sender_domain_reputation": "malicious",
"urls_flagged": 2,
"spf_result": "fail",
"dkim_result": "fail"
}
}
04 同仓库更多 Skills
openai--sentry--sentry
Use when the user asks to inspect Sentry issues or events, summarize recent production errors, or pull basic Sentry health data via the Sentry API; perform read-only queries with the bundled script and require `SENTRY_AUTH_TOKEN`.
ito-basket-compare
Compare Itô prediction-market baskets against a user's knowledge base, portfolio notes, financial context, watchlist, or research thesis. Use for read-only basket comparison and gap analysis without investment advice or live trading.
implementing-network-traffic-baselining
Build network traffic baselines from NetFlow/IPFIX data using Python pandas for statistical analysis, z-score anomaly detection, and hourly/daily traffic pattern profiling
detecting-evasion-techniques-in-endpoint-logs
Detects defense evasion techniques used by adversaries in endpoint logs including log tampering, timestomping, process injection, and security tool disabling. Use when investigating suspicious endpoint behavior, building detection rules for evasion tactics, or conducting threat hunting for stealthy adversary activity. Activates for requests involving evasion detection, defense evasion analysis, log tampering detection, or MITRE ATT&CK TA0005.
implementing-microsegmentation-with-guardicore
Implementing microsegmentation using Akamai Guardicore Segmentation to map application dependencies, create granular network policies, visualize east-west traffic flows, and enforce least-privilege communication between workloads across data centers and cloud.
ramdisk-tmpfs-patterns
暂无简介