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>
52 lines
1.7 KiB
TOML
52 lines
1.7 KiB
TOML
[metadata]
|
|
creation_date = "2020/09/01"
|
|
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 when an Azure Conditional Access policy is modified. Azure Conditional Access policies control access to
|
|
resources via if-then statements. For example, if a user wants to access a resource, then they must complete an action
|
|
such as using multi-factor authentication to access it. An adversary may modify a Conditional Access policy in order to
|
|
weaken their target's security controls.
|
|
"""
|
|
from = "now-25m"
|
|
index = ["filebeat-*", "logs-azure*"]
|
|
language = "kuery"
|
|
license = "Elastic License v2"
|
|
name = "Azure Conditional Access Policy 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/active-directory/conditional-access/overview"]
|
|
risk_score = 47
|
|
rule_id = "bc48bba7-4a23-4232-b551-eca3ca1e3f20"
|
|
severity = "medium"
|
|
tags = ["Elastic", "Cloud", "Azure", "Continuous Monitoring", "SecOps", "Configuration Audit"]
|
|
timestamp_override = "event.ingested"
|
|
type = "query"
|
|
|
|
query = '''
|
|
event.dataset:(azure.activitylogs or azure.auditlogs) and
|
|
event.action:"Update conditional access policy" and event.outcome:(Success or success)
|
|
'''
|
|
|
|
|
|
[[rule.threat]]
|
|
framework = "MITRE ATT&CK"
|
|
[[rule.threat.technique]]
|
|
id = "T1098"
|
|
name = "Account Manipulation"
|
|
reference = "https://attack.mitre.org/techniques/T1098/"
|
|
|
|
|
|
[rule.threat.tactic]
|
|
id = "TA0003"
|
|
name = "Persistence"
|
|
reference = "https://attack.mitre.org/tactics/TA0003/"
|
|
|