38. Active Directory Attacks and Defence
38.6 BloodHound Attack-Path Analysis
BloodHound graph edges (ideas):
| Edge | Meaning (simple) | Blue action |
|---|---|---|
MemberOf |
User/group nesting | Flatten crazy nesting; remove stale groups |
AdminTo |
Local admin rights on a computer | Least privilege; LAPS; no DA on workstations |
HasSession |
User session on a host (cred theft risk) | Privileged users avoid Tier-2; RDP jump hosts |
GenericAll / WriteDacl |
Dangerous ACL rights on object | ACL reviews; remove unnecessary rights; AdminSDHolder awareness |
ForceChangePassword |
Can reset user password | Limit helpdesk scope; audit 4724 |
Attacker query: "Shortest path to Domain Admins from owned user." Blue query: "Same – then delete edges (rights) until path gone." BloodHound = Red and Blue tool. He khup important aahe.
| Red team (attacker) does | Blue team (defender) detects / stops |
|---|---|
| Imports SharpHound zip; chases path to DA | Monthly Blue BloodHound; ticket to remove AdminTo/GenericAll edges |
Abuses GenericAll on group/user |
ACL change auditing; privileged access workstations; Just-In-Time admin |
Waits for DA HasSession on messy PC |
Block DA on Tier-2; Privileged Access Workstation (PAW) |
Ravindra Bagale's Tip
Students see a red path in the GUI, panic and delete the Domain Admin. Remove the path's edge – don't delete the user. Example: if helpdesk has GenericAll on an OU, shrink those rights. The graph is a map for remediation, not a panic button.
Ravindra Bagale's Tip – मराठी
Students GUI मध्ये red path बघून घाबरून Domain Admin delete करतात. Path चा edge remove करा – user delete नको. Example: helpdesk ला OU वर GenericAll असेल तर rights कमी करा. Graph = remediation साठी map, panic button नाही.
Ravindra Bagale's Tip – हिंदी
Students GUI में red path देखकर घबराकर Domain Admin delete कर देते हैं. Path का edge remove करो – user delete नहीं. Example: helpdesk को OU पर GenericAll हो तो rights कम करो. Graph = remediation के लिए map, panic button नहीं.
Lab
BloodHound madhe query: shortest paths to Domain Admins. Jar path asel (tumhi lab madhe shahrukh la local admin on a server dile asel) tar edge note kara → remove that local admin → re-collect → path gayab? Yes/No screenshot. Path nahi asel tar ek intentional weak edge add (lab only), collect, then fix.
Extended teaching notes
Why this lesson matters
Active Directory is the identity plane for many Indian enterprises. Attack path tools exist so defenders can remove dangerous edges: excessive admin rights, unconstrained delegation, stale accounts.
- Tiered admin model; no daily Domain Admin use.
- LAPS for local admin passwords.
- Monitor for unusual Kerberos / replication behaviour.
- Lab AD only — never against a corporate domain without a signed engagement.
Mini case study
Suppose we are on a purple-team exercise for an Indian mid-size company (sample data). Red notes a technique from this lesson against a lab clone. Blue must show the control that stops it, the log that would have fired, and the ticket that hardens production. That is the standard this course trains you for.
Defender's worksheet (do this today)
- Write the lesson title, date and the exact lab target you are allowed to use.
- List three owned systems (VMs, apps, or cloud accounts) where this lesson applies.
- Run one safe check from the lesson on a lab system only. Paste the command and output.
- Write a two-sentence fix you would give a teammate.
- Name one related public advisory (CERT-In, CISA, NVD, or a vendor bulletin) with its date.
Indian workplace (sample data)
Suppose we are a junior analyst at Infosys, TCS, Wipro or a fintech SOC in Bengaluru/Pune. Turn this lesson into one checklist item with an owner, a due date and a place to store evidence (ticket + screenshot).
Global practice
Compare your notes with OWASP, CIS Benchmarks, NIST CSF/IR guidance or a cloud Well-Architected security question. Write five lines on what overlaps.
Everyday analogy
Explain the risk and the fix to a family member without jargon. If they can repeat the warning, you understand it well enough to teach juniors.
Key terms
- Control: a safeguard (patch, config, process, detection).
- Finding: a weakness backed by evidence.
- Remediation: the fix plus how you verified it.
- Scope: systems you have written permission to touch.
- Least privilege: only the access the task needs.
- Defence in depth: several layers so one failure does not end the story.
Common mistakes
- Skipping written permission "just for a quick scan".
- Practising on hostel, office or public targets without authorisation.
- Collecting tool output without writing the fix.
- Copying attack steps onto production to "verify". Defenders verify with versions, configs and patches.
- Publishing screenshots that contain secrets, cookies or internal hostnames.
Recap
- Evidence, fix, owner, date.
- Own lab only.
- Fix > spectacle.