Cross-source coverage

T1558.004 / ATT&CK

Steal or Forge Kerberos Tickets: AS-REP Roasting

9 rules across 3 sources.

From MITRE ATT&CK 19.2

Adversaries may reveal credentials of accounts that have disabled Kerberos preauthentication by Password Cracking Kerberos messages.

Preauthentication offers protection against offline Password Cracking. When enabled, a user requesting access to a resource initiates communication with the Domain Controller (DC) by sending an Authentication Server Request (AS-REQ) message with a timestamp that is encrypted with the hash of their password. If and only if the DC is able to successfully decrypt the timestamp with the hash of the user’s password, it will then send an Authentication Server Response (AS-REP) message that contains the Ticket Granting Ticket (TGT) to the user. Part of the AS-REP message is signed with the user’s password.

For each account found without preauthentication, an adversary may send an AS-REQ message without the encrypted timestamp and receive an AS-REP message with TGT data which may be encrypted with an insecure algorithm such as RC4. The recovered encrypted data may be vulnerable to offline Password Cracking attacks similarly to Kerberoasting and expose plaintext credentials.

An account registered to a domain, with or without special privileges, can be abused to list all domain accounts that have preauthentication disabled by utilizing Windows tools like PowerShell with an LDAP filter. Alternatively, the adversary may send an AS-REQ message for each user. If the DC responds without errors, the account does not require preauthentication and the AS-REP message will already contain the encrypted data.

Cracked hashes may enable Persistence, Privilege Escalation, and Lateral Movement via access to Valid Accounts.

Platforms
Windows
Telemetry
WinEventLog:SecurityWinEventLog:Sysmon

How MITRE says to detect it DET0113

Detect AS-REP Roasting Attempts (T1558.004)

Windows Analytic 0316

Detects AS-REP roasting attempts by monitoring for Kerberos AS-REQ/AS-REP authentication patterns where preauthentication is disabled (Event ID 4768 with Pre-Auth Type 0). Correlates these requests with subsequent service ticket activity (Event ID 4769) and anomalies such as requests using weak RC4 encryption (etype 0x17). Excessive enumeration of accounts with 'Do not require Kerberos preauthentication' set in Active Directory is another key detection point.

  • WinEventLog:Security EventCode=4768
  • WinEventLog:Sysmon EventCode=1

splunk/security_content

6 rules
Detection Severity Format
Disabled Kerberos Pre-Authentication Discovery With Get-ADUser Undefined SPL
Disabled Kerberos Pre-Authentication Discovery With PowerView Undefined SPL
Kerberos Pre-Authentication Flag Disabled in UserAccountControl Undefined SPL
Kerberos Pre-Authentication Flag Disabled with PowerShell Undefined SPL
Rubeus Command Line Parameters Undefined SPL
Windows Process With NetExec Command Line Parameters Undefined SPL

elastic/detection-rules

2 rules
Detection Severity Format
Suspicious Kerberos Authentication Ticket Request High Elastic TOML
Kerberos Pre-authentication Disabled for User Medium Elastic TOML

Bert-JanP/Hunting-Queries-Detection-Rules

1 rule
Detection Severity Format
Kerberos attacks Undefined KQL

Detection rules belong to the projects that publish them and remain under their own licenses. This site indexes and links to them; it claims no rights in them.