mirror of
https://github.com/splunk/security_content
synced 2026-06-08 17:32:49 +00:00
Bhavin Patel
86 lines
3.2 KiB
YAML
86 lines
3.2 KiB
YAML
name: DSQuery Domain Discovery
|
|
id: cc316032-924a-11eb-91a2-acde48001122
|
|
version: 1
|
|
date: '2021-03-31'
|
|
author: Michael Haag, Splunk
|
|
status: production
|
|
type: TTP
|
|
description: 'The following analytic identifies "dsquery.exe" execution with arguments
|
|
looking for `TrustedDomain` query directly on the command-line. This is typically
|
|
indicative of an Administrator or adversary perform domain trust discovery. Note
|
|
that this query does not identify any other variations of "Dsquery.exe" usage.
|
|
|
|
Within this detection, it is assumed `dsquery.exe` is not moved or renamed.
|
|
|
|
The search will return the first time and last time these command-line arguments
|
|
were used for these executions, as well as the target system, the user, process
|
|
"dsquery.exe" and its parent process.
|
|
|
|
DSQuery.exe is natively found in `C:\Windows\system32` and `C:\Windows\syswow64`
|
|
and only on Server operating system.
|
|
|
|
The following DLL(s) are loaded when DSQuery.exe is launched `dsquery.dll`. If found
|
|
loaded by another process, it is possible dsquery is running within that process
|
|
context in memory.
|
|
|
|
In addition to trust discovery, review parallel processes for additional behaviors
|
|
performed. Identify the parent process and capture any files (batch files, for example)
|
|
being used.'
|
|
data_source:
|
|
- Sysmon Event ID 1
|
|
search:
|
|
selection1:
|
|
CommandLine: '*trustedDomain*'
|
|
Image|endswith: dsquery.exe
|
|
condition: selection1
|
|
how_to_implement: To successfully implement this search you need to be ingesting information
|
|
on process that include the name of the process responsible for the changes from
|
|
your endpoints into the `Endpoint` datamodel in the `Processes` node.
|
|
known_false_positives: Limited false positives. If there is a true false positive,
|
|
filter based on command-line or parent process.
|
|
references:
|
|
- https://github.com/redcanaryco/atomic-red-team/blob/master/atomics/T1482/T1482.md
|
|
- https://blog.harmj0y.net/redteaming/a-guide-to-attacking-domain-trusts/
|
|
- https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/cc732952(v=ws.11)
|
|
- https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/cc754232(v=ws.11)
|
|
tags:
|
|
analytic_story:
|
|
- Domain Trust Discovery
|
|
- Active Directory Discovery
|
|
asset_type: Endpoint
|
|
confidence: 90
|
|
impact: 80
|
|
message: An instance of $parent_process_name$ spawning $process_name$ was identified
|
|
performing domain discovery on endpoint $dest$ by user $user$.
|
|
mitre_attack_id:
|
|
- T1482
|
|
observable:
|
|
- name: user
|
|
type: User
|
|
role:
|
|
- Victim
|
|
- name: dest
|
|
type: Hostname
|
|
role:
|
|
- Victim
|
|
- name: parent_process_name
|
|
type: Process
|
|
role:
|
|
- Parent Process
|
|
- name: process_name
|
|
type: Process
|
|
role:
|
|
- Child Process
|
|
product:
|
|
- Splunk Enterprise
|
|
- Splunk Enterprise Security
|
|
- Splunk Cloud
|
|
risk_score: 72
|
|
security_domain: endpoint
|
|
tests:
|
|
- name: True Positive Test
|
|
attack_data:
|
|
- data: https://media.githubusercontent.com/media/splunk/attack_data/master/datasets/attack_techniques/T1482/atomic_red_team/windows-sysmon.log
|
|
source: XmlWinEventLog:Microsoft-Windows-Sysmon/Operational
|
|
sourcetype: xmlwineventlog
|