implementing-soar-playbook-for-phishing
Automates phishing incident response by calling the Splunk SOAR (Phantom)
v1.03 установки+3 за 7 дней36,3 тыс. ЗвездыApache-2.0синхронизировано 12 часов назад
Установка
Ещё нет NotHoly CLI? Сначала установите её.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install mukul975/implementing-soar-playbook-for-phishingПишет в ~/.notholy/skills после проверки подписи и SHA-256.
ПодписьПодписано, ed25519
Пакет1a298d8b…102186fd
1a298d8b3dcb…76e9102186fd4 файла · 9.1 KBПроверкаСредний2 замечания
- Исполняемый скрипт в составе навыкаscripts/agent.py
- Ссылки на внешние домены
Источникgithub.com/mukul975/Anthropic-Cybersecurity-Skills/tree/main/skills/implementing-soar-playbook-for-phishing@54a7988
Эта запись еще не переведена на русский, поэтому показан текст на другом языке: English.
На странице
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"
}
}Файлы этой версии
references/12.5 KB
- api-reference.md2.5 KB
scripts/18.6 KB
- agent.py8.6 KB
- LICENSE11.0 KB
- SKILL.md4.8 KB
Права
| Право | Заявлено | Найдено проверкой |
|---|---|---|
| Читает файлы | Нет | Нет |
| Пишет файлы | Да | Да |
| Выполняет команды shell | Да | Да |
| Ходит в сеть | Да | Да |
| Использует коннекторы | Нет | Нет |
| Управляет браузером | Нет | Нет |
Замечания проверки
Проверено 13 нояб. 2026 г.
- СредняяФайл · Исполняемый скрипт в составе навыкаscripts/agent.py
- ИнфоСсылка · Ссылки на внешние домены
Чистая проверка снижает риск, но не доказывает, что пакет безопасен. Читайте то, что ставите.
| Версия | Опубликована | Коммит | SHA-256 | Подпись | Изменение прав |
|---|---|---|---|---|---|
| v1.0 | 13 нояб. 2026 г. | 54a7988 | 1a298d8b | Подписана | – |
Ещё от mukul975
Всё от этого издателя- testing-for-xml-injection-vulnerabilitiesmukul975/testing-for-xml-injection-vulnerabilities5
- testing-for-sensitive-data-exposuremukul975/testing-for-sensitive-data-exposure5
- performing-jwt-none-algorithm-attackmukul975/performing-jwt-none-algorithm-attack5
- detecting-aws-credential-exposure-with-trufflehogmukul975/detecting-aws-credential-exposure-with-trufflehog5
Еще в категории «Социальная инженерия и физическая безопасность»
Вся категория- performing-phishing-simulation-with-gophishmukul975/performing-phishing-simulation-with-gophish4
- social-engineering-techniqueaeondave/social-engineering-technique3
- phishing-techniqueaeondave/phishing-technique3
- performing-red-team-phishing-with-gophishmukul975/performing-red-team-phishing-with-gophish3
- performing-physical-intrusion-assessmentmukul975/performing-physical-intrusion-assessment3
- performing-brand-monitoring-for-impersonationmukul975/performing-brand-monitoring-for-impersonation3
Спрашивайте обо всём, что позволяет ваш скоуп.
Создайте аккаунт, пополните баланс и задайте первый вопрос в чате или в терминале.
- 1/3
Создайте аккаунт
Личный или для компании. Позже можно перейти на аккаунт компании без потери баланса и ключей.
ЛичныйКомпания - 2/3
Пополните баланс
Картой. Оплата за токены, без подписки.
$5.00минимальное пополнение - 3/3
Спрашивайте
В чате, или установите CLI и выполните notholy login в терминале.
$ notholy login