4.2 Ensure a log metric filter and alarm exist for Management Console sign-in without MFA - 'subscription exists'

Information

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 console logins that are not protected by multi-factor authentication (MFA).

Rationale:

Monitoring for single-factor console logins will increase visibility into accounts that are not protected by MFA.

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 sign-in without MFA and the <cloudtrail_log_group_name> taken from audit step 1.

Use Command:

aws logs put-metric-filter --log-group-name <cloudtrail_log_group_name> --filter-name '<no_mfa_console_signin_metric>' --metric-transformations metricName= '<no_mfa_console_signin_metric>' ,metricNamespace='CISBenchmark',metricValue=1 --filter-pattern '{ ($.eventName = 'ConsoleLogin') && ($.additionalEventData.MFAUsed != 'Yes') }'

Or (To reduce false positives incase Single Sign-On (SSO) is used in organization):

aws logs put-metric-filter --log-group-name <cloudtrail_log_group_name> --filter-name '<no_mfa_console_signin_metric>' --metric-transformations metricName= '<no_mfa_console_signin_metric>' ,metricNamespace='CISBenchmark',metricValue=1 --filter-pattern '{ ($.eventName = 'ConsoleLogin') && ($.additionalEventData.MFAUsed != 'Yes') && ($.userIdentity.type = 'IAMUser') && ($.responseElements.ConsoleLogin = 'Success') }'

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 <sns_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 <sns_topic_arn> --protocol <protocol_for_sns> --notification-endpoint <sns_subscription_endpoints>

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 '<no_mfa_console_signin_alarm>' --metric-name '<no_mfa_console_signin_metric>' --statistic Sum --period 300 --threshold 1 --comparison-operator GreaterThanOrEqualToThreshold --evaluation-periods 1 --namespace 'CISBenchmark' --alarm-actions <sns_topic_arn>

Item Details

Audit Name: CIS Amazon Web Services Foundations L1 1.5.0

References: CCE|CCE-79187-1, CSCv7|16

Plugin: amazon_aws

Control ID: 19d8dea861aabdfbe8d34a65d70aeb76502f64c52451042d80c450dc08decdf0

Detections

Analytics

4.2 Ensure a log metric filter and alarm exist for Management Console sign-in without MFA - 'subscription exists'

Information

Solution

See Also

Item Details