Detect Kerberoasting in Elastic Security
Adversaries may abuse a valid Kerberos ticket-granting ticket (TGT) to request Kerberos ticket-granting service (TGS) tickets for any service principal name (SPN) registered in Active Directory. Portions of these tickets encrypted with RC4 (etype 0x17) use the service account's NTLM hash as the private key, making them vulnerable to offline brute force attacks using tools like Hashcat or John the Ripper. Cracked credentials enable persistence, privilege escalation, and lateral movement via valid domain accounts. Common tooling includes Rubeus, Invoke-Kerberoast (PowerSploit/Empire), Impacket GetUserSPNs.py, SILENTTRINITY, and Brute Ratel C4. Confirmed threat actor usage includes Wizard Spider (Ryuk ransomware campaigns), FIN7, and Indrik Spider.
MITRE ATT&CK
- Tactic
- Credential Access
- Technique
- T1558 Steal or Forge Kerberos Tickets
- Sub-technique
- T1558.003 Kerberoasting
- Canonical reference
- https://attack.mitre.org/techniques/T1558/003/
Elastic Detection Query
sequence by winlog.event_data.TargetUserName, source.ip with maxspan=1h
[authentication where event.code == "4769"
and winlog.event_data.TicketEncryptionType == "0x17"
and not winlog.event_data.TargetUserName like~ "*$"
and not winlog.event_data.ServiceName like~ "*$"
and winlog.event_data.ServiceName != "krbtgt"] with runs=5Detects Kerberoasting by identifying 5 or more RC4-encrypted (etype 0x17) Kerberos TGS ticket requests from the same user and source IP within a 1-hour window. Uses EQL sequence with runs=5 to flag bulk SPN enumeration indicative of automated tooling such as Rubeus, Invoke-Kerberoast (PowerSploit/Empire), or Impacket GetUserSPNs.py. Requires Winlogbeat or Elastic Agent with the Windows integration forwarding Security event logs from domain controllers.
Data Sources
Required Tables
False Positives & Tuning
- Legacy enterprise applications that authenticate to many services using RC4 because the domain has not enforced AES-only Kerberos via Group Policy — validate by confirming whether AES-encrypted TGS requests (etype 0x12/0x11) also occur for the same account during normal operation
- Authorized vulnerability scanners or Active Directory health-check tools (e.g. PingCastle, BloodHound run with legitimate domain credentials) that enumerate SPNs as part of a scheduled assessment — verify against change management or pentest calendar before escalating
- Service accounts used by backup or monitoring software (e.g. Veeam, SolarWinds SAM) that authenticate to numerous server SPNs in quick succession during scheduled backup or polling windows
- Authorized red team or penetration test exercises targeting Kerberos credential theft — cross-reference change management records before escalating
Other platforms for T1558.003
Testing Methodology
Validate this detection against 4 adversary techniques from Atomic Red Team. Each test below lists the behaviour to exercise and the telemetry you should expect to see. Executable commands and cleanup steps are available with Pro.
- Test 1Invoke-Kerberoast via PowerSploit — Bulk Hash Extraction
Expected signal: Domain Controller Security Event ID 4769 for each SPN enumerated with TicketEncryptionType=0x17. Sysmon Event ID 1 on source host: powershell.exe with 'Invoke-Kerberoast' in CommandLine. Sysmon Event ID 3: TCP connection to DC on port 88 (Kerberos). PowerShell ScriptBlock Event ID 4104 with full Invoke-Kerberoast script content (deobfuscated). Sysmon Event ID 11: file creation for kerberoast_hashes.txt.
- Test 2Rubeus Kerberoast — All Roastable Accounts
Expected signal: Domain Controller Security Event ID 4769 for each SPN with TicketEncryptionType=0x17. Sysmon Event ID 1: Rubeus.exe process creation with 'kerberoast' argument. Sysmon Event ID 3: TCP connection to DC on port 88. Sysmon Event ID 11: file creation for rubeus_hashes.txt. Windows Defender may independently generate alerts for Rubeus.exe based on signature detection.
- Test 3Impacket GetUserSPNs — Linux-Based Kerberoasting
Expected signal: Domain Controller Security Event ID 4769 for each SPN with TicketEncryptionType=0x17, IpAddress field contains the Linux host IP. Event ID 4768 (TGT request) from Linux host IP preceding the 4769 events. No Sysmon telemetry (Linux source). DC Security logs capture the full activity. The source IP not matching any domain-joined Windows workstation is a high-fidelity anomaly indicator.
- Test 4Targeted Single-SPN Request via .NET KerberosRequestorSecurityToken
Expected signal: Domain Controller Security Event ID 4769: ServiceName=MSSQLSvc/sql01.corp.local:1433, TicketEncryptionType=0x17 (if target service account supports RC4). Sysmon Event ID 1: powershell.exe with 'KerberosRequestorSecurityToken' in CommandLine. PowerShell ScriptBlock Event ID 4104 with full .NET reflection code. Note: If the target account enforces AES-only encryption, EncryptionType will be 0x12 and detection will not fire on the RC4 rule — the account is not kerberoastable.
References (10)
- https://attack.mitre.org/techniques/T1558/003/
- https://blogs.technet.microsoft.com/motiba/2018/02/23/detecting-kerberoasting-activity-using-azure-security-center/
- https://adsecurity.org/?p=2293
- https://blog.harmj0y.net/powershell/kerberoasting-without-mimikatz/
- https://github.com/GhostPack/Rubeus
- https://github.com/fortra/impacket/blob/master/examples/GetUserSPNs.py
- https://learn.microsoft.com/en-us/windows/security/threat-protection/auditing/event-4769
- https://redsiege.com/kerberoast-slides
- https://github.com/redcanaryco/atomic-red-team/blob/master/atomics/T1558.003/T1558.003.md
- https://www.crowdstrike.com/blog/meet-carbon-spider/
Unlock Pro Content
Get the full detection package for T1558.003 including response playbook, investigation guide, and atomic red team tests.