Mika Ayenson
a52751494e
* Convert config header to setup in note field * Parse note field into separate setup and note field with marko gfm * only validate and parse note on elastic authored rules and add CLI description for new DR_BYPASS_NOTE_VALIDATION_AND_PARSE environment variable Co-authored-by: brokensound77 <brokensound77@users.noreply.github.com>
92 lines
3.9 KiB
TOML
92 lines
3.9 KiB
TOML
[metadata]
|
|
creation_date = "2020/10/19"
|
|
maturity = "production"
|
|
updated_date = "2022/04/21"
|
|
|
|
[rule]
|
|
author = ["Elastic"]
|
|
description = """
|
|
Identifies the use of Windows Management Instrumentation Command (WMIC) to discover certain System Security Settings
|
|
such as AntiVirus or Host Firewall details.
|
|
"""
|
|
from = "now-9m"
|
|
index = ["logs-endpoint.events.*", "winlogbeat-*", "logs-windows.*"]
|
|
language = "eql"
|
|
license = "Elastic License v2"
|
|
name = "Security Software Discovery using WMIC"
|
|
note = """## Triage and analysis
|
|
|
|
### Investigating Security Software Discovery using WMIC
|
|
|
|
After successfully compromising an environment, attackers may try to gain situational awareness to plan their next steps.
|
|
This can happen by running commands to enumerate network resources, users, connections, files, and installed security
|
|
software.
|
|
|
|
This rule looks for the execution of the `wmic` utility with arguments compatible to the enumeration of the security
|
|
software installed on the host. Attackers can use this information to decide whether or not to infect a system, disable
|
|
protections, use bypasses, etc.
|
|
|
|
#### Possible investigation steps
|
|
|
|
- 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.
|
|
- Identify the user account that performed the action and whether it should perform this kind of action.
|
|
- Investigate other alerts associated with the user/host during the past 48 hours.
|
|
- Investigate abnormal behaviors observed using the account, such as commands executed, files created or modified, and
|
|
network connections.
|
|
|
|
### False positive analysis
|
|
|
|
- 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.
|
|
|
|
### Response and remediation
|
|
|
|
- Initiate the incident response process based on the outcome of the triage.
|
|
- Isolate the involved hosts to prevent further post-compromise behavior.
|
|
- 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.
|
|
- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and
|
|
malware components.
|
|
- Determine the initial vector abused by the attacker and take action to prevent reinfection via the same vector.
|
|
- 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).
|
|
|
|
## Setup
|
|
|
|
If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2, events will not define `event.ingested` and default fallback for EQL rules was not added until 8.2, so you will need to add a custom pipeline to populate `event.ingested` to @timestamp for this rule to work.
|
|
"""
|
|
risk_score = 47
|
|
rule_id = "6ea55c81-e2ba-42f2-a134-bccf857ba922"
|
|
severity = "medium"
|
|
tags = ["Elastic", "Host", "Windows", "Threat Detection", "Discovery"]
|
|
timestamp_override = "event.ingested"
|
|
type = "eql"
|
|
|
|
query = '''
|
|
process where event.type in ("start", "process_started") and
|
|
(process.name:"wmic.exe" or process.pe.original_file_name:"wmic.exe") and
|
|
process.args:"/namespace:\\\\root\\SecurityCenter2" and process.args:"Get"
|
|
'''
|
|
|
|
|
|
[[rule.threat]]
|
|
framework = "MITRE ATT&CK"
|
|
[[rule.threat.technique]]
|
|
id = "T1518"
|
|
name = "Software Discovery"
|
|
reference = "https://attack.mitre.org/techniques/T1518/"
|
|
[[rule.threat.technique.subtechnique]]
|
|
id = "T1518.001"
|
|
name = "Security Software Discovery"
|
|
reference = "https://attack.mitre.org/techniques/T1518/001/"
|
|
|
|
|
|
|
|
[rule.threat.tactic]
|
|
id = "TA0007"
|
|
name = "Discovery"
|
|
reference = "https://attack.mitre.org/tactics/TA0007/"
|
|
|