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>
66 lines
2.3 KiB
TOML
66 lines
2.3 KiB
TOML
[metadata]
|
|
creation_date = "2020/08/31"
|
|
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 modifications to a Key Vault in Azure. The Key Vault is a service that safeguards encryption keys and secrets
|
|
like certificates, connection strings, and passwords. Because this data is sensitive and business critical, access to
|
|
key vaults should be secured to allow only authorized applications and users.
|
|
"""
|
|
false_positives = [
|
|
"""
|
|
Key vault modifications 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. Key vault modifications 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 Key Vault Modified"
|
|
note = """## Setup
|
|
|
|
The Azure Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule."""
|
|
references = [
|
|
"https://docs.microsoft.com/en-us/azure/key-vault/general/basic-concepts",
|
|
"https://docs.microsoft.com/en-us/azure/key-vault/general/secure-your-key-vault",
|
|
"https://www.elastic.co/security-labs/detect-credential-access",
|
|
]
|
|
risk_score = 47
|
|
rule_id = "792dd7a6-7e00-4a0a-8a9a-a7c24720b5ec"
|
|
severity = "medium"
|
|
tags = ["Elastic", "Cloud", "Azure", "Continuous Monitoring", "SecOps", "Data Protection"]
|
|
timestamp_override = "event.ingested"
|
|
type = "query"
|
|
|
|
query = '''
|
|
event.dataset:azure.activitylogs and azure.activitylogs.operation_name:"MICROSOFT.KEYVAULT/VAULTS/WRITE" and event.outcome:(Success or success)
|
|
'''
|
|
|
|
|
|
[[rule.threat]]
|
|
framework = "MITRE ATT&CK"
|
|
[[rule.threat.technique]]
|
|
id = "T1552"
|
|
name = "Unsecured Credentials"
|
|
reference = "https://attack.mitre.org/techniques/T1552/"
|
|
[[rule.threat.technique.subtechnique]]
|
|
id = "T1552.001"
|
|
name = "Credentials In Files"
|
|
reference = "https://attack.mitre.org/techniques/T1552/001/"
|
|
|
|
|
|
|
|
[rule.threat.tactic]
|
|
id = "TA0006"
|
|
name = "Credential Access"
|
|
reference = "https://attack.mitre.org/tactics/TA0006/"
|
|
|