ir-playbook-data-exfiltration skillA
ir-playbook-data-exfiltration is agent-read markdown (skill) from gensecaihq/wazuh-autopilot: Incident-response playbook for suspected data exfiltration — archive staging, uploads to cloud storage, exfil over C2 or DNS, removable media and exposed cloud buckets; use when Wazuh flags staging or transfer indicators (e.g. rules 92212, 91846, 92038, 81101, 99548) or when volume/destination anomalies are reported. Most volume and DNS detections need custom rules — see section 1..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# IR Playbook — Data Exfiltration Severity **high → critical** depending on data classification and whether transfer is ongoing. Regulated data (PII/PHI/cardholder) can start breach-notification clocks, so record timestamps precisely. Rule IDs are from the stock Wazuh 4.14 ruleset (levels official). Full procedure, forensic commands and notification templates: `references/playbook.md`. ## 1. Detection signals Stock Wazuh coverage for exfiltration is thin: it detects **staging** and some **transfer tooling** on Windows, cloud-provider findings, and USB storage. Volume thresholds and DNS tunnelling need network telemetry plus custom rules. | Technique | Stock Wazuh rules (level) | Needs | |---|---|---| | T1560.001 Archive staging (Windows) | rules 92212 (L14, compression by PowerShell), 92210 (L6, compression in Users\Public), 91846 (L10, PowerShell .NET compression), 91825 (L4), 91821 (L4, archive of a filesystem search) | Sysmon Event ID 11, PowerShell/Operational | | T1567.002 Exfil to cloud storage | rule 92038 (L12, connection to a cloud resource started by a script/binary) | Sysmon Event ID 1 | …
Read the whole file at its exact version.
How to install
mdr add gensecaihq/wazuh-autopilot/ir-playbook-data-exfiltration@v2.1mdr add gensecaihq/wazuh-autopilot/ir-playbook-data-exfiltration@sha256:e96224e408863de3Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_pfgo22i7fetd6boc)
1 badge views in 30 days
Versions
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (8160 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
gensecaihq/wazuh-autopilot · 57 stars · license MIT · pushed 2026-09-24 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_pfgo22i7fetd6boc GET https://markdownregistry.com/api/v1/resolve?ref=gensecaihq/wazuh-autopilot/ir-playbook-data-exfiltration GET https://markdownregistry.com/api/v1/blob/e96224e408863de392c187837e5d537fde6101cfdf419d0ad43a460d49208ea4
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.