analyzing-active-directory-acl-abuse

analyzing-active-directory-acl-abuse is a skill for Claude Code from mukul975/Anthropic-Cybersecurity-Skills. It costs 36 tokens per session (992 once invoked), scanned A, original, Apache-2.0.

A procedure for finding dangerous permission settings in Active Directory, Microsoft’s system for managing Windows users, computers, and groups. It checks access rules for rights such as full control, permission changes, or ownership changes.

In plain words
What is it for?
Investigating incidents, hunting for threats, validating security controls, and identifying risky Active Directory permissions with Python and LDAP.
Why use it?
It reveals attack paths where ordinary accounts can control sensitive users, groups, domain controllers, or policy objects because of incorrect permissions.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the cybersecurity-skills plugin — 56 skills shipped together

Good fit Investigating incidents, hunting for threats, validating security controls, and identifying risky Active Directory permissions with Python and LDAP.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/mukul975/anthropic-cybersecurity-skills/analyzing-active-directory-acl-abuse
About the project

Anthropic Cybersecurity Skills is a library of structured cybersecurity procedures for AI agents, covering security domains and mappings to established security frameworks. It is for authorized security analysis, penetration testing, incident response, research, defense, and education across compatible AI platforms. The catalogue entries package parts of this library as agent skills, instructions, or a plugin.

mukul975/Anthropic-Cybersecurity-Skills · 32,631 stars · on GitHub · mahipal.engineer

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill analyzing-active-directory-acl-abuse
Clone the repo
git clone --depth 1 https://github.com/mukul975/Anthropic-Cybersecurity-Skills

Made for: Claude Code.

Or install cybersecurity-skills, the plugin that ships this one along with the rest of its 56 skills.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for analyzing-active-directory-acl-abuse

README.md
[![agentmods](https://agentmods.dev/badge/skills/mukul975/anthropic-cybersecurity-skills/analyzing-active-directory-acl-abuse/github.svg)](https://agentmods.dev/skills/mukul975/anthropic-cybersecurity-skills/analyzing-active-directory-acl-abuse)
Your own site
<a href="https://agentmods.dev/skills/mukul975/anthropic-cybersecurity-skills/analyzing-active-directory-acl-abuse"><img src="https://agentmods.dev/badge/skills/mukul975/anthropic-cybersecurity-skills/analyzing-active-directory-acl-abuse/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for analyzing-active-directory-acl-abuse

Your own site · 80×15
<a href="https://agentmods.dev/skills/mukul975/anthropic-cybersecurity-skills/analyzing-active-directory-acl-abuse"><img src="https://agentmods.dev/badge/skills/mukul975/anthropic-cybersecurity-skills/analyzing-active-directory-acl-abuse.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 36 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 992 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • Socket warn 6 Apr 2026
  • Snyk pass 6 Apr 2026
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 1 finding, up to high

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • high YARA Match · line 34
    YARA rule matched a hack tool or exploit indicator (offensive tools, reconnaissance, privilege escalation, or exploit frameworks).
    Fix: Remove offensive tool references and exploit code. Legitimate agent skills should not contain penetration testing tools, exploit frameworks, or reconnaissance utilities.
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00036 $0.00992
Opus 5 $0.00018 $0.00496
Sonnet 5 $0.00007 $0.00198
Haiku 4.5 $0.00004 $0.00099

Measured 12d ago against content hash e72ab21e752e, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

analyzing-active-directory-acl-abuse scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.

The scan reads SKILL.md. This mod also ships 1 executable file (scripts/agent.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

Copies of this mod

8 near-identical copies found in the catalogue:

skills/analyzing-active-directory-acl-abuse/SKILL.md · 91 lines

How it starts

The opening of the file, as written. The whole thing — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Analyzing Active Directory ACL Abuse

Overview

Active Directory Access Control Lists (ACLs) define permissions on AD objects through Discretionary Access Control Lists (DACLs) containing Access Control Entries (ACEs). Misconfigured ACEs can grant non-privileged users dangerous permissions such as GenericAll (full control), WriteDACL (modify permissions), WriteOwner (take ownership), and GenericWrite (modify attributes) on sensitive objects like Domain Admins groups, domain controllers, or GPOs.

This skill uses the ldap3 Python library to connect to a Domain Controller, query objects with their nTSecurityDescriptor attribute, parse the binary security descriptor into SDDL (Security Descriptor Definition Language) format, and identify ACEs that grant dangerous permissions to non-administrative principals. These misconfigurations are the basis for ACL-based attack paths discovered by tools like BloodHound.

When to Use

  • When investigating security incidents that require analyzing active directory acl abuse
  • When building detection rules or threat hunting queries for this domain
  • When SOC analysts need structured procedures for this analysis type
  • When validating security monitoring coverage for related attack techniques

Prerequisites

  • Python 3.9 or later with ldap3 library (pip install ldap3)
  • Domain user credentials with read access to AD objects
  • Network connectivity to Domain Controller on port 389 (LDAP) or 636 (LDAPS)
  • Understanding of Active Directory security model and SDDL format

Steps

  1. Connect to Domain Controller: Establish an LDAP connection using ldap3 with NTLM or simple authentication. Use LDAPS (port 636) for encrypted connections in production.

  2. Query target objects: Search the target OU or entire domain for objects including users, groups, computers, and OUs. Request the nTSecurityDescriptor, distinguishedName, objectClass, and sAMAccountName attributes.

  3. Parse security descriptors: Convert the binary nTSecurityDescriptor into its SDDL string representation. Parse each ACE in the DACL to extract the trustee SID, access mask, and ACE type (allow/deny).

Read the full file on GitHub · 91 lines

Files

What ships with it

3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 12d ago First seen · 91 lines · 36 tokens per session scan A e72ab21e752e

Subscribe to this mod's changes

analyzing-active-directory-acl-abuse is a skill published in the GitHub repository mukul975/Anthropic-Cybersecurity-Skills (32,631 stars, last pushed 12d ago), licensed Apache-2.0. It adds 36 tokens to every session and 992 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories