Menu

Individual skill

compliance-mapping

0upvotes

A high-level conceptual mapping from Active Directory attack techniques to the compliance controls they touch. Kerberoasting relates to authentication and logging, so it brushes ENS op.acc.5 / op.exp.8, NIS2 Art.21(2)(h), DORA RTS Art.9 / Art.21. Use this when a reader wants to understand which regulatory control an AD finding relates to, or to add an orientation note to a technical finding. This is a conceptual, orientative mapping only; it is NOT an auditor-defensible, curated, ID-by-ID control matrix. Covers ENS (op.acc.*, op.exp.*), NIS2 (Directive 2022/2555 Art.21), and DORA (RTS 2024/1774).

skills/compliance-mapping/SKILL.md

Read pinned source

Source commit 73efec51207f6f740cb398e1c490e5edd60c1113

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Not checked yet
Last checked
Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
216
Repository last updated
Aug 24, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# AD Technique → Compliance Control (Conceptual Mapping)

> **Disclaimer, read first.** This is a *conceptual, orientative* mapping. It shows, at a
> high level, which family of controls an AD attack technique relates to, so a practitioner
> can point a finding in the right regulatory direction. **It is not an auditor-defensible
> control matrix.** A defensible mapping (one an auditor accepts, cross-referenced ID by ID
> to the exact control text, scoped to your organization's applicability statement, with
> evidence per control) is a curated product, not something you infer from a technique name.
> ADscan (free and source-available) produces that curated, ID-by-ID matrix as part of its
> report. Use this skill to orient a finding; do not present it to an auditor as compliance
> evidence.

## How to read this
Back to top