Kerberos Authentication Failure Investigation

AuthenticationAttacks Windows Security Kerberos Attack

What This Means

Investigate Kerberos authentication failures including AS-REP Roasting, Kerberoasting, ticket manipulation, and protocol-specific attack patterns in Active Directory environments.

Example Log

Kerberos pre-authentication failed.
Account Name: svc_sql
Failure Code: 0x18
Client Address: ::ffff:10.0.8.99
Pre-Authentication Type: 2

Indicators of Suspicious Activity

How to Investigate

  1. Correlate Events 4768, 4769, and 4771 for a complete Kerberos picture
  2. Identify which accounts are being targeted and their privilege level
  3. Check encryption types in ticket requests for downgrade attempts
  4. Verify targeted accounts require Kerberos pre-authentication
  5. Review SPN assignments for potential Kerberoasting targets
  6. Cross-reference with AD audit logs for recent account or SPN changes

Recommended Mitigations

Scan This Log Instantly

Paste a suspicious log line below and get an instant AI-powered security assessment.

0 / 2000

Need a Full Investigation?

Scan entire log files, detect attack patterns, reconstruct timelines, and generate a full investigation report.

Run Smart Scan

Related Log Types

Related Attack Patterns

Frequently Asked Questions

What are the main Kerberos attack types?
Key attacks: AS-REP Roasting (cracking TGTs for accounts without pre-auth), Kerberoasting (cracking service tickets for accounts with SPNs), Golden Ticket (forging TGTs with krbtgt hash), and Silver Ticket (forging service tickets).
How do I find vulnerable Kerberos accounts?
Audit for: accounts without pre-auth required, accounts with SPNs and weak passwords, the krbtgt account password age, and any delegation configurations that could be abused.
What Kerberos failure codes should I alert on?
Alert on: 0x18 (bad password) in volume, 0x6 (unknown principal) from single IPs, 0x17 encryption type in ticket requests, and Pre-Authentication Type 0 in Event 4768.