Threat Intel URL Indicator Match

  1[metadata]
  2creation_date = "2023/05/22"
  3maturity = "production"
  4updated_date = "2024/01/17"
  5min_stack_comments = """
  6Limiting the backport of these rules to the stack version which we are deprecating the Threat Intel Indicator Match
  7general rules.
  8"""
  9min_stack_version = "8.5.0"
 10
 11[transform]
 12[[transform.osquery]]
 13label = "Osquery - Retrieve DNS Cache"
 14query = "SELECT * FROM dns_cache"
 15
 16[[transform.osquery]]
 17label = "Osquery - Retrieve All Services"
 18query = "SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services"
 19
 20[[transform.osquery]]
 21label = "Osquery - Retrieve Services Running on User Accounts"
 22query = """
 23SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE
 24NOT (user_account LIKE '%LocalSystem' OR user_account LIKE '%LocalService' OR user_account LIKE '%NetworkService' OR
 25user_account == null)
 26"""
 27
 28[[transform.osquery]]
 29label = "Osquery - Retrieve Service Unsigned Executables with Virustotal Link"
 30query = """
 31SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid,
 32services.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path =
 33authenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != 'trusted'
 34"""
 35
 36[rule]
 37author = ["Elastic"]
 38description = """
 39This rule is triggered when a URL indicator from the Threat Intel Filebeat module or integrations has a match against an
 40event that contains URL data, like DNS events, network logs, etc.
 41"""
 42from = "now-65m"
 43index = ["auditbeat-*", "endgame-*", "filebeat-*", "logs-*", "packetbeat-*", "winlogbeat-*"]
 44interval = "1h"
 45language = "kuery"
 46license = "Elastic License v2"
 47name = "Threat Intel URL Indicator Match"
 48note = """## Triage and Analysis
 49
 50### Investigating Threat Intel URL Indicator Match
 51
 52Threat Intel indicator match rules allow matching from a local observation, such as an endpoint event that records a file hash with an entry of a file hash stored within the Threat Intel integrations index.
 53
 54Matches are based on threat intelligence data that's been ingested during the last 30 days. Some integrations don't place expiration dates on their threat indicators, so we strongly recommend validating ingested threat indicators and reviewing match results. When reviewing match results, check associated activity to determine whether the event requires additional investigation.
 55
 56This rule is triggered when a URL indicator from the Threat Intel Filebeat module or a threat intelligence integration matches against an event that contains URL data, like DNS events, network logs, etc.
 57
 58> **Note**:
 59> 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.
 60
 61#### Possible investigation steps
 62
 63- Investigate the URL, which can be found in the `threat.indicator.matched.atomic` field:
 64  - Identify the type of malicious activity related to the URL (phishing, malware, etc.).
 65  - Check the reputation of the IP address in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
 66  - Execute a WHOIS lookup to retrieve information about the domain registration and contacts to report abuse.
 67  - If dealing with a phishing incident:
 68    - Contact the user to gain more information around the delivery method, information sent, etc.
 69    - Analyze whether the URL is trying to impersonate a legitimate address. Look for typosquatting, extra or unusual subdomains, or other anomalies that could lure the user.
 70    - Investigate the phishing page to identify which information may have been sent to the attacker by the user.
 71- Identify the process responsible for the connection, and 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- Retrieve the involved process executable and examine the host for derived artifacts that indicate suspicious activities:
 73  - Analyze the process executable using a private sandboxed analysis system.
 74  - Observe and collect information about the following activities in both the sandbox and the alert subject host:
 75    - Attempts to contact external domains and addresses.
 76      - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by filtering by the process' `process.entity_id`.
 77      - Examine the DNS cache for suspicious or anomalous entries.
 78        - $osquery_0
 79    - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related processes in the process tree.
 80    - Examine the host services for suspicious or anomalous entries.
 81      - $osquery_1
 82      - $osquery_2
 83      - $osquery_3
 84- Using the data collected through the analysis, scope users targeted and other machines infected in the environment.
 85
 86### False Positive Analysis
 87
 88- False positives might occur after large and publicly written campaigns if curious employees interact with attacker infrastructure.
 89- Some feeds may include internal or known benign addresses by mistake (e.g., 8.8.8.8, google.com, 127.0.0.1, etc.). Make sure you understand how blocking a specific domain or address might impact the organization or normal system functioning.
 90
 91### Response and Remediation
 92
 93- Initiate the incident response process based on the outcome of the triage.
 94- Isolate the involved host to prevent further post-compromise behavior.
 95- If the triage identified malware, search the environment for additional compromised hosts.
 96  - Implement temporary network rules, procedures, and segmentation to contain the malware.
 97  - Stop suspicious processes.
 98  - Immediately block the identified indicators of compromise (IoCs).
 99  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
100- Consider reporting the address for abuse using the provided contact information.
101- Remove and block malicious artifacts identified during triage.
102- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
103- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
104- 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).
105"""
106references = [
107    "https://www.elastic.co/guide/en/beats/filebeat/current/filebeat-module-threatintel.html",
108    "https://www.elastic.co/guide/en/security/master/es-threat-intel-integrations.html",
109    "https://www.elastic.co/security/tip"
110]
111risk_score = 99
112rule_id = "f3e22c8b-ea47-45d1-b502-b57b6de950b3"
113setup = """## Setup
114
115This rule needs threat intelligence indicators to work.
116Threat intelligence indicators can be collected using an [Elastic Agent integration](https://www.elastic.co/guide/en/security/current/es-threat-intel-integrations.html#agent-ti-integration),
117the [Threat Intel module](https://www.elastic.co/guide/en/security/current/es-threat-intel-integrations.html#ti-mod-integration),
118or a [custom integration](https://www.elastic.co/guide/en/security/current/es-threat-intel-integrations.html#custom-ti-integration).
119
120More information can be found [here](https://www.elastic.co/guide/en/security/current/es-threat-intel-integrations.html).
121"""
122severity = "critical"
123tags = ["OS: Windows", "Data Source: Elastic Endgame", "Rule Type: Indicator Match"]
124timeline_id = "495ad7a7-316e-4544-8a0f-9c098daee76e"
125timeline_title = "Generic Threat Match Timeline"
126timestamp_override = "event.ingested"
127type = "threat_match"
128
129threat_index = ["filebeat-*", "logs-ti_*"]
130threat_indicator_path = "threat.indicator"
131threat_language = "kuery"
132
133threat_query = '''
134@timestamp >= "now-30d/d" and event.module:(threatintel or ti_*) and
135  threat.indicator.url.full:* and not labels.is_ioc_transform_source:"true"
136'''
137
138query = """
139url.full:*
140"""
141
142
143[[rule.threat_filters]]
144[rule.threat_filters."$state"]
145store = "appState"
146[rule.threat_filters.meta]
147negate = false
148disabled = false
149type = "phrase"
150key = "event.category"
151[rule.threat_filters.meta.params]
152query = "threat"
153[rule.threat_filters.query.match_phrase]
154"event.category" = "threat"
155
156[[rule.threat_filters]]
157[rule.threat_filters."$state"]
158store = "appState"
159[rule.threat_filters.meta]
160negate = false
161disabled = false
162type = "phrase"
163key = "event.kind"
164[rule.threat_filters.meta.params]
165query = "enrichment"
166[rule.threat_filters.query.match_phrase]
167"event.kind" = "enrichment"
168
169[[rule.threat_filters]]
170[rule.threat_filters."$state"]
171store = "appState"
172[rule.threat_filters.meta]
173negate = false
174disabled = false
175type = "phrase"
176key = "event.type"
177[rule.threat_filters.meta.params]
178query = "indicator"
179[rule.threat_filters.query.match_phrase]
180"event.type" = "indicator"
181
182[[rule.threat_mapping]]
183[[rule.threat_mapping.entries]]
184field = "url.full"
185type = "mapping"
186value = "threat.indicator.url.full"
187
188[[rule.threat_mapping]]
189[[rule.threat_mapping.entries]]
190field = "url.original"
191type = "mapping"
192value = "threat.indicator.url.original"