Group Policy Discovery via Microsoft GPResult Utility

 1[metadata]
 2creation_date = "2023/01/18"
 3integration = ["windows", "endpoint", "system", "m365_defender", "sentinel_one_cloud_funnel"]
 4maturity = "production"
 5updated_date = "2024/10/15"
 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 = """
12Detects the usage of gpresult.exe to query group policy objects. Attackers may query group policy objects during the
13reconnaissance phase after compromising a system to gain a better understanding of the active directory environment and
14possible methods to escalate privileges or move laterally.
15"""
16from = "now-9m"
17index = [
18    "winlogbeat-*",
19    "logs-endpoint.events.process-*",
20    "logs-windows.forwarded*",
21    "logs-windows.sysmon_operational-*",
22    "endgame-*",
23    "logs-system.security*",
24    "logs-m365_defender.event-*",
25    "logs-sentinel_one_cloud_funnel.*",
26]
27language = "eql"
28license = "Elastic License v2"
29name = "Group Policy Discovery via Microsoft GPResult Utility"
30note = """## Triage and analysis
31
32### Investigating Group Policy Discovery via Microsoft GPResult Utility
33
34Group Policy is a Windows feature that allows administrators to manage and configure settings for users and computers in an Active Directory environment. The Microsoft GPResult utility (gpresult.exe) is a command-line tool used to query and display Group Policy Objects (GPOs) applied to a system. Attackers may abuse this utility to gain insights into the active directory environment and identify potential privilege escalation or lateral movement opportunities.
35
36The detection rule 'Group Policy Discovery via Microsoft GPResult Utility' is designed to identify the usage of gpresult.exe with specific arguments ("/z", "/v", "/r", "/x") that are commonly used by adversaries during the reconnaissance phase to perform group policy discovery.
37
38#### Possible investigation steps
39
40- Review the alert details to understand the context of the gpresult.exe usage, such as the user account, system, and time of execution.
41- Identify the user account that performed the action and whether it should perform this kind of action.
42- 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.
43- Investigate other alerts associated with the user/host during the past 48 hours.
44- Investigate any abnormal account behavior, such as command executions, file creations or modifications, and network connections.
45- Inspect the host for suspicious or abnormal behavior in the alert timeframe.
46- Validate the activity is not related to planned patches, updates, network administrator activity, or legitimate software installations.
47- Investigate any abnormal behavior by the parent process, such as network connections, registry or file modifications, and any other spawned child processes.
48
49### False positive analysis
50
51- Discovery activities are not inherently malicious if they occur in isolation. As long as the analyst did not identify suspicious activity related to the user or host, such alerts can be dismissed.
52
53### Response and remediation
54
55- Initiate the incident response process based on the outcome of the triage.
56- Isolate the involved hosts to prevent further post-compromise behavior.
57- 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.
58- Reimage the host operating system or restore the compromised files to clean versions.
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 via 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"""
63risk_score = 21
64rule_id = "94a401ba-4fa2-455c-b7ae-b6e037afc0b7"
65severity = "low"
66tags = [
67    "Domain: Endpoint",
68    "OS: Windows",
69    "Use Case: Threat Detection",
70    "Tactic: Discovery",
71    "Data Source: Elastic Endgame",
72    "Data Source: Elastic Defend",
73    "Data Source: System",
74    "Data Source: Microsoft Defender for Endpoint",
75    "Data Source: Sysmon",
76    "Data Source: SentinelOne",
77]
78timestamp_override = "event.ingested"
79type = "eql"
80
81query = '''
82process where host.os.type == "windows" and event.type == "start" and
83(process.name: "gpresult.exe" or ?process.pe.original_file_name == "gprslt.exe") and process.args: ("/z", "/v", "/r", "/x")
84'''
85
86
87[[rule.threat]]
88framework = "MITRE ATT&CK"
89[[rule.threat.technique]]
90id = "T1615"
91name = "Group Policy Discovery"
92reference = "https://attack.mitre.org/techniques/T1615/"
93
94
95[rule.threat.tactic]
96id = "TA0007"
97name = "Discovery"
98reference = "https://attack.mitre.org/tactics/TA0007/"