The following analytic identifies the default service name created by KrbRelayUp. Defenders should be aware that attackers could change the hardcoded service name of the KrbRelayUp tool and bypass this detection.
- Type: TTP
- Product: Splunk Enterprise, Splunk Enterprise Security, Splunk Cloud
- Datamodel: Endpoint
- Last Updated: 2022-05-02
- Author: Michael Haag, Splunk
- ID: e40ef542-8241-4419-9af4-6324582ea60a
|T1543.003||Windows Service||Persistence, Privilege Escalation|
Kill Chain Phase
- CIS 3
- CIS 5
- CIS 16
1 2 3 4 5 `wineventlog_system` EventCode=7045 Service_Name IN ("KrbSCM") | stats count min(_time) as firstTime max(_time) as lastTime by EventCode Service_File_Name Service_Name Service_Start_Type Service_Type | `security_content_ctime(firstTime)` | `security_content_ctime(lastTime)` | `windows_krbrelayup_service_creation_filter`
The SPL above uses the following Macros:
Note that windows_krbrelayup_service_creation_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 System Event Logs with 7045 EventCode enabled. The Windows TA is also required.
Known False Positives
False positives should be limited as this is specific to KrbRelayUp based attack. Filter as needed.
Associated Analytic story
|64.0||80||80||A service was created on $dest$, related to KrbRelayUp.|
source | version: 1