{
 "schema_version": 1,
 "generated": "2026-10-20",
 "id": "adscanpro-claude-ad--map-ad-findings-to-compliance-controls",
 "repo": "ADScanPro/Claude-AD",
 "repo_url": "https://github.com/ADScanPro/Claude-AD",
 "repo_slug": "adscanpro-claude-ad",
 "title": "Map AD findings to DORA, NIS2 and ENS controls",
 "page_title": "How to map AD findings to DORA, NIS2 and ENS controls with Claude AD",
 "summary": "Use the compliance-mapping skill to tie each technique you tested to a control family for an audit report.",
 "who": "A security consultant or compliance lead who needs to write up an internal AD assessment for an organization under DORA, NIS2 or ENS.",
 "problem": "Technical findings like Kerberoasting or ESC misconfigurations do not map cleanly to the control language an auditor expects.",
 "outcome": "A findings table where each technique is linked to a conceptual control family in DORA, NIS2 or ENS, ready for review.",
 "steps": [
  "Install the plugin with `/plugin marketplace add ADScanPro/Claude-AD` and `/plugin install claude-ad@claude-ad`.",
  "List the techniques confirmed during the engagement, such as Kerberoasting or ADCS findings.",
  "Ask Claude to apply the compliance-mapping skill to each technique for DORA, NIS2 and ENS.",
  "Check each mapping against the control text your auditor uses before submitting.",
  "Add the mapped findings and their fixes to the report."
 ],
 "agent_prompt": "Using the Claude-AD repo (ADScanPro/Claude-AD), apply the compliance-mapping skill to these confirmed techniques from the authorized assessment: <technique-list>. Expected output is a table mapping each technique to a conceptual DORA, NIS2 or ENS control family. Verify that each mapping is labeled conceptual and confirmed against the auditor's own control catalog.",
 "agents": [
  "claude-code"
 ],
 "difficulty": "Intermediate",
 "time": "30 minutes",
 "basis": "readme",
 "caveat": "The mappings are conceptual and do not replace a formal control assessment by your auditor.",
 "category": "Security and science",
 "tags": [
  "Security and science"
 ],
 "lang": "",
 "requirements": [
  "Claude Code installed",
  "Written authorization to test the target domain (your own lab, a contracted engagement, or a CTF)",
  "The standard tools the plugin drives (netexec, impacket, certipy, bloodyAD, BloodHound CE) available to you for the engagement"
 ],
 "risk": "dual-use",
 "seen_in_the_wild": false,
 "mentioned_publicly": false,
 "risks": [],
 "best": false,
 "score": 0.7,
 "evidence": [],
 "url": "https://dedupedai.com/use-cases/adscanpro-claude-ad/map-ad-findings-to-compliance-controls/",
 "md": "https://dedupedai.com/use-cases/adscanpro-claude-ad/map-ad-findings-to-compliance-controls/index.md",
 "disclaimer": "Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked \"Seen in the wild\", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email hello@dedupedai.com and we will look at it promptly.",
 "api": "https://dedupedai.com/api/v1/usecases/adscanpro-claude-ad--map-ad-findings-to-compliance-controls.json",
 "api_version": "v1"
}