Try in Splunk Security Cloud

Description

Aside from being used to promote genuine domain controllers, the DSRM (Directory Services Restore Mode) account can be used to persist within a Domain. A DC can be configured to allow the DSRM account to logon & be used in the same way as a local administrator account. This detection is looking for alterations to the behaviour of the account via registry.

  • Type: TTP
  • Product: Splunk Enterprise, Splunk Enterprise Security, Splunk Cloud
  • Datamodel: Endpoint
  • Last Updated: 2022-09-08
  • Author: Dean Luxton
  • ID: 08cb291e-ea77-48e8-a95a-0799319bf056

Annotations

ATT&CK

ATT&CK

ID Technique Tactic
T1098 Account Manipulation Persistence
Kill Chain Phase
  • Actions on Objectives
NIST
  • DE.CM
CIS20
  • CIS 6
CVE 


1
2
3
4
5
6
7
8



| tstats `security_content_summariesonly` min(_time) as _time from datamodel=Endpoint.Registry where Registry.registry_path= "*\\System\\CurrentControlSet\\Control\\Lsa\\DSRMAdminLogonBehavior" Registry.registry_value_data IN ("*1","*2") by Registry.action Registry.registry_path Registry.registry_value_data Registry.registry_value_type Registry.process_guid 
| `drop_dm_object_name(Registry)` 
| join type=outer process_guid [
| tstats `security_content_summariesonly` count FROM datamodel=Endpoint.Processes by Processes.user Processes.process_name Processes.process Processes.dest Processes.parent_process_name Processes.parent_process Processes.process_guid 
| `drop_dm_object_name(Processes)`] 
| table _time action dest user parent_process_name parent_process process_name process process_guid registry_path registry_value_data registry_value_type 
| `windows_ad_dsrm_account_changes_filter`

Macros

The SPL above uses the following Macros:

:information_source: windows_ad_dsrm_account_changes_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
  • Registry.registry_value_data
  • Registry.registry_path
  • Registry.dest
  • Registry.user

How To Implement

To successfully implement this search, you must be ingesting data that records registry activity from your hosts to populate the endpoint data model in the registry node. This is typically populated via endpoint detection-and-response product, such as Carbon Black or endpoint data sources, such as Sysmon. The data used for this search is typically generated via logs that report reads and writes to the registry.

Known False Positives

Disaster recovery events.

Associated Analytic Story

RBA

Risk Score Impact Confidence Message
100.0 100 100 DSRM Account Changes Initiated on $dest$ by $user$

: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: 1