Suspicious Process Access via Direct System Call

  1[metadata]
  2creation_date = "2021/10/11"
  3integration = ["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 suspicious process access events from an unknown memory region. Endpoint security solutions usually hook
 39userland Windows APIs in order to decide if the code that is being executed is malicious or not. It's possible to bypass
 40hooked functions by writing malicious functions that call syscalls directly.
 41"""
 42from = "now-9m"
 43index = ["winlogbeat-*", "logs-windows.sysmon_operational-*"]
 44language = "eql"
 45license = "Elastic License v2"
 46name = "Suspicious Process Access via Direct System Call"
 47note = """## Triage and analysis
 48
 49### Investigating Suspicious Process Access via Direct System Call
 50
 51Endpoint security solutions usually hook userland Windows APIs in order to decide if the code that is being executed is malicious or not. It's possible to bypass hooked functions by writing malicious functions that call syscalls directly.
 52
 53More context and technical details can be found in this [research blog](https://outflank.nl/blog/2019/06/19/red-team-tactics-combining-direct-system-calls-and-srdi-to-bypass-av-edr/).
 54
 55This rule identifies suspicious process access events from an unknown memory region. Attackers can use direct system calls to bypass security solutions that rely on hooks.
 56
 57> **Note**:
 58> 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.
 59
 60#### Possible investigation steps
 61
 62- 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.
 63- Investigate other alerts associated with the user/host during the past 48 hours.
 64- Investigate any abnormal behavior by the subject process such as network connections, registry or file modifications, and any spawned child processes.
 65- Examine the host for derived artifacts that indicate suspicious activities:
 66  - Analyze the process executable using a private sandboxed analysis system.
 67  - Observe and collect information about the following activities in both the sandbox and the alert subject host:
 68    - Attempts to contact external domains and addresses.
 69      - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by filtering by the process' `process.entity_id`.
 70      - Examine the DNS cache for suspicious or anomalous entries.
 71        - $osquery_0
 72    - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related processes in the process tree.
 73    - Examine the host services for suspicious or anomalous entries.
 74      - $osquery_1
 75      - $osquery_2
 76      - $osquery_3
 77  - 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.
 78- Investigate potentially compromised accounts. Analysts can do this by searching for login events (for example, 4624) to the target host after the registry modification.
 79
 80
 81### False positive analysis
 82
 83- This detection may be triggered by certain applications that install root certificates for the purpose of inspecting SSL traffic. Benign true positives (B-TPs) can be added as exceptions if necessary.
 84
 85### Response and remediation
 86
 87- Initiate the incident response process based on the outcome of the triage.
 88- Isolate the involved host to prevent further post-compromise behavior.
 89- If the triage identified malware, search the environment for additional compromised hosts.
 90  - Implement temporary network rules, procedures, and segmentation to contain the malware.
 91  - Stop suspicious processes.
 92  - Immediately block the identified indicators of compromise (IoCs).
 93  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
 94- Remove the malicious certificate from the root certificate store.
 95- Remove and block malicious artifacts identified during triage.
 96- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
 97- 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.
 98- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
 99- 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).
100"""
101references = [
102    "https://twitter.com/SBousseaden/status/1278013896440324096",
103    "https://www.ired.team/offensive-security/defense-evasion/using-syscalls-directly-from-visual-studio-to-bypass-avs-edrs",
104]
105risk_score = 73
106rule_id = "2dd480be-1263-4d9c-8672-172928f6789a"
107setup = """## Setup
108
109If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
110events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
111Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
112`event.ingested` to @timestamp.
113For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
114"""
115severity = "high"
116tags = [
117    "Domain: Endpoint",
118    "OS: Windows",
119    "Use Case: Threat Detection",
120    "Tactic: Defense Evasion",
121    "Tactic: Execution",
122    "Resources: Investigation Guide",
123    "Data Source: Sysmon",
124]
125timestamp_override = "event.ingested"
126type = "eql"
127
128query = '''
129process where host.os.type == "windows" and event.code == "10" and
130 length(winlog.event_data.CallTrace) > 0 and
131
132 /* Sysmon CallTrace starting with unknown memory module instead of ntdll which host Windows NT Syscalls */
133 not winlog.event_data.CallTrace :
134            ("?:\\WINDOWS\\SYSTEM32\\ntdll.dll*",
135             "?:\\WINDOWS\\SysWOW64\\ntdll.dll*",
136             "?:\\Windows\\System32\\wow64cpu.dll*",
137             "?:\\WINDOWS\\System32\\wow64win.dll*",
138             "?:\\Windows\\System32\\win32u.dll*") and
139
140 not winlog.event_data.TargetImage :
141            ("?:\\Program Files (x86)\\Malwarebytes Anti-Exploit\\mbae-svc.exe",
142             "?:\\Program Files\\Cisco\\AMP\\*\\sfc.exe",
143             "?:\\Program Files (x86)\\Microsoft\\EdgeWebView\\Application\\*\\msedgewebview2.exe",
144             "?:\\Program Files\\Adobe\\Acrobat DC\\Acrobat\\*\\AcroCEF.exe") and
145
146 not (process.executable : ("?:\\Program Files\\Adobe\\Acrobat DC\\Acrobat\\Acrobat.exe",
147                            "?:\\Program Files (x86)\\World of Warcraft\\_classic_\\WowClassic.exe") and
148      not winlog.event_data.TargetImage : "?:\\WINDOWS\\system32\\lsass.exe")
149'''
150
151
152[[rule.threat]]
153framework = "MITRE ATT&CK"
154[[rule.threat.technique]]
155id = "T1055"
156name = "Process Injection"
157reference = "https://attack.mitre.org/techniques/T1055/"
158
159
160[rule.threat.tactic]
161id = "TA0005"
162name = "Defense Evasion"
163reference = "https://attack.mitre.org/tactics/TA0005/"
164[[rule.threat]]
165framework = "MITRE ATT&CK"
166[[rule.threat.technique]]
167id = "T1106"
168name = "Native API"
169reference = "https://attack.mitre.org/techniques/T1106/"
170
171
172[rule.threat.tactic]
173id = "TA0002"
174name = "Execution"
175reference = "https://attack.mitre.org/tactics/TA0002/"