The following analytic identifies a ComputerAccount requesting a Kerberos Ticket. typically, a user account requests a Kerberos ticket. This behavior was identified with KrbUpRelay, but additional Kerberos attacks have exhibited similar behavior.
- Type: TTP
- Product: Splunk Enterprise, Splunk Enterprise Security, Splunk Cloud
- Datamodel: Endpoint
- Last Updated: 2022-04-27
- Author: Michael Haag, Splunk
- ID: fb3b2bb3-75a4-4279-848a-165b42624770
|T1558||Steal or Forge Kerberos Tickets||Credential Access|
Kill Chain Phase
- Actions on Objectives
- CIS 3
- CIS 5
- CIS 16
1 2 3 4 5 `wineventlog_security` EventCode=4768 Account_Name="*$" src_ip!="::1" | stats count min(_time) as firstTime max(_time) as lastTime by dest, subject, action, Supplied_Realm_Name, user, Account_Name, src_ip | `security_content_ctime(firstTime)` | `security_content_ctime(lastTime)` | `windows_computer_account_requesting_kerberos_ticket_filter`
The SPL above uses the following Macros:
Note that windows_computer_account_requesting_kerberos_ticket_filter is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
How To Implement
To successfully implement this search, you need to be ingesting Windows Security Event Logs with 4768 EventCode enabled. The Windows TA is also required.
Known False Positives
It is possible false positives will be present based on third party applications. Filtering may be needed.
Associated Analytic story
|35.0||50||70||A Computer Account requested a Kerberos ticket on $dest$, possibly indicative of Kerberos relay attack.|
source | version: 1