SAM Database File Access Attempt

Try in Splunk Security Cloud

Description

The following analytic detects attempts to access the SAM, SYSTEM, or SECURITY database files within the windows\system32\config directory using Windows Security EventCode 4663. This detection leverages Windows Security Event logs to identify unauthorized access attempts. Monitoring this activity is crucial as it indicates potential credential access attempts, possibly exploiting vulnerabilities like CVE-2021-36934. If confirmed malicious, an attacker could extract user passwords, leading to unauthorized access, privilege escalation, and further compromise of the system.

• Type: Hunting

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

• Last Updated: 2024-05-22
• Author: Michael Haag, Mauricio Velazco, Splunk
• ID: 57551656-ebdb-11eb-afdf-acde48001122

Annotations

ATT&CK

ATT&CK

ID	Technique	Tactic
T1003.002	Security Account Manager	Credential Access

T1003

OS Credential Dumping

Credential Access

Kill Chain Phase

• Exploitation

NIST

• DE.AE

CIS20

• CIS 10

CVE

Search

`wineventlog_security` (EventCode=4663)  ProcessName!=*\\dllhost.exe ObjectName IN ("*\\Windows\\System32\\config\\SAM*","*\\Windows\\System32\\config\\SYSTEM*","*\\Windows\\System32\\config\\SECURITY*") 
| stats values(AccessList) count by ProcessName ObjectName dest src_user 
| rename ProcessName as process_name 
| `sam_database_file_access_attempt_filter`

Macros

The SPL above uses the following Macros:

• wineventlog_security

sam_database_file_access_attempt_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
• process_name
• Object_Name
• dest
• user

How To Implement

To successfully implement this search, you must ingest Windows Security Event logs and track event code 4663. For 4663, enable "Audit Object Access" in Group Policy. Then check the two boxes listed for both "Success" and "Failure."

Known False Positives

Natively, dllhost.exe will access the files. Every environment will have additional native processes that do as well. Filter by process_name. As an aside, one can remove process_name entirely and add Object_Name=*ShadowCopy*.

Associated Analytic Story

• Credential Dumping
• Graceful Wipe Out Attack
• Rhysida Ransomware

RBA

Risk Score	Impact	Confidence	Message
80.0	80	100	The following process $process_name$ accessed the object $ObjectName$ attempting to gain access to credentials on $dest$ by user $src_user$.

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

• https://www.ultimatewindowssecurity.com/securitylog/encyclopedia/event.aspx?eventID=4663
• https://docs.microsoft.com/en-us/windows/security/threat-protection/auditing/event-4663
• https://msrc.microsoft.com/update-guide/vulnerability/CVE-2021-36934
• https://github.com/GossiTheDog/HiveNightmare
• https://github.com/JumpsecLabs/Guidance-Advice/tree/main/SAM_Permissions
• https://en.wikipedia.org/wiki/Security_Account_Manager

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