View a markdown version of this page

Cybersecurity Maturity Model Certification (CMMC) 2.0 - Level 2 - AWS Config

Cybersecurity Maturity Model Certification (CMMC) 2.0 - Level 2

This AWS Config managed conformance pack provides a curated mapping between the Cybersecurity Maturity Model Certification (CMMC) Level 2 practices and AWS Config managed rules. Each Config rule evaluates specific AWS resources and is associated with one or more CMMC practices. AWS Config maintains and automatically updates the managed conformance pack as supported rules and resource types evolve. Refer to the table below for details on the rules, associated controls, guidance, and AWS Region availability.

Source identifier: CMMC_LEVEL-2

This conformance pack is available in all commercial AWS Regions (Regions other than the AWS GovCloud (US) Regions and the China Regions). It's also available in AWS GovCloud (US) Regions.

This conformance pack contains up to 251 AWS Config managed rules. The rules deployed vary by Region. The following table lists each rule, its control IDs, guidance, and the Regions where it's available. To see details about a rule, choose its name.

AWS Config Rule Control IDs Guidance Region availability

acm-certificate-expiration-check

SC.L2-3.13.15 Expired certificates could allow malicious actors to impersonate legitimate entities, potentially leading to data breaches or other security incidents.

Available in all commercial Regions. Available in the AWS GovCloud (US) Regions.

alb-internal-scheme-check

SC.L2-3.13.6 Internal scheme configuration for Application Load Balancers is critical for maintaining network security boundaries and implementing defense-in-depth strategies. Load balancers with internal schemes are only accessible from within the VPC, preventing direct internet exposure of internal applications and services. This configuration helps protect sensitive workloads from external threats, reduces the attack surface, and ensures that traffic routing occurs through controlled network pathways. Organizations often require internal load balancers to comply with security frameworks and regulatory requirements that mandate network segmentation and controlled access to application infrastructure. Available in all commercial Regions except Asia Pacific (Malaysia), Asia Pacific (New Zealand), Asia Pacific (Taipei), Asia Pacific (Thailand), and Mexico (Central). Not available in the AWS GovCloud (US) Regions.

alb-listener-tagged

CM.L2-3.4.1 Proper tagging of ALB listeners enables effective resource management, cost allocation, and governance across cloud environments. Tags facilitate automated compliance reporting, support billing transparency by enabling cost tracking per business unit or project, and ensure adherence to organizational tagging policies. Consistent tagging practices improve operational visibility and enable automated resource lifecycle management through tag-based policies. Available in all commercial Regions except Asia Pacific (Hyderabad), Asia Pacific (Jakarta), Asia Pacific (Malaysia), Asia Pacific (Melbourne), Asia Pacific (New Zealand), Asia Pacific (Taipei), Asia Pacific (Thailand), Canada West (Calgary), Europe (Spain), Europe (Zurich), Israel (Tel Aviv), Mexico (Central), and Middle East (UAE). Not available in the AWS GovCloud (US) Regions.

alb-tagged

CM.L2-3.4.1 Proper tagging of Application Load Balancers enables effective resource management, cost allocation, access control, and compliance reporting. Tags provide essential metadata for organizing resources, implementing automated governance policies, tracking resource ownership, and maintaining operational visibility across environments. Consistent tagging practices support security incident response, cost optimization initiatives, and regulatory compliance requirements. Available in all commercial Regions except Asia Pacific (Malaysia), Asia Pacific (New Zealand), Asia Pacific (Taipei), Asia Pacific (Thailand), and Mexico (Central). Not available in the AWS GovCloud (US) Regions.

amplify-app-branch-auto-deletion-enabled

SC.L2-3.13.2 Enabling automatic branch deletion prevents the accumulation of orphaned branches in Amplify Hosting that no longer correspond to active Git repository branches. This reduces operational overhead by eliminating manual cleanup tasks, minimizes resource waste from unused hosting environments, and maintains consistency between the Git repository structure and deployed environments. Proper branch lifecycle management also reduces potential security risks from abandoned or forgotten deployment branches that may contain outdated code or configurations. Available in all commercial Regions except Africa (Cape Town), Asia Pacific (Hyderabad), Asia Pacific (Jakarta), Asia Pacific (Malaysia), Asia Pacific (Melbourne), Asia Pacific (New Zealand), Asia Pacific (Taipei), Asia Pacific (Thailand), Canada West (Calgary), Europe (Spain), Europe (Zurich), Israel (Tel Aviv), Mexico (Central), and Middle East (UAE). Not available in the AWS GovCloud (US) Regions.

api-gw-execution-logging-enabled

AU.L2-3.3.1 Execution logging for API Gateway stages provides critical visibility into API usage patterns, error conditions, and potential security incidents. Without proper logging enabled, organizations lose the ability to audit API activity, troubleshoot issues, detect unauthorized access attempts, and maintain compliance with security requirements. Comprehensive logging is essential for effective incident response, forensic analysis, and maintaining an audit trail of all API interactions.

Available in all commercial Regions except Asia Pacific (New Zealand) and Asia Pacific (Taipei). Available in the AWS GovCloud (US) Regions.

api-gw-rest-api-tagged

CM.L2-3.4.1 Proper tagging of API Gateway REST APIs is essential for resource management, cost allocation, access control, and operational visibility. Tags enable organizations to categorize resources by environment, owner, project, or business unit, facilitating accurate cost tracking and billing. They also support automated resource management, security policies, and compliance reporting. Without consistent tagging, organizations lose visibility into resource ownership and usage patterns, making it difficult to manage costs, implement governance policies, and maintain operational control over their API infrastructure. Available in all commercial Regions except Asia Pacific (Malaysia), Asia Pacific (New Zealand), Asia Pacific (Taipei), Asia Pacific (Thailand), and Mexico (Central). Not available in the AWS GovCloud (US) Regions.

api-gw-ssl-enabled

SC.L2-3.13.15 Use SSL certificates with API Gateway to provide an additional layer of security. With this configuration, API Gateway authenticates HTTP requests and allows only those originating from API Gateway to access backend systems, even if the backend is publicly accessible.

Available in all commercial Regions except Asia Pacific (New Zealand) and Asia Pacific (Taipei). Available in the AWS GovCloud (US) Regions.

api-gw-stage-tagged

CM.L2-3.4.1 Proper tagging of API Gateway stages enables effective resource management, cost allocation, access control, and operational visibility. Tags provide essential metadata for organizing resources, implementing automated governance policies, tracking resource ownership, and maintaining compliance with organizational standards. Consistent tagging practices facilitate resource discovery, cost optimization, and security monitoring across API Gateway deployments. Available in all commercial Regions except Asia Pacific (Malaysia), Asia Pacific (New Zealand), Asia Pacific (Taipei), Asia Pacific (Thailand), and Mexico (Central). Not available in the AWS GovCloud (US) Regions.

appconfig-application-tagged

CM.L2-3.4.1 Resource tagging is essential for effective resource management, inventory, cost tracking, and security controls in AWS environments. Without proper tagging, organizations cannot effectively track resource ownership, allocate costs, or implement tag-based access controls. Well-structured tagging enables automated resource management and compliance monitoring. Available in all commercial Regions except Asia Pacific (Hyderabad), Asia Pacific (Malaysia), Asia Pacific (New Zealand), Asia Pacific (Taipei), Asia Pacific (Thailand), Canada West (Calgary), Europe (Spain), Europe (Zurich), Mexico (Central), and Middle East (UAE). Not available in the AWS GovCloud (US) Regions.

appconfig-configuration-profile-tagged

CM.L2-3.4.1 Proper tagging of configuration profiles is crucial for maintaining organizational consistency and operational oversight. Tags facilitate resource tracking, access management, and cost allocation. Without structured tagging, organizations risk losing visibility and control over their configuration profiles. Available in all commercial Regions except Asia Pacific (Hyderabad), Asia Pacific (Malaysia), Asia Pacific (New Zealand), Asia Pacific (Taipei), Asia Pacific (Thailand), Canada West (Calgary), Europe (Spain), Europe (Zurich), Mexico (Central), and Middle East (UAE). Not available in the AWS GovCloud (US) Regions.

appconfig-configuration-profile-validators-not-empty

CM.L2-3.4.3 Configuration validators are essential for ensuring that deployed configurations function as intended and meet quality standards. Validators perform syntactic checks to verify proper formatting and semantic checks to validate business logic, preventing deployment of malformed or incorrect configurations that could cause application failures, security vulnerabilities, or operational issues. This control helps maintain configuration integrity and reduces the risk of deploying faulty configurations to production environments. Available in all commercial Regions except Asia Pacific (Hyderabad), Asia Pacific (Malaysia), Asia Pacific (New Zealand), Asia Pacific (Taipei), Asia Pacific (Thailand), Canada West (Calgary), Europe (Spain), Europe (Zurich), Mexico (Central), and Middle East (UAE). Not available in the AWS GovCloud (US) Regions.

appconfig-environment-tagged

CM.L2-3.4.1 Tagging environments is vital for maintaining organizational structure, tracking resource usage and implementing security controls. Without proper tagging, organizations may struggle with resource attribution, cost management, and enforcing access policies across different environments. Available in all commercial Regions except Asia Pacific (Hyderabad), Asia Pacific (Malaysia), Asia Pacific (New Zealand), Asia Pacific (Taipei), Asia Pacific (Thailand), Canada West (Calgary), Europe (Spain), Europe (Zurich), Mexico (Central), and Middle East (UAE). Not available in the AWS GovCloud (US) Regions.

appconfig-extension-association-tagged

CM.L2-3.4.1 Tagging extension associations is crucial for maintaining visibility and control over resource relationships. Proper tagging facilitates easier management, aids in cost attribution, and supports granular access controls. Without structured tagging, organizations may face challenges in tracking and managing their AppConfig extension associations effectively. Available in all commercial Regions except Asia Pacific (Malaysia), Asia Pacific (New Zealand), Asia Pacific (Taipei), Asia Pacific (Thailand), Canada West (Calgary), and Mexico (Central). Not available in the AWS GovCloud (US) Regions.

appconfig-freeform-profile-config-storage

CM.L2-3.4.2 Storing configuration data in approved AWS services ensures proper security controls, encryption, access management, and audit capabilities. AWS Secrets Manager provides automatic encryption, rotation capabilities, and fine-grained access controls for sensitive configuration data. AWS AppConfig hosted configuration store offers integrated security features and simplified management within the AppConfig service. Using unapproved storage locations may expose configuration data to security risks, lack proper encryption, or bypass organizational governance controls. Available in all commercial Regions except Asia Pacific (Hyderabad), Asia Pacific (Malaysia), Asia Pacific (New Zealand), Asia Pacific (Taipei), Asia Pacific (Thailand), Canada West (Calgary), Europe (Spain), Europe (Zurich), Mexico (Central), and Middle East (UAE). Not available in the AWS GovCloud (US) Regions.

appintegrations-event-integration-tagged

CM.L2-3.4.1 Proper tagging of AppIntegrations event integrations is essential for resource management, cost allocation, access control, and operational governance. Tags enable organizations to categorize resources by purpose, owner, environment, or project, facilitating automated management workflows and compliance reporting. Consistent tagging practices improve visibility into resource usage, support accurate cost tracking and billing allocation, and enable effective resource lifecycle management across integration workflows. Available only in US East (N. Virginia), US West (Oregon), Africa (Cape Town), Asia Pacific (Seoul), Asia Pacific (Singapore), Asia Pacific (Sydney), Asia Pacific (Tokyo), Canada (Central), Europe (Frankfurt), and Europe (London). Not available in the AWS GovCloud (US) Regions.

appmesh-gateway-route-tagged

CM.L2-3.4.1 Tagging gateway routes is essential for maintaining clear visibility and control over network traffic configurations. Proper tagging enables efficient resource management, accurate cost allocation, and granular access controls. Without structured tagging, organizations may struggle to effectively manage and secure their App Mesh gateway routes. Available in all commercial Regions except Asia Pacific (Hyderabad), Asia Pacific (Malaysia), Asia Pacific (Melbourne), Asia Pacific (New Zealand), Asia Pacific (Taipei), Asia Pacific (Thailand), Canada West (Calgary), Europe (Spain), Europe (Zurich), Mexico (Central), and Middle East (UAE). Not available in the AWS GovCloud (US) Regions.

appmesh-mesh-deny-tcp-forwarding

SC.L2-3.13.1, SC.L2-3.13.6 Preventing TCP forwarding to services without proxies is critical for maintaining service mesh security and observability. When egress filtering is set to 'ALLOW ALL', traffic can bypass the mesh's security controls, encryption, and monitoring capabilities by communicating directly with services that lack proper proxy configuration. This creates security gaps, reduces visibility into service-to-service communications, and undermines the mesh's ability to enforce policies, collect telemetry, and provide traffic management features. Available in all commercial Regions except Asia Pacific (Hyderabad), Asia Pacific (Malaysia), Asia Pacific (Melbourne), Asia Pacific (New Zealand), Asia Pacific (Taipei), Asia Pacific (Thailand), Canada West (Calgary), Europe (Spain), Europe (Zurich), Mexico (Central), and Middle East (UAE). Not available in the AWS GovCloud (US) Regions.

appmesh-mesh-tagged

CM.L2-3.4.1 Proper tagging of service meshes is crucial for maintaining operational visibility, inventory and control. Tags enable effective resource management, cost tracking, and access control implementation. Without structured tagging, organizations risk losing oversight of their service mesh infrastructure and associated resources. Available in all commercial Regions except Asia Pacific (Hyderabad), Asia Pacific (Malaysia), Asia Pacific (Melbourne), Asia Pacific (New Zealand), Asia Pacific (Taipei), Asia Pacific (Thailand), Canada West (Calgary), Europe (Spain), Europe (Zurich), Mexico (Central), and Middle East (UAE). Not available in the AWS GovCloud (US) Regions.

appmesh-route-tagged

CM.L2-3.4.1 Tagging routes is essential for maintaining clear visibility and control over service mesh traffic patterns. Proper tagging supports efficient resource management, accurate cost attribution, and granular access controls. Without structured tagging, organizations may face difficulties in managing and securing their App Mesh route configurations. Available in all commercial Regions except Asia Pacific (Hyderabad), Asia Pacific (Malaysia), Asia Pacific (Melbourne), Asia Pacific (New Zealand), Asia Pacific (Taipei), Asia Pacific (Thailand), Canada West (Calgary), Europe (Spain), Europe (Zurich), Mexico (Central), and Middle East (UAE). Not available in the AWS GovCloud (US) Regions.

appmesh-virtual-gateway-backend-defaults-tls

SC.L2-3.13.8 Enforcing TLS communication in App Mesh virtual gateway backend defaults ensures data in transit is encrypted between the gateway and backend services, protecting against eavesdropping and man-in-the-middle attacks. This control helps maintain data confidentiality and integrity across service mesh communications, supports compliance with security frameworks that require encryption in transit, and establishes a secure-by-default posture for service-to-service communications within the mesh infrastructure. Available in all commercial Regions except Asia Pacific (Hyderabad), Asia Pacific (Malaysia), Asia Pacific (Melbourne), Asia Pacific (New Zealand), Asia Pacific (Taipei), Asia Pacific (Thailand), Canada West (Calgary), Europe (Spain), Europe (Zurich), Mexico (Central), and Middle East (UAE). Not available in the AWS GovCloud (US) Regions.

appmesh-virtual-gateway-logging-file-path-exists

CM.L2-3.4.2 Access logging is essential for monitoring traffic patterns, troubleshooting connectivity issues, and maintaining security visibility within service mesh environments. Virtual gateways serve as entry points to the mesh and handle external traffic, making comprehensive logging critical for detecting anomalous behavior, performance issues, and potential security threats. Proper log file path configuration ensures that access logs are consistently captured and stored in designated locations for analysis, compliance reporting, and incident response activities. Available in all commercial Regions except Asia Pacific (Hyderabad), Asia Pacific (Malaysia), Asia Pacific (Melbourne), Asia Pacific (New Zealand), Asia Pacific (Taipei), Asia Pacific (Thailand), Canada West (Calgary), Europe (Spain), Europe (Zurich), Mexico (Central), and Middle East (UAE). Not available in the AWS GovCloud (US) Regions.

appmesh-virtual-gateway-tagged

CM.L2-3.4.1 Tagging virtual gateways is crucial for maintaining operational control and visibility. Proper tagging enables efficient resource tracking, cost allocation, and access management. Without structured tagging, organizations risk losing oversight of their gateway configurations and associated security controls. Available in all commercial Regions except Asia Pacific (Hyderabad), Asia Pacific (Malaysia), Asia Pacific (Melbourne), Asia Pacific (New Zealand), Asia Pacific (Taipei), Asia Pacific (Thailand), Canada West (Calgary), Europe (Spain), Europe (Zurich), Mexico (Central), and Middle East (UAE). Not available in the AWS GovCloud (US) Regions.

appmesh-virtual-node-backend-defaults-tls-on

SC.L2-3.13.8 Enforcing TLS communication as the default for App Mesh virtual node backends is critical for maintaining data confidentiality and integrity in service mesh communications. This control helps ensure that all inter-service communication is encrypted by default, reducing the risk of data interception, man-in-the-middle attacks, and unauthorized access to sensitive information transmitted between microservices. Consistent TLS enforcement also supports compliance with security frameworks and regulatory requirements that mandate encryption of data in transit. Available in all commercial Regions except Asia Pacific (Hyderabad), Asia Pacific (Malaysia), Asia Pacific (Melbourne), Asia Pacific (New Zealand), Asia Pacific (Taipei), Asia Pacific (Thailand), Canada West (Calgary), Europe (Spain), Europe (Zurich), Mexico (Central), and Middle East (UAE). Not available in the AWS GovCloud (US) Regions.

appmesh-virtual-node-logging-file-path-exists

CM.L2-3.4.2 Access logging is essential for monitoring application traffic, troubleshooting connectivity issues, and maintaining security visibility within service mesh environments. Without a properly configured log file path, organizations lose critical observability data needed for performance analysis, security incident response, and compliance auditing. Ensuring all App Mesh virtual nodes have designated log file paths enables consistent log collection and supports effective monitoring of service-to-service communications. Available in all commercial Regions except Asia Pacific (Hyderabad), Asia Pacific (Malaysia), Asia Pacific (Melbourne), Asia Pacific (New Zealand), Asia Pacific (Taipei), Asia Pacific (Thailand), Canada West (Calgary), Europe (Spain), Europe (Zurich), Mexico (Central), and Middle East (UAE). Not available in the AWS GovCloud (US) Regions.

appmesh-virtual-node-tagged

CM.L2-3.4.1 Proper tagging of virtual nodes is essential for maintaining clear visibility and control over service mesh resources. Tags facilitate effective resource management, cost tracking, and access control implementation. Without structured tagging, organizations may struggle to manage and secure their virtual node configurations effectively. Available in all commercial Regions except Asia Pacific (Hyderabad), Asia Pacific (Malaysia), Asia Pacific (Melbourne), Asia Pacific (New Zealand), Asia Pacific (Taipei), Asia Pacific (Thailand), Canada West (Calgary), Europe (Spain), Europe (Zurich), Mexico (Central), and Middle East (UAE). Not available in the AWS GovCloud (US) Regions.

appmesh-virtual-router-tagged

CM.L2-3.4.1 Tagging virtual routers is crucial for maintaining operational visibility and control over traffic routing. Proper tagging enables efficient resource management, accurate cost attribution, and granular access controls. Without structured tagging, organizations risk losing oversight of their routing infrastructure and associated security controls. Available in all commercial Regions except Asia Pacific (Hyderabad), Asia Pacific (Malaysia), Asia Pacific (Melbourne), Asia Pacific (New Zealand), Asia Pacific (Taipei), Asia Pacific (Thailand), Canada West (Calgary), Europe (Spain), Europe (Zurich), Mexico (Central), and Middle East (UAE). Not available in the AWS GovCloud (US) Regions.

appmesh-virtual-service-tagged

CM.L2-3.4.1 Tagging virtual services is essential for maintaining operational control and visibility. Proper tagging facilitates resource management, cost allocation, and access controls. Without structured tagging, organizations may face challenges in managing and securing their virtual service configurations. Available in all commercial Regions except Asia Pacific (Hyderabad), Asia Pacific (Malaysia), Asia Pacific (Melbourne), Asia Pacific (New Zealand), Asia Pacific (Taipei), Asia Pacific (Thailand), Canada West (Calgary), Europe (Spain), Europe (Zurich), Mexico (Central), and Middle East (UAE). Not available in the AWS GovCloud (US) Regions.

apprunner-service-in-vpc

AC.L2-3.1.3, SC.L2-3.13.1, SC.L2-3.13.6 Routing App Runner service egress traffic through a custom VPC provides enhanced network security and control capabilities. Custom VPC configuration enables organizations to implement network-level security controls such as security groups, network ACLs, and VPC endpoints. It also allows for better network monitoring, traffic inspection, and compliance with organizational network policies. Additionally, VPC routing facilitates secure connectivity to private resources and enables more granular control over outbound internet access through NAT gateways and route tables. Available only in US East (N. Virginia), US East (Ohio), US West (Oregon), Asia Pacific (Mumbai), Asia Pacific (Singapore), Asia Pacific (Sydney), Asia Pacific (Tokyo), Europe (Frankfurt), Europe (Ireland), Europe (London), and Europe (Paris). Not available in the AWS GovCloud (US) Regions.

apprunner-service-no-public-access

SC.L2-3.13.1 Preventing public accessibility of AppRunner services reduces the attack surface and minimizes exposure to internet-based threats. Services that do not require public internet access should be configured with private network access to implement defense-in-depth security principles. This control helps organizations maintain network segmentation, comply with security frameworks that require private service deployment, and reduce the risk of unauthorized access to application workloads. Available only in US East (N. Virginia), US East (Ohio), US West (Oregon), Asia Pacific (Mumbai), Asia Pacific (Singapore), Asia Pacific (Sydney), Asia Pacific (Tokyo), Europe (Frankfurt), Europe (Ireland), Europe (London), and Europe (Paris). Not available in the AWS GovCloud (US) Regions.

apprunner-service-observability-enabled

AU.L2-3.3.1, AU.L2-3.3.2, SI.L2-3.14.6 Enabling observability for App Runner services is essential for maintaining operational visibility, performance monitoring, and troubleshooting capabilities. Observability features provide critical insights into application performance, request tracing, and system health metrics. Without proper observability configuration, organizations lose visibility into application behavior, making it difficult to detect performance issues, security incidents, or operational problems. This monitoring capability supports incident response, performance optimization, and compliance requirements by ensuring comprehensive logging and monitoring coverage across containerized applications. Available only in US East (N. Virginia), US East (Ohio), US West (Oregon), Asia Pacific (Mumbai), Asia Pacific (Singapore), Asia Pacific (Sydney), Asia Pacific (Tokyo), Europe (Frankfurt), Europe (Ireland), Europe (London), and Europe (Paris). Not available in the AWS GovCloud (US) Regions.

appstream-fleet-in-vpc

AC.L2-3.1.3, SC.L2-3.13.1 Deploying AppStream 2.0 fleets within a VPC provides enhanced network security and isolation capabilities. VPC deployment enables administrators to implement granular network access controls, security groups, and network ACLs to restrict traffic flow. This configuration supports compliance with security frameworks that require network segmentation and helps prevent unauthorized access to streaming resources and underlying infrastructure. Available only in US East (N. Virginia), US East (Ohio), US West (Oregon), Asia Pacific (Mumbai), Asia Pacific (Seoul), Asia Pacific (Singapore), Asia Pacific (Sydney), Asia Pacific (Tokyo), Canada (Central), Europe (Frankfurt), Europe (Ireland), and Europe (London). Not available in the AWS GovCloud (US) Regions.

appsync-cache-ct-encryption-at-rest

SC.L2-3.13.16 Encryption at rest is a critical security control for protecting cached API data. Unencrypted cache data could be vulnerable to unauthorized access if storage is compromised. Implementing encryption provides an essential layer of defense for sensitive information. Available only in US East (N. Virginia), Europe (Frankfurt), Middle East (Bahrain), and South America (Sao Paulo). Not available in the AWS GovCloud (US) Regions.

appsync-cache-ct-encryption-in-transit

SC.L2-3.13.8 Encryption in transit is crucial for protecting data as it moves between services and components. Without proper encryption, sensitive information could be exposed to man-in-the-middle attacks or unauthorized interception. Implementing transit encryption safeguards data confidentiality and integrity. Available only in US East (N. Virginia), Europe (Frankfurt), Middle East (Bahrain), and South America (Sao Paulo). Not available in the AWS GovCloud (US) Regions.

appsync-cache-encryption-at-rest

SC.L2-3.13.16 Encryption at rest is essential for protecting GraphQL API data from unauthorized access. Unencrypted API data could be vulnerable to security breaches if storage systems are compromised. Implementing encryption adds a crucial layer of data protection. Available in all commercial Regions except Africa (Cape Town), Asia Pacific (Hyderabad), Asia Pacific (Jakarta), Asia Pacific (Malaysia), Asia Pacific (Melbourne), Asia Pacific (New Zealand), Asia Pacific (Taipei), Asia Pacific (Thailand), Canada West (Calgary), Europe (Spain), Europe (Zurich), Israel (Tel Aviv), Mexico (Central), and Middle East (UAE). Not available in the AWS GovCloud (US) Regions.

appsync-graphql-api-xray-enabled

AU.L2-3.3.1, SI.L2-3.14.6 Enabling AWS X-Ray tracing on AppSync GraphQL APIs provides critical visibility into application performance, request flows, and potential bottlenecks across distributed systems. X-Ray tracing helps identify performance issues, debug errors, and understand service dependencies, which is essential for maintaining application reliability and optimizing user experience. This monitoring capability also supports compliance requirements for application observability and helps detect anomalous behavior patterns that could indicate security issues. Available in all commercial Regions except Asia Pacific (Malaysia), Asia Pacific (New Zealand), Asia Pacific (Taipei), Asia Pacific (Thailand), Canada West (Calgary), and Mexico (Central). Not available in the AWS GovCloud (US) Regions.

appsync-logging-enabled

AU.L2-3.3.1 Enabling logging for AWS AppSync GraphQL APIs provides critical visibility into API operations, request patterns, and potential errors. Without proper logging, troubleshooting issues becomes significantly more difficult, potentially leading to extended outages, security incidents going undetected, and inability to audit API usage. Logs are essential for debugging, performance monitoring, and maintaining operational awareness of your GraphQL API endpoints.

Available in all commercial Regions except Asia Pacific (Melbourne), Asia Pacific (New Zealand), Asia Pacific (Taipei), Canada West (Calgary), and Mexico (Central). Not available in the AWS GovCloud (US) Regions.

athena-workgroup-encrypted-at-rest

SC.L2-3.13.16 Encrypting Athena query results at rest with AWS KMS keys provides enhanced data protection for potentially sensitive information. Without encryption, query results stored in S3 may be vulnerable to unauthorized access if bucket permissions are compromised. KMS encryption adds a critical security layer by ensuring that even if the underlying storage is accessed, the data remains protected through cryptographic controls, helping organizations meet compliance requirements and safeguard sensitive data.

Available in all commercial Regions except Asia Pacific (Hyderabad), Asia Pacific (Malaysia), Asia Pacific (Melbourne), Asia Pacific (New Zealand), Asia Pacific (Taipei), Asia Pacific (Thailand), Canada West (Calgary), Europe (Spain), Europe (Zurich), Israel (Tel Aviv), Mexico (Central), and Middle East (UAE). Not available in the AWS GovCloud (US) Regions.

athena-workgroup-enforce-workgroup-configuration

CM.L2-3.4.2 Enforcing workgroup configuration settings is essential for maintaining consistent security policies, cost controls, and query execution standards across an organization. When workgroup configuration enforcement is disabled, individual users can override important settings such as query result encryption, output locations, and resource limits, potentially leading to security vulnerabilities, compliance violations, and unexpected costs. This control helps ensure that centrally defined governance policies are consistently applied regardless of client-side configurations. Available in all commercial Regions except Asia Pacific (Malaysia), Asia Pacific (New Zealand), Asia Pacific (Taipei), Asia Pacific (Thailand), and Mexico (Central). Not available in the AWS GovCloud (US) Regions.

athena-workgroup-engine-version-auto-upgrade

SI.L2-3.14.1 Enabling automatic engine version upgrades for Athena workgroups ensures that query processing benefits from the latest performance improvements, security patches, and feature enhancements without manual intervention. This configuration reduces operational overhead by eliminating the need to manually track and apply engine updates, while maintaining access to the most current security fixes and optimizations that AWS provides for the Athena service. Available in all commercial Regions except Asia Pacific (Malaysia), Asia Pacific (New Zealand), Asia Pacific (Taipei), Asia Pacific (Thailand), and Mexico (Central). Not available in the AWS GovCloud (US) Regions.

athena-workgroup-logging-enabled

AU.L2-3.3.1, AU.L2-3.3.2 Audit logs track and monitor system activities. They provide a record of events that can help you detect security breaches, investigate incidents, and comply with regulations. Audit logs also enhance the overall accountability and transparency of your organization.

Available in all commercial Regions except Mexico (Central). Available in the AWS GovCloud (US) Regions.

aurora-mysql-cluster-audit-logging

AU.L2-3.3.1, AU.L2-3.3.2, AU.L2-3.3.8, AU.L2-3.3.9 Database logs can assist with security and access audits and help diagnose availability issues. Audit logs capture a record of database activity, including login attempts, data modifications, schema changes, and other events that can be audited for security and compliance purposes.

Available in all commercial Regions except Asia Pacific (Malaysia), Asia Pacific (New Zealand), Asia Pacific (Taipei), Asia Pacific (Thailand), and Mexico (Central). Available in the AWS GovCloud (US) Regions.

autoscaling-launch-config-public-ip-disabled

SC.L2-3.13.6 By disabling public IP assignment, the attack surface for EC2 instances launched via ASGs, the attack surface is reduced by prohibiting direct internet access. Instead, place EC2 instances in private VPC subnets and enforce access through the associated load balancer.

Available in all commercial Regions. Available in the AWS GovCloud (US) Regions.

batch-compute-environment-enabled

CM.L2-3.4.2 Enabled Batch compute environments are essential for maintaining operational continuity and ensuring that batch processing workloads can execute as expected. Disabled compute environments prevent job queues from launching instances and processing jobs, which can lead to application failures, delayed data processing, and potential business impact. Monitoring the enabled state helps detect unintended configuration changes that could disrupt critical batch processing operations and ensures that compute resources remain available for scheduled and on-demand workloads. Available in all commercial Regions except Asia Pacific (Malaysia), Asia Pacific (Melbourne), Asia Pacific (New Zealand), Asia Pacific (Taipei), Asia Pacific (Thailand), Canada West (Calgary), Israel (Tel Aviv), and Mexico (Central). Not available in the AWS GovCloud (US) Regions.

batch-compute-environment-managed

CM.L2-3.4.2 Managed compute environments provide significant operational and security advantages by allowing AWS to automatically handle infrastructure provisioning, scaling, and maintenance tasks. This reduces the operational overhead of managing compute resources manually, ensures consistent application of security patches and updates, and provides better integration with AWS services for monitoring and logging. Managed environments also help maintain compliance with organizational standards by leveraging AWS-managed configurations and reducing the risk of misconfigurations that could lead to security vulnerabilities or operational issues. Available in all commercial Regions except Asia Pacific (Malaysia), Asia Pacific (Melbourne), Asia Pacific (New Zealand), Asia Pacific (Taipei), Asia Pacific (Thailand), Canada West (Calgary), Israel (Tel Aviv), and Mexico (Central). Not available in the AWS GovCloud (US) Regions.

cloudfront-custom-ssl-certificate

SC.L2-3.13.15 Only encrypted connections over HTTPS (TLS) should be allowed using custom SSL/TLS certificates, to prevent potential attackers from man-in-the-middle (MitM) or similar attacks. Available only in US East (N. Virginia). Not available in the AWS GovCloud (US) Regions.

cloudfront-no-deprecated-ssl-protocols

CM.L2-3.4.7, SC.L2-3.13.15, SC.L2-3.13.8 In 2015, the Internet Engineering Task Force (IETF) officially announced that SSL 3.0 should be deprecated due to the protocol being insufficiently secure. Additionally, in 2020, the IETF officially deprecated the TLS 1.0 and TLS 1.1 due to the discovery of security risks after several attacks placing encrypted internet communications at risk. The IETF recommends the use of the two latest versions of the TLS standard - namely TLS 1.2 and TLS 1.3, both deemed secure. Available only in US East (N. Virginia). Not available in the AWS GovCloud (US) Regions.

cloudfront-origin-lambda-url-oac-enabled

AC.L2-3.1.3, AC.L2-3.1.5, SC.L2-3.13.1 Origin Access Control (OAC) provides enhanced security for CloudFront distributions by ensuring that Lambda Function URLs can only be accessed through CloudFront and not directly by end users. This prevents unauthorized direct access to Lambda functions, reduces exposure to potential attacks, and ensures that all traffic flows through CloudFront's security features including AWS WAF protections, geographic restrictions, and access logging. OAC also helps maintain proper access controls and supports compliance requirements by providing a centralized point of control for function access. Available only in US East (N. Virginia). Not available in the AWS GovCloud (US) Regions.

cloudtrail-all-read-s3-data-event-check

AU.L2-3.3.1, AU.L2-3.3.2 S3 object-level operations, such as GetObject, DeleteObject, and PutObject, are called data events. By default, CloudTrail doesnt log data events, but you can configure trails to log data events for S3 buckets. When you enable object-level logging for read data events, you can log each individual object (file) access within an S3 bucket. Enabling object-level logging can help you meet data compliance requirements, perform comprehensive security analysis, monitor specific patterns of user behavior in your AWS account, and take action on object-level API activity within your S3 buckets by using Amazon CloudWatch Events. This control produces a PASSED finding if you configure a multi-Region trail that logs read-only or all types of data events for all S3 buckets.

Available in all commercial Regions. Available in the AWS GovCloud (US) Regions.

cloudtrail-all-write-s3-data-event-check

AU.L2-3.3.1, AU.L2-3.3.2 Logging S3 write operations is essential for maintaining data integrity and security compliance. Without proper logging, organizations cannot track changes to sensitive data or investigate potential security incidents. Complete audit trails of write operations enable effective security monitoring.

Available in all commercial Regions. Available in the AWS GovCloud (US) Regions.

cloudtrail-s3-bucket-access-logging

AU.L2-3.3.1, AU.L2-3.3.2 S3 server access logging is crucial for maintaining security visibility and compliance for audit logs. Without this additional logging layer, organizations may miss unauthorized access attempts to their CloudTrail logs. Complete access logging supports security monitoring and forensic investigations.

Available in all commercial Regions except Asia Pacific (Malaysia), Asia Pacific (New Zealand), Asia Pacific (Taipei), Asia Pacific (Thailand), Canada West (Calgary), and Mexico (Central). Available in the AWS GovCloud (US) Regions.

cloudtrail-s3-bucket-public-access-prohibited

SC.L2-3.13.1 Protecting CloudTrail logs from public access is essential for maintaining the security of audit data. Public exposure of audit logs could reveal sensitive information about your infrastructure and operations. Implementing strict access controls prevents unauthorized access to critical security information.

Available in all commercial Regions except Asia Pacific (Malaysia), Asia Pacific (New Zealand), Asia Pacific (Taipei), Asia Pacific (Thailand), Canada West (Calgary), and Mexico (Central). Available in the AWS GovCloud (US) Regions.

cloudtrail-security-trail-enabled

AU.L2-3.3.1 Without enabling AWS CloudTrail trail logs and storing them into S3 buckets, organizations run the risk of not having sufficient log history since the default AWS CloudTrail event history is saved for the past 90 days only.

Available in all commercial Regions. Available in the AWS GovCloud (US) Regions.

cloudwatch-alarm-action-check

AU.L2-3.3.4, SI.L2-3.14.6, SI.L2-3.14.7 CloudWatch alarms provide proactive alerting and automated responses to critical events that can maintain system confidentiality, integrity and availability.

Available in all commercial Regions. Available in the AWS GovCloud (US) Regions.

cloudwatch-log-group-encrypted

AU.L2-3.3.8 Although the CloudWatch Log groups are encrypted by default using SSE (Server Side encryption), encrypting Amazon CloudWatch logs with KMS keys enhances the security and protection of sensitive log data. Encrypting logs at rest ensures if unauthorized individuals gain access to the underlying storage infrastructure, they will not be able to read the log data without the encryption key. Encrypting CloudWatch logs provides an additional layer of defense and assists with preventing unauthorized modification or tampering of log data, ensuring the integrity and reliability of the logs for auditing, troubleshooting, and forensic analysis purposes.

Available in all commercial Regions. Available in the AWS GovCloud (US) Regions.

cloudwatch-metric-stream-tagged

CM.L2-3.4.1 Proper tagging of CloudWatch metric streams enables effective resource management, cost allocation, and governance. Tags provide essential metadata for organizing resources, tracking ownership, implementing automated policies, and maintaining compliance with organizational standards. Without consistent tagging, organizations lose visibility into resource usage patterns and struggle to implement effective cost controls and access management policies. Available in all commercial Regions except Asia Pacific (Malaysia), Asia Pacific (New Zealand), Asia Pacific (Taipei), Asia Pacific (Thailand), Canada West (Calgary), and Mexico (Central). Not available in the AWS GovCloud (US) Regions.

cloudtrail-enabled

AU.L2-3.3.1, AU.L2-3.3.2, SI.L2-3.14.6, SI.L2-3.14.7 Enabling CloudTrail provides essential visibility into your AWS environment by recording API activity and changes, aiding in security monitoring, compliance audits, and troubleshooting incidents. It enhances accountability, enables rapid incident response, and facilitates thorough forensic analysis of events within your cloud infrastructure.

Available in all commercial Regions. Available in the AWS GovCloud (US) Regions.

cloud-trail-encryption-enabled

SC.L2-3.13.16 Encrypting CloudTrail logs at rest is essential to safeguard sensitive information and maintain data privacy. By employing encryption, organizations can thwart unauthorized access to log files, ensuring that even if the underlying storage is compromised, the data remains unreadable. This practice aligns with security best practices, compliance requirements, and helps to build trust with customers by demonstrating a commitment to protecting their valuable data.

Available in all commercial Regions. Available in the AWS GovCloud (US) Regions.

cloud-trail-log-file-validation-enabled

AU.L2-3.3.8 Enabling log file validation ensures the integrity of CloudTrail log files by digitally signing log files using cryptographic hash functions verifying log data has not been tampered with or modified providing a mechanism to investigate the event, trace its origin, and understand the impact supporting effective incident response.

Available in all commercial Regions. Available in the AWS GovCloud (US) Regions.

codebuild-report-group-encrypted-at-rest

SC.L2-3.13.16 Encrypting CodeBuild report groups is crucial for protecting sensitive build and test information. Unencrypted report data could be exposed if storage systems are compromised. Implementing encryption adds an essential layer of security for build and test results.

Available in all commercial Regions except Asia Pacific (Taipei), Canada West (Calgary), and Mexico (Central). Available in the AWS GovCloud (US) Regions.

codebuild-report-group-tagged

CM.L2-3.4.1 Proper tagging of CodeBuild report groups enables effective resource management, cost allocation, and governance. Tags provide essential metadata for organizing resources, tracking ownership, implementing automated policies, and maintaining compliance with organizational standards. Without consistent tagging, organizations lose visibility into resource utilization and struggle to implement effective cost controls and security policies. Available in all commercial Regions except Asia Pacific (Malaysia), Asia Pacific (New Zealand), Asia Pacific (Taipei), Asia Pacific (Thailand), Canada West (Calgary), and Mexico (Central). Not available in the AWS GovCloud (US) Regions.

codedeploy-deployment-group-outdated-instances-update

SI.L2-3.14.1 Automatically updating outdated instances during CodeDeploy deployments ensures consistent application versions across all instances in a deployment group. When outdated instances are ignored, they may continue running older versions of applications, creating security vulnerabilities, inconsistent behavior, and potential compliance issues. This control helps maintain deployment consistency, reduces security risks from unpatched applications, and ensures all instances receive the latest updates and security fixes. Available in all commercial Regions except Asia Pacific (Hyderabad), Asia Pacific (Jakarta), Asia Pacific (Malaysia), Asia Pacific (Melbourne), Asia Pacific (New Zealand), Asia Pacific (Taipei), Asia Pacific (Thailand), Canada West (Calgary), Europe (Spain), Europe (Zurich), Israel (Tel Aviv), Mexico (Central), and Middle East (UAE). Not available in the AWS GovCloud (US) Regions.

cognito-identity-pool-unauth-access-check

AC.L2-3.1.1, IA.L2-3.5.2 Preventing unauthenticated access to Cognito Identity Pools is critical for maintaining security boundaries and implementing proper access controls. Allowing unauthenticated identities can expose AWS resources to unauthorized users, potentially leading to data breaches, resource abuse, or compliance violations. By monitoring and detecting Identity Pools with unauthenticated access enabled, organizations can ensure that all users are properly authenticated before receiving temporary AWS credentials, supporting defense-in-depth security strategies and regulatory compliance requirements.

Available in all commercial Regions. Available in AWS GovCloud (US-West).

cognito-user-pool-advanced-security-enabled

AC.L2-3.1.1, AC.L2-3.1.2 Advanced security features in Cognito user pools are essential for protecting against unauthorized access and potential threats. Without these features, user accounts may be more vulnerable to attacks such as credential stuffing or brute force attempts. Enabling advanced security strengthens overall user authentication and access control. Available in all commercial Regions except Africa (Cape Town), Asia Pacific (Hong Kong), Asia Pacific (Hyderabad), Asia Pacific (Melbourne), Canada West (Calgary), Europe (Spain), Europe (Zurich), and Middle East (UAE). Not available in the AWS GovCloud (US) Regions.

cognito-user-pool-tagged

CM.L2-3.4.1 Proper tagging of Cognito user pools enables effective resource management, cost allocation, and governance oversight. Tags facilitate automated compliance reporting, support billing transparency across business units or projects, and enable consistent application of security policies. Without standardized tagging, organizations lose visibility into resource ownership, struggle with cost optimization, and face challenges in maintaining regulatory compliance requirements. Available in all commercial Regions except Asia Pacific (Malaysia), Asia Pacific (New Zealand), Asia Pacific (Taipei), Asia Pacific (Thailand), and Mexico (Central). Not available in the AWS GovCloud (US) Regions.

connect-instance-logging-enabled

AU.L2-3.3.1, AU.L2-3.3.2, SI.L2-3.14.7 Enabling flow logs for Amazon Connect instances provides critical visibility into call flows, customer interactions, and system operations. Flow logs capture detailed information about contact routing, agent interactions, and system events, which are essential for troubleshooting issues, monitoring performance, analyzing customer experience, and maintaining audit trails. This logging capability supports compliance requirements, enables proactive monitoring of contact center operations, and provides the data necessary for optimizing call flows and identifying potential security or operational issues. Available only in US East (N. Virginia), US West (Oregon), Africa (Cape Town), Asia Pacific (Seoul), Asia Pacific (Singapore), Asia Pacific (Sydney), Asia Pacific (Tokyo), Canada (Central), Europe (Frankfurt), and Europe (London). Available in AWS GovCloud (US-West).

custom-eventbus-policy-attached

AC.L2-3.1.1 Attaching a resource policy helps control access to custom EventBus resources, enforcing least privilege and reducing the risk of unauthorized access.

Available in all commercial Regions. Not available in the AWS GovCloud (US) Regions.

datasync-location-object-storage-using-https

SC.L2-3.13.1, SC.L2-3.13.15 Enforcing HTTPS protocol for DataSync location object storage communications is critical for maintaining data security and confidentiality during transfer operations. HTTPS provides encryption in transit, protecting sensitive data from interception, tampering, and unauthorized access while data moves between AWS DataSync and external object storage systems. This control helps organizations meet compliance requirements for data protection standards such as PCI DSS, HIPAA, and SOC 2, while reducing the risk of data breaches during transfer operations. Additionally, using HTTPS ensures data integrity verification and authentication of storage endpoints, preventing man-in-the-middle attacks and ensuring data reaches its intended destination securely. Available in all commercial Regions except Asia Pacific (Malaysia), Asia Pacific (New Zealand), Asia Pacific (Taipei), Asia Pacific (Thailand), Canada West (Calgary), Israel (Tel Aviv), and Mexico (Central). Not available in the AWS GovCloud (US) Regions.

datasync-task-data-verification-enabled

MP.L2-3.8.9 Data verification in DataSync tasks is critical for ensuring data integrity during transfer operations. When enabled, DataSync performs additional checksums and validation to verify that data has been accurately transferred from source to destination. This helps detect potential data corruption, incomplete transfers, or transmission errors that could compromise data quality. Without verification, organizations may unknowingly have corrupted or incomplete data in their destination systems, which could lead to application failures, data loss, or compliance violations in regulated environments. Available in all commercial Regions except Asia Pacific (Malaysia), Asia Pacific (New Zealand), Asia Pacific (Taipei), Asia Pacific (Thailand), and Mexico (Central). Not available in the AWS GovCloud (US) Regions.

datasync-task-logging-enabled

AU.L2-3.3.1, AU.L2-3.3.2 Audit logs track and monitor system activities. They provide a record of events that can help you detect security breaches, investigate incidents, and comply with regulations. Audit logs also enhance the overall accountability and transparency of your organization.

Available in all commercial Regions except Canada West (Calgary) and Mexico (Central). Available in the AWS GovCloud (US) Regions.

dax-tls-endpoint-encryption

SC.L2-3.13.8 HTTPS (TLS) can be used to help prevent potential attackers from using person-in-the-middle or similar attacks to eavesdrop on or manipulate network traffic. You should only allow encrypted connections over TLS to access DAX clusters. However, encrypting data in transit can affect performance. You should test your application with encryption turned on to understand the performance profile and the impact of TLS. Available only in US East (N. Virginia), US East (Ohio), US West (N. California), US West (Oregon), Asia Pacific (Malaysia), Asia Pacific (Mumbai), Asia Pacific (Singapore), Asia Pacific (Sydney), Asia Pacific (Tokyo), Europe (Frankfurt), Europe (Ireland), Europe (London), Europe (Paris), and South America (Sao Paulo). Not available in the AWS GovCloud (US) Regions.

dms-endpoint-tagged

CM.L2-3.4.1 Proper tagging of DMS endpoints is essential for resource management, cost allocation, and operational governance. Tags enable organizations to categorize migration endpoints by project, environment, owner, or business unit, facilitating accurate cost tracking and resource organization. Consistent tagging practices support automated resource management, security policies, and compliance reporting requirements. Without proper tagging, organizations lose visibility into resource ownership and purpose, making it difficult to manage costs, apply appropriate security controls, and maintain operational accountability across database migration projects. Available in all commercial Regions except Asia Pacific (Hyderabad), Asia Pacific (Jakarta), Asia Pacific (Malaysia), Asia Pacific (Melbourne), Asia Pacific (New Zealand), Asia Pacific (Taipei), Asia Pacific (Thailand), Canada West (Calgary), Europe (Spain), Europe (Zurich), Israel (Tel Aviv), Mexico (Central), and Middle East (UAE). Not available in the AWS GovCloud (US) Regions.

dms-mongo-db-authentication-enabled

AC.L2-3.1.1 Enabling authentication for MongoDB endpoints is critical for maintaining data security during migrations. Without proper authentication, unauthorized access to sensitive data could occur. Implementing password-based authentication helps protect MongoDB data stores from unauthorized access and potential data breaches. Available in all commercial Regions except Asia Pacific (Hyderabad), Asia Pacific (Melbourne), Canada West (Calgary), Europe (Spain), Europe (Zurich), Mexico (Central), and Middle East (UAE). Available in the AWS GovCloud (US) Regions.

dms-neptune-iam-authorization-enabled

AC.L2-3.1.1, AC.L2-3.1.2, AC.L2-3.1.5 IAM authentication for Neptune endpoints provides robust, scalable access control. Without IAM authentication, managing access to Neptune databases during migrations could be less secure and more complex. Implementing IAM authorization ensures fine-grained control over who can access Neptune data through DMS. Available only in US East (N. Virginia), US East (Ohio), US West (N. California), US West (Oregon), Asia Pacific (Hong Kong), Asia Pacific (Mumbai), Asia Pacific (Seoul), Asia Pacific (Singapore), Asia Pacific (Sydney), Asia Pacific (Tokyo), Canada (Central), Europe (Frankfurt), Europe (Ireland), Europe (London), Europe (Paris), Europe (Stockholm), Middle East (Bahrain), and South America (Sao Paulo). Available in the AWS GovCloud (US) Regions.

dms-redis-tls-enabled

SC.L2-3.13.8 TLS provides end-to-end security when data is sent between applications or databases over the internet. When you configure SSL encryption for your DMS endpoint, it enables encrypted communication between the source and target databases during the migration process. This helps prevent eavesdropping and interception of sensitive data by malicious actors. Without SSL encryption, sensitive data may be accessed, resulting in data breaches, data loss, or other security incidents. Available in all commercial Regions except Asia Pacific (Hyderabad), Asia Pacific (Jakarta), Asia Pacific (Malaysia), Asia Pacific (Melbourne), Asia Pacific (New Zealand), Asia Pacific (Taipei), Asia Pacific (Thailand), Canada West (Calgary), Europe (Spain), Europe (Zurich), Israel (Tel Aviv), Mexico (Central), and Middle East (UAE). Available in the AWS GovCloud (US) Regions.

dms-replication-task-sourcedb-logging

AU.L2-3.3.1, AU.L2-3.3.3 Proper logging of DMS replication tasks is crucial for maintaining operational visibility and ensuring data integrity. Without adequate logging, issues in the replication process might go undetected, potentially leading to data inconsistencies. Configuring appropriate logging supports efficient troubleshooting and monitoring of migration processes.

Available in all commercial Regions except Asia Pacific (Hyderabad), Asia Pacific (Melbourne), Asia Pacific (New Zealand), Asia Pacific (Taipei), Canada West (Calgary), Europe (Spain), Europe (Zurich), Mexico (Central), and Middle East (UAE). Not available in the AWS GovCloud (US) Regions.

dms-replication-task-tagged

CM.L2-3.4.1 Proper tagging of DMS replication tasks enables effective resource management, cost allocation, and governance. Tags facilitate tracking of migration projects, identifying resource ownership, implementing automated policies, and maintaining compliance with organizational standards. Without consistent tagging, organizations lose visibility into their migration activities and cannot effectively manage costs or apply security policies across their DMS infrastructure. Available in all commercial Regions except Asia Pacific (Hyderabad), Asia Pacific (Jakarta), Asia Pacific (Malaysia), Asia Pacific (Melbourne), Asia Pacific (New Zealand), Asia Pacific (Taipei), Asia Pacific (Thailand), Canada West (Calgary), Europe (Spain), Europe (Zurich), Israel (Tel Aviv), Mexico (Central), and Middle East (UAE). Not available in the AWS GovCloud (US) Regions.

docdb-cluster-encrypted

SC.L2-3.13.16 Encrypting Amazon DocumentDB clusters at rest protects sensitive data from unauthorized access if storage is compromised. Without encryption, data stored in DocumentDB clusters remains vulnerable to unauthorized access through direct storage access. Encryption at rest is a critical data protection control that helps meet compliance requirements for sensitive workloads and prevents data breaches by ensuring all cluster data remains encrypted across all storage components.

Available in all commercial Regions except US West (N. California), Africa (Cape Town), Asia Pacific (Melbourne), Asia Pacific (New Zealand), Asia Pacific (Osaka), Asia Pacific (Taipei), Canada West (Calgary), Europe (Spain), Europe (Stockholm), Europe (Zurich), Mexico (Central), and Middle East (Bahrain). Not available in the AWS GovCloud (US) Regions.

docdb-cluster-encrypted-in-transit

SC.L2-3.13.8 Encryption in transit protects sensitive data as it moves between DocumentDB clients and clusters, preventing unauthorized interception and eavesdropping on database communications. This control helps organizations meet compliance requirements for data protection standards such as PCI DSS, HIPAA, and SOC 2, while reducing the risk of data breaches during transmission. Enabling TLS encryption ensures that database credentials, queries, and results remain confidential and maintain integrity during network transmission.

Available in all commercial Regions except US West (N. California), Africa (Cape Town), Asia Pacific (Melbourne), Asia Pacific (New Zealand), Asia Pacific (Osaka), Asia Pacific (Taipei), Canada West (Calgary), Europe (Spain), Europe (Stockholm), Europe (Zurich), and Middle East (Bahrain). Available in the AWS GovCloud (US) Regions.

ebs-snapshot-public-restorable-check

AC.L2-3.1.5 Public EBS snapshots can be accessible to other AWS accounts. EBS snapshots should not be restorable by everyone unless it is explicitly allowed, to avoid accidental exposure of data.

Available in all commercial Regions except Europe (Spain). Available in the AWS GovCloud (US) Regions.

ec2-capacity-reservation-tagged

CM.L2-3.4.1 Proper tagging of EC2 capacity reservations is essential for resource management, cost allocation, and operational governance. Tags enable organizations to track resource ownership, categorize reservations by project or department, implement automated billing and chargeback processes, and maintain compliance with internal policies. Without consistent tagging, capacity reservations become difficult to manage at scale, leading to inefficient resource utilization and challenges in cost optimization and accountability. Available in all commercial Regions except Asia Pacific (Malaysia), Asia Pacific (New Zealand), Asia Pacific (Taipei), Asia Pacific (Thailand), and Mexico (Central). Not available in the AWS GovCloud (US) Regions.

ec2-carrier-gateway-tagged

CM.L2-3.4.1 Proper tagging of EC2 carrier gateways is essential for resource management, cost allocation, access control, operational visibility. Tags enable organizations to categorize track network infrastructure components, implement automated governance policies, maintain compliance with organizational standards. Consistent tagging practices facilitate resource identification, billing attribution, security policy enforcement across carrier gateway resources that provide connectivity between VPCs carrier networks. Available only in US East (N. Virginia), US East (Ohio), US West (Oregon), Asia Pacific (Seoul), Asia Pacific (Sydney), Asia Pacific (Tokyo), Canada (Central), Europe (Frankfurt), Europe (Ireland), Europe (London), and Europe (Paris). Not available in the AWS GovCloud (US) Regions.

ec2-client-vpn-connection-log-enabled

AC.L2-3.1.12, AC.L2-3.1.20 Enabling logging captures connection details, facilitating monitoring, auditing, and troubleshooting of Client VPN activities and potential security incidents. Available in all commercial Regions except Asia Pacific (Hyderabad), Canada West (Calgary), Europe (Spain), Mexico (Central), and Middle East (UAE). Available in the AWS GovCloud (US) Regions.

ec2-client-vpn-endpoint-tagged

CM.L2-3.4.1 Proper tagging of EC2 Client VPN endpoints enables effective resource management, cost allocation, access control, compliance reporting. Tags provide essential metadata for organizing resources, implementing automated governance policies, tracking resource ownership, maintaining security boundaries. Without consistent tagging, organizations lose visibility into resource utilization struggle to enforce governance policies across their VPN infrastructure. Available in all commercial Regions except Asia Pacific (Hyderabad), Asia Pacific (Jakarta), Asia Pacific (Malaysia), Asia Pacific (New Zealand), Asia Pacific (Taipei), Asia Pacific (Thailand), Canada West (Calgary), Europe (Spain), Israel (Tel Aviv), Mexico (Central), and Middle East (UAE). Not available in the AWS GovCloud (US) Regions.

ec2-enis-source-destination-check-enabled

AC.L2-3.1.3, SC.L2-3.13.1, SC.L2-3.13.4, SC.L2-3.13.6 Source/destination checking for Amazon EC2 instances and attached ENIs should be enabled and configured consistently across your EC2 instances. Each ENI has its own setting for source/destination checks. If source/destination checking is enabled, Amazon EC2 enforces source/destination address validation, which ensures that an instance is either the source or the destination of any traffic that it receives. This provides an additional layer of network security by preventing resources from handling unintended traffic and preventing IP address spoofing.

Available in all commercial Regions. Available in the AWS GovCloud (US) Regions.

ec2-fleet-tagged

CM.L2-3.4.1 Proper tagging of EC2 fleets is essential for resource management, cost allocation, security governance, operational visibility. Tags enable organizations to categorize resources by purpose, owner, environment, or project, facilitating accurate cost tracking billing allocation. Consistent tagging practices support automated resource management, security policy enforcement, compliance reporting. Without proper tagging, organizations lose visibility into resource utilization, struggle with cost optimization, face challenges in maintaining security compliance postures across their EC2 fleet infrastructure. Available in all commercial Regions except Asia Pacific (Malaysia), Asia Pacific (New Zealand), Asia Pacific (Taipei), Asia Pacific (Thailand), Canada West (Calgary), Israel (Tel Aviv), and Mexico (Central). Not available in the AWS GovCloud (US) Regions.

ec2-instance-launched-with-allowed-ami

CM.L2-3.4.1, CM.L2-3.4.2 Using approved AMIs ensures EC2 instances are built from standardized, secure, properly configured base images. This control helps maintain consistent security baselines, reduces exposure to vulnerabilities from unvetted images, supports compliance requirements for standardized computing environments, enables organizations to enforce governance policies around approved software configurations security hardening standards.

Available in all commercial Regions. Available in the AWS GovCloud (US) Regions.

ec2-launch-template-imdsv2-check

AC.L2-3.1.1, MA.L2-3.7.1, SC.L2-3.13.15 Running resources on supported software versions ensures optimal performance, security, and access to the latest features. Regular updates safeguard against vulnerabilities, which help ensure a stable and efficient user experience.

Available in all commercial Regions except Asia Pacific (Hyderabad), Asia Pacific (Melbourne), Canada West (Calgary), Europe (Spain), Europe (Zurich), Mexico (Central), and Middle East (UAE). Not available in the AWS GovCloud (US) Regions.

ec2-managedinstance-patch-compliance-status-check

MA.L2-3.7.1 Regular patching is crucial for addressing vulnerabilities. You can leverage SSM to patch EC2 instances and address security vulnerabilities, maintain compliance and improve performance.

Available in all commercial Regions except Asia Pacific (Osaka) and Europe (Milan). Available in the AWS GovCloud (US) Regions.

ec2-network-insights-access-scope-analysis-tagged

CM.L2-3.4.1 Proper tagging of Network Insights access scope analyses is essential for resource management, cost allocation, operational governance. Tags enable organizations to categorize track network analysis activities, assign ownership responsibility, implement automated lifecycle management, maintain compliance with internal policies. Without consistent tagging, organizations lose visibility into their network analysis resources, making it difficult to manage costs, enforce governance policies, maintain operational accountability across different teams projects. Available in all commercial Regions except Asia Pacific (Hyderabad), Asia Pacific (Jakarta), Asia Pacific (Malaysia), Asia Pacific (Melbourne), Asia Pacific (New Zealand), Asia Pacific (Taipei), Asia Pacific (Thailand), Canada West (Calgary), Europe (Spain), Europe (Zurich), Israel (Tel Aviv), Mexico (Central), and Middle East (UAE). Not available in the AWS GovCloud (US) Regions.

ec2-network-insights-access-scope-tagged

CM.L2-3.4.1 Proper tagging of Network Insights access scopes enables effective resource management, cost allocation, governance across AWS environments. Tags provide essential metadata for tracking resource ownership, purpose, lifecycle management. Consistent tagging practices support automated operations, security policies, compliance reporting requirements. Without adequate tagging, organizations lose visibility into resource utilization patterns struggle to implement effective cost controls access management policies. Available in all commercial Regions except Asia Pacific (Hyderabad), Asia Pacific (Jakarta), Asia Pacific (Malaysia), Asia Pacific (Melbourne), Asia Pacific (New Zealand), Asia Pacific (Taipei), Asia Pacific (Thailand), Canada West (Calgary), Europe (Spain), Europe (Zurich), Israel (Tel Aviv), Mexico (Central), and Middle East (UAE). Not available in the AWS GovCloud (US) Regions.

ec2-network-insights-path-tagged

CM.L2-3.4.1 Proper tagging of Network Insights paths enables effective resource management, cost allocation, operational governance. Tags facilitate automated resource discovery, support compliance reporting requirements, enable consistent application of organizational policies across network analysis resources. Without standardized tagging, organizations lose visibility into resource ownership, purpose, associated costs, making it difficult to maintain operational control meet regulatory requirements. Available in all commercial Regions except Asia Pacific (Hyderabad), Asia Pacific (Jakarta), Asia Pacific (Malaysia), Asia Pacific (Melbourne), Asia Pacific (New Zealand), Asia Pacific (Taipei), Asia Pacific (Thailand), Canada West (Calgary), Europe (Spain), Europe (Zurich), Israel (Tel Aviv), Mexico (Central), and Middle East (UAE). Not available in the AWS GovCloud (US) Regions.

ec2-security-group-attached-to-eni

CM.L2-3.4.7 Unused EC2 security groups adds unnecessary attack surfaces and clutter to an AWS account. Periodic account reviews and hygiene helps provide improved resource management and security.

Available in all commercial Regions. Available in the AWS GovCloud (US) Regions.

ec2-security-group-attached-to-eni-periodic

CM.L2-3.4.7 Unused EC2 security groups adds unnecessary attack surfaces and clutter to an AWS account. Periodic account reviews and hygiene helps provide improved resource management and security. Available in all commercial Regions except Asia Pacific (Hyderabad), Asia Pacific (Jakarta), Asia Pacific (Malaysia), Asia Pacific (Melbourne), Asia Pacific (New Zealand), Asia Pacific (Osaka), Asia Pacific (Taipei), Asia Pacific (Thailand), Canada West (Calgary), Europe (Spain), Europe (Zurich), Israel (Tel Aviv), Mexico (Central), and Middle East (UAE). Not available in the AWS GovCloud (US) Regions.

ec2-spot-fleet-request-ct-encryption-at-rest

SC.L2-3.13.11, SC.L2-3.13.16, SC.L2-3.13.6 For an additional layer of security, you should enable encryption for Amazon EBS volumes. Encryption operations then occur on the servers that host Amazon EC2 instances, which helps ensure the security of both data at rest and data in transit between an instance and its attached EBS storage. Amazon EBS encryption is a straightforward encryption solution for EBS resources associated with your EC2 instances. With EBS encryption, you arent required to build, maintain, and secure your own key management infrastructure. EBS encryption uses AWS KMS keys when creating encrypted volumes.

Available in all commercial Regions except Canada West (Calgary). Available in the AWS GovCloud (US) Regions.

ec2-transit-gateway-multicast-domain-tagged

CM.L2-3.4.1 Proper tagging of transit gateway multicast domains is essential for resource management, cost allocation, access control, operational visibility. Tags enable organizations to categorize resources by purpose, owner, environment, or project, facilitating automated management workflows compliance reporting. Consistent tagging practices improve security posture by supporting attribute-based access controls help maintain governance standards across distributed network infrastructure. Without proper tagging, organizations lose visibility into resource ownership usage patterns, making it difficult to manage costs maintain security boundaries. Available in all commercial Regions except Asia Pacific (Malaysia), Asia Pacific (New Zealand), Asia Pacific (Taipei), Asia Pacific (Thailand), and Mexico (Central). Not available in the AWS GovCloud (US) Regions.

ec2-vpn-connection-logging-enabled

AU.L2-3.3.1, AU.L2-3.3.2, AU.L2-3.3.8, AU.L2-3.3.9 AWS Site-to-Site VPN logs provide you with deeper visibility into your Site-to-Site VPN deployments. With this feature, you have access to Site-to-Site VPN connection logs that provide details on IP Security (IPsec) tunnel establishment, Internet Key Exchange (IKE) negotiations, and dead peer detection (DPD) protocol messages. Site-to-Site VPN logs can be published to CloudWatch Logs. This feature provides customers with a single consistent way to access and analyze detailed logs for all of their Site-to-Site VPN connections. Available in all commercial Regions except Canada West (Calgary). Available in the AWS GovCloud (US) Regions.

ec2-vpn-connection-tagged

CM.L2-3.4.1 Proper tagging of VPN connections enables effective resource management, cost allocation, governance oversight. Tags facilitate automated operations, security policies, compliance reporting by providing metadata that identifies resource ownership, purpose, environment, other critical attributes. Consistent tagging practices improve operational visibility support organizational policies for resource lifecycle management. Available in all commercial Regions except Asia Pacific (Malaysia), Asia Pacific (New Zealand), Asia Pacific (Taipei), Asia Pacific (Thailand), and Mexico (Central). Not available in the AWS GovCloud (US) Regions.

ecr-repository-tagged

CM.L2-3.4.1 Proper tagging of ECR repositories is essential for resource management, cost allocation, access control, operational visibility. Tags enable organizations to categorize container repositories by environment, application, team ownership, or compliance requirements. Consistent tagging practices facilitate automated resource management, security policies, cost tracking across containerized applications. Without proper tagging, organizations lose visibility into repository ownership purpose, making it difficult to implement governance policies maintain security standards. Available in all commercial Regions except Asia Pacific (Malaysia), Asia Pacific (New Zealand), Asia Pacific (Taipei), Asia Pacific (Thailand), and Mexico (Central). Not available in the AWS GovCloud (US) Regions.

ecs-awsvpc-networking-enabled

CM.L2-3.4.2 The awsvpc networking mode provides improved security isolation and network control for containerized applications. Without this mode, containers may have limited network security options and visibility. Implementing awsvpc networking enables better container-level network security and monitoring. Available in all commercial Regions except Asia Pacific (Hyderabad), Asia Pacific (Jakarta), Asia Pacific (Malaysia), Asia Pacific (Melbourne), Asia Pacific (New Zealand), Asia Pacific (Osaka), Asia Pacific (Taipei), Asia Pacific (Thailand), Canada West (Calgary), Europe (Spain), Europe (Zurich), Israel (Tel Aviv), Mexico (Central), and Middle East (UAE). Not available in the AWS GovCloud (US) Regions.

ecs-capacity-provider-tagged

CM.L2-3.4.1 Proper tagging of ECS capacity providers enables effective resource management, cost allocation, governance across containerized workloads. Tags facilitate automated resource discovery, support compliance reporting requirements, enable granular access control policies. Consistent tagging practices improve operational visibility help organizations track resource ownership, environment classification, billing attribution for their container infrastructure. Available in all commercial Regions except Asia Pacific (Malaysia), Asia Pacific (New Zealand), Asia Pacific (Taipei), Asia Pacific (Thailand), and Mexico (Central). Not available in the AWS GovCloud (US) Regions.

ecs-task-definition-network-mode-not-host

AC.L2-3.1.3 Using host network mode in ECS task definitions creates significant security risks by allowing containers to share the host's network stack directly. This configuration bypasses Docker's network isolation, potentially exposing the host system to network-based attacks allowing containers to access services running on the host. Avoiding host network mode helps maintain proper network segmentation, reduces the attack surface, ensures containers operate within isolated network environments as intended by containerization security best practices.

Available in all commercial Regions. Available in the AWS GovCloud (US) Regions.

efs-filesystem-ct-encrypted

SC.L2-3.13.16, SC.L2-3.13.6 Encryption at rest is crucial for protecting sensitive data stored in EFS file systems. Without encryption, data could be vulnerable to unauthorized access if storage systems are compromised. Implementing KMS-based encryption provides strong data protection.

Available in all commercial Regions except Canada West (Calgary). Available in the AWS GovCloud (US) Regions.

efs-file-system-tagged

CM.L2-3.4.1 Proper tagging of EFS file systems is essential for resource management, cost allocation, access control, compliance reporting. Tags enable organizations to categorize resources by purpose, owner, environment, or project, facilitating automated governance policies cost tracking. Consistent tagging practices improve operational visibility support security frameworks that rely on resource classification for appropriate access controls monitoring. Available in all commercial Regions except Asia Pacific (Malaysia), Asia Pacific (New Zealand), Asia Pacific (Taipei), Asia Pacific (Thailand), and Mexico (Central). Not available in the AWS GovCloud (US) Regions.

efs-mount-target-public-accessible

AC.L2-3.1.20, SC.L2-3.13.6 Preventing public access to EFS mount targets is essential for maintaining data security. Public accessibility could expose sensitive file systems to unauthorized access from the internet. Restricting mount targets to private subnets helps protect against unauthorized access. Available in all commercial Regions. Available in the AWS GovCloud (US) Regions.

eks-addon-tagged

CM.L2-3.4.1 Proper tagging of EKS add-ons is essential for resource management, cost allocation, operational visibility. Tags enable organizations to categorize track add-ons by environment, owner, project, or cost center, facilitating accurate billing resource governance. Consistent tagging practices support automated management workflows, security policies, compliance reporting. Without proper tagging, organizations lose visibility into resource ownership usage patterns, making it difficult to optimize costs maintain operational control over their Kubernetes infrastructure components. Available in all commercial Regions except Asia Pacific (Malaysia), Asia Pacific (New Zealand), Asia Pacific (Taipei), Asia Pacific (Thailand), Canada West (Calgary), Israel (Tel Aviv), and Mexico (Central). Not available in the AWS GovCloud (US) Regions.

eks-cluster-log-enabled

AU.L2-3.3.1 Logging is essential for maintaining operational visibility and security monitoring in Kubernetes clusters. Without proper logging, organizations cannot effectively track cluster activities or investigate security incidents. Enabled logging supports better operational insights and security analysis.

Available in all commercial Regions except Asia Pacific (Malaysia), Asia Pacific (New Zealand), Asia Pacific (Taipei), Asia Pacific (Thailand), Canada West (Calgary), Israel (Tel Aviv), and Mexico (Central). Not available in the AWS GovCloud (US) Regions.

eks-cluster-secrets-encrypted

SC.L2-3.13.16 When you encrypt secrets, you can use AWS Key Management Service (AWS KMS) keys to provide envelope encryption of Kubernetes secrets stored in etcd for your cluster. This encryption is in addition to the EBS volume encryption that is enabled by default for all data (including secrets) that is stored in etcd as part of an EKS cluster. Using secrets encryption for your EKS cluster allows you to deploy a defense in depth strategy for Kubernetes applications by encrypting Kubernetes secrets with a KMS key that you define and manage. Available in all commercial Regions except Asia Pacific (Malaysia), Asia Pacific (New Zealand), Asia Pacific (Taipei), Asia Pacific (Thailand), Canada West (Calgary), and Mexico (Central). Available in the AWS GovCloud (US) Regions.

elasticache-rbac-auth-enabled

AC.L2-3.1.2 RBAC authentication provides fine-grained access control for Redis clusters. Without RBAC, managing access to cache resources could be less secure and more difficult to maintain. Implementing RBAC ensures proper authentication and authorization for cache access. Available in all commercial Regions except Asia Pacific (Hyderabad), Asia Pacific (Jakarta), Asia Pacific (Malaysia), Asia Pacific (Melbourne), Asia Pacific (New Zealand), Asia Pacific (Taipei), Asia Pacific (Thailand), Canada West (Calgary), Europe (Spain), Europe (Zurich), Israel (Tel Aviv), Mexico (Central), and Middle East (UAE). Not available in the AWS GovCloud (US) Regions.

elastic-beanstalk-logs-to-cloudwatch

CA.L2-3.12.3, SI.L2-3.14.6 Enhanced health reporting in Elastic Beanstalk provides deeper visibility into application health status beyond basic instance health checks. This capability monitors additional metrics including CPU utilization, application latency, and request rates, enabling more effective troubleshooting and faster incident response. Without enhanced health reporting, organizations may experience delayed detection of performance degradation, potentially resulting in extended service disruptions and negative impact on application availability. Available in all commercial Regions except Asia Pacific (Hyderabad), Asia Pacific (Malaysia), Asia Pacific (Melbourne), Asia Pacific (New Zealand), Asia Pacific (Taipei), Asia Pacific (Thailand), Canada West (Calgary), Europe (Spain), Europe (Zurich), Israel (Tel Aviv), Mexico (Central), and Middle East (UAE). Not available in the AWS GovCloud (US) Regions.

elbv2-acm-certificate-required

SC.L2-3.13.15, SC.L2-3.13.8 SSL certificates provided by AWS Certificate Manager (ACM) on Load balancers facilitate the management of certificates, keep data secure and prevent data in transit from Man in the Middle attacks.

Available in all commercial Regions except Asia Pacific (Hyderabad), Asia Pacific (Jakarta), Asia Pacific (Malaysia), Asia Pacific (Melbourne), Asia Pacific (New Zealand), Asia Pacific (Osaka), Asia Pacific (Taipei), Asia Pacific (Thailand), Canada West (Calgary), Europe (Spain), Europe (Zurich), Israel (Tel Aviv), Mexico (Central), and Middle East (UAE). Not available in the AWS GovCloud (US) Regions.

elbv2-listener-encryption-in-transit

SC.L2-3.13.1, SC.L2-3.13.8 To encrypt data thats transmitted between a client and a load balancer, Elastic Load Balancer listeners should be configured to use industry-standard security protocols: HTTPS for Application Load Balancers, or TLS for Network Load Balancers. Otherwise, data thats transmitted between a client and a load balancer is vulnerable to interception, tampering, and unauthorized access. Use of HTTPS or TLS by a listener aligns with security best practices and helps ensure the confidentiality and integrity of data during transmission. This is particularly important for applications that handle sensitive information, or must comply with security standards that require encryption of data in transit.

Available in all commercial Regions except Asia Pacific (Hyderabad), Asia Pacific (Melbourne), Canada West (Calgary), Europe (Spain), Europe (Zurich), and Middle East (UAE). Available in the AWS GovCloud (US) Regions.

elb-acm-certificate-required

SC.L2-3.13.8 Encrypt data in transit to maintain the confidentiality and integrity of data as it traverses public and unsecured networks and reduce the risk of unauthorized access to data.

Available in all commercial Regions except Africa (Cape Town), Asia Pacific (New Zealand), Asia Pacific (Osaka), Canada West (Calgary), Europe (Milan), Europe (Spain), Europe (Zurich), and Israel (Tel Aviv). Available in the AWS GovCloud (US) Regions.

elb-internal-scheme-check

SC.L2-3.13.1 Internal load balancer schemes provide an additional layer of network security by restricting access to applications and services from within the VPC only, preventing direct internet exposure. This configuration helps reduce the attack surface, supports network segmentation strategies, and ensures that sensitive internal applications are not inadvertently exposed to external traffic. Monitoring load balancer schemes helps maintain proper network boundaries and supports compliance with security frameworks that require internal service isolation. Available in all commercial Regions except Asia Pacific (Malaysia), Asia Pacific (New Zealand), Asia Pacific (Taipei), Asia Pacific (Thailand), and Mexico (Central). Not available in the AWS GovCloud (US) Regions.

elb-tagged

CM.L2-3.4.1 Proper tagging of Classic Load Balancers enables effective resource management, cost allocation, and governance. Tags provide essential metadata for identifying resource ownership, environment classification, cost center attribution, and compliance tracking. Consistent tagging practices facilitate automated resource management, security policy enforcement, and operational visibility across the infrastructure. This control helps ensure organizational tagging standards are maintained and supports audit requirements for resource accountability. Available in all commercial Regions except Asia Pacific (Malaysia), Asia Pacific (New Zealand), Asia Pacific (Taipei), Asia Pacific (Thailand), and Mexico (Central). Not available in the AWS GovCloud (US) Regions.

elb-tls-https-listeners-only

SC.L2-3.13.15, SC.L2-3.13.8 Custom TLS policies for listeners on AWS Load Balancers help you be compatible, or disable certain TLS protocol versions to meet your organization's security compliance standards and manage connections between the client and the load balancer effectively.

Available in all commercial Regions. Available in the AWS GovCloud (US) Regions.

emr-master-no-public-ip

SC.L2-3.13.6 Disallowing public IP addresses for cluster master nodes isolates the cluster from the public internet which reduces the attack surface and minimizes the risk of unauthorized access.

Available in all commercial Regions. Available in the AWS GovCloud (US) Regions.

emr-security-configuration-encryption-rest

SC.L2-3.13.16 Encryption at rest for Amazon EMR clusters protects sensitive data stored on cluster instances from unauthorized access. This control helps ensure compliance with data protection regulations and security best practices by detecting EMR configurations that lack proper encryption settings. Monitoring encryption configuration helps prevent data exposure risks and maintains data confidentiality for big data processing workloads. Available in all commercial Regions except Asia Pacific (New Zealand), Asia Pacific (Taipei), Asia Pacific (Thailand), and Mexico (Central). Not available in the AWS GovCloud (US) Regions.

emr-security-configuration-encryption-transit

SC.L2-3.13.1, SC.L2-3.13.8 Data in transit refers to data that moves from one location to another, such as between nodes in your cluster or between your cluster and your application. Data may move across the internet or within a private network. Encrypting data in transit reduces the risk that an unauthorized user can eavesdrop on network traffic. Available in all commercial Regions except Asia Pacific (New Zealand), Asia Pacific (Taipei), Asia Pacific (Thailand), and Mexico (Central). Not available in the AWS GovCloud (US) Regions.

encrypted-volumes

SC.L2-3.13.6 Encrypting data at rest on EBS volumes facilitates protection of data from unauthorized access and rendering the data unreadable and unusable to an unauthorized actor.

Available in all commercial Regions. Available in the AWS GovCloud (US) Regions.

evidently-launch-tagged

CM.L2-3.4.1 Tagging Evidently launches is crucial for maintaining operational visibility and resource management. Proper tagging enables effective resource tracking, cost allocation, and access control. Without structured tagging, organizations may struggle to manage and monitor their feature launches effectively. Available only in US East (N. Virginia), US East (Ohio), US West (Oregon), Asia Pacific (Singapore), Asia Pacific (Sydney), Asia Pacific (Tokyo), Europe (Frankfurt), Europe (Ireland), and Europe (Stockholm). Not available in the AWS GovCloud (US) Regions.

evidently-project-tagged

CM.L2-3.4.1 Proper tagging of Evidently projects is essential for maintaining project organization and visibility. Tags enable effective resource management, cost tracking, and access control. Without structured tagging, organizations risk losing oversight of their experimentation projects. Available only in US East (N. Virginia), US East (Ohio), US West (Oregon), Asia Pacific (Singapore), Asia Pacific (Sydney), Asia Pacific (Tokyo), Europe (Frankfurt), Europe (Ireland), and Europe (Stockholm). Not available in the AWS GovCloud (US) Regions.

evidently-segment-tagged

CM.L2-3.4.1 Tagging Evidently segments is crucial for maintaining clear visibility and control over user segmentation. Proper tagging enables efficient resource management, accurate cost allocation, and granular access controls. Without structured tagging, organizations may face challenges in managing and analyzing their user segments effectively. Available only in US East (N. Virginia), US East (Ohio), US West (Oregon), Asia Pacific (Singapore), Asia Pacific (Sydney), Asia Pacific (Tokyo), Europe (Frankfurt), Europe (Ireland), and Europe (Stockholm). Not available in the AWS GovCloud (US) Regions.

fis-experiment-template-log-configuration-exists

AU.L2-3.3.1 Experiment logging is essential for maintaining visibility into chaos engineering activities fault injection experiments. Proper logging enables security teams to monitor experiment execution, track changes to infrastructure during testing, maintain audit trails for compliance purposes. Without logging configuration, organizations lose critical visibility into potentially disruptive testing activities, making it difficult to correlate system behavior changes with experiment actions hindering incident response forensic analysis capabilities. Available in all commercial Regions except Asia Pacific (Hyderabad), Asia Pacific (Jakarta), Asia Pacific (Malaysia), Asia Pacific (Melbourne), Asia Pacific (New Zealand), Asia Pacific (Osaka), Asia Pacific (Taipei), Asia Pacific (Thailand), Canada West (Calgary), Europe (Zurich), Israel (Tel Aviv), Mexico (Central), and Middle East (UAE). Not available in the AWS GovCloud (US) Regions.

fis-experiment-template-tagged

CM.L2-3.4.1 Proper tagging of FIS experiment templates enables effective resource management, cost allocation, governance oversight of chaos engineering activities. Tags facilitate tracking experiment ownership, categorizing test scenarios by environment or application, implementing automated policies for experiment lifecycle management. Consistent tagging practices also support compliance requirements help organizations maintain visibility into their fault injection testing activities across different teams projects. Available in all commercial Regions except Asia Pacific (Hyderabad), Asia Pacific (Jakarta), Asia Pacific (Malaysia), Asia Pacific (Melbourne), Asia Pacific (New Zealand), Asia Pacific (Osaka), Asia Pacific (Taipei), Asia Pacific (Thailand), Canada West (Calgary), Europe (Zurich), Israel (Tel Aviv), Mexico (Central), and Middle East (UAE). Not available in the AWS GovCloud (US) Regions.

fsx-last-backup-recovery-point-created

MP.L2-3.8.9 Regular recovery point creation is essential for maintaining data resilience and enabling quick recovery in case of data loss or corruption. Without recent recovery points, organizations risk extended downtime or permanent data loss. Implementing regular backups provides a reliable mechanism for data protection and business continuity. Available in all commercial Regions except Asia Pacific (Malaysia), Asia Pacific (New Zealand), Asia Pacific (Taipei), Asia Pacific (Thailand), Canada West (Calgary), Israel (Tel Aviv), and Mexico (Central). Available in the AWS GovCloud (US) Regions.

fsx-lustre-copy-tags-to-backups

CM.L2-3.4.1 Identification and inventory of your IT assets is an important aspect of governance and security. Tags help you categorize your AWS resources in different ways, for example, by purpose, owner, or environment. This is useful when you have many resources of the same type because you can quickly identify a specific resource based on the tags that you assigned to it. Available in all commercial Regions except Asia Pacific (Malaysia), Asia Pacific (New Zealand), Asia Pacific (Taipei), Asia Pacific (Thailand), Canada West (Calgary), and Mexico (Central). Not available in the AWS GovCloud (US) Regions.

fsx-windows-audit-log-configured

AU.L2-3.3.1 File access auditing is crucial for maintaining security visibility and compliance in file storage environments. Without proper auditing, organizations cannot track who accessed sensitive files or detect potential security incidents. Enabling file access auditing supports security monitoring and forensic investigations. Available in all commercial Regions except Asia Pacific (Malaysia), Asia Pacific (Melbourne), Asia Pacific (New Zealand), Asia Pacific (Taipei), Asia Pacific (Thailand), Canada West (Calgary), Israel (Tel Aviv), and Mexico (Central). Not available in the AWS GovCloud (US) Regions.

glb-listener-tagged

CM.L2-3.4.1 Proper tagging of Gateway Load Balancer listeners enables effective resource management, cost allocation, operational governance. Tags provide essential metadata for tracking resource ownership, environment classification, billing attribution, automated management processes. Consistent tagging practices improve visibility into network infrastructure components, facilitate compliance reporting, support security policies that rely on resource categorization. Without proper tagging, organizations lose critical context for managing load balancer resources may face challenges in cost optimization operational oversight. Available in all commercial Regions except Asia Pacific (Hyderabad), Asia Pacific (Jakarta), Asia Pacific (Malaysia), Asia Pacific (Melbourne), Asia Pacific (New Zealand), Asia Pacific (Taipei), Asia Pacific (Thailand), Canada West (Calgary), Europe (Spain), Europe (Zurich), Israel (Tel Aviv), Mexico (Central), and Middle East (UAE). Not available in the AWS GovCloud (US) Regions.

glb-tagged

CM.L2-3.4.1 Proper tagging of Gateway Load Balancers enables effective resource management, cost allocation, governance. Tags facilitate automated operations, help track resource ownership purpose, support compliance reporting, enable consistent application of security policies. Without adequate tagging, organizations lose visibility into resource utilization, struggle with cost management, may fail to meet regulatory requirements for asset tracking accountability. Available in all commercial Regions except Asia Pacific (Malaysia), Asia Pacific (New Zealand), Asia Pacific (Taipei), Asia Pacific (Thailand), and Mexico (Central). Not available in the AWS GovCloud (US) Regions.

glue-job-logging-enabled

AU.L2-3.3.1 Logging Glue job activities is essential for maintaining operational visibility and security compliance. Without proper logging, organizations cannot effectively monitor ETL processes or investigate potential issues. Enabled logging supports better operational insights and facilitates troubleshooting of data processing workflows.

Available in all commercial Regions except Asia Pacific (Malaysia), Asia Pacific (New Zealand), Asia Pacific (Taipei), Asia Pacific (Thailand), Canada West (Calgary), and Mexico (Central). Available in the AWS GovCloud (US) Regions.

glue-ml-transform-encrypted-at-rest

SC.L2-3.13.16 Encryption at rest is crucial for protecting sensitive ML data and models from unauthorized access. Without encryption, ML-related data could be vulnerable if storage systems are compromised. Implementing encryption adds an essential layer of security for machine learning assets.

Available in all commercial Regions. Available in AWS GovCloud (US-West).

guardduty-ec2-protection-runtime-enabled

SI.L2-3.14.7 GuardDuty Runtime Monitoring observes and analyzes operating system-level, networking, and file events to help you detect potential threats in specific AWS workloads in your environment. It uses GuardDuty security agents that add visibility into runtime behavior, such as file access, process execution, command line arguments, and network connections. You can enable and manage the security agent for each type of resource that you want to monitor for potential threats. This includes Amazon EC2 instances. Available in all commercial Regions except Asia Pacific (Taipei), Canada West (Calgary), and Mexico (Central). Not available in the AWS GovCloud (US) Regions.

guardduty-ecs-protection-runtime-enabled

CA.L2-3.12.3, SI.L2-3.14.6, SI.L2-3.14.7 Enabling ECS Runtime Monitoring with automated agent management in GuardDuty provides continuous threat detection security monitoring for containerized workloads running on Amazon ECS. This capability detects malicious activities, suspicious network communications, potential security threats within ECS tasks containers at runtime. Automated agent management ensures consistent deployment maintenance of monitoring agents across ECS infrastructure without manual intervention, reducing the risk of security gaps improving operational efficiency. This monitoring is essential for maintaining security visibility in containerized environments meeting compliance requirements for runtime threat detection. Available in all commercial Regions except Canada West (Calgary). Not available in the AWS GovCloud (US) Regions.

guardduty-eks-protection-audit-enabled

CA.L2-3.12.3, SI.L2-3.14.3, SI.L2-3.14.6 EKS Audit Log Monitoring is crucial for maintaining security visibility in Kubernetes environments. Without this feature, organizations may miss important security events and potential threats in their EKS clusters. Enabling this GuardDuty feature enhances threat detection capabilities for containerized workloads. Available in all commercial Regions. Available in the AWS GovCloud (US) Regions.

guardduty-eks-protection-runtime-enabled

CA.L2-3.12.3, SI.L2-3.14.3, SI.L2-3.14.6 EKS Protection in Amazon GuardDuty provides threat detection coverage to help you protect Amazon EKS clusters within your AWS environment. EKS Runtime Monitoring uses operating system-level events to help you detect potential threats in EKS nodes and containers within your EKS clusters. Available in all commercial Regions except Asia Pacific (New Zealand), Asia Pacific (Taipei), Asia Pacific (Thailand), Canada West (Calgary), and Mexico (Central). Not available in the AWS GovCloud (US) Regions.

guardduty-enabled-centralized

SI.L2-3.14.6, SI.L2-3.14.7 Enabling GuardDuty provides a proactive approach to threat detection and response, helping to identify and respond to potential security threats before they can cause significant harm. By implementing GuardDuty for all regions in all accounts, organizations can better protect their AWS environment and reduce the risk of a security breach.

Available in all commercial Regions except Asia Pacific (New Zealand), Asia Pacific (Taipei), Asia Pacific (Thailand), and Mexico (Central). Available in the AWS GovCloud (US) Regions.

guardduty-lambda-protection-enabled

CA.L2-3.12.3, SI.L2-3.14.3, SI.L2-3.14.6 In a multi-account environment, the control generates findings in only the delegated GuardDuty administrator account. Only the delegated administrator can enable or disable the Lambda Protection feature for the member accounts in the organization. GuardDuty member accounts cant modify this configuration from their accounts. This control generates FAILED findings if the delegated GuardDuty administrator has a suspended member account that doesnt have GuardDuty Lambda Protection enabled. To receive a PASSED finding, the delegated administrator must disassociate these suspended accounts in GuardDuty. Available in all commercial Regions. Available in the AWS GovCloud (US) Regions.

guardduty-malware-protection-enabled

SI.L2-3.14.2, SI.L2-3.14.3 In a multi-account environment, the control generates findings in only the delegated GuardDuty administrator account. Only the delegated administrator can enable or disable the Malware Protection feature for the member accounts in the organization. GuardDuty member accounts cant modify this configuration from their accounts. This control generates FAILED findings if the delegated GuardDuty administrator has a suspended member account that doesnt have GuardDuty Malware Protection enabled. To receive a PASSED finding, the delegated administrator must disassociate these suspended accounts in GuardDuty. Available in all commercial Regions. Not available in the AWS GovCloud (US) Regions.

guardduty-rds-protection-enabled

SI.L2-3.14.2, SI.L2-3.14.3, SI.L2-3.14.6 RDS Protection is crucial for maintaining database security and detecting potential threats. Without this feature, organizations may miss security incidents targeting their database instances. Enabling RDS Protection provides enhanced security monitoring for database environments. Available in all commercial Regions except Asia Pacific (New Zealand), Asia Pacific (Taipei), Canada West (Calgary), and Mexico (Central). Not available in the AWS GovCloud (US) Regions.

guardduty-runtime-monitoring-enabled

CA.L2-3.12.3, SI.L2-3.14.6, SI.L2-3.14.7 Runtime Monitoring in Amazon GuardDuty provides enhanced threat detection capabilities by analyzing runtime behavior patterns identifying malicious activities that may not be detected through traditional monitoring methods. Enabling this feature strengthens your security posture by providing real-time visibility into potential threats, improving incident response times, helping meet compliance requirements for continuous security monitoring. Without Runtime Monitoring enabled, organizations may miss critical security events face increased exposure to advanced persistent threats runtime-based attacks. Available in all commercial Regions except Canada West (Calgary). Not available in the AWS GovCloud (US) Regions.

guardduty-s3-protection-enabled

SI.L2-3.14.6, SI.L2-3.14.7 S3 Protection is essential for maintaining security visibility over storage resources. Without this feature, organizations may miss potential security threats targeting their S3 buckets. Enabling S3 Protection enhances threat detection capabilities for storage environments. Available in all commercial Regions. Available in the AWS GovCloud (US) Regions.

iam-oidc-provider-tagged

CM.L2-3.4.1 Tagging IAM OIDC identity providers is essential for resource management, cost allocation, security governance. Tags enable organizations to categorize track identity providers, implement automated security policies, ensure proper access controls, maintain compliance with organizational standards. Consistent tagging practices also facilitate resource discovery, ownership identification, lifecycle management of identity federation components. Available only in US East (N. Virginia). Not available in the AWS GovCloud (US) Regions.

iam-password-policy

IA.L2-3.5.2, IA.L2-3.5.7, IA.L2-3.5.8 Attackers can launch a brute force attack and retrieve weak passwords if they do not meet specified requirements. Ensure to setup and enforce strong password configuration requirements to mitigate the risk of password guessing, brute force or dictionary attacks, which could lead to unauthorized access to sensitive data.

Available in all commercial Regions. Available in the AWS GovCloud (US) Regions.

iam-policy-blacklisted-check

AC.L2-3.1.1, AC.L2-3.1.2, AC.L2-3.1.5, AC.L2-3.1.7, AU.L2-3.3.9, SC.L2-3.13.3 By validating that policies are not attached to user, group, or role resource types, mitigation of risks of unauthorized access, privilege escalation, or policy violations can be mitigated and ensure compliance with least privilege principles applicable to security best practices and regulatory compliance.

Available in all commercial Regions except Asia Pacific (Hyderabad), Asia Pacific (Malaysia), Asia Pacific (Melbourne), Asia Pacific (New Zealand), Asia Pacific (Taipei), Asia Pacific (Thailand), Canada West (Calgary), Europe (Spain), Europe (Zurich), Israel (Tel Aviv), Mexico (Central), and Middle East (UAE). Available in the AWS GovCloud (US) Regions.

iam-policy-no-statements-with-admin-access

AC.L2-3.1.4 To ensure the confidentiality, integrity and availability of AWS resources from accidental or malicious activity, IAM policies containing full administrative privileges must not be permitted.

Available in all commercial Regions except Asia Pacific (Hyderabad), Asia Pacific (Malaysia), Asia Pacific (Melbourne), Asia Pacific (New Zealand), Asia Pacific (Taipei), Asia Pacific (Thailand), Canada West (Calgary), Europe (Spain), Europe (Zurich), Israel (Tel Aviv), Mexico (Central), and Middle East (UAE). Available in the AWS GovCloud (US) Regions.

iam-policy-no-statements-with-full-access

AC.L2-3.1.1, AC.L2-3.1.2, AC.L2-3.1.5, AC.L2-3.1.7, AU.L2-3.3.8, AU.L2-3.3.9, SC.L2-3.13.3, SC.L2-3.13.4 Restricting policy statements from allowing all actions on resources in AWS IAM is a critical control that enforces the principle of least privilege, strengthens access controls, mitigates risks, ensures compliance, and enhances auditing and accountability. It helps organizations maintain a secure and well-governed AWS environment by granting only the necessary permissions to IAM entities.

Available in all commercial Regions except Asia Pacific (Hyderabad), Asia Pacific (Malaysia), Asia Pacific (Melbourne), Asia Pacific (New Zealand), Asia Pacific (Taipei), Asia Pacific (Thailand), Canada West (Calgary), Europe (Spain), Europe (Zurich), Israel (Tel Aviv), Mexico (Central), and Middle East (UAE). Available in the AWS GovCloud (US) Regions.

iam-saml-provider-tagged

CM.L2-3.4.1 Proper tagging of IAM SAML identity providers is essential for resource management, cost allocation, security governance. Tags enable organizations to categorize track identity providers, implement automated policies, maintain compliance with internal governance standards. Untagged SAML providers can lead to difficulties in resource identification, cost tracking, may indicate resources that were created outside of established provisioning processes. This control helps ensure consistent application of organizational tagging strategies across identity access management resources. Available only in US East (N. Virginia). Not available in the AWS GovCloud (US) Regions.

iam-server-certificate-expiration-check

SC.L2-3.13.10 Expired SSL/TLS server certificates left in IAM can be inadvertently associated with resources, causing failed or insecure connections and weakening trust in the certificate chain. Promptly removing expired certificates reduces the risk of outages and of clients negotiating connections with invalid credentials, and keeps the certificate inventory accurate.

Available only in US East (N. Virginia). Available in AWS GovCloud (US-West).

iam-server-certificate-tagged

CM.L2-3.4.1 Tagging IAM server certificates is essential for effective resource management, cost allocation, security governance. Tags enable organizations to categorize certificates by environment, application, owner, or purpose, facilitating easier identification management of SSL/TLS certificates. Proper tagging supports compliance requirements, enables automated certificate lifecycle management, helps track certificate usage across different applications, ensures accountability for certificate ownership. Without consistent tagging, organizations may struggle to maintain visibility into their certificate inventory, leading to potential security risks from expired or unused certificates. Available only in US East (N. Virginia). Not available in the AWS GovCloud (US) Regions.

iam-user-mfa-enabled

IA.L2-3.5.3, MA.L2-3.7.5 MFA adds an extra layer of security to user authentication by requiring users to provide a second form of authentication, such as a security token. This helps protect resources from unauthorized access, meets compliance requirements, and enhances the security of your overall environment.

Available in all commercial Regions except Asia Pacific (Hyderabad), Asia Pacific (Malaysia), Asia Pacific (Melbourne), Asia Pacific (New Zealand), Asia Pacific (Taipei), Asia Pacific (Thailand), Canada West (Calgary), Europe (Spain), Europe (Zurich), Israel (Tel Aviv), Mexico (Central), and Middle East (UAE). Available in the AWS GovCloud (US) Regions.

iam-user-no-policies-check

AC.L2-3.1.1, AC.L2-3.1.2, AC.L2-3.1.7, AU.L2-3.3.9, SC.L2-3.13.3 By validating that policies are not attached to user, group, or role resource types, mitigation of risks of unauthorized access, privilege escalation, or policy violations can be mitigated and ensure compliance with least privilege principles applicable to security best practices and regulatory compliance.

Available in all commercial Regions except Asia Pacific (Hyderabad), Asia Pacific (Malaysia), Asia Pacific (Melbourne), Asia Pacific (New Zealand), Asia Pacific (Taipei), Asia Pacific (Thailand), Canada West (Calgary), Europe (Spain), Europe (Zurich), Israel (Tel Aviv), Mexico (Central), and Middle East (UAE). Available in the AWS GovCloud (US) Regions.

iam-user-unused-credentials-check

AC.L2-3.1.2 Unused IAM credentials can pose security risks if compromised. This identification will facilitate the removal of credentials to reduce the risk of unauthorized access to AWS resources.

Available in all commercial Regions except Asia Pacific (Hyderabad), Asia Pacific (Malaysia), Asia Pacific (Melbourne), Asia Pacific (New Zealand), Asia Pacific (Taipei), Asia Pacific (Thailand), Canada West (Calgary), Europe (Spain), Europe (Zurich), Israel (Tel Aviv), Mexico (Central), and Middle East (UAE). Available in the AWS GovCloud (US) Regions.

restricted-ssh

AC.L2-3.1.3, SC.L2-3.13.1 It is recommended that no security group allows unrestricted ingress access to secure remote access services. Traffic should be scoped to a narrow range of IP addresses required for specific business needs to reduce risk of exposure.

Available in all commercial Regions. Available in the AWS GovCloud (US) Regions.

inspector-ec2-scan-enabled

RA.L2-3.11.2 Amazon Inspector EC2 scanning extracts metadata from your Amazon Elastic Compute Cloud (Amazon EC2) instance, and then compares this metadata against rules collected from security advisories to produce findings. Amazon Inspector scans instances for package vulnerabilities and network reachability issues. For information about supported operating systems, including which operating system can be scanned without an SSM agent, see Supported operating systems: Amazon EC2 scanning. Available in all commercial Regions except Asia Pacific (Hyderabad), Asia Pacific (Melbourne), Asia Pacific (New Zealand), Canada West (Calgary), Europe (Spain), Mexico (Central), and Middle East (UAE). Available in the AWS GovCloud (US) Regions.

inspector-ecr-scan-enabled

RA.L2-3.11.2, SI.L2-3.14.5 Container image scanning is essential for maintaining security in containerized environments. Without regular scanning, organizations may deploy containers with known vulnerabilities. Implementing automated ECR scanning helps ensure container image security. Available in all commercial Regions except Asia Pacific (Hyderabad), Asia Pacific (Melbourne), Asia Pacific (New Zealand), Canada West (Calgary), Europe (Spain), Mexico (Central), and Middle East (UAE). Available in the AWS GovCloud (US) Regions.

inspector-lambda-code-scan-enabled

RA.L2-3.11.2 Lambda code scanning is crucial for maintaining security in serverless architectures. Without code scanning, organizations may deploy functions with security weaknesses. Implementing automated code scanning helps identify and address potential vulnerabilities in Lambda functions. Available only in US East (N. Virginia), US East (Ohio), US West (Oregon), Asia Pacific (Singapore), Asia Pacific (Sydney), Asia Pacific (Tokyo), Europe (Frankfurt), Europe (Ireland), Europe (London), and Europe (Stockholm). Not available in the AWS GovCloud (US) Regions.

inspector-lambda-standard-scan-enabled

RA.L2-3.11.2 Standard Lambda scanning is essential for maintaining security in serverless architectures. Without regular scanning, organizations may miss potential vulnerabilities in their Lambda runtime environments. Implementing standard scanning helps ensure comprehensive Lambda function security. Available in all commercial Regions except Asia Pacific (Hyderabad), Asia Pacific (Melbourne), Asia Pacific (New Zealand), Canada West (Calgary), Europe (Spain), and Middle East (UAE). Available in the AWS GovCloud (US) Regions.

internet-gateway-authorized-vpc-only

AC.L2-3.1.3, SC.L2-3.13.1 This control provides a mechanism that forces attention on which VPC(s) should be allowed to access the public internet. This control will require the appropriate VPC(s) to be identified and labeled as approved for internet accesses through use of an IGW. Failure to identify and validate the list of authorized VPC's could cause unintended access to AWS resources.

Available in all commercial Regions. Available in the AWS GovCloud (US) Regions.

iotdevicedefender-custom-metric-tagged

CM.L2-3.4.1 Proper tagging of IoT Device Defender custom metrics enables effective resource management, cost allocation, and governance across IoT monitoring infrastructure. Tags facilitate automated resource discovery, support compliance reporting requirements, and enable granular access control policies. Consistent tagging practices improve operational visibility and help organizations track resource ownership, environment classification, and billing attribution for their IoT security monitoring capabilities. Available only in US East (N. Virginia), US East (Ohio), US West (N. California), US West (Oregon), Asia Pacific (Hong Kong), Asia Pacific (Mumbai), Asia Pacific (Seoul), Asia Pacific (Singapore), Asia Pacific (Sydney), Asia Pacific (Tokyo), Canada (Central), Europe (Frankfurt), Europe (Ireland), Europe (London), Europe (Paris), Europe (Stockholm), Middle East (Bahrain), and Middle East (UAE). Not available in the AWS GovCloud (US) Regions.

iotsitewise-asset-model-tagged

CM.L2-3.4.1 Proper tagging of IoT asset models is crucial for maintaining operational visibility and control. Without structured tagging, organizations may struggle to manage and track their industrial asset configurations effectively. Tags enable efficient resource management and access control. Available only in US East (N. Virginia), US East (Ohio), US West (Oregon), Asia Pacific (Mumbai), Asia Pacific (Seoul), Asia Pacific (Singapore), Asia Pacific (Sydney), Asia Pacific (Tokyo), Canada (Central), Europe (Frankfurt), and Europe (Ireland). Not available in the AWS GovCloud (US) Regions.

iotsitewise-dashboard-tagged

CM.L2-3.4.1 Proper tagging IoT dashboards is essential for maintaining clear visibility and control over industrial monitoring interfaces. Proper tagging enables efficient resource management and access control. Without structured tagging, organizations risk losing oversight of their visualization resources. Available only in US East (N. Virginia), US East (Ohio), US West (Oregon), Asia Pacific (Mumbai), Asia Pacific (Seoul), Asia Pacific (Singapore), Asia Pacific (Sydney), Asia Pacific (Tokyo), Canada (Central), Europe (Frankfurt), and Europe (Ireland). Not available in the AWS GovCloud (US) Regions.

iotsitewise-gateway-tagged

CM.L2-3.4.1 Proper tagging IoT gateways is crucial for maintaining operational control and visibility of industrial edge devices. Without proper tagging, organizations may face challenges in managing their IoT gateway infrastructure. Implementing structured tagging supports efficient device management and security control. Available only in US East (N. Virginia), US East (Ohio), US West (Oregon), Asia Pacific (Mumbai), Asia Pacific (Seoul), Asia Pacific (Singapore), Asia Pacific (Sydney), Asia Pacific (Tokyo), Canada (Central), Europe (Frankfurt), and Europe (Ireland). Not available in the AWS GovCloud (US) Regions.

iotsitewise-portal-tagged

CM.L2-3.4.1 Proper tagging IoT portals is essential for maintaining visibility and control over industrial web interfaces. Without structured tagging, organizations may struggle to manage access and resources effectively. Proper tagging facilitates efficient portal management and security control. Available only in US East (N. Virginia), US East (Ohio), US West (Oregon), Asia Pacific (Mumbai), Asia Pacific (Seoul), Asia Pacific (Singapore), Asia Pacific (Sydney), Asia Pacific (Tokyo), Canada (Central), Europe (Frankfurt), and Europe (Ireland). Not available in the AWS GovCloud (US) Regions.

iotsitewise-project-tagged

CM.L2-3.4.1 Proper tagging IoT projects is crucial for maintaining clear visibility and control over industrial IoT initiatives. Without proper tagging, organizations may lose track of project resources and responsibilities. Implementing structured tagging supports efficient project management and goverce. Available only in US East (N. Virginia), US East (Ohio), US West (Oregon), Asia Pacific (Mumbai), Asia Pacific (Seoul), Asia Pacific (Singapore), Asia Pacific (Sydney), Asia Pacific (Tokyo), Canada (Central), Europe (Frankfurt), and Europe (Ireland). Not available in the AWS GovCloud (US) Regions.

iottwinmaker-component-type-tagged

CM.L2-3.4.1 Proper tagging of IoT TwinMaker component types enables effective resource management, cost allocation, and governance across digital twin implementations. Tags facilitate automated resource discovery, support compliance reporting requirements, and enable granular access control policies. Consistent tagging practices improve operational visibility and help organizations track resource ownership, project attribution, and lifecycle management of their digital twin components. Available only in US East (N. Virginia), US West (Oregon), Asia Pacific (Mumbai), Asia Pacific (Seoul), Asia Pacific (Singapore), Asia Pacific (Sydney), Asia Pacific (Tokyo), Europe (Frankfurt), and Europe (Ireland). Not available in the AWS GovCloud (US) Regions.

iot-authorizer-token-signing-enabled

CM.L2-3.4.2 Enabling token signing requirements for IoT authorizers is critical for maintaining secure authentication and authorization in IoT environments. Token signing provides cryptographic assurance that authorization tokens have not been tampered with and originate from trusted sources. Without proper token signature validation, unauthorized devices or malicious actors could potentially forge or manipulate tokens to gain unauthorized access to IoT resources and data. This control helps ensure the integrity of the authorization process and prevents token-based attacks in IoT deployments. Available in all commercial Regions except Africa (Cape Town), Asia Pacific (Hyderabad), Asia Pacific (Jakarta), Asia Pacific (Malaysia), Asia Pacific (Melbourne), Asia Pacific (New Zealand), Asia Pacific (Osaka), Asia Pacific (Taipei), Asia Pacific (Thailand), Canada West (Calgary), Europe (Milan), Europe (Spain), Europe (Zurich), Israel (Tel Aviv), and Mexico (Central). Not available in the AWS GovCloud (US) Regions.

iot-job-template-tagged

CM.L2-3.4.1 Tagging IoT job templates is essential for maintaining proper resource governance, enabling accurate cost tracking and allocation, and supporting automated resource management workflows. Tags facilitate resource organization, access control policies, and compliance reporting. Without proper tagging, organizations lose visibility into resource ownership, struggle with cost optimization, and face challenges in implementing consistent security and operational policies across their IoT infrastructure. Available in all commercial Regions except Africa (Cape Town), Asia Pacific (Hyderabad), Asia Pacific (Jakarta), Asia Pacific (Malaysia), Asia Pacific (Melbourne), Asia Pacific (New Zealand), Asia Pacific (Osaka), Asia Pacific (Taipei), Asia Pacific (Thailand), Canada West (Calgary), Europe (Milan), Europe (Spain), Europe (Zurich), Israel (Tel Aviv), and Mexico (Central). Not available in the AWS GovCloud (US) Regions.

ivs-channel-playback-authorization-enabled

AC.L2-3.1.2, AU.L2-3.3.1 Enabling playback authorization on IVS channels provides essential access control mechanisms for video streaming content. This control helps prevent unauthorized viewing of video streams, protects sensitive or premium content from being accessed without proper authentication, and ensures compliance with content distribution policies. Playback authorization allows organizations to implement viewer authentication, token-based access control, and content protection strategies that are critical for maintaining the security and integrity of video streaming services. Available only in US East (N. Virginia), US West (Oregon), Asia Pacific (Mumbai), Asia Pacific (Seoul), Asia Pacific (Tokyo), Europe (Frankfurt), and Europe (Ireland). Not available in the AWS GovCloud (US) Regions.

kinesis-firehose-delivery-stream-encrypted

SC.L2-3.13.16 Encryption of streaming data is essential for maintaining data security and compliance. Without encryption, sensitive data could be vulnerable to unauthorized access. Implementing server-side encryption provides crucial protection for streaming data at rest. Available in all commercial Regions. Available in the AWS GovCloud (US) Regions.

kms-key-policy-no-public-access

AC.L2-3.1.1, AC.L2-3.1.5 Restricting public access to KMS keys is essential for maintaining encryption security. Public exposure of encryption keys could compromise data security across multiple services. Implementing strict access controls on KMS keys helps prevent unauthorized key usage.

Available in all commercial Regions except Canada West (Calgary). Not available in the AWS GovCloud (US) Regions.

kms-key-tagged

CM.L2-3.4.1 Tagging KMS keys is essential for proper resource management, cost allocation, and security governance. Tags enable organizations to categorize encryption keys by purpose, owner, environment, or compliance requirements, facilitating easier key lifecycle management and access control policies. Proper tagging also supports automated security processes, audit trails, and helps ensure encryption keys can be quickly identified and managed according to organizational policies and regulatory requirements. Available in all commercial Regions except Asia Pacific (Malaysia), Asia Pacific (New Zealand), Asia Pacific (Taipei), Asia Pacific (Thailand), and Mexico (Central). Not available in the AWS GovCloud (US) Regions.

lambda-function-xray-enabled

AU.L2-3.3.1, SI.L2-3.14.7 Enabling AWS X-Ray tracing on Lambda functions provides critical visibility into application performance, request flows, and potential bottlenecks in serverless architectures. X-Ray tracing enables developers and operations teams to identify performance issues, debug errors, and understand service dependencies across distributed applications. This monitoring capability is essential for maintaining application reliability, optimizing performance, and meeting operational excellence standards in production environments.

Available in all commercial Regions. Available in the AWS GovCloud (US) Regions.

lightsail-bucket-tagged

CM.L2-3.4.1 Tagging Lightsail buckets enables proper resource management, cost allocation, and organizational governance. Tags facilitate automated resource discovery, help track ownership and purpose, support billing categorization, and ensure compliance with organizational policies. Without proper tagging, organizations lose visibility into resource utilization and struggle to maintain effective cloud governance practices. Available only in US East (N. Virginia), US East (Ohio), US West (Oregon), Asia Pacific (Mumbai), Asia Pacific (Seoul), Asia Pacific (Singapore), Asia Pacific (Sydney), Asia Pacific (Tokyo), Canada (Central), Europe (Frankfurt), Europe (Ireland), Europe (London), Europe (Paris), and Europe (Stockholm). Not available in the AWS GovCloud (US) Regions.

lightsail-certificate-tagged

CM.L2-3.4.1 Tagging Lightsail certificates enables proper resource management, cost allocation, and governance. Tags provide essential metadata for tracking certificate ownership, purpose, and lifecycle management. Consistent tagging practices improve operational visibility, facilitate automated management tasks, and support compliance requirements by ensuring all SSL/TLS certificates can be properly identified and categorized within the infrastructure. Available only in US East (N. Virginia), US East (Ohio), US West (Oregon), Asia Pacific (Mumbai), Asia Pacific (Seoul), Asia Pacific (Singapore), Asia Pacific (Sydney), Asia Pacific (Tokyo), Canada (Central), Europe (Frankfurt), Europe (Ireland), Europe (London), Europe (Paris), and Europe (Stockholm). Not available in the AWS GovCloud (US) Regions.

lightsail-disk-tagged

CM.L2-3.4.1 Proper tagging of Lightsail disks enables effective resource management, cost allocation, and operational visibility. Tags facilitate automated governance policies, help track resource ownership and purpose, and support compliance requirements for asset identification. Without consistent tagging, organizations lose visibility into resource utilization, struggle with cost attribution, and face challenges in implementing automated management workflows. Available only in US East (N. Virginia), US East (Ohio), US West (Oregon), Asia Pacific (Mumbai), Asia Pacific (Seoul), Asia Pacific (Singapore), Asia Pacific (Sydney), Asia Pacific (Tokyo), Canada (Central), Europe (Frankfurt), Europe (Ireland), Europe (London), Europe (Paris), and Europe (Stockholm). Not available in the AWS GovCloud (US) Regions.

mq-active-broker-ldap-authentication

AC.L2-3.1.1 LDAP authentication provides centralized user management and enhanced security controls for Amazon MQ brokers. Using LDAP enables organizations to leverage existing directory services for consistent authentication policies, supports advanced features like group-based authorization, and provides better audit trails for user access. This approach reduces security risks associated with local user accounts and ensures compliance with enterprise identity management standards. Available in all commercial Regions except Asia Pacific (Hyderabad), Asia Pacific (Malaysia), Asia Pacific (New Zealand), Asia Pacific (Taipei), Asia Pacific (Thailand), Canada West (Calgary), Europe (Spain), Europe (Zurich), Israel (Tel Aviv), and Mexico (Central). Not available in the AWS GovCloud (US) Regions.

mq-active-single-instance-broker-storage-type-efs

MA.L2-3.7.1 Using EFS storage type for Amazon MQ ActiveMQ single-instance brokers provides enhanced durability, availability, and performance characteristics compared to other storage options. EFS offers automatic scaling, built-in redundancy across multiple Availability Zones, and better integration with AWS backup and recovery services. This storage configuration helps ensure message persistence, reduces the risk of data loss during broker failures, and supports better disaster recovery capabilities for messaging infrastructure. Available in all commercial Regions except Asia Pacific (Hyderabad), Asia Pacific (Malaysia), Asia Pacific (New Zealand), Asia Pacific (Taipei), Asia Pacific (Thailand), Canada West (Calgary), Europe (Spain), Europe (Zurich), Israel (Tel Aviv), and Mexico (Central). Not available in the AWS GovCloud (US) Regions.

mq-broker-general-logging-enabled

AU.L2-3.3.1 Enabling general logging on Amazon MQ brokers is essential for security monitoring, operational troubleshooting, and compliance requirements. General logs capture important broker activities, connection events, and operational metrics that are crucial for detecting security incidents, diagnosing performance issues, and maintaining audit trails. Without proper logging, organizations lose visibility into message broker operations and may fail to meet regulatory compliance requirements that mandate comprehensive logging of messaging infrastructure. Available in all commercial Regions except Asia Pacific (Hyderabad), Asia Pacific (Malaysia), Asia Pacific (New Zealand), Asia Pacific (Taipei), Asia Pacific (Thailand), Canada West (Calgary), Europe (Spain), Europe (Zurich), Israel (Tel Aviv), and Mexico (Central). Not available in the AWS GovCloud (US) Regions.

mq-cloudwatch-audit-log-enabled

AU.L2-3.3.1 By publishing ActiveMQ broker logs to CloudWatch Logs, you can create CloudWatch alarms and metrics that increase the visibility of security-related information. Available in all commercial Regions except Asia Pacific (Hyderabad), Asia Pacific (New Zealand), Canada West (Calgary), Europe (Spain), Europe (Zurich), and Mexico (Central). Available in the AWS GovCloud (US) Regions.

mq-no-public-access

SC.L2-3.13.6 Restricting public access to MQ brokers is essential for maintaining messaging security. Public exposure of message brokers could lead to unauthorized access and data breaches. Implementing private access controls helps protect sensitive messaging infrastructure. Available in all commercial Regions except Africa (Cape Town), Asia Pacific (Hyderabad), Asia Pacific (Jakarta), Asia Pacific (Malaysia), Asia Pacific (Melbourne), Asia Pacific (New Zealand), Asia Pacific (Taipei), Asia Pacific (Thailand), Canada West (Calgary), Europe (Spain), Europe (Zurich), Israel (Tel Aviv), Mexico (Central), and Middle East (UAE). Not available in the AWS GovCloud (US) Regions.

msk-cluster-public-access-disabled

AC.L2-3.1.20, AC.L2-3.1.3, SC.L2-3.13.6 Disabling public access on Amazon MSK clusters is critical for maintaining data security and preventing unauthorized access to streaming data. MSK clusters often handle sensitive business data and real-time analytics that should remain within controlled network boundaries. Enabling public access exposes clusters to potential security threats from the internet, including data breaches, unauthorized data consumption, and malicious attacks. Restricting access to private networks ensures that only authorized applications and users within your VPC can connect to the MSK cluster, supporting defense-in-depth security strategies and compliance with data protection regulations.

Available in all commercial Regions except Asia Pacific (Malaysia), Canada West (Calgary), and Mexico (Central). Available in the AWS GovCloud (US) Regions.

msk-cluster-tagged

CM.L2-3.4.1 Proper tagging of MSK clusters is essential for resource management, cost allocation, access control, and operational visibility. Tags enable organizations to categorize resources by environment, owner, project, or cost center, facilitating automated governance policies and billing analysis. Without consistent tagging, organizations lose visibility into resource ownership and usage patterns, making it difficult to implement effective security policies, track costs, and maintain compliance with organizational standards. Available in all commercial Regions except Asia Pacific (Malaysia), Asia Pacific (New Zealand), Asia Pacific (Taipei), Asia Pacific (Thailand), Canada West (Calgary), Israel (Tel Aviv), and Mexico (Central). Not available in the AWS GovCloud (US) Regions.

msk-connect-connector-logging-enabled

AU.L2-3.3.1 Enabling logging for MSK Connect connectors is essential for operational visibility, troubleshooting, and security monitoring. Logs provide critical insights into connector performance, data processing activities, error conditions, and potential security events. Without proper logging, organizations lose the ability to effectively monitor data pipeline operations, diagnose issues, meet compliance requirements for audit trails, and detect suspicious activities or data processing anomalies. Available in all commercial Regions except Africa (Cape Town), Asia Pacific (Hong Kong), Asia Pacific (Hyderabad), Asia Pacific (Melbourne), Asia Pacific (New Zealand), Asia Pacific (Osaka), Asia Pacific (Taipei), Asia Pacific (Thailand), Canada West (Calgary), Europe (Milan), Europe (Spain), Europe (Zurich), Mexico (Central), Middle East (Bahrain), and Middle East (UAE). Not available in the AWS GovCloud (US) Regions.

msk-unrestricted-access-check

AC.L2-3.1.1, AC.L2-3.1.5, IA.L2-3.5.1, IA.L2-3.5.2 Amazon MSK supports client authentication and authorization mechanisms to control access to a cluster. These mechanisms verify the identity of clients connecting to the cluster and determine which actions clients can perform. An MSK cluster can be configured to allow unauthenticated access, which allows any client with network connectivity to publish and subscribe to Kafka topics without providing credentials. Running an MSK cluster without requiring authentication violates the principle of least privilege and can expose the cluster to unauthorized access. It can allow any client to access, modify, or delete data in Kafka topics, potentially resulting in data breaches, unauthorized data modifications, or service disruptions. We recommend enabling authentication mechanisms such as IAM authentication, SASL/SCRAM, or mutual TLS to ensure proper access control and maintain security compliance.

Available in all commercial Regions except Asia Pacific (Malaysia), Asia Pacific (New Zealand), Canada West (Calgary), and Mexico (Central). Available in the AWS GovCloud (US) Regions.

multi-region-cloudtrail-enabled

AU.L2-3.3.1, AU.L2-3.3.2 Enabling AWS CloudTrail trails in all regions provides comprehensive visibility, compliance adherence, incident response capabilities, and proactive security monitoring. It ensures that no region is left unmonitored, reducing the risk of undetected security incidents and enabling effective security management across the entire AWS infrastructure.

Available in all commercial Regions. Available in the AWS GovCloud (US) Regions.

nacl-no-unrestricted-ssh-rdp

AC.L2-3.1.20, AC.L2-3.1.3, SC.L2-3.13.1 Network access control list (NACL) should not allow unrestricted ingress access to secure remote access services. Traffic should be scoped to a narrow range of IP addresses required for specific business needs to reduce risk of exposure.

Available in all commercial Regions. Available in the AWS GovCloud (US) Regions.

neptune-cluster-encrypted

SC.L2-3.13.16 Enabling storage encryption for Neptune DB clusters protects sensitive data at rest from unauthorized access. This security measure helps prevent data breaches if storage media is compromised or improperly disposed of. Encrypted Neptune instances fulfill compliance requirements for data-at-rest encryption across various regulatory frameworks and industry standards, reducing organizational risk and strengthening your overall cloud security posture.

Available in all commercial Regions except Asia Pacific (Hyderabad), Asia Pacific (Melbourne), Asia Pacific (New Zealand), Asia Pacific (Taipei), Asia Pacific (Thailand), Canada West (Calgary), Europe (Milan), Europe (Spain), Europe (Zurich), and Mexico (Central). Not available in the AWS GovCloud (US) Regions.

netfw-logging-enabled

SC.L2-3.13.1 Enabling firewall logging for AWS Network Firewall gives detailed information about network traffic, including the time that the stateful engine received a packet flow, detailed information about the packet flow, and any stateful rule action taken against the packet flow. Available in all commercial Regions except Asia Pacific (Thailand), Canada West (Calgary), and Mexico (Central). Not available in the AWS GovCloud (US) Regions.

netfw-policy-rule-group-associated

AC.L2-3.1.3, SC.L2-3.13.1 Associating network firewall policies with rule groups ensures that consistent and appropriate criteria is used for inspecting and handling stateful and stateless network traffic. Available in all commercial Regions except Canada West (Calgary) and Mexico (Central). Available in the AWS GovCloud (US) Regions.

netfw-stateless-rule-group-not-empty

AC.L2-3.1.14, AC.L2-3.1.3, SC.L2-3.13.1, SC.L2-3.13.6 A rule group contains rules that define how firewall processes traffic in a VPC. An empty stateless rule group, when present in a firewall policy, might give the impression that the rule group will process traffic. However, when the stateless rule group is empty, it does not process traffic. Available in all commercial Regions except Canada West (Calgary) and Mexico (Central). Available in the AWS GovCloud (US) Regions.

netfw-subnet-change-protection-enabled

AC.L2-3.1.3, CM.L2-3.4.5, SC.L2-3.13.1, SC.L2-3.13.6 AWS Network Firewall is a stateful, managed network firewall and intrusion detection service that you can use to inspect and filter traffic to, from, or between your Virtual Private Clouds (VPCs). If you enable subnet change protection for a Network Firewall firewall, you can protect the firewall against accidental changes to the firewalls subnet associations.

Available in all commercial Regions. Available in the AWS GovCloud (US) Regions.

nlb-internal-scheme-check

SC.L2-3.13.1, SC.L2-3.13.6 Enforcing internal scheme configuration for Network Load Balancers helps maintain network security boundaries and reduces attack surface by ensuring load balancers are only accessible from within the VPC. This control supports defense-in-depth strategies by preventing unintended internet exposure of internal applications and services. Internal load balancers also help organizations comply with security frameworks that require network segmentation and controlled access to application infrastructure. Available in all commercial Regions except Asia Pacific (Malaysia), Asia Pacific (New Zealand), Asia Pacific (Taipei), Asia Pacific (Thailand), and Mexico (Central). Not available in the AWS GovCloud (US) Regions.

nlb-listener-tagged

CM.L2-3.4.1 Proper tagging of Network Load Balancer listeners enables effective resource management, cost allocation, and operational visibility. Tags facilitate automated governance policies, help track resource ownership and purpose, support compliance reporting requirements, and enable efficient filtering and organization of load balancing resources across environments. Consistent tagging practices are essential for maintaining security boundaries and implementing least-privilege access controls. Available in all commercial Regions except Asia Pacific (Hyderabad), Asia Pacific (Jakarta), Asia Pacific (Malaysia), Asia Pacific (Melbourne), Asia Pacific (New Zealand), Asia Pacific (Taipei), Asia Pacific (Thailand), Canada West (Calgary), Europe (Spain), Europe (Zurich), Israel (Tel Aviv), Mexico (Central), and Middle East (UAE). Not available in the AWS GovCloud (US) Regions.

nlb-logging-enabled

AU.L2-3.3.1, AU.L2-3.3.2 Access logging for Network Load Balancers provides detailed records of requests sent to the load balancer, including client IP addresses, latencies, request paths, and server responses. This logging capability is essential for security monitoring, troubleshooting performance issues, analyzing traffic patterns, and meeting compliance requirements. Without access logging enabled, organizations lose visibility into network traffic patterns and may be unable to detect security incidents, perform forensic analysis, or troubleshoot connectivity issues effectively.

Available in all commercial Regions except Asia Pacific (Malaysia), Asia Pacific (New Zealand), Asia Pacific (Taipei), Asia Pacific (Thailand), and Mexico (Central). Available in the AWS GovCloud (US) Regions.

nlb-tagged

CM.L2-3.4.1 Tagging Network Load Balancers enables proper resource management, cost allocation, and governance. Tags facilitate automated operations, help identify resource ownership and purpose, support compliance reporting, and enable effective cost tracking across different projects, environments, or business units. Consistent tagging practices are essential for maintaining visibility and control over load balancer resources in large-scale AWS environments. Available in all commercial Regions except Asia Pacific (Malaysia), Asia Pacific (New Zealand), Asia Pacific (Taipei), Asia Pacific (Thailand), and Mexico (Central). Not available in the AWS GovCloud (US) Regions.

no-unrestricted-route-to-igw

AC.L2-3.1.20, AC.L2-3.1.3, SC.L2-3.13.1 Restricting access to the IGW enhances the security of EC2 instances by protecting sensitive data and reduces the potential for data breaches or unauthorized activities. Restricting access to the IGW aligns with the principle of least privilege and allows for implementation of network segmentation and isolation strategies by controlling outbound connections creating communication boundaries between different parts of network infrastructure reducing the occurrence of lateral movement of threats, limits the impact of potential security incidents, and enhances overall network security and resilience.

Available in all commercial Regions. Available in the AWS GovCloud (US) Regions.

rds-aurora-postgresql-logs-to-cloudwatch

AU.L2-3.3.1 CloudWatch logging for Aurora PostgreSQL is essential for maintaining operational visibility and security compliance. Without proper logging, organizations cannot effectively monitor database activities or investigate security incidents. Enabled logging supports better operational insights and facilitates auditing.

Available in all commercial Regions except Asia Pacific (Hyderabad), Asia Pacific (Melbourne), Canada West (Calgary), and Europe (Spain). Available in the AWS GovCloud (US) Regions.

rds-event-subscription-tagged

CM.L2-3.4.1 Proper tagging of RDS event subscriptions enables effective resource management, cost allocation, and governance. Tags provide essential metadata for tracking ownership, environment classification, billing attribution, and automated operations. Consistent tagging across all AWS resources, including RDS event subscriptions, supports compliance with organizational policies and facilitates resource discovery and management at scale. Available in all commercial Regions except Asia Pacific (Malaysia), Asia Pacific (New Zealand), Asia Pacific (Taipei), Asia Pacific (Thailand), and Mexico (Central). Not available in the AWS GovCloud (US) Regions.

rds-instance-subnet-igw-check

SC.L2-3.13.6 RDS instances deployed in public subnets with internet gateway routes create significant security risks by potentially exposing database resources directly to the internet. This configuration increases the attack surface and makes databases vulnerable to unauthorized access attempts, data breaches, and other security threats. Following the principle of least privilege and defense in depth, RDS instances should be deployed in private subnets and accessed through secure channels such as VPN connections, bastion hosts, or application servers in public subnets.

Available in all commercial Regions. Available in the AWS GovCloud (US) Regions.

rds-mariadb-instance-encrypted-in-transit

SC.L2-3.13.11, SC.L2-3.13.8 Data in transit refers to data that moves from one location to another, such as between nodes in a DB cluster or between a DB cluster and a client application. Data can move across the internet or within a private network. Encrypting data in transit reduces the risk of unauthorized users eavesdropping on network traffic.

Available in all commercial Regions except Canada West (Calgary). Available in the AWS GovCloud (US) Regions.

rds-mysql-instance-encrypted-in-transit

SC.L2-3.13.1, SC.L2-3.13.8 Data in transit refers to data that moves from one location to another, such as between nodes in your cluster or between your cluster and your application. Data may move across the internet or within a private network. Encrypting data in transit reduces the risk that an unauthorized user can eavesdrop on network traffic.

Available in all commercial Regions except Canada West (Calgary). Available in the AWS GovCloud (US) Regions.

rds-option-group-tagged

CM.L2-3.4.1 Tagging RDS option groups enables proper resource management, cost allocation, and governance. Tags provide essential metadata for tracking resource ownership, environment classification, and automated management processes. Consistent tagging practices improve operational visibility, support compliance reporting requirements, and facilitate effective resource lifecycle management across RDS deployments. Available in all commercial Regions except Asia Pacific (Malaysia), Asia Pacific (New Zealand), Asia Pacific (Taipei), Asia Pacific (Thailand), and Mexico (Central). Not available in the AWS GovCloud (US) Regions.

rds-postgresql-logs-to-cloudwatch

AU.L2-3.3.1 CloudWatch logging for RDS PostgreSQL is essential for maintaining operational visibility and security compliance. Without proper logging, organizations cannot effectively monitor database activities or investigate security incidents. Enabled logging supports better operational insights and facilitates auditing.

Available in all commercial Regions except Canada West (Calgary). Available in the AWS GovCloud (US) Regions.

rds-postgres-instance-encrypted-in-transit

SC.L2-3.13.1, SC.L2-3.13.8 Data in transit refers to data that moves from one location to another, such as between nodes in your cluster or between your cluster and your application. Data may move across the internet or within a private network. Encrypting data in transit reduces the risk that an unauthorized user can eavesdrop on network traffic.

Available in all commercial Regions except Asia Pacific (Malaysia), Asia Pacific (Thailand), Canada West (Calgary), and Mexico (Central). Available in the AWS GovCloud (US) Regions.

rds-proxy-tls-encryption

SC.L2-3.13.8 Enforcing TLS encryption on RDS proxy connections protects sensitive database traffic from interception and eavesdropping attacks. TLS encryption ensures data confidentiality and integrity during transmission between applications and databases, helping organizations meet compliance requirements for data protection standards such as PCI DSS, HIPAA, and SOC 2. Additionally, encrypted connections prevent credential theft and man-in-the-middle attacks that could compromise database security.

Available in all commercial Regions except Asia Pacific (Taipei). Not available in the AWS GovCloud (US) Regions.

rds-sqlserver-encrypted-in-transit

SC.L2-3.13.11, SC.L2-3.13.8 Data in transit refers to data that moves from one location to another, such as between nodes in a DB cluster or between a DB cluster and a client application. Data can move across the internet or within a private network. Encrypting data in transit reduces the risk of unauthorized users eavesdropping on network traffic.

Available in all commercial Regions. Available in the AWS GovCloud (US) Regions.

rds-sql-server-logs-to-cloudwatch

AU.L2-3.3.1 CloudWatch logging for RDS SQL Server is essential for maintaining operational visibility and security compliance. Without proper logging, organizations cannot effectively monitor database activities or investigate security incidents. Enabled logging supports better operational insights and facilitates auditing.

Available in all commercial Regions except Asia Pacific (New Zealand), Asia Pacific (Taipei), Asia Pacific (Thailand), Canada West (Calgary), and Mexico (Central). Available in the AWS GovCloud (US) Regions.

redshift-serverless-default-db-name-check

CM.L2-3.4.2 Using custom database names instead of default values enhances security by reducing predictability for potential attackers and supports better organizational practices. Default database names are well-known and can be easily guessed, potentially increasing the attack surface. Custom naming also improves operational management by making it easier to identify and organize databases according to business requirements, environments, or applications, while supporting compliance requirements that mandate unique identifiers for database resources.

Available in all commercial Regions except Africa (Cape Town), Asia Pacific (Hyderabad), Asia Pacific (Malaysia), Asia Pacific (Melbourne), Asia Pacific (New Zealand), Asia Pacific (Osaka), Asia Pacific (Taipei), Asia Pacific (Thailand), Canada West (Calgary), Europe (Milan), Mexico (Central), and Middle East (Bahrain). Available in the AWS GovCloud (US) Regions.

redshift-serverless-publish-logs-to-cloudwatch

AU.L2-3.3.1, AU.L2-3.3.2 If you configure Amazon Redshift Serverless to export connection log (connectionlog) and user log (userlog) data to a log group in Amazon CloudWatch Logs, you can collect and store your log records in durable storage, which can support security, access, and availability reviews and audits. With CloudWatch Logs, you can also perform real-time analysis of log data and use CloudWatch to create alarms and review metrics.

Available in all commercial Regions except Africa (Cape Town), Asia Pacific (Hyderabad), Asia Pacific (Melbourne), Asia Pacific (Osaka), Canada West (Calgary), Europe (Milan), and Middle East (Bahrain). Not available in the AWS GovCloud (US) Regions.

redshift-serverless-workgroup-encrypted-in-transit

CM.L2-3.4.2, SC.L2-3.13.8 Enforcing SSL encryption for Amazon Redshift Serverless workgroups protects sensitive data transmitted between clients and the data warehouse from interception and tampering. Unencrypted data in transit is vulnerable to man-in-the-middle attacks and eavesdropping, which could lead to data breaches and compromise data integrity. This control helps organizations meet compliance requirements for data protection standards such as PCI DSS, HIPAA, and SOX, while maintaining the confidentiality and integrity of data warehouse communications.

Available in all commercial Regions except Africa (Cape Town), Asia Pacific (Hong Kong), Asia Pacific (Hyderabad), Asia Pacific (Melbourne), Asia Pacific (Osaka), Canada West (Calgary), Europe (Milan), Middle East (Bahrain), Middle East (UAE), and South America (Sao Paulo). Not available in the AWS GovCloud (US) Regions.

redshift-serverless-workgroup-no-public-access

AC.L2-3.1.3, SC.L2-3.13.1 Preventing public access to Redshift Serverless workgroups is critical for maintaining data security and reducing attack surface. Workgroups that allow public access expose sensitive data warehouses to potential unauthorized access from the internet, increasing the risk of data breaches, unauthorized queries, and compliance violations. Restricting access to private networks ensures that data warehouse resources are only accessible through controlled network paths with appropriate security controls.

Available in all commercial Regions except Africa (Cape Town), Asia Pacific (Hyderabad), Asia Pacific (Melbourne), Asia Pacific (Osaka), Canada West (Calgary), Europe (Milan), and Middle East (Bahrain). Not available in the AWS GovCloud (US) Regions.

redshift-serverless-workgroup-routes-within-vpc

AC.L2-3.1.3, CM.L2-3.4.2, SC.L2-3.13.1 Routing Redshift Serverless workgroup traffic through a VPC provides essential network isolation and security controls. VPC routing enables organizations to implement network-level access controls, monitor traffic patterns, and maintain compliance with security frameworks that require private network configurations. This control helps prevent unauthorized external access to data warehouse resources and ensures that sensitive data processing occurs within a controlled network environment.

Available in all commercial Regions except Africa (Cape Town), Asia Pacific (Hong Kong), Asia Pacific (Hyderabad), Asia Pacific (Melbourne), Asia Pacific (Osaka), Canada West (Calgary), Europe (Milan), Middle East (Bahrain), Middle East (UAE), and South America (Sao Paulo). Not available in the AWS GovCloud (US) Regions.

redshift-unrestricted-port-access

AC.L2-3.1.3, SC.L2-3.13.6 Limiting inbound access to Redshift clusters is essential for maintaining database security. Unrestricted access could lead to unauthorized data access or potential attacks. Implementing strict inbound rules helps protect sensitive data and maintain cluster security. Available in all commercial Regions except Canada West (Calgary). Available in the AWS GovCloud (US) Regions.

route53-health-check-tagged

CM.L2-3.4.1 Proper tagging of Route 53 health checks enables effective resource management, cost allocation, and operational visibility. Tags facilitate automated governance policies, help track resource ownership and purpose, and support compliance requirements for resource identification and categorization. Without consistent tagging, organizations lose visibility into health check usage patterns and may struggle with cost optimization and resource lifecycle management. Available only in US East (N. Virginia). Not available in the AWS GovCloud (US) Regions.

route53-hosted-zone-tagged

CM.L2-3.4.1 Proper tagging of Route 53 hosted zones enables effective resource management, cost allocation, and governance. Tags facilitate automated operations, help track resource ownership and purpose, support compliance reporting, and enable consistent application of security policies across DNS infrastructure. Without tags, organizations lose visibility into resource utilization and struggle to maintain proper cost controls and operational oversight of their DNS services. Available only in US East (N. Virginia). Not available in the AWS GovCloud (US) Regions.

s3-bucket-logging-enabled

AU.L2-3.3.1, AU.L2-3.3.2 Enabling S3 bucket logging on target S3 buckets allows you to capture all events that might affect objects in a target bucket. Configuring logs to be placed in a separate bucket enables access to log information, which can be useful in security and incident response workflows and provides redundancy.

Available in all commercial Regions. Available in the AWS GovCloud (US) Regions.

s3-bucket-ssl-requests-only

SC.L2-3.13.15, SC.L2-3.13.8 Protect data in transit by using TLS encryption when sending data to S3 buckets.

Available in all commercial Regions. Available in the AWS GovCloud (US) Regions.

s3-bucket-tagged

CM.L2-3.4.1 Tagging S3 buckets is essential for effective resource management, cost allocation, and governance. Tags enable organizations to categorize buckets by purpose, owner, environment, or project, facilitating accurate cost tracking and billing. Proper tagging also supports automated resource management, security policies, and compliance reporting. Without consistent tagging, organizations lose visibility into resource usage patterns and may struggle to implement effective access controls or lifecycle policies. Available in all commercial Regions except Asia Pacific (Malaysia), Asia Pacific (New Zealand), Asia Pacific (Taipei), Asia Pacific (Thailand), and Mexico (Central). Not available in the AWS GovCloud (US) Regions.

s3-bucket-versioning-enabled

AU.L2-3.3.8 Object versioning in S3 buckets allows users to keep, restore and recover objects from unintended user actions and application failures. When combined with MFA delete, additional protection is provided to delete objects in S3 permanently, or disable object versioning.

Available in all commercial Regions. Available in the AWS GovCloud (US) Regions.

s3-default-encryption-kms

MP.L2-3.8.9, SC.L2-3.13.11, SC.L2-3.13.16 Protecting objects in S3 using encryption at rest with KMS prevents unauthorized access of data at rest and reduces the risk of a potential data breach or related security incident.

Available in all commercial Regions. Available in the AWS GovCloud (US) Regions.

s3-event-notifications-enabled

AU.L2-3.3.8 By enabling event notifications in S3 buckets, alerts can be generated when pre-defined behavior occurs. Notifications from S3 buckets can then trigger prompt response to identified threats and reduce the impact of a security incident. Example events include object ACL PUT, object tagging, S3 lifecycle, new object created, object removal, and more.

Available in all commercial Regions except Mexico (Central). Available in the AWS GovCloud (US) Regions.

sagemaker-domain-in-vpc

SC.L2-3.13.1 Using customer-owned VPCs for SageMaker domains provides enhanced network security and control by allowing organizations to implement custom network access controls, security groups, and network monitoring. This configuration enables better isolation of machine learning workloads, prevents unauthorized network access, and ensures compliance with organizational network security policies. Additionally, VPC configuration allows for integration with existing network security tools and provides audit trails for network traffic analysis. Available in all commercial Regions except Asia Pacific (Hyderabad), Asia Pacific (Malaysia), Asia Pacific (Melbourne), Asia Pacific (New Zealand), Asia Pacific (Taipei), Asia Pacific (Thailand), Canada West (Calgary), Europe (Spain), Europe (Zurich), Israel (Tel Aviv), Mexico (Central), and Middle East (UAE). Not available in the AWS GovCloud (US) Regions.

sagemaker-domain-tagged

CM.L2-3.4.1 Proper tagging of SageMaker domains enables effective resource management, cost allocation, and governance across machine learning workloads. Tags facilitate automated compliance reporting, support billing transparency by enabling cost tracking across projects or departments, and help enforce organizational policies for resource classification. Additionally, consistent tagging practices improve operational efficiency by enabling automated resource discovery and management workflows. Available in all commercial Regions except Asia Pacific (Hyderabad), Asia Pacific (Malaysia), Asia Pacific (Melbourne), Asia Pacific (New Zealand), Asia Pacific (Taipei), Asia Pacific (Thailand), Canada West (Calgary), Europe (Spain), Europe (Zurich), Israel (Tel Aviv), Mexico (Central), and Middle East (UAE). Not available in the AWS GovCloud (US) Regions.

sagemaker-feature-group-tagged

CM.L2-3.4.1 Tagging SageMaker feature groups is essential for resource management, cost allocation, and governance. Tags enable organizations to categorize and track machine learning resources, implement proper access controls, automate operational tasks, and maintain compliance with organizational policies. Without proper tagging, it becomes difficult to manage costs, enforce security policies, and maintain visibility into ML infrastructure usage across teams and projects. Available in all commercial Regions except Asia Pacific (Hyderabad), Asia Pacific (Malaysia), Asia Pacific (Melbourne), Asia Pacific (New Zealand), Asia Pacific (Taipei), Asia Pacific (Thailand), Canada West (Calgary), Europe (Zurich), Mexico (Central), and Middle East (UAE). Not available in the AWS GovCloud (US) Regions.

sagemaker-model-in-vpc

SC.L2-3.13.1 Configuring SageMaker models to use VPC for container traffic provides essential network isolation and security controls for machine learning workloads. VPC configuration enables organizations to control network access, implement security groups and network ACLs, monitor traffic flows, and ensure that model inference and training data remain within controlled network boundaries. This control helps prevent unauthorized access to sensitive ML models and data, supports compliance with data privacy regulations, and reduces the attack surface by eliminating exposure to public internet traffic. Available in all commercial Regions except Asia Pacific (Hyderabad), Asia Pacific (Malaysia), Asia Pacific (Melbourne), Asia Pacific (New Zealand), Asia Pacific (Taipei), Asia Pacific (Thailand), Canada West (Calgary), Europe (Spain), Europe (Zurich), Israel (Tel Aviv), Mexico (Central), and Middle East (UAE). Not available in the AWS GovCloud (US) Regions.

sagemaker-model-isolation-enabled

SC.L2-3.13.1 Network isolation for SageMaker models is critical for maintaining data security and preventing unauthorized network access during machine learning operations. When network isolation is enabled, models cannot make outbound network calls, reducing the risk of data exfiltration, unauthorized external communications, and potential security breaches. This control helps organizations maintain compliance with data protection regulations and implement defense-in-depth security strategies for their machine learning workloads. Available in all commercial Regions except Asia Pacific (Hyderabad), Asia Pacific (Melbourne), Asia Pacific (New Zealand), Asia Pacific (Taipei), Asia Pacific (Thailand), Canada West (Calgary), Europe (Spain), Europe (Zurich), Israel (Tel Aviv), Mexico (Central), and Middle East (UAE). Not available in the AWS GovCloud (US) Regions.

service-catalog-portfolio-tagged

CM.L2-3.4.1 Proper tagging of Service Catalog portfolios enables effective resource management, cost allocation, and governance oversight. Tags provide essential metadata for tracking ownership, environment classification, cost center attribution, and compliance requirements. Without consistent tagging, organizations lose visibility into resource utilization, struggle with accurate cost reporting, and face challenges in maintaining security and compliance postures across their Service Catalog offerings. Available in all commercial Regions except Asia Pacific (Jakarta), Asia Pacific (Malaysia), Asia Pacific (New Zealand), Asia Pacific (Taipei), Asia Pacific (Thailand), Canada West (Calgary), Israel (Tel Aviv), and Mexico (Central). Not available in the AWS GovCloud (US) Regions.

service-catalog-shared-within-organization

AC.L2-3.1.1 Portfolio sharing only within Organizations helps ensure that a portfolio isnt shared with incorrect AWS accounts. To share a Service Catalog portfolio with an account in an organization, Security Hub recommends using ORGANIZATIONMEMBERACCOUNT instead of ACCOUNT. This simplifies administration by governing the access granted to the account across the organization. If you have a business need to share Service Catalog portfolios with an external account, you can automatically suppress the findings from this control or disable it. Available in all commercial Regions except Asia Pacific (Jakarta), Asia Pacific (Malaysia), Asia Pacific (Taipei), Asia Pacific (Thailand), Canada West (Calgary), Israel (Tel Aviv), and Mexico (Central). Available in the AWS GovCloud (US) Regions.

ses-malware-scanning-enabled

SI.L2-3.14.5 Malware scanning in SES is crucial for protecting email workflows from potential security threats. Without scanning, malicious attachments or spam could infiltrate your systems. Implementing malware scanning helps maintain email security and prevents potential infections. Available only in US East (N. Virginia), US West (Oregon), and Europe (Ireland). Not available in the AWS GovCloud (US) Regions.

sns-encrypted-kms

SC.L2-3.13.11, SC.L2-3.13.16 Encrypting data at rest reduces the risk of data stored on disk being accessed by unauthenticated users. This adds a data protection layer from a threat actor attempting to gain unauthorized access to SNS topic data.

Available in all commercial Regions. Available in the AWS GovCloud (US) Regions.

sns-topic-no-public-access

AC.L2-3.1.1, AC.L2-3.1.2 Restricting public access to SNS topics is essential for maintaining messaging security and data privacy. Public exposure of SNS topics could lead to unauthorized data access or potential information leaks. Implementing private access controls helps protect sensitive communication channels.

Available in all commercial Regions except Canada West (Calgary). Not available in the AWS GovCloud (US) Regions.

sqs-queue-no-public-access

AC.L2-3.1.1, AC.L2-3.1.2, AC.L2-3.1.5, IA.L2-3.5.2 Preventing public access to SQS queues is critical for maintaining data confidentiality and preventing unauthorized message consumption or injection. Publicly accessible queues can expose sensitive information contained in messages, allow malicious actors to consume legitimate messages intended for authorized applications, or enable message flooding attacks that could disrupt service operations. Implementing proper access controls ensures that only authorized entities can interact with queue messages, supporting compliance with data protection regulations and maintaining the integrity of message-based application architectures.

Available in all commercial Regions except Asia Pacific (Hyderabad), Asia Pacific (Melbourne), Canada West (Calgary), Europe (Spain), Europe (Zurich), Mexico (Central), and Middle East (UAE). Not available in the AWS GovCloud (US) Regions.

sqs-queue-policy-full-access-check

AC.L2-3.1.1, AC.L2-3.1.2, AC.L2-3.1.5, IA.L2-3.5.2 Overly permissive SQS queue policies can expose sensitive message data to unauthorized access and create security vulnerabilities. By monitoring for full access permissions, organizations can identify and remediate queue policies that violate the principle of least privilege. This control helps prevent unauthorized message consumption, modification, or deletion, and supports compliance with security frameworks that require proper access controls on messaging resources. Detecting overly broad permissions enables security teams to implement more restrictive policies that limit access to only necessary actions and authorized principals.

Available in all commercial Regions except Asia Pacific (Hyderabad), Asia Pacific (Jakarta), Asia Pacific (Malaysia), Asia Pacific (Melbourne), Asia Pacific (New Zealand), Asia Pacific (Taipei), Asia Pacific (Thailand), Canada West (Calgary), Europe (Spain), Europe (Zurich), Israel (Tel Aviv), Mexico (Central), and Middle East (UAE). Available in the AWS GovCloud (US) Regions.

ssm-automation-block-public-sharing

AC.L2-3.1.1, AC.L2-3.1.2, AC.L2-3.1.5, IA.L2-3.5.2 Enabling block public sharing on Systems Manager Documents prevents accidental exposure of sensitive automation workflows, scripts, and operational procedures to unauthorized users. This control helps maintain the confidentiality of organizational processes, reduces the risk of information disclosure, and ensures that automation documents containing potentially sensitive configuration details or business logic remain accessible only to authorized personnel within the organization.

Available in all commercial Regions except Asia Pacific (Melbourne). Available in the AWS GovCloud (US) Regions.

ssm-automation-logging-enabled

AU.L2-3.3.1, AU.L2-3.3.2 SSM Automation is an AWS Systems Manager tool that helps you build automated solutions to deploy, configure, and manage AWS resources at scale using predefined or custom runbooks. To meet operational or security requirements for your organization, you might need to provide a record of the scripts that it runs. You can configure SSM Automation to send the output from aws:executeScript actions in your runbooks to an Amazon CloudWatch Logs log group that you specify. With CloudWatch Logs, you can monitor, store, and access log files from various AWS services.

Available in all commercial Regions. Available in the AWS GovCloud (US) Regions.

stepfunctions-state-machine-tagged

CM.L2-3.4.1 Tagging Step Functions state machines is essential for resource management, cost allocation, and operational visibility. Tags enable organizations to categorize workflows by environment, project, or business unit, facilitating accurate cost tracking and billing. Proper tagging also supports automated governance policies, simplifies resource discovery, and ensures compliance with organizational standards for resource identification and management. Available in all commercial Regions except Asia Pacific (Malaysia), Asia Pacific (New Zealand), Asia Pacific (Taipei), Asia Pacific (Thailand), and Mexico (Central). Not available in the AWS GovCloud (US) Regions.

storagegateway-last-backup-recovery-point-created

MP.L2-3.8.5, MP.L2-3.8.9 Regular recovery point creation is crucial for maintaining data resilience and enabling quick recovery for Storage Gateway volumes. Without recent recovery points, organizations risk data loss in case of volume failures or corruption. Implementing regular backups provides a reliable mechanism for data protection. Available in all commercial Regions except Asia Pacific (Malaysia), Asia Pacific (New Zealand), Asia Pacific (Taipei), Asia Pacific (Thailand), Canada West (Calgary), Israel (Tel Aviv), and Mexico (Central). Available in the AWS GovCloud (US) Regions.

storagegateway-resources-in-logically-air-gapped-vault

SC.L2-3.13.1 Logical air-gapping is essential for protecting critical Storage Gateway data from unauthorized access and potential threats. This isolation helps prevent both accidental and malicious access to sensitive information. Implementing air-gapping provides an additional security barrier for critical Storage Gateway volume data. Available in all commercial Regions except Asia Pacific (Malaysia), Asia Pacific (New Zealand), Asia Pacific (Taipei), Asia Pacific (Thailand), Canada West (Calgary), Israel (Tel Aviv), and Mexico (Central). Not available in the AWS GovCloud (US) Regions.

transfer-connector-logging-enabled

AU.L2-3.3.1, AU.L2-3.3.2 Enabling CloudWatch logging for an AWS Transfer Family connector records file-transfer activity and errors that are essential for monitoring, troubleshooting, and investigating unauthorized or anomalous transfers. Without these logs, malicious activity can go undetected and forensic analysis is limited.

Available in all commercial Regions except Asia Pacific (Hyderabad), Asia Pacific (Melbourne), Canada West (Calgary), Europe (Spain), and Europe (Zurich). Available in the AWS GovCloud (US) Regions.

transfer-family-server-no-ftp

SC.L2-3.13.8 FTP (File Transfer Protocol) establishes the endpoint connection through unencrypted channels, leaving data sent over these channels vulnerable to interception. Using SFTP (SSH File Transfer Protocol), FTPS (File Transfer Protocol Secure), or AS2 (Applicability Statement 2) offers an extra layer of security by encrypting your data in transit and can be used to help prevent potential attackers from using person-in-the-middle or similar attacks to eavesdrop on or manipulate network traffic. Available in all commercial Regions except Canada West (Calgary). Available in the AWS GovCloud (US) Regions.

vpc-flow-logs-enabled

AU.L2-3.3.1, SC.L2-3.13.1 The VPC flow logs provide detailed records for information about the IP traffic going to and from network interfaces in your Amazon Virtual Private Cloud (Amazon VPC). By default, the flow log record includes values for the different components of the IP flow, including the source, destination, and protocol. These logs can be used to respond quickly to anomalous traffic and can aid in incident response investigations.

Available in all commercial Regions. Available in the AWS GovCloud (US) Regions.

vpc-network-acl-unused-check

CM.L2-3.4.7 Having unused network Access Control Lists (ACLs) increases the risk of unauthorized access to VPC EC2 resources and should be removed once not needed any longer.

Available in all commercial Regions. Available in the AWS GovCloud (US) Regions.

vpc-sg-open-only-to-authorized-ports

AC.L2-3.1.20, AC.L2-3.1.3, SC.L2-3.13.1 High risk ports are often exposed to the Internet and easily exploitable by attackers. Security groups provide stateful filtering of ingress and egress network traffic to AWS. Security group rules should follow the principal of least privileged access. Unrestricted access (IP address with a /0 suffix) increases the opportunity for malicious activity such as hacking, denial-of-service attacks, and loss of data.

Available in all commercial Regions. Available in the AWS GovCloud (US) Regions.

vpc-sg-port-restriction-check

AC.L2-3.1.3, SC.L2-3.13.1, SC.L2-3.13.6 Controlling inbound access to sensitive ports is crucial for maintaining network security. Unrestricted access to ports like SSH (22) or RDP (3389) could lead to unauthorized system access and potential breaches. Implementing strict port access controls helps prevent unauthorized access to resources.

Available in all commercial Regions. Available in the AWS GovCloud (US) Regions.

vpc-vpn-2-tunnels-up

AC.L2-3.1.13, AC.L2-3.1.20 Ensuring that both VPN tunnels are up for an AWS Site-to-Site VPN connection is important for confirming a secure and highly available connection between an AWS VPC and your remote network. Available in all commercial Regions. Available in the AWS GovCloud (US) Regions.

wafv2-rulegroup-logging-enabled

SI.L2-3.14.6, SI.L2-3.14.7 Enabling Amazon CloudWatch metrics for AWS Web Application Firewall (WAF) V2 rules and rule groups provides visibility into web traffic patterns, potential threats, and WAF enforcement actions. This data supports security monitoring, incident response, and continuous improvement of web application security posture.

Available in all commercial Regions. Not available in the AWS GovCloud (US) Regions.

workspaces-connection-alias-tagged

CM.L2-3.4.1 Proper tagging of WorkSpaces connection aliases is essential for resource management, cost allocation, governance. Tags enable organizations to categorize resources by purpose, owner, environment, or cost center, facilitating accurate billing attribution resource tracking. Consistent tagging practices also support automated management workflows, security policies, compliance reporting requirements. Without proper tagging, organizations lose visibility into resource ownership usage patterns, making it difficult to optimize costs maintain operational control. Available only in US East (N. Virginia), US West (Oregon), Asia Pacific (Seoul), Asia Pacific (Singapore), Asia Pacific (Sydney), Asia Pacific (Tokyo), Canada (Central), Europe (Frankfurt), Europe (Ireland), Europe (London), and South America (Sao Paulo). Not available in the AWS GovCloud (US) Regions.

workspaces-root-volume-encryption-enabled

SC.L2-3.13.16 Root volume encryption is essential for protecting sensitive WorkSpaces data. Without encryption, operating system and application data could be exposed if storage systems are compromised. Implementing root volume encryption provides necessary data protection for virtual desktop environments.

Available only in US East (N. Virginia), US West (Oregon), Africa (Cape Town), Asia Pacific (Malaysia), Asia Pacific (Mumbai), Asia Pacific (Seoul), Asia Pacific (Singapore), Asia Pacific (Sydney), Asia Pacific (Tokyo), Canada (Central), Europe (Frankfurt), Europe (Ireland), Europe (London), and South America (Sao Paulo). Available in AWS GovCloud (US-West).

workspaces-user-volume-encryption-enabled

SC.L2-3.13.16 User volume encryption is crucial for protecting sensitive user data in virtual desktop environments. Without encryption, user files and data could be exposed if storage systems are compromised. Implementing user volume encryption provides necessary protection for end-user data.

Available only in US East (N. Virginia), US West (Oregon), Africa (Cape Town), Asia Pacific (Malaysia), Asia Pacific (Mumbai), Asia Pacific (Seoul), Asia Pacific (Singapore), Asia Pacific (Sydney), Asia Pacific (Tokyo), Canada (Central), Europe (Frankfurt), Europe (Ireland), Europe (London), and South America (Sao Paulo). Available in AWS GovCloud (US-West).

workspaces-workspace-tagged

CM.L2-3.4.1 Proper tagging of WorkSpaces resources is essential for cost allocation, resource management, governance. Tags enable organizations to track ownership, categorize resources by department or project, implement automated policies, maintain compliance with internal standards. Without consistent tagging, organizations lose visibility into resource utilization, struggle with cost attribution, cannot effectively manage their virtual desktop infrastructure at scale. Available only in US East (N. Virginia), US West (Oregon), Africa (Cape Town), Asia Pacific (Mumbai), Asia Pacific (Seoul), Asia Pacific (Singapore), Asia Pacific (Sydney), Asia Pacific (Tokyo), Canada (Central), Europe (Frankfurt), Europe (Ireland), Europe (London), and South America (Sao Paulo). Not available in the AWS GovCloud (US) Regions.