How infosecn1nja/ad-attack-defense works
Project Type and Purpose
• This project is a knowledge base focused on the tactics, techniques, and procedures (TTPs) used in Active Directory attacks as well as the guidance to mitigate, detect, and prevent these methods.
• Its purpose is educational and strategic—it maps out the progression of an AD kill chain, listing stages of attacks (Discovery, Privilege Escalation, Defense Evasion, Credential Dumping, Lateral Movement, Persistence) and then provides defensive measures and detection strategies.
Breaking Down the File Structure
• Since the only file is “README.md,” the “architecture” isn’t code-driven but rather is an organized, hierarchical document.
• Despite the lack of multiple directories or source files, the document itself has a clear layer/section structure (for example, headings for each attack phase and sections for tools/resources and defenses).
Main Components
• Attack Stages – Treat each major heading as a separate component:
○ Discovery
○ Privilege Escalation
○ Defense Evasion
○ Credential Dumping
○ Lateral Movement
○ Persistence
• Defensive Measures – This is represented in the “Defense & Detection” section and includes resources, security updates, and best practices.
• External Resources – Indicate that references, cheat sheets, and eBooks supplement the information.
Representing Relationships and Interactions
• Branching where defensive measures are applied—such as how “Defense & Detection” may intercept or mitigate various stages.
• Integration points where the attacker’s tools interface with specific AD vulnerabilities or technologies.
Highlighting Architectural Patterns and Design Principles
• Modularity; each stage is a discrete area but is also interconnected. This hints at the modular nature of attacks and defensive measures.
• Annotations to note external resources or key attack examples (for instance, specific CVEs or documented proof-of-concept attacks like Zerologon or PetitPotam).
Putting It All Together
• Every component is clearly labeled with a brief descriptor; for example, note next to “Privilege Escalation” that it includes methods such as Kerberoasting, DNSAdmins abuse, or exploiting vulnerabilities like Zerologon.
Final Advice
• Detail is key. While the document is vast, do not shy away from capturing as much of the “logical architecture” as possible—even if it means having many components.
Happy diagramming!