ir-playbook-vulnerability-spike skillA
ir-playbook-vulnerability-spike is agent-read markdown (skill) from gensecaihq/wazuh-autopilot: Incident-response playbook (PB-005) for vulnerability spikes — sudden jumps in new CVE findings, the same CVE across many hosts, KEV-listed CVEs on exposed assets, SCA regressions, or exploitation attempts against vulnerable assets; use when Wazuh vulnerability-detector alerts surge (rules 23505, 23506) or web/IDS exploitation alerts (rules 31106, 31152, 86601) hit a known-vulnerable host..
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 — Vulnerability Spike (PB-005) Owned by the **vuln-management** agent; escalates to the incident swarm when exploitation is observed. Severity varies with CVSS, KEV status, exposure and asset criticality. MITRE ATT&CK (exploitation): T1190, T1203, T1210, T1068. Rule IDs are from the stock Wazuh 4.14 ruleset (levels official). Full procedure: `references/playbook.md`. ## 1. Detection signals | Signal | Wazuh rules (level) | Trigger | |---|---|---| | New active vulnerabilities by severity (group `vulnerability-detector`) | rule 23506 (L13, Critical), rule 23505 (L10, High), rule 23504 (L7, Medium), rule 23503 (L5, Low) | spike > 3σ above the 7-day average and ≥ 10 findings | | Vulnerability fixed / cleared | rule 23502 (L3, CVE solved by an update), rule 23507 (L3, vulnerabilities cleared) | use for remediation tracking, **not** as new findings | | CVE without severity yet | rule 23508 (L3, awaiting analysis) | re-check once NVD scores it | | Same CVE on many hosts | vulnerability inventory (`get_wazuh_vulnerabilities`) | CVE on ≥ 20 % of hosts and ≥ 5 hosts | …
Read the whole file at its exact version.
How to install
mdr add gensecaihq/wazuh-autopilot/ir-playbook-vulnerability-spike@v2.1mdr add gensecaihq/wazuh-autopilot/ir-playbook-vulnerability-spike@sha256:b548570c967a9897Pin 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_oqk226alyupi4rso)
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 (7125 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_oqk226alyupi4rso GET https://markdownregistry.com/api/v1/resolve?ref=gensecaihq/wazuh-autopilot/ir-playbook-vulnerability-spike GET https://markdownregistry.com/api/v1/blob/b548570c967a9897cd5f185455aafa1f9cefbb65651eb5a5296187319fec0e45
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.