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 failed console authentication attempts.

Rationale:

Monitoring failed console logins may decrease lead time to detect an attempt to brute force a credential, which may provide an indicator, such as source IP, that can be used in other event correlation.

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 AWS management Console Login Failures and the taken from audit step 1.

aws logs put-metric-filter –log-group-name –filter-name ‘‘ –metric-transformations metricName= ‘‘ ,metricNamespace=’CISBenchmark’,metricValue=1 –filter-pattern ‘{ ($.eventName = ConsoleLogin) && ($.errorMessage = ‘Failed authentication’) }’

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 –protocol –notification-endpoint

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 ‘‘ –metric-name ‘‘ –statistic Sum –period 300 –threshold 1 –comparison-operator GreaterThanOrEqualToThreshold –evaluation-periods 1 –namespace ‘CISBenchmark’ –alarm-actions

Supportive Information

The following resource is also helpful.

• https://workbench.cisecurity.org/files/3416https://workbench.cisecurity.org/files/3416

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.

References

• 800-53|AU-6
• CSCv6|6.5
• CSCv6|6.7
• CSCv7|16

Source

• Tenable.com/audits