Try in Splunk Security Cloud

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.

  • Type: TTP

  • Product: Splunk Enterprise, Splunk Enterprise Security, Splunk Cloud

  • Last Updated: 2024-05-16
  • Author: Mauricio Velazco, Splunk
  • ID: 1155e47d-307f-4247-beab-71071e3a458c

Annotations

ATT&CK

ATT&CK

ID Technique Tactic
T1134 Access Token Manipulation Defense Evasion, Privilege Escalation
T1134.005 SID-History Injection Defense Evasion, Privilege Escalation
Kill Chain Phase
  • Exploitation
NIST
  • DE.CM
CIS20
  • CIS 10
CVE 


1
2
3
4



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

Macros

The SPL above uses the following Macros:

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

Required fields

List of fields required to use this analytic.

  • _time
  • EventCode
  • AttributeLDAPDisplayName
  • OperationType=
  • ObjectDN
  • Computer
  • SubjectUserName
  • AttributeValue

How To Implement

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

RBA

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

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

Reference

Test Dataset

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 | version: 2