GitHub Repo

Detection: Investigate Pass the Ticket Attempts

REMOVED DETECTION

This detection has been removed from the Splunk Threat Research content library and is no longer maintained or supported.

Reason: As of Splunk Enterprise Security version 8.0, Splunk Enterprise Security no longer supports Investigations. As such, all Investigations have been deprecated in ES Content Update.

Removed in version: 5.2.0

If you have any questions or concerns, please reach out to us at research@splunk.com.

Updated Date: 2026-05-13 ID: 990007ad-d798-4b29-ab2f-f0034144c937 Author: Patrick Bareiss, Splunk Type: Investigation Product: Splunk Enterprise Security

Description

This search hunts for dumped kerberos ticket from LSASS memory.

1`wineventlog_security` EventCode=4768 OR EventCode=4769 
2| rex field=user "(?<new_user>[^\@]+)" 
3| stats count BY new_user, dest, EventCode 
4| stats max(count) AS max_count sum(count) AS sum_count BY new_user, dest
5| search dest=$dest$ 
6| where sum_count/max_count!=2 
7| rename new_user AS user

Data Source

No data sources specified for this detection.

Macros Used

Name Value
wineventlog_security eventtype="wineventlog_security" OR Channel="security" OR source="XmlWinEventLog:Security" OR source="WinEventLog:Security"

Annotations

- MITRE ATT&CK
+ Kill Chain Phases
+ NIST
+ CIS
- Threat Actors
ID Technique Tactic

Default Configuration

This detection is configured by default in Splunk Enterprise Security to run with the following settings:

Setting Value
Disabled true
Cron Schedule N/A
Earliest Time N/A
Latest Time N/A
Schedule Window N/A
Creates Finding (Notable) No
Creates Intermediate Finding (Risk Event) No

Implementation

To successfully implement this search you need to be ingesting windows security logs. This search uses an input macro named wineventlog_security. We strongly recommend that you specify your environment-specific configurations (index, source, sourcetype, etc.) for Windows Security logs. Replace the macro definition with configurations for your Splunk environment. The search also uses a post-filter macro designed to filter out known false positives.

Known False Positives

Associated Analytic Story

Detection Testing

Test Type Status Dataset Source Sourcetype
Validation Not Applicable N/A N/A N/A
Unit Not Applicable N/A N/A N/A
Integration Not Applicable N/A N/A N/A

Replay any dataset to Splunk Enterprise by using our replay.py tool or the UI. Alternatively you can replay a dataset into a Splunk Attack Range

Source: GitHub |

Version: 2