executing-active-directory-attack-simulation

name	executing-active-directory-attack-simulation
description	Executes authorized attack simulations against Active Directory environments to identify misconfigurations, weak credentials, dangerous privilege paths, and exploitable trust relationships that could lead to domain compromise. The tester uses BloodHound for attack path analysis, Mimikatz for credential extraction, and Impacket for protocol-level attacks including Kerberoasting, AS-REP Roasting, and delegation abuse. Use when working with executing active directory attack simulation.
domain	cybersecurity
tags	["Active-Directory","BloodHound","Mimikatz","Kerberoasting","domain-compromise"]
subdomain	penetration-testing
version	1.0.0
author	oyi77
license	Apache-2.0
d3fend_techniques	["Application Protocol Command Analysis","Network Isolation","Network Traffic Analysis","Client-server Payload Profiling","Network Traffic Community Deviation"]
nist_csf	["ID.RA-01","ID.RA-06","GV.OV-02","DE.AE-07"]

Executing Active Directory Attack Simulation

Overview

Cybersecurity skill for executing active directory attack simulation. Follows industry best practices and security standards.

When to Use

Trigger phrases:

• "executing active directory attack simulation"

• "Executes authorized attack simulations against Active Directory environments to "

• Assessing the security of an Active Directory domain and forest against common and advanced attack techniques

• Identifying attack paths from low-privilege domain user to Domain Admin using privilege relationship analysis

• Validating that Kerberos security configurations, credential policies, and delegation settings resist known attacks

• Testing detection capabilities of the SOC and EDR tools against Active Directory-specific TTPs

• Evaluating the effectiveness of tiered administration models and privileged access workstations

Do not use without explicit written authorization from the domain owner, against production domain controllers during business hours unless approved, or for testing that could cause account lockouts affecting real users without prior coordination.

When NOT to Use

• When you lack proper authorization for testing
• For production systems without change management
• When the task requires legal or compliance expertise beyond technical scope

Prerequisites

• Written authorization specifying the target AD domain, testing constraints, and any off-limits accounts or systems
• Low-privilege domain user account (minimum starting point) to simulate realistic attacker position
• Testing workstation joined to the domain or network access to domain controllers on ports 88, 135, 139, 389, 445, 636, 3268, 3269
• BloodHound Community Edition or Enterprise with SharpHound/AzureHound collectors
• Impacket toolkit, Mimikatz (or pypykatz), Rubeus, and CrackMapExec installed on the attack platform
• Hashcat or John the Ripper with current wordlists (rockyou.txt, SecLists) for offline credential cracking

Workflow

# Example: IOC detection
import re

IOC_PATTERNS = {
    "ip": r"\b(?:\d{1,3}\.){3}\d{1,3}\b",
    "domain": r"\b[a-z0-9-]+\.[a-z]{2,}\b",
    : ,
    : ,
}

 () -> :
     {k: re.findall(v, text)  k, v  IOC_PATTERNS.items()}