Detection: Windows AD SID History Attribute Modified

Updated Date: 2024-05-16 ID: 1155e47d-307f-4247-beab-71071e3a458c Author: Mauricio Velazco, Splunk Type: TTP Product: Splunk Enterprise Security

Description

The following analytic detects modifications to the SID History attribute in Active Directory by leveraging event code 5136. This detection uses logs from the wineventlog_security data source to identify changes to the sIDHistory attribute. Monitoring this activity is crucial as the SID History attribute can be exploited by adversaries to inherit permissions from other accounts, potentially granting unauthorized access. If confirmed malicious, this activity could allow attackers to maintain persistent access and escalate privileges within the domain, posing a significant security risk.

Search

1 `wineventlog_security` EventCode=5136 AttributeLDAPDisplayName=sIDHistory OperationType="%%14674" 
2| stats values(ObjectDN) as ObjectDN by _time, Computer, SubjectUserName, AttributeValue 
3| rename Computer as dest 
4| `windows_ad_sid_history_attribute_modified_filter`

Data Source

Name	Platform	Sourcetype	Source	Supported App
Windows Event Log Security 5136	Windows	`'xmlwineventlog'`	`'XmlWinEventLog:Security'`	N/A

Macros Used

Name	Value
wineventlog_security	`eventtype=wineventlog_security OR Channel=security OR source=XmlWinEventLog:Security`
windows_ad_sid_history_attribute_modified_filter	`search *`

windows_ad_sid_history_attribute_modified_filter is an empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.

Annotations

- MITRE ATT&CK

+ Kill Chain Phases

+ NIST

+ CIS

- Threat Actors

ID	Technique	Tactic
T1134	Access Token Manipulation	Defense Evasion
T1134.005	SID-History Injection	Privilege Escalation

KillChainPhase.EXPLOITAITON

NistCategory.DE_CM

Cis18Value.CIS_10

Blue Mockingbird

FIN6

Default Configuration

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

Setting	Value
Disabled	true
Cron Schedule	`0 * * * *`
Earliest Time	`-70m@m`
Latest Time	`-10m@m`
Schedule Window	`auto`
Creates Notable	Yes
Rule Title	`%name%`
Rule Description	`%description%`
Notable Event Fields	user, dest
Creates Risk Event	True

This configuration file applies to all detections of type TTP. These detections will use Risk Based Alerting and generate Notable Events.

Implementation

To successfully implement this search, you ned to be ingesting eventcode 5136. The Advanced Security Audit policy setting Audit Directory Services Changes within DS Access needs to be enabled. Additionally, a SACL needs to be created for AD objects in order to ingest attribute modifications.

Known False Positives

Domain mergers and migrations may generate large volumes of false positives for this analytic.

Associated Analytic Story

Sneaky Active Directory Persistence Tricks

Risk Based Analytics (RBA)

Risk Message	Risk Score	Impact	Confidence
SID History AD attribute modified by $SubjectUserName$ for $ObjectDN$ on $dest$	56	80	70

The Risk Score is calculated by the following formula: Risk Score = (Impact * Confidence/100). Initial Confidence and Impact is set by the analytic author.

References

Detection Testing

Test Type	Status	Dataset	Source	Sourcetype
Validation	✅ Passing	N/A	N/A	N/A
Unit	✅ Passing	Dataset	`XmlWinEventLog:Security`	`XmlWinEventLog`
Integration	✅ Passing	Dataset	`XmlWinEventLog:Security`	`XmlWinEventLog`

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