Ensure management console sign-in without MFA is monitored
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.
It is recommended that a metric filter and alarm be established for console logins that are not protected by multi-factor authentication (MFA).
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 for single-factor console logins will increase visibility into accounts that are not protected by MFA. These type of accounts are more susceptible to compromise and unauthorized access.
Impact
N/A
Audit Procedure
Using AWS CLI
If you are using CloudTrail trails and CloudWatch, perform the following to ensure that there is at least one active multi-region CloudTrail trail with the prescribed metric filters and alarms configured:
- Identify the log group name that is configured for use with the active multi-region CloudTrail trail:
- List all CloudTrail trails:
aws cloudtrail describe-trails
Identify multi-region CloudTrail trails: Trails with
"IsMultiRegionTrail"set totrueNote the value associated with
"Name":<trail-name>Note the
<trail-log-group-name>within the value associated with"CloudWatchLogsLogGroupArn"- Example:
arn:aws:logs:<region>:<account-id>:log-group:<trail-log-group-name>:*
- Example:
Ensure the identified multi-region CloudTrail trail is active:
aws cloudtrail get-trail-status --name <trail-name>
Ensure
IsLoggingis set toTRUEEnsure the identified multi-region CloudTrail trail captures all management events:
aws cloudtrail get-event-selectors --trail-name <trail-name>
- Ensure there is at least one event selector for a trail with
IncludeManagementEventsset totrueandReadWriteTypeset toAll
- Get a list of all associated metric filters for the
<trail-log-group-name>captured in step 1:
aws logs describe-metric-filters --log-group-name <trail-log-group-name>
- Ensure the output from the above command contains the following:
"filterPattern": "{ ($.eventName = "ConsoleLogin") && ($.additionalEventData.MFAUsed != "Yes") }"
Or, to reduce false positives in case Single Sign-On (SSO) is used in the organization:
"filterPattern": "{ ($.eventName = "ConsoleLogin") && ($.additionalEventData.MFAUsed != "Yes") && ($.userIdentity.type = "IAMUser") && ($.responseElements.ConsoleLogin = "Success") }"
Note the
<no-mfa-console-signin-metric>value associated with thefilterPatternfrom step 3.Get a list of CloudWatch alarms, and filter on the
<no-mfa-console-signin-metric>captured in step 4:
aws cloudwatch describe-alarms --query 'MetricAlarms[?MetricName== <no-mfa-console-signin-metric>]'
Note the
AlarmActionsvalue; this will provide the SNS topic ARN value.Ensure there is at least one active subscriber to the SNS topic:
aws sns list-subscriptions-by-topic --topic-arn <sns-topic-arn>
- At least one subscription should have "SubscriptionArn" with a valid AWS ARN.
- Example of valid "SubscriptionArn":
arn:aws:sns:<region>:<account-id>:<sns-topic-name>:<subscription-id>
- Example of valid "SubscriptionArn":
Expected Result
A metric filter exists with the filter pattern matching console sign-in events without MFA, a CloudWatch alarm is configured for the metric, and the alarm has an active SNS topic with at least one subscriber.
Remediation
Using AWS CLI
If you are using CloudTrail trails and CloudWatch, perform the following steps to set up the metric filter, alarm, SNS topic, and subscription:
- Create a metric filter based on the provided filter pattern that checks for AWS Management Console sign-ins without MFA and uses the
<trail-log-group-name>taken from audit step 1:
aws logs put-metric-filter --log-group-name <trail-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 in case Single Sign-On (SSO) is used in the organization:
aws logs put-metric-filter --log-group-name <trail-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>
- Create an SNS subscription for the topic created in step 2:
aws sns subscribe --topic-arn <sns-topic-arn> --protocol <sns-protocol> --notification-endpoint <sns-subscription-endpoints>
- Create an alarm that is associated with the CloudWatch Logs metric filter created in step 1 and the 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>
Default Value
By default, no CloudWatch metric filters or alarms exist for console sign-ins without MFA.
References
- https://docs.aws.amazon.com/AmazonCloudWatch/latest/DeveloperGuide/viewing_metrics_with_cloudwatch.html
- CCE-79187-1
- https://docs.aws.amazon.com/awscloudtrail/latest/userguide/receive-cloudtrail-log-files-from-multiple-regions.html
- https://docs.aws.amazon.com/awscloudtrail/latest/userguide/cloudwatch-alarms-for-cloudtrail.html
- https://docs.aws.amazon.com/sns/latest/dg/SubscribeTopic.html
CIS Controls
| Controls Version | Control | IG 1 | IG 2 | IG 3 |
|---|---|---|---|---|
| v8 | 8.5 Collect Detailed Audit Logs | x | x | |
| v8 | 8.11 Conduct Audit Log Reviews | x | x | |
| v7 | 6.3 Enable Detailed Logging | x | x |
Profile
Level 1 | Manual