CyberKit

Kerberos Pre-Authentication

The Kerberos step proving a client knows the password before a TGT.

What it is

A Kerberos mechanism in which the client proves knowledge of the account password (typically by encrypting a timestamp) before the KDC issues a ticket-granting ticket. It exists to stop attackers from requesting crackable authentication material for arbitrary accounts.

Why it matters

When pre-authentication is disabled on an account, anyone can request roastable material for it without credentials, so its state directly governs AS-REP roasting exposure. Failed pre-auth events are also a useful signal of password-guessing activity.

In practice

An auditor lists every account with pre-authentication disabled and prioritizes them, knowing each is open to AS-REP roasting.

What to look for

  • Event 4771 failures, which point to wrong passwords during pre-auth.
  • Accounts with pre-auth disabled.
  • Spikes in pre-auth failures across many accounts.

Common mistake

Turning it off for compatibility. That makes the account roastable without any password.

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

  • AS-REP Roasting: Cracking accounts that don't require Kerberos pre-authentication.
  • Kerberoasting: Cracking service-account passwords from requested Kerberos tickets offline.
  • Brute-Force Attack: Systematically guessing credentials until one works.

Sources