Details
Real-time monitoring of API calls can be achieved by directing CloudTrail Logs to CloudWatch Logs and establishing corresponding metric filters and alarms. It is recommended that a metric filter and alarm be established for ‘root’ login attempts.
Rationale:
Monitoring for ‘root’ account logins will provide visibility into the use of a fully privileged account and an opportunity to reduce the use of it.
Solution
Perform the following to setup the metric filter, alarm, SNS topic, and subscription:
Create a metric filter based on filter pattern provided which checks for ‘Root’ account usage and the
aws logs put-metric-filter –log-group-name ‘
Note: You can choose your own metricName and metricNamespace strings. Using the same metricNamespace for all Foundations Benchmark metrics will group them together.
Create an SNS topic that the alarm will notify
aws sns create-topic –name
Note: you can execute this command once and then re-use the same topic for all monitoring alarms.
Create an SNS subscription to the topic created in step 2
aws sns subscribe –topic-arn
Note: you can execute this command once and then re-use the SNS subscription for all monitoring alarms.
Create an alarm that is associated with the CloudWatch Logs Metric Filter created in step 1 and an SNS topic created in step 2
aws cloudwatch put-metric-alarm –alarm-name ‘
Supportive Information
The following resource is also helpful.
This security hardening control applies to the following category of controls within NIST 800-53: Audit and Accountability.This control applies to the following type of system amazon_aws.