Jonhnathan
90 lines
3.4 KiB
TOML
90 lines
3.4 KiB
TOML
[metadata]
|
|
creation_date = "2020/02/18"
|
|
maturity = "production"
|
|
updated_date = "2022/04/13"
|
|
|
|
[rule]
|
|
author = ["Elastic"]
|
|
description = """
|
|
Windows services typically run as SYSTEM and can be used as a privilege escalation opportunity. Malware or penetration
|
|
testers may run a shell as a service to gain SYSTEM permissions.
|
|
"""
|
|
from = "now-9m"
|
|
index = ["winlogbeat-*", "logs-endpoint.events.*", "logs-windows.*"]
|
|
language = "eql"
|
|
license = "Elastic License v2"
|
|
name = "System Shells via Services"
|
|
note = """## Triage and analysis
|
|
|
|
### Investigating System Shells via Services
|
|
|
|
Attackers may configure existing services or create new ones to execute system shells to elevate their privileges from
|
|
administrator to SYSTEM. They can also configure services to execute these shells with persistence payloads.
|
|
|
|
This rule looks for system shells being spawned by `services.exe`, which is compatible with the above behavior.
|
|
|
|
#### Possible investigation steps
|
|
|
|
- Investigate the process execution chain (parent process tree).
|
|
- Identify how the service was created or modified. Look for registry changes events or Windows events related to
|
|
service activities (for example, 4697 and/or 7045).
|
|
- Identify the user account that performed the action and whether it should perform this kind of action.
|
|
- Contact the account owner and confirm whether they are aware of this activity.
|
|
- Investigate other alerts associated with the user/host during the past 48 hours.
|
|
- Check for similar behavior in other hosts on the environment.
|
|
- Check for commands executed under the spawned shell.
|
|
|
|
### False positive analysis
|
|
|
|
- This activity should not happen legitimately. The security team should address any potential benign true positive
|
|
(B-TP), as this configuration can put the user and the domain at risk.
|
|
|
|
### Response and remediation
|
|
|
|
- Initiate the incident response process based on the outcome of the triage.
|
|
- Isolate the involved host to prevent further post-compromise behavior.
|
|
- Reset passwords for the user account and other potentially compromised accounts (email, services, CRMs, etc.).
|
|
- Delete the service or restore it to the original configuration.
|
|
- Investigate the initial attack vector.
|
|
|
|
|
|
## Config
|
|
|
|
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 = "0022d47d-39c7-4f69-a232-4fe9dc7a3acd"
|
|
severity = "medium"
|
|
tags = ["Elastic", "Host", "Windows", "Threat Detection", "Persistence"]
|
|
timestamp_override = "event.ingested"
|
|
type = "eql"
|
|
|
|
query = '''
|
|
process where event.type in ("start", "process_started") and
|
|
process.parent.name : "services.exe" and
|
|
process.name : ("cmd.exe", "powershell.exe", "pwsh.exe", "powershell_ise.exe") and
|
|
|
|
/* Third party FP's */
|
|
not process.args : "NVDisplay.ContainerLocalSystem"
|
|
'''
|
|
|
|
|
|
[[rule.threat]]
|
|
framework = "MITRE ATT&CK"
|
|
[[rule.threat.technique]]
|
|
id = "T1543"
|
|
name = "Create or Modify System Process"
|
|
reference = "https://attack.mitre.org/techniques/T1543/"
|
|
[[rule.threat.technique.subtechnique]]
|
|
id = "T1543.003"
|
|
name = "Windows Service"
|
|
reference = "https://attack.mitre.org/techniques/T1543/003/"
|
|
|
|
|
|
|
|
[rule.threat.tactic]
|
|
id = "TA0003"
|
|
name = "Persistence"
|
|
reference = "https://attack.mitre.org/tactics/TA0003/"
|
|
|