Potential Credential Access via Windows Utilities

  1[metadata]
  2creation_date = "2020/11/24"
  3integration = ["endpoint", "windows", "m365_defender", "sentinel_one_cloud_funnel", "system"]
  4maturity = "production"
  5updated_date = "2024/10/17"
  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 = """
 12Identifies the execution of known Windows utilities often abused to dump LSASS memory or the Active Directory database
 13(NTDS.dit) in preparation for credential access.
 14"""
 15from = "now-9m"
 16index = [
 17    "winlogbeat-*",
 18    "logs-endpoint.events.process-*",
 19    "logs-windows.forwarded*",
 20    "logs-windows.sysmon_operational-*",
 21    "endgame-*",
 22    "logs-system.security*",
 23    "logs-m365_defender.event-*",
 24    "logs-sentinel_one_cloud_funnel.*",
 25]
 26language = "eql"
 27license = "Elastic License v2"
 28name = "Potential Credential Access via Windows Utilities"
 29note = """## Triage and analysis
 30
 31### Investigating Potential Credential Access via Windows Utilities
 32
 33Local Security Authority Server Service (LSASS) is a process in Microsoft Windows operating systems that is responsible for enforcing security policy on the system. It verifies users logging on to a Windows computer or server, handles password changes, and creates access tokens.
 34
 35The `Ntds.dit` file is a database that stores Active Directory data, including information about user objects, groups, and group membership.
 36
 37This rule looks for the execution of utilities that can extract credential data from the LSASS memory and Active Directory `Ntds.dit` file.
 38
 39#### Possible investigation steps
 40
 41- Investigate the process 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- Investigate abnormal behaviors observed by the subject process, such as network connections, registry or file modifications, and any spawned child processes.
 43- Investigate other alerts associated with the user/host during the past 48 hours.
 44- Examine the command line to identify what information was targeted.
 45- Identify the target computer and its role in the IT environment.
 46
 47### False positive analysis
 48
 49- This activity is unlikely to happen legitimately. Any activity that triggered the alert and is not inherently malicious must be monitored by the security team.
 50
 51### Response and remediation
 52
 53- Initiate the incident response process based on the outcome of the triage.
 54- If the host is a domain controller (DC):
 55  - Activate your incident response plan for total Active Directory compromise.
 56  - Review the privileges assigned to users that can access the DCs, to ensure that the least privilege principle is being followed and to reduce the attack surface.
 57- Isolate the involved hosts to prevent further post-compromise behavior.
 58- 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.
 59- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
 60- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
 61- 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).
 62"""
 63references = [
 64    "https://lolbas-project.github.io/",
 65    "https://www.elastic.co/security-labs/elastic-protects-against-data-wiper-malware-targeting-ukraine-hermeticwiper",
 66]
 67risk_score = 73
 68rule_id = "00140285-b827-4aee-aa09-8113f58a08f3"
 69severity = "high"
 70tags = [
 71    "Domain: Endpoint",
 72    "OS: Windows",
 73    "Use Case: Threat Detection",
 74    "Tactic: Credential Access",
 75    "Tactic: Defense Evasion",
 76    "Resources: Investigation Guide",
 77    "Data Source: Elastic Endgame",
 78    "Data Source: Elastic Defend",
 79    "Data Source: System",
 80    "Data Source: Microsoft Defender for Endpoint",
 81    "Data Source: SentinelOne",
 82    "Data Source: Sysmon",
 83]
 84timestamp_override = "event.ingested"
 85type = "eql"
 86
 87query = '''
 88process where host.os.type == "windows" and event.type == "start" and
 89(
 90  (
 91    (?process.pe.original_file_name : "procdump" or process.name : "procdump.exe") and process.args : "-ma"
 92  ) or
 93  (
 94    process.name : "ProcessDump.exe" and not process.parent.executable regex~ """C:\\Program Files( \(x86\))?\\Cisco Systems\\.*"""
 95  ) or
 96  (
 97    (?process.pe.original_file_name : "WriteMiniDump.exe" or process.name : "WriteMiniDump.exe") and
 98      not process.parent.executable regex~ """C:\\Program Files( \(x86\))?\\Steam\\.*"""
 99  ) or
100  (
101    (?process.pe.original_file_name : "RUNDLL32.EXE" or process.name : "RUNDLL32.exe") and
102      (process.args : "MiniDump*" or process.command_line : "*comsvcs.dll*#24*")
103  ) or
104  (
105    (?process.pe.original_file_name : "RdrLeakDiag.exe" or process.name : "RdrLeakDiag.exe") and
106      process.args : "/fullmemdmp"
107  ) or
108  (
109    (?process.pe.original_file_name : "SqlDumper.exe" or process.name : "SqlDumper.exe") and
110      process.args : "0x01100*") or
111  (
112    (?process.pe.original_file_name : "TTTracer.exe" or process.name : "TTTracer.exe") and
113      process.args : "-dumpFull" and process.args : "-attach") or
114  (
115    (?process.pe.original_file_name : "ntdsutil.exe" or process.name : "ntdsutil.exe") and
116      process.args : "create*full*") or
117  (
118    (?process.pe.original_file_name : "diskshadow.exe" or process.name : "diskshadow.exe") and process.args : "/s")
119)
120'''
121
122
123[[rule.threat]]
124framework = "MITRE ATT&CK"
125[[rule.threat.technique]]
126id = "T1003"
127name = "OS Credential Dumping"
128reference = "https://attack.mitre.org/techniques/T1003/"
129[[rule.threat.technique.subtechnique]]
130id = "T1003.001"
131name = "LSASS Memory"
132reference = "https://attack.mitre.org/techniques/T1003/001/"
133
134[[rule.threat.technique.subtechnique]]
135id = "T1003.003"
136name = "NTDS"
137reference = "https://attack.mitre.org/techniques/T1003/003/"
138
139
140
141[rule.threat.tactic]
142id = "TA0006"
143name = "Credential Access"
144reference = "https://attack.mitre.org/tactics/TA0006/"
145[[rule.threat]]
146framework = "MITRE ATT&CK"
147[[rule.threat.technique]]
148id = "T1218"
149name = "System Binary Proxy Execution"
150reference = "https://attack.mitre.org/techniques/T1218/"
151[[rule.threat.technique.subtechnique]]
152id = "T1218.011"
153name = "Rundll32"
154reference = "https://attack.mitre.org/techniques/T1218/011/"
155
156
157
158[rule.threat.tactic]
159id = "TA0005"
160name = "Defense Evasion"
161reference = "https://attack.mitre.org/tactics/TA0005/"