compliance-mapping skillA
compliance-mapping is agent-read markdown (skill) from gensecaihq/wazuh-autopilot: Map incidents, control checks and SCA results to ISO 27001:2022, PCI DSS v4.0.1, NIST SP 800-53r5 and CIS Controls v8.1 and write auditor-ready evidence statements; use for compliance checks, audit questions, or incidents on regulated assets..
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
# Compliance Mapping Translate security evidence into control language auditors accept. You report status and gaps; you don't certify compliance. ## Tools | Need | Tool | |---|---| | Framework check | `run_compliance_check(framework="PCI-DSS", agent_id=...)`; `framework` is one of PCI-DSS, HIPAA, SOX, GDPR, NIST, ISO27001; omit `agent_id` for the whole environment | | CIS benchmark / SCA results per agent | `get_sca_policy_checks(agent_id)` | | ISO 27001 posture | `get_iso27001_dashboard` | | ISO 27001 gaps | `get_iso27001_gap_analysis` | | One ISO control | `get_iso27001_control_detail(control_id="A.8.16")` | | Alerts tagged to ISO controls | `get_iso27001_alerts` | ### Wazuh compliance tags Stock Wazuh rules declare compliance mappings as groups in the ruleset (`pci_dss_10.2.4`, `gdpr_IV_32.2`, `hipaa_164.312.b`, `nist_800_53_AC.7`, `tsc_CC6.1`, `gpg13_7.1`). In alerts Wazuh emits them as arrays: `rule.pci_dss`, `rule.gdpr`, `rule.hipaa`, `rule.nist_800_53`, `rule.tsc`, `rule.gpg13`. For example, rule 5712 (sshd brute force) carries PCI DSS 10.2.4 / 10.2.5 / 11.4, NIST 800-53 AC.7 / AU.14 / SI.4, HIPAA 164.312.b and TSC CC6.1 / CC6.8 / CC7.2 / CC7.3. …
Read the whole file at its exact version.
How to install
mdr add gensecaihq/wazuh-autopilot/compliance-mapping@v1.1mdr add gensecaihq/wazuh-autopilot/compliance-mapping@sha256:978ecdee5017fc1dPin 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_e6355ezlpqbqcxuh)
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 (4920 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_e6355ezlpqbqcxuh GET https://markdownregistry.com/api/v1/resolve?ref=gensecaihq/wazuh-autopilot/compliance-mapping GET https://markdownregistry.com/api/v1/blob/978ecdee5017fc1d99875d423d3c227b44338cfa66f7610aba83378d968352be
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.
More from gensecaihq/wazuh-autopilot
Every file in gensecaihq/wazuh-autopilot