CyberKit

AS-REP Roasting

Cracking accounts that don't require Kerberos pre-authentication.

What it is

An attack against accounts configured with Kerberos pre-authentication disabled, which lets anyone request an authentication-service reply (AS-REP) containing material encrypted with the account's password key. That reply is then cracked offline to recover the password.

Why it matters

Unlike Kerberoasting it needs no prior authentication, so an attacker who only knows a username can pull crackable material for any pre-auth-disabled account. Hunting for accounts with the 'do not require pre-authentication' flag is a quick, high-value audit.

In practice

During an assessment, the team enumerates accounts with pre-auth disabled, roasts them, and recovers a legacy service password still valid across the domain.

What to look for

  • Accounts with Kerberos pre-authentication disabled.
  • Event 4768 with pre-authentication type 0 for those accounts.
  • One source requesting tickets for several such accounts.

Common mistake

Leaving the setting on for an old app nobody remembers. Find accounts with pre-auth disabled and fix or monitor each one.

Practice it nearby

CyberKit has no tool for this term itself. These are the closest places to practice it.

In the field

Well-known tools where this shows up on the job. They are listed to show the landscape, not as a recommendation.

  • Microsoft Defender for Identity Commercial

    Watches domain controller traffic and events for attacks such as Kerberoasting and DCSync.

  • BloodHound Open source

    Maps attack paths through Active Directory, the same view an attacker builds.

  • Splunk Enterprise Security Commercial

    Where many teams search domain controller logs, such as Kerberos ticket events, for these attacks.

Read next

Sources