mitre-attack-mapping skillA
mitre-attack-mapping is agent-read markdown (skill) from gensecaihq/wazuh-autopilot: Map Wazuh alerts and observed behaviour to MITRE ATT&CK techniques and tactics and record them on the case; use whenever you identify attacker behaviour or see rule.mitre data..
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
# MITRE ATT&CK Mapping ATT&CK is the shared language between triage, hunting, response and detection engineering. Map precisely: prefer a sub-technique when evidence supports it, otherwise the parent technique. ## Procedure 1. Start with `rule.mitre.id` / `rule.mitre.tactic` from each alert — Wazuh ships these on many rules. Treat them as a hint, not truth: verify against the behaviour. 2. Add techniques for behaviour seen in logs that the rule didn't tag (e.g. a process command line showing discovery commands). 3. Pick the tactic from the context: the same technique can serve multiple tactics (T1078 Valid Accounts: Initial Access, Persistence, Privilege Escalation, Defense Evasion) — record the tactic that fits this case. 4. Assign a numeric confidence per technique: 0.9 confirmed (log evidence of the behaviour), 0.7 likely (strong indicator), 0.4 possible (rule tag only). ## Wazuh rule → technique mappings The first column is taken from the Wazuh 4.14 ruleset's own `<mitre>` tags. The ruleset is not always right: rule 60122 (Windows logon failure, level 5) is tagged T1531 Account Access Removal, which one failed logon isn't. Treat every tag as a hint. …
Read the whole file at its exact version.
How to install
mdr add gensecaihq/wazuh-autopilot/mitre-attack-mapping@v1.1mdr add gensecaihq/wazuh-autopilot/mitre-attack-mapping@sha256:62263969510abbf3Pin 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_mhf2wvrdfhqcwaao)
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 (5139 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_mhf2wvrdfhqcwaao GET https://markdownregistry.com/api/v1/resolve?ref=gensecaihq/wazuh-autopilot/mitre-attack-mapping GET https://markdownregistry.com/api/v1/blob/62263969510abbf35ecf0a5de11072d370a267d049581b3f2ca236fa4dfdc72d
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.