Network Connection via Registration Utility

  1[metadata]
  2creation_date = "2020/02/18"
  3integration = ["endpoint", "windows"]
  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[transform]
 10[[transform.osquery]]
 11label = "Osquery - Retrieve DNS Cache"
 12query = "SELECT * FROM dns_cache"
 13
 14[[transform.osquery]]
 15label = "Osquery - Retrieve All Services"
 16query = "SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services"
 17
 18[[transform.osquery]]
 19label = "Osquery - Retrieve Services Running on User Accounts"
 20query = """
 21SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE
 22NOT (user_account LIKE '%LocalSystem' OR user_account LIKE '%LocalService' OR user_account LIKE '%NetworkService' OR
 23user_account == null)
 24"""
 25
 26[[transform.osquery]]
 27label = "Osquery - Retrieve Service Unsigned Executables with Virustotal Link"
 28query = """
 29SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid,
 30services.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path =
 31authenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != 'trusted'
 32"""
 33
 34
 35[rule]
 36author = ["Elastic"]
 37description = """
 38Identifies the native Windows tools regsvr32.exe, regsvr64.exe, RegSvcs.exe, or RegAsm.exe making a network connection.
 39This may be indicative of an attacker bypassing allowlists or running arbitrary scripts via a signed Microsoft binary.
 40"""
 41false_positives = [
 42    """
 43    Security testing may produce events like this. Activity of this kind performed by non-engineers and ordinary users
 44    is unusual.
 45    """,
 46]
 47from = "now-9m"
 48index = [
 49    "winlogbeat-*",
 50    "logs-endpoint.events.process-*",
 51    "logs-endpoint.events.network-*",
 52    "logs-windows.sysmon_operational-*",
 53]
 54language = "eql"
 55license = "Elastic License v2"
 56name = "Network Connection via Registration Utility"
 57note = """## Triage and analysis
 58
 59### Investigating Network Connection via Registration Utility
 60
 61By examining the specific traits of Windows binaries -- such as process trees, command lines, network connections, registry modifications, and so on -- it's possible to establish a baseline of normal activity. Deviations from this baseline can indicate malicious activity such as masquerading, and deserve further investigation.
 62
 63This rule looks for the execution of `regsvr32.exe`, `RegAsm.exe`, or `RegSvcs.exe` utilities followed by a network connection to an external address. Attackers can abuse utilities to execute malicious files or masquerade as those utilities in order to bypass detections and evade defenses.
 64
 65> **Note**:
 66> This investigation guide uses the [Osquery Markdown Plugin](https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html) introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
 67
 68#### Possible investigation steps
 69
 70- Investigate other alerts associated with the user/host during the past 48 hours.
 71- 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.
 72  - Investigate any abnormal behavior by the subject process such as network connections, registry or file modifications, and any spawned child processes.
 73  - Investigate the file digital signature and process original filename, if suspicious, treat it as potential malware.
 74- Investigate the target host that the signed binary is communicating with.
 75  - Check if the domain is newly registered or unexpected.
 76  - Check the reputation of the domain or IP address.
 77- Assess whether this behavior is prevalent in the environment by looking for similar occurrences across hosts.
 78- Examine the host for derived artifacts that indicate suspicious activities:
 79  - Analyze the process executable using a private sandboxed analysis system.
 80  - Observe and collect information about the following activities in both the sandbox and the alert subject host:
 81    - Attempts to contact external domains and addresses.
 82      - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by filtering by the process' `process.entity_id`.
 83      - Examine the DNS cache for suspicious or anomalous entries.
 84        - $osquery_0
 85    - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related processes in the process tree.
 86    - Examine the host services for suspicious or anomalous entries.
 87      - $osquery_1
 88      - $osquery_2
 89      - $osquery_3
 90  - Retrieve the files' SHA-256 hash values using the PowerShell `Get-FileHash` cmdlet and search for the existence and reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
 91
 92### False positive analysis
 93
 94- If this activity is expected and noisy in your environment, consider adding exceptions — preferably with a combination of destination IP address and command line conditions.
 95
 96### Response and remediation
 97
 98- Initiate the incident response process based on the outcome of the triage.
 99- Isolate the involved host to prevent further post-compromise behavior.
100- If the triage identified malware, search the environment for additional compromised hosts.
101  - Implement temporary network rules, procedures, and segmentation to contain the malware.
102  - Stop suspicious processes.
103  - Immediately block the identified indicators of compromise (IoCs).
104  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
105- Remove and block malicious artifacts identified during triage.
106- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
107- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
108- 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).
109"""
110references = ["https://www.iana.org/assignments/iana-ipv4-special-registry/iana-ipv4-special-registry.xhtml"]
111risk_score = 21
112rule_id = "fb02b8d3-71ee-4af1-bacd-215d23f17efa"
113severity = "low"
114tags = [
115    "Domain: Endpoint",
116    "OS: Windows",
117    "Use Case: Threat Detection",
118    "Tactic: Execution",
119    "Tactic: Defense Evasion",
120    "Resources: Investigation Guide",
121    "Data Source: Elastic Defend",
122    "Data Source: Sysmon",
123]
124type = "eql"
125
126query = '''
127sequence by process.entity_id
128  [process where host.os.type == "windows" and event.type == "start" and
129   process.name : ("regsvr32.exe", "RegAsm.exe", "RegSvcs.exe") and
130   not (
131         (?process.Ext.token.integrity_level_name : "System" or ?winlog.event_data.IntegrityLevel : "System") and
132         (process.parent.name : "msiexec.exe" or process.parent.executable : ("C:\\Program Files (x86)\\*.exe", "C:\\Program Files\\*.exe"))
133       )
134   ]
135  [network where host.os.type == "windows" and process.name : ("regsvr32.exe", "RegAsm.exe", "RegSvcs.exe")  and
136   not cidrmatch(destination.ip, "10.0.0.0/8", "127.0.0.0/8", "169.254.0.0/16", "172.16.0.0/12", "192.0.0.0/24",
137       "192.0.0.0/29", "192.0.0.8/32", "192.0.0.9/32", "192.0.0.10/32", "192.0.0.170/32", "192.0.0.171/32",
138       "192.0.2.0/24", "192.31.196.0/24", "192.52.193.0/24", "192.168.0.0/16", "192.88.99.0/24", "224.0.0.0/4",
139       "100.64.0.0/10", "192.175.48.0/24","198.18.0.0/15", "198.51.100.0/24", "203.0.113.0/24", "240.0.0.0/4", "::1",
140       "FE80::/10", "FF00::/8") and network.protocol != "dns"]
141'''
142
143
144[[rule.threat]]
145framework = "MITRE ATT&CK"
146
147[rule.threat.tactic]
148id = "TA0002"
149name = "Execution"
150reference = "https://attack.mitre.org/tactics/TA0002/"
151[[rule.threat]]
152framework = "MITRE ATT&CK"
153[[rule.threat.technique]]
154id = "T1218"
155name = "System Binary Proxy Execution"
156reference = "https://attack.mitre.org/techniques/T1218/"
157[[rule.threat.technique.subtechnique]]
158id = "T1218.009"
159name = "Regsvcs/Regasm"
160reference = "https://attack.mitre.org/techniques/T1218/009/"
161
162[[rule.threat.technique.subtechnique]]
163id = "T1218.010"
164name = "Regsvr32"
165reference = "https://attack.mitre.org/techniques/T1218/010/"
166
167
168
169[rule.threat.tactic]
170id = "TA0005"
171name = "Defense Evasion"
172reference = "https://attack.mitre.org/tactics/TA0005/"