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>
55 lines
1.9 KiB
TOML
55 lines
1.9 KiB
TOML
[metadata]
|
|
creation_date = "2021/06/05"
|
|
integration = ["aws"]
|
|
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", "Austin Songer"]
|
|
description = "Identifies when an AWS Route Table has been created."
|
|
false_positives = [
|
|
"""
|
|
Route Tables may be created by a system or network administrators. Verify whether the user identity, user agent,
|
|
and/or hostname should be making changes in your environment. Route Table creation by unfamiliar users or hosts
|
|
should be investigated. If known behavior is causing false positives, it can be exempted from the rule. Automated
|
|
processes that use Terraform may lead to false positives.
|
|
""",
|
|
]
|
|
from = "now-60m"
|
|
index = ["filebeat-*", "logs-aws*"]
|
|
interval = "10m"
|
|
language = "kuery"
|
|
license = "Elastic License v2"
|
|
name = "AWS Route Table Created"
|
|
note = """## Setup
|
|
|
|
The AWS Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule."""
|
|
references = [
|
|
"https://docs.datadoghq.com/security_platform/default_rules/aws-ec2-route-table-modified/",
|
|
"https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_CreateRoute.html",
|
|
"https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_CreateRouteTable",
|
|
]
|
|
risk_score = 21
|
|
rule_id = "e12c0318-99b1-44f2-830c-3a38a43207ca"
|
|
severity = "low"
|
|
tags = ["Elastic", "Cloud", "AWS", "Continuous Monitoring", "SecOps", "Network Security", "Persistence"]
|
|
timestamp_override = "event.ingested"
|
|
type = "query"
|
|
|
|
query = '''
|
|
event.dataset:aws.cloudtrail and event.provider:cloudtrail.amazonaws.com and event.action:(CreateRoute or CreateRouteTable) and
|
|
event.outcome:success
|
|
'''
|
|
|
|
|
|
[[rule.threat]]
|
|
framework = "MITRE ATT&CK"
|
|
|
|
[rule.threat.tactic]
|
|
id = "TA0003"
|
|
name = "Persistence"
|
|
reference = "https://attack.mitre.org/tactics/TA0003/"
|
|
|