Skip to main content

🛡️ AWS CloudTrail Route Table Changes Monitoring is not enabled🟢⚪

Similar Policies​

Similar Internal Rules​

RulePoliciesFlags
✉️ dec-x-0ef94ece1

Description​

Open File

Description​

Real-time monitoring of API calls can be achieved by directing CloudTrail Logs to CloudWatch Logs or an external Security Information and Event Management (SIEM) environment, and establishing corresponding metric filters and alarms.

Routing tables are used to route network traffic between subnets and to network gateways.

It is recommended that a metric filter and alarm be established for changes to route tables.

Rationale​

CloudWatch is an AWS native service that allows you to observe and monitor resources and applications. CloudTrail Logs can also be sent to an external Security information and event management (SIEM) environment for monitoring and alerting.

Monitoring changes to route tables will help ensure that all VPC traffic flows through an expected path and prevent any accidental or intentional modifications that may lead to uncontrolled network traffic. An alarm should be triggered every time an AWS API call is performed to create, replace, delete, or disassociate a Route Table.

Audit​

If you are using CloudTrails and CloudWatch, perform the following to ensure that there is at least one active multi-region CloudTrail with prescribed metric filters and alarms configured:

... see more

Remediation​

Open File

Remediation​

If you are using CloudTrails and CloudWatch, perform the following to setup the metric filter, alarm, SNS topic, and subscription:

  1. Create a metric filter based on filter pattern provided which checks for route table changes and the <cloudtrail_log_group_name> taken from audit step 1:
aws logs put-metric-filter --log-group-name <cloudtrail_log_group_name> --filter-name <route_table_changes_metric> --metric-transformations metricName=<route_table_changes_metric>, metricNamespace='CISBenchmark',metricValue=1 --filter-pattern '{ ($.eventName = CreateRoute) || ($.eventName = CreateRouteTable) || ($.eventName = ReplaceRoute) || ($.eventName = ReplaceRouteTableAssociation) || ($.eventName = DeleteRouteTable) || ($.eventName = DeleteRoute) || ($.eventName = DisassociateRouteTable) }'

Note: You can choose your own metricName and metricNamespace strings. Using the same metricNamespace for all Foundations Benchmark metrics will group them together.

  1. Create an SNS topic that the alarm will notify:

... see more

policy.yaml​

Open File

Linked Framework Sections​

SectionSub SectionsInternal RulesPoliciesFlagsCompliance
💼 CIS AWS v1.2.0 → 💼 3.13 Ensure a log metric filter and alarm exist for route table changes1no data
💼 CIS AWS v1.3.0 → 💼 4.13 Ensure a log metric filter and alarm exist for route table changes1no data
💼 CIS AWS v1.4.0 → 💼 4.13 Ensure a log metric filter and alarm exist for route table changes1no data
💼 CIS AWS v1.5.0 → 💼 4.13 Ensure a log metric filter and alarm exist for route table changes - Level 1 (Automated)1no data
💼 CIS AWS v2.0.0 → 💼 4.13 Ensure route table changes are monitored - Level 1 (Manual)1no data
💼 CIS AWS v3.0.0 → 💼 4.13 Ensure route table changes are monitored - Level 1 (Manual)1no data
💼 CIS AWS v4.0.0 → 💼 4.13 Ensure route table changes are monitored (Manual)1no data
💼 CIS AWS v4.0.1 → 💼 4.13 Ensure route table changes are monitored (Manual)1no data
💼 CIS AWS v5.0.0 → 💼 4.13 Ensure route table changes are monitored (Manual)1no data
💼 CIS AWS v6.0.0 → 💼 5.13 Ensure route table changes are monitored (Manual)1no data
💼 Cloudaware Framework → 💼 Alerting and Notification27no data
💼 FedRAMP High Security Controls → 💼 AU-12 Audit Record Generation (L)(M)(H)265no data
💼 FedRAMP High Security Controls → 💼 SI-4(20) Privileged Users (H)4851no data
💼 FedRAMP Low Security Controls → 💼 AU-12 Audit Record Generation (L)(M)(H)65no data
💼 FedRAMP Moderate Security Controls → 💼 AU-12 Audit Record Generation (L)(M)(H)65no data
💼 NIST CSF v2.0 → 💼 DE.CM-01: Networks and network services are monitored to find potentially adverse events145no data
💼 NIST CSF v2.0 → 💼 DE.CM-03: Personnel activity and technology usage are monitored to find potentially adverse events85no data
💼 NIST CSF v2.0 → 💼 DE.CM-09: Computing hardware and software, runtime environments, and their data are monitored to find potentially adverse events142no data
💼 NIST SP 800-53 Revision 5 → 💼 AU-12 Audit Record Generation44765no data