Terrance DeJesus
4312d8c958
* initial commit * addressing flake errors * added apm to _get_packagted_integrations logic * addressed flake errors * adjusted integration schema and updated rules to be a list * updated several rules and removed a unit test * updated rules with logs-* only index patterns * Update tests/test_all_rules.py Co-authored-by: Mika Ayenson <Mikaayenson@users.noreply.github.com> * addressed flake errors * integration is none is windows, endpoint or apm * adding rules with accepted incoming changes from main * fixed tag and tactic alignment errors from unit testing * adjusted unit testing logic for integration tags; added more exclusion rules * adjusted test_integration logic to be rule resistent and skip if -8.3 * adjusted comments for unit test skip * fixed merge conflicts from main * changing test_integration_tag to remove logic for rule version comparisons * added integration tag to new rule * adjusted rules updated_date value * ignore guided onboarding rule in unit tests * added integration tag to new rule Co-authored-by: Mika Ayenson <Mikaayenson@users.noreply.github.com>
63 lines
2.3 KiB
TOML
63 lines
2.3 KiB
TOML
[metadata]
|
||
creation_date = "2020/08/17"
|
||
integration = ["azure"]
|
||
maturity = "production"
|
||
min_stack_comments = "New fields added: required_fields, related_integrations, setup"
|
||
min_stack_version = "8.3.0"
|
||
updated_date = "2022/12/14"
|
||
|
||
[rule]
|
||
author = ["Elastic"]
|
||
description = """
|
||
Identifies command execution on a virtual machine (VM) in Azure. A Virtual Machine Contributor role lets you manage
|
||
virtual machines, but not access them, nor access the virtual network or storage account they’re connected to. However,
|
||
commands can be run via PowerShell on the VM, which execute as System. Other roles, such as certain Administrator roles
|
||
may be able to execute commands on a VM as well.
|
||
"""
|
||
false_positives = [
|
||
"""
|
||
Command execution on a virtual machine may be done by a system or network administrator. Verify whether the
|
||
username, hostname, and/or resource name should be making changes in your environment. Command execution from
|
||
unfamiliar users or hosts should be investigated. If known behavior is causing false positives, it can be exempted
|
||
from the rule.
|
||
""",
|
||
]
|
||
from = "now-25m"
|
||
index = ["filebeat-*", "logs-azure*"]
|
||
language = "kuery"
|
||
license = "Elastic License v2"
|
||
name = "Azure Command Execution on Virtual Machine"
|
||
note = """## Setup
|
||
|
||
The Azure Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule."""
|
||
references = [
|
||
"https://adsecurity.org/?p=4277",
|
||
"https://posts.specterops.io/attacking-azure-azure-ad-and-introducing-powerzure-ca70b330511a",
|
||
"https://docs.microsoft.com/en-us/azure/role-based-access-control/built-in-roles#virtual-machine-contributor",
|
||
]
|
||
risk_score = 47
|
||
rule_id = "60884af6-f553-4a6c-af13-300047455491"
|
||
severity = "medium"
|
||
tags = ["Elastic", "Cloud", "Azure", "Continuous Monitoring", "SecOps", "Log Auditing"]
|
||
timestamp_override = "event.ingested"
|
||
type = "query"
|
||
|
||
query = '''
|
||
event.dataset:azure.activitylogs and azure.activitylogs.operation_name:"MICROSOFT.COMPUTE/VIRTUALMACHINES/RUNCOMMAND/ACTION" and event.outcome:(Success or success)
|
||
'''
|
||
|
||
|
||
[[rule.threat]]
|
||
framework = "MITRE ATT&CK"
|
||
[[rule.threat.technique]]
|
||
id = "T1059"
|
||
name = "Command and Scripting Interpreter"
|
||
reference = "https://attack.mitre.org/techniques/T1059/"
|
||
|
||
|
||
[rule.threat.tactic]
|
||
id = "TA0002"
|
||
name = "Execution"
|
||
reference = "https://attack.mitre.org/tactics/TA0002/"
|
||
|