Skip to main content

🛡️ AWS CloudTrail Management Console Sign-In without MFA Monitoring is not enabled🟢⚪

  • Contextual name: 🛡️ Management Console Sign-In without MFA Monitoring is not enabled🟢⚪
  • ID: /ce/ca/aws/cloudtrail/management-console-sign-in-without-mfa-onitoring
  • Tags:
  • Policy Type: COMPLIANCE_POLICY
  • Policy Categories: SECURITY

Similar Policies​

Similar Internal Rules​

RulePoliciesFlags
✉️ dec-x-42eac3871

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.

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.

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 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") }'

... [see more](remediation.md)

policy.yaml​

Open File

Linked Framework Sections​

SectionSub SectionsInternal RulesPoliciesFlagsCompliance
💼 CIS AWS v1.2.0 → 💼 3.2 Ensure a log metric filter and alarm exist for Management Console sign-in without MFA1no data
💼 CIS AWS v1.3.0 → 💼 4.2 Ensure a log metric filter and alarm exist for Management Console sign-in without MFA1no data
💼 CIS AWS v1.4.0 → 💼 4.2 Ensure a log metric filter and alarm exist for Management Console sign-in without MFA1no data
💼 CIS AWS v1.5.0 → 💼 4.2 Ensure a log metric filter and alarm exist for Management Console sign-in without MFA - Level 1 (Automated)1no data
💼 CIS AWS v2.0.0 → 💼 4.2 Ensure management console sign-in without MFA is monitored - Level 1 (Manual)1no data
💼 CIS AWS v3.0.0 → 💼 4.2 Ensure management console sign-in without MFA is monitored - Level 1 (Manual)1no data
💼 CIS AWS v4.0.0 → 💼 4.2 Ensure management console sign-in without MFA is monitored (Manual)1no data
💼 CIS AWS v4.0.1 → 💼 4.2 Ensure management console sign-in without MFA is monitored (Manual)1no data
💼 CIS AWS v5.0.0 → 💼 4.2 Ensure management console sign-in without MFA is monitored (Manual)1no data
💼 CIS AWS v6.0.0 → 💼 5.2 Ensure management console sign-in without MFA is monitored (Manual)1no data
💼 Cloudaware Framework → 💼 Alerting and Notification27no data
💼 Cloudaware Framework → 💼 Multi-Factor Authentication (MFA) Implementation16no data
💼 FedRAMP High Security Controls → 💼 AU-12 Audit Record Generation (L)(M)(H)269no data
💼 FedRAMP High Security Controls → 💼 SI-4(20) Privileged Users (H)4853no data
💼 FedRAMP Low Security Controls → 💼 AU-12 Audit Record Generation (L)(M)(H)69no data
💼 FedRAMP Moderate Security Controls → 💼 AU-12 Audit Record Generation (L)(M)(H)69no data
💼 NIST CSF v2.0 → 💼 DE.CM-01: Networks and network services are monitored to find potentially adverse events161no data
💼 NIST CSF v2.0 → 💼 DE.CM-03: Personnel activity and technology usage are monitored to find potentially adverse events94no data
💼 NIST CSF v2.0 → 💼 DE.CM-09: Computing hardware and software, runtime environments, and their data are monitored to find potentially adverse events162no data
💼 NIST SP 800-53 Revision 5 → 💼 AU-12 Audit Record Generation44769no data