BiTree
  • Search For Lessons
  • Curriculum
  • Pricing
  • For Educators
  • Become a Tutor
  • About
  • Contact
Log InGet Started

Questions, concerns, bug reports, or suggestions? We read every message, write to us at [email protected].

More ways to reach us →
BiTree

Live coding lessons for aspiring developers and security professionals.

[email protected]

(201) 785-7951

Mon–Fri, 9 AM–5 PM EST

Learn

  • Search For Lessons
  • Curriculum
  • Pricing

Company

  • About
  • For Educators & Schools
  • Become a Tutor
  • Contact Us

Legal

  • Terms of Service
  • Privacy Policy
© 2026 BiTree. All rights reserved.
Curriculum/Cybersecurity/Active Directory and Windows Security/Common AD Attack Techniques
50 minAdvanced

Common AD Attack Techniques

After this lesson, you will be able to: Explain and demonstrate (in a lab) the common AD attacks: Pass-the-Hash, Pass-the-Ticket, Kerberoasting, AS-REP Roasting, and Golden Ticket.

This lesson covers the canonical AD attacks that turn a foothold into domain dominance, mapping each to the authentication flow from the previous lesson, all demonstrated only in a lab you control.

Prerequisites:AD Authentication: Kerberos and NTLM

💡 Authorization first

Run these only in your own lab (Detection Lab, a Windows Server eval VM) or sanctioned platforms (TryHackMe's Attacktive Directory, HackTheBox). These are real attacker techniques.

Pass-the-Hash and Pass-the-Ticket

Pass-the-Hash abuses NTLM: with a stolen NTLM password hash, an attacker authenticates as that user without cracking the password, because NTLM accepts the hash. Pass-the-Ticket abuses Kerberos: a stolen TGT or service ticket is injected into a session to impersonate the user for the ticket's lifetime. Both let an attacker move laterally using credentials they captured (from memory with tools like Mimikatz) without ever knowing the plaintext password.

Kerberoasting and AS-REP Roasting

Kerberoasting: any authenticated user can request service tickets for accounts with a Service Principal Name; those tickets are encrypted with the service account's password hash, so the attacker cracks them offline. Service accounts often have weak, rarely-changed passwords, making this highly effective. AS-REP Roasting targets accounts with Kerberos pre-authentication disabled: the attacker requests an AS-REP and cracks the returned material offline. Both yield credentials without touching the target account directly.

Golden Ticket: total domain compromise

If an attacker steals the krbtgt account's password hash (which signs all TGTs), they can forge a Golden Ticket: a valid TGT for any user, including a fabricated Domain Admin, with an arbitrary lifetime. This is near-total, persistent domain compromise, and it is why protecting domain controllers and rotating the krbtgt key (twice) after a suspected compromise is critical. Related is the Silver Ticket (forging a service ticket using a service account's hash).

Lab: demonstrate the attacks

Lab AD only. Tools like Impacket, Rubeus, and Mimikatz.

  1. 1

    1. In your lab domain, start as a low-privilege user.

  2. 2

    2. Kerberoast: use Impacket's GetUserSPNs or Rubeus to request service tickets, then crack them with hashcat.

  3. 3

    3. AS-REP Roast: find accounts without pre-auth (GetNPUsers) and crack the output.

  4. 4

    4. With a cracked or dumped credential, demonstrate Pass-the-Hash/Pass-the-Ticket lateral movement.

  5. 5

    5. Discuss (and only in a fully owned lab, demonstrate) how a stolen krbtgt hash enables a Golden Ticket. Then move to defenses next lesson.

Quick Check

Why is stealing the krbtgt account hash so catastrophic?

Pick one.

Common mistakes only experienced practitioners catch

Running these outside an owned lab. Assuming strong user passwords protect you while service accounts stay weak (Kerberoasting). Leaving pre-authentication disabled on accounts (AS-REP Roasting). Not protecting domain controllers and the krbtgt account. Treating a single rotation of krbtgt as enough (it must be rotated twice). Forgetting that Pass-the-Hash needs no cracking, so a stolen hash is immediately dangerous.

Sign in and purchase access to unlock this lesson.

Sign in to purchase
←AD Authentication: Kerberos and NTLM
Back to Active Directory and Windows Security
BloodHound and Attack Paths→