| 💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [AutoScaling.2] Amazon EC2 Auto Scaling group should cover multiple Availability Zones | | | 1 | | no data |
| 💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [AutoScaling.6] Auto Scaling groups should use multiple instance types in multiple Availability Zones | | | | | no data |
| 💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [CloudFront.4] CloudFront distributions should have origin failover configured | | | | | no data |
| 💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [DynamoDB.1] DynamoDB tables should automatically scale capacity with demand | | 1 | 1 | | no data |
| 💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [DynamoDB.2] DynamoDB tables should have point-in-time recovery enabled | | 1 | 1 | | no data |
| 💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [EC2.20] Both VPN tunnels for an AWS Site-to-Site VPN connection should be up | | | 1 | | no data |
| 💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [EFS.2] Amazon EFS volumes should be in backup plans | | | | | no data |
| 💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [ElastiCache.1] ElastiCache (Valkey and Redis OSS) clusters should have automatic backups enabled | | | 1 | | no data |
| 💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [ElastiCache.3] ElastiCache replication groups should have automatic failover enabled | | | | | no data |
| 💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [ELB.9] Classic Load Balancers should have cross-zone load balancing enabled | | | 1 | | no data |
| 💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [ELB.10] Classic Load Balancer should span multiple Availability Zones | | | 1 | | no data |
| 💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [ELB.13] Application, Network and Gateway Load Balancers should span multiple Availability Zones | | | 1 | | no data |
| 💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [ES.6] Elasticsearch domains should have at least three data nodes | | | | | no data |
| 💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [ES.7] Elasticsearch domains should be configured with at least three dedicated master nodes | | | | | no data |
| 💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [Lambda.5] VPC Lambda functions should operate in multiple Availability Zones | | | | | no data |
| 💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [Opensearch.6] OpenSearch domains should have at least three data nodes | | | | | no data |
| 💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [RDS.5] RDS DB instances should be configured with multiple Availability Zones | | 1 | 1 | | no data |
| 💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [RDS.8] RDS DB instances should have deletion protection enabled | | | | | no data |
| 💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [RDS.11] RDS instances should have automatic backups enabled | | | 1 | | no data |
| 💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [RDS.14] Amazon Aurora clusters should have backtracking enabled | | | | | no data |
| 💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [RDS.15] RDS DB clusters should be configured for multiple Availability Zones | | | | | no data |
| 💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [Redshift.3] Amazon Redshift clusters should have automatic snapshots enabled | | | | | no data |
| 💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [S3.13] S3 general purpose buckets should have Lifecycle configurations | | 1 | 1 | | no data |