6bdfddac8e
* Expand timestamp_override tests * removed timestamp_override from eql sequence rules * add config entry for eql rules with beats index and t_o * add timestamp_override to missing fields
50 lines
1.5 KiB
TOML
50 lines
1.5 KiB
TOML
[metadata]
|
|
creation_date = "2020/03/18"
|
|
maturity = "production"
|
|
updated_date = "2022/03/31"
|
|
|
|
[rule]
|
|
author = ["Elastic"]
|
|
description = """
|
|
Identifies when the SYSTEM account uses an account discovery utility. This could be a sign of discovery activity after
|
|
an adversary has achieved privilege escalation.
|
|
"""
|
|
from = "now-9m"
|
|
index = ["winlogbeat-*", "logs-endpoint.events.*", "logs-windows.*"]
|
|
language = "eql"
|
|
license = "Elastic License v2"
|
|
name = "Net command via SYSTEM account"
|
|
note = """## 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 = 21
|
|
rule_id = "2856446a-34e6-435b-9fb5-f8f040bfa7ed"
|
|
severity = "low"
|
|
tags = ["Elastic", "Host", "Windows", "Threat Detection", "Discovery"]
|
|
timestamp_override = "event.ingested"
|
|
type = "eql"
|
|
|
|
query = '''
|
|
process where event.type in ("start", "process_started") and
|
|
(process.Ext.token.integrity_level_name : "System" or
|
|
winlog.event_data.IntegrityLevel : "System") and
|
|
process.name : "whoami.exe" or
|
|
(process.name : "net1.exe" and not process.parent.name : "net.exe")
|
|
'''
|
|
|
|
|
|
[[rule.threat]]
|
|
framework = "MITRE ATT&CK"
|
|
[[rule.threat.technique]]
|
|
id = "T1033"
|
|
name = "System Owner/User Discovery"
|
|
reference = "https://attack.mitre.org/techniques/T1033/"
|
|
|
|
|
|
[rule.threat.tactic]
|
|
id = "TA0007"
|
|
name = "Discovery"
|
|
reference = "https://attack.mitre.org/tactics/TA0007/"
|
|
|