Detection rules › Splunk
Suspicious Certificate Authentication (Windows Event Log)
Adversaries may steal an AD CA’s root certificate, and forge a certificate for any active user or computer. This use case looks for Kerberos ticket requests with certificate thumbprints.
MITRE ATT&CK coverage
| Tactic | Techniques |
|---|---|
| Persistence | T1556 Modify Authentication Process |
| Defense Impairment | T1556 Modify Authentication Process |
| Credential Access | T1556 Modify Authentication Process |
References
Event coverage
| Provider | Event | Title |
|---|---|---|
| Security-Auditing | Event ID 4768 | A Kerberos authentication ticket (TGT) was requested. |
Rule body yaml
id: '8651.11135'
title: Suspicious Certificate Authentication
description: 'Adversaries may steal an AD CA’s root certificate, and forge a certificate
for any active user or computer. This use case looks for Kerberos ticket requests
with certificate thumbprints. '
logic_format: Splunk
logic: ' `get_endpoint_data` `get_endpoint_data_winevent` (TERM(EventCode=4768) OR
"<EventID>4768<") Certificate_Issuer_Name=* | eval certificate_name=Certificate_Issuer_Name
| table _time, host, user process, process_*, parent_process, parent_process_*,
src_*, dest_*, subject, certificate_* | bin span=1s | stats values(*) as * by _time,
host '
techniques:
- persistence:modify authentication process
technique_id:
- T1556
data_category:
- Windows event logs
references:
- https://www.specterops.io/assets/resources/Certified_Pre-Owned.pdf
Stages and Predicates
Stage 1: search
`get_endpoint_data` `get_endpoint_data_winevent` (TERM(EventCode=4768) OR "<EventID>4768<") Certificate_Issuer_Name=*
Stage 2: eval
| eval certificate_name=Certificate_Issuer_Name
Stage 3: table
| table _time, host, user process, process_*, parent_process, parent_process_*, src_*, dest_*, subject, certificate_*
Stage 4: bucket
| bin span=1s
Stage 5: stats
| stats values(*) as * by _time, host
Indicators
Each row is a field, operator, and value that the rule matches. The corpus column counts how many other rules in the catalog look for the same combination: high numbers point to widely-used, community-vetted indicators. Blank or 1 shows that the indicator is specific to this rule.
| Field | Kind | Values |
|---|---|---|
Certificate_Issuer_Name | eq |
|
EventCode | eq |
|
Search terms
Bare-string tokens in the SPL search body. Splunk matches each token against _raw (the untyped raw event text) anywhere it appears, not against a specific field. These don't surface in the Indicators table because they aren't predicates on a known field.
| Stage | Term |
|---|---|
| 1 | TERM |
| 1 | "<EventID>4768<" |