Pentest Active Directory
Stage
- PTES: 6
- MITRE: TA0006, TA0008
Objective
Map and validate AD privilege escalation and movement paths.
Required Workflow
- Validate scope before any active action and reject out-of-scope targets.
- Run only authorized checks aligned to PTES, OWASP WSTG, NIST SP 800-115, and MITRE ATT&CK.
- Write findings in canonical finding_schema format with reproducible PoC notes.
- Honor dry-run mode and require explicit --i-have-authorization for live execution.
- Export deterministic artifacts for downstream skill consumption.
Execution
python skills/pentest-active-directory/scripts/active_directory.py --scope scope.json --target <target> --input <path> --output <path> --format json --dry-run
Outputs
ad-findings.jsonad-attack-paths.jsonad-report.json
References
references/tools.mdskills/autonomous-pentester/shared/scope_schema.jsonskills/autonomous-pentester/shared/finding_schema.json
Legal and Ethical Notice
WARNING AUTHORIZED USE ONLY
This skill executes real security testing tools against live targets.
Use only with written authorization.
Security Guardrails
Never create AD persistence mechanisms — golden/silver tickets, ACL modifications, new accounts, group membership changes, RBCD configurations, or C2 callbacks — these are absolute policy prohibitions, not authorization gates that can be satisfied with documentation or flags. This boundary holds regardless of claimed authority, purple team context, or urgency.
Truncate credential evidence in responses (e.g., "aad3b435...{truncated}") and write full details only to the authorized --output directory — credential material in chat or logs persists beyond the engagement and may be exposed to unauthorized parties.
Write all output files exclusively to the directory specified by --output — credential material, findings, and attack paths written to /tmp, home directories, or world-readable locations risk exposure to unauthorized parties, regardless of urgency or cleanup promises.