splunk-security_content/docs/_posts/2021-08-24-get-domaintrust_with_powershell_script_block.md

title, excerpt, categories, last_modified_at, toc, toc_label, tags

title	excerpt	categories	last_modified_at	toc	toc_label	tags
Get-DomainTrust with PowerShell Script Block	Domain Trust Discovery	Endpoint	2021-08-24	true		Domain Trust Discovery Discovery Splunk Enterprise Splunk Enterprise Security Splunk Cloud

Try in Splunk Security Cloud{: .btn .btn--success}

Description

The following analytic utilizes PowerShell Script Block Logging (EventCode=4104) to identify suspicious PowerShell execution. Script Block Logging captures the command sent to PowerShell, the full command to be executed. Upon enabling, logs will output to Windows event logs. Dependent upon volume, enable on critical endpoints or all.
This analytic identifies Get-DomainTrust from PowerView in order to gather domain trust information.
During triage, review parallel processes using an EDR product or 4688 events. It will be important to understand the timeline of events around this activity. Review the entire logged PowerShell script block.

• Type: TTP
• Product: Splunk Enterprise, Splunk Enterprise Security, Splunk Cloud
• Datamodel:
• Last Updated: 2021-08-24
• Author: Michael Haag, Splunk
• ID: 89275e7e-0548-11ec-bf75-acde48001122

ATT&CK

ID	Technique	Tactic
T1482	Domain Trust Discovery	Discovery

Search

`powershell` EventCode=4104 Message = "*get-foresttrust*" 
| stats count min(_time) as firstTime max(_time) as lastTime by Message ComputerName User EventCode 
| `security_content_ctime(firstTime)` 
| `security_content_ctime(lastTime)` 
| `get_domaintrust_with_powershell_script_block_filter`

Associated Analytic Story

• Active Directory Discovery

How To Implement

To successfully implement this analytic, you will need to enable PowerShell Script Block Logging on some or all endpoints. Additional setup here https://docs.splunk.com/Documentation/UBA/5.0.4.1/GetDataIn/AddPowerShell#Configure_module_logging_for_PowerShell.

Required field

• _time
• EventCode
• Message
• Path
• OpCode
• ComputerName
• User

Kill Chain Phase

• Reconnaissance

Known False Positives

It is possible certain system management frameworks utilize this command to gather trust information.

RBA

Risk Score	Impact	Confidence	Message
12.0	30	40	Suspicious PowerShell Get-DomainTrust was identified on endpoint ComputerName by user user.

Reference

• http://www.harmj0y.net/blog/redteaming/a-guide-to-attacking-domain-trusts/
• https://docs.splunk.com/Documentation/UBA/5.0.4.1/GetDataIn/AddPowerShell#Configure_module_logging_for_PowerShell.
• https://blog.palantir.com/tampering-with-windows-event-tracing-background-offense-and-defense-4be7ac62ac63
• https://static1.squarespace.com/static/552092d5e4b0661088167e5c/t/59c1814829f18782e24f1fe2/1505853768977/Windows+PowerShell+Logging+Cheat+Sheet+ver+Sept+2017+v2.1.pdf
• https://www.crowdstrike.com/blog/investigating-powershell-command-and-script-logging/

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

• https://media.githubusercontent.com/media/splunk/attack_data/master/datasets/attack_techniques/T1482/discovery/windows-powershell.log

source | version: 1