Credential Acquisition via Registry Hive Dumping

  1[metadata]
  2creation_date = "2020/11/23"
  3integration = ["endpoint", "windows", "system", "m365_defender", "sentinel_one_cloud_funnel", "crowdstrike"]
  4maturity = "production"
  5updated_date = "2024/11/02"
  6min_stack_version = "8.14.0"
  7min_stack_comments = "Breaking change at 8.14.0 for the Windows Integration."
  8
  9[rule]
 10author = ["Elastic"]
 11description = "Identifies attempts to export a registry hive which may contain credentials using the Windows reg.exe tool."
 12from = "now-9m"
 13index = [
 14    "winlogbeat-*",
 15    "logs-endpoint.events.process-*",
 16    "logs-windows.forwarded*",
 17    "logs-windows.sysmon_operational-*",
 18    "endgame-*",
 19    "logs-system.security*",
 20    "logs-m365_defender.event-*",
 21    "logs-sentinel_one_cloud_funnel.*",
 22    "logs-crowdstrike.fdr*",
 23]
 24language = "eql"
 25license = "Elastic License v2"
 26name = "Credential Acquisition via Registry Hive Dumping"
 27note = """## Triage and analysis
 28
 29### Investigating Credential Acquisition via Registry Hive Dumping
 30
 31Dumping registry hives is a common way to access credential information as some hives store credential material.
 32
 33For example, the SAM hive stores locally cached credentials (SAM Secrets), and the SECURITY hive stores domain cached credentials (LSA secrets).
 34
 35Dumping these hives in combination with the SYSTEM hive enables the attacker to decrypt these secrets.
 36
 37This rule identifies the usage of `reg.exe` to dump SECURITY and/or SAM hives, which potentially indicates the compromise of the credentials stored in the host.
 38
 39#### Possible investigation steps
 40
 41- Investigate the script execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
 42- Identify the user account that performed the action and whether it should perform this kind of action.
 43- Contact the account owner and confirm whether they are aware of this activity.
 44- Investigate other alerts associated with the user/host during the past 48 hours.
 45- Investigate if the credential material was exfiltrated or processed locally by other tools.
 46- Investigate potentially compromised accounts. Analysts can do this by searching for login events (e.g., 4624) to the target host.
 47
 48### False positive analysis
 49
 50- Administrators can export registry hives for backup purposes using command line tools like `reg.exe`. Check whether the user is legitamitely performing this kind of activity.
 51
 52### Related rules
 53
 54- Registry Hive File Creation via SMB - a4c7473a-5cb4-4bc1-9d06-e4a75adbc494
 55
 56### Response and remediation
 57
 58- Initiate the incident response process based on the outcome of the triage.
 59- Isolate the involved hosts to prevent further post-compromise behavior.
 60- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
 61- Reimage the host operating system and restore compromised files to clean versions.
 62- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
 63- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
 64- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
 65"""
 66references = [
 67    "https://medium.com/threatpunter/detecting-attempts-to-steal-passwords-from-the-registry-7512674487f8",
 68    "https://www.elastic.co/security-labs/detect-credential-access",
 69]
 70risk_score = 73
 71rule_id = "a7e7bfa3-088e-4f13-b29e-3986e0e756b8"
 72severity = "high"
 73tags = [
 74    "Domain: Endpoint",
 75    "OS: Windows",
 76    "Use Case: Threat Detection",
 77    "Tactic: Credential Access",
 78    "Resources: Investigation Guide",
 79    "Data Source: Elastic Endgame",
 80    "Data Source: Elastic Defend",
 81    "Data Source: System",
 82    "Data Source: Microsoft Defender for Endpoint",
 83    "Data Source: SentinelOne",
 84    "Data Source: Sysmon",
 85    "Data Source: Crowdstrike",
 86]
 87timestamp_override = "event.ingested"
 88type = "eql"
 89
 90query = '''
 91process where host.os.type == "windows" and event.type == "start" and
 92 (?process.pe.original_file_name == "reg.exe" or process.name : "reg.exe") and
 93 process.args : ("save", "export") and
 94 process.args : ("hklm\\sam", "hklm\\security")
 95'''
 96
 97
 98[[rule.threat]]
 99framework = "MITRE ATT&CK"
100[[rule.threat.technique]]
101id = "T1003"
102name = "OS Credential Dumping"
103reference = "https://attack.mitre.org/techniques/T1003/"
104[[rule.threat.technique.subtechnique]]
105id = "T1003.002"
106name = "Security Account Manager"
107reference = "https://attack.mitre.org/techniques/T1003/002/"
108
109[[rule.threat.technique.subtechnique]]
110id = "T1003.004"
111name = "LSA Secrets"
112reference = "https://attack.mitre.org/techniques/T1003/004/"
113
114
115
116[rule.threat.tactic]
117id = "TA0006"
118name = "Credential Access"
119reference = "https://attack.mitre.org/tactics/TA0006/"