AWS New Checks
598 articles
- GuardDuty EKS Runtime Monitoring should be enabled
- EFS Access Points Should Enforce a User Identity
- Check if GuardDuty Lambda Protection is enabled
- GuardDuty EKS Audit Log Monitoring Enabled
- EFS Should Not Have Policies Allowing Unrestricted Access Within VPC
- Ensure API Gateway V2 has Access Logging enabled.
- Check if Neptune DB clusters are configured to copy tags to snapshots
- Check for Neptune Clusters Backup Retention Period
- Check if Neptune Clusters have audit cloudwatch logs enabled
- Check if Neptune Clusters storage has deletion protection enabled
- Check if Neptune Clusters storage is encrypted at rest
- Check if Neptune Clusters have multi-AZ enabled
- Check if Neptune Clusters have IAM authentication enabled
- Ensure EFS Mount Targets Are Not Publicly Accessible
- Check if NeptuneDB Manual Cluster Snapshot is Public
- Ensure Amazon EFS File Systems Have Backups Enabled
- Ensure Classic Load Balancer is Configured with Defensive or Strictest Desync Mitigation Mode
- Ensure Neptune Cluster is Not Using a Public Subnet
- Check if Neptune DB Cluster Snapshots Are Encrypted At Rest
- Ensure OpenSearch Service Domain should have at least three dedicated master nodes
- Check if Amazon Elasticsearch/Opensearch Service domains have fine grained access control enabled
- Ensure Classic Load Balancers with SSL/HTTPS Listeners Use Certificates from AWS Certificate Manager (ACM)
- Check if Amazon Elasticsearch/Opensearch Service domains have encryption at-rest enabled
- Ensure Classic Load Balancer is Configured Across Multiple Availability Zones
- Ensure Elasticsearch/Opensearch domains have fault-tolerant data nodes
- Ensure Classic Load Balancer Connection Draining is Enabled
- Ensure Cross-Zone Load Balancing is Enabled for Classic Load Balancers (CLBs)
- Check if Amazon SageMaker Notebook instances have data encryption enabled
- Check if Amazon Elasticsearch/Opensearch Service domains has either Amazon Cognito or SAML authentication for Kibana enabled
- Ensure EMR Clusters Do Not Have Public IPs Assigned
- Ensure instances have automated snapshots enabled
- Ensure Transfer Family Servers have encryption in transit enabled
- Ensure RabbitMQ Brokers use cluster deployment mode
- Ensure AWS Glue Data Catalog Settings Have Encrypt Connection Password Enabled
- Ensure MQ Broker Auto Minor Version Upgrades are enabled
- Ensure Apache ActiveMQ brokers are configured in active/standby mode
- Ensure Publicly Accessible EMR Cluster is Disabled
- Ensure EMR Account Public Access Block Is Enabled
- Ensure MQ brokers are not publicly accessible
- Ensure MQ brokers stream audit logs to CloudWatch
- Ensure Glue data catalog settings have metadata encryption enabled.
- Maintain different contact details to security, billing and operations
- Ensure there are no S3 buckets listable by Everyone or Any AWS customer
- Ensure Glue ETL Jobs have logging enabled.
- Ensure Security Contact Information is Registered
- Ensure Glue ETL Jobs have S3 encryption enabled
- Ensure Contact Details Are Maintained and Kept Current
- Ensure Glue Data Catalogs are not publicly accessible.
- Ensure Security Questions are Registered in the AWS Account
- Ensure S3 bucket MFA Delete is not enabled
- Ensure S3 buckets have event notifications enabled
- Ensure S3 Account Level Public Access Block
- Ensure FSx File Systems are Configured to Copy Tags to Volumes
- Ensure Block Public Access Settings enabled on Multi-Region Access Points
- Ensure Glue development endpoints have S3 encryption enabled.
- Ensure S3 Bucket Level Public Access Block
- Ensure FSx File Systems Are Configured to Copy Tags to Backups
- Ensure S3 buckets use cross-region replication (CRR)
- Ensure Glue database connection has SSL connection enabled.
- Ensure Block Public Access Settings enabled on Access Points
- Ensure FSx Windows File Systems are Configured with Multi-AZ
- Ensure S3 buckets have object lock enabled
- Ensure Glue development endpoints have Job bookmark encryption enabled.
- Ensure S3 buckets have a Lifecycle configuration enabled
- Ensure S3 buckets have ACLs enabled
- Ensure there are no S3 buckets writable by Everyone or Any AWS customer
- Ensure Glue ML Transform Encryption at Rest is Enabled.
- Check if Glue ETL Jobs have CloudWatch Logs encryption enabled
- Ensure Glue ETL Jobs have Job bookmark encryption enabled.
- Ensure S3 buckets have KMS encryption enabled
- Ensure that general-purpose bucket policies restrict access to other AWS accounts
- Ensure that logging is enabled for Amazon Athena workgroups to capture query activity.
- Ensure that encryption at rest is enabled for Amazon Athena query results stored in Amazon S3 in order to secure data and meet compliance requirements for data-at-rest encryption.
- Ensure that workgroup configuration is enforced so it cannot be overriden by client-side settings.
- Ensure a Premium support plan is subscribed.
- Ensure Amazon Elasticsearch/Opensearch Service domains have audit logging enabled
- Ensure CloudWatch Has Allowed Cross-Account Sharing
- Ensure a Log Metric Filter and Alarm Exist for AWS Organizations Changes
- Ensure Secrets Are Not Logged in CloudWatch Logs
- Ensure Route Table Changes are Monitored
- Check if Amazon Elasticsearch/Opensearch Service domains have node-to-node encryption enabled
- Ensure that there is at least one AWS Backup report plan
- Ensure CloudWatch Log Groups Have a Retention Policy of Specific Days
- Ensure CloudWatch Log Groups Are Not Publicly Accessible
- Ensure ECS task definitions should not share the host's process namespace
- Ensure AWS Backup vaults exist
- Ensure Amazon Elasticsearch/Opensearch Service domains have updates available.
- Ensure AWS Backup recovery points are encrypted at rest
- Ensure that there is at least one AWS Backup plan
- Ensure that AWS Backup vaults are encrypted with AWS KMS
- Ensure Data Firehose delivery streams are encrypted at rest
- Ensure ECS Task Definition Containers Have Logging Configured with Non-Blocking Mode
- Ensure AWS WAF Classic Regional rule group has at least one rule
- Ensure ECS task definitions containers should have a logging configuration
- Ensure Logging Is Enabled for AWS WAF Classic Global WebACL
- Ensure CloudWatch Alarms Have Specified Actions Configured for the ALARM State
- Ensure AWS WAF Classic Global WebACL Has at Least One Rule or Rule Group
- Ensure ECS Fargate services should run on the latest Fargate platform version
- Ensure AWS WAF Classic Regional Rules Have at Least One Condition
- Ensure AWS WAF Classic Global Rule Groups Have at Least One Rule
- Ensure CloudWatch Log Groups are Protected by AWS KMS
- Ensure ECS clusters should use Container Insights
- Ensure AWS WAF Classic Global Rules Have at Least One Condition
- Ensure AWS WAF Classic Regional WebACL Has at Least One Rule or Rule Group
- Ensure Authentication Mechanism Is Enabled for DMS Endpoints for MongoDB
- Ensure CloudWatch Alarms Have Actions Enabled
- Ensure ECS services should not assign public IPs automatically
- Ensure SSL Mode Is Enabled in DMS Endpoints
- Ensure Multi-AZ Is Enabled for DMS Instances
- Ensure CloudFront Distributions Are Not Using Deprecated SSL Protocols
- Ensure Logging Is Enabled for DMS Replication Tasks (Source Database)
- Ensure ECS task definitions shouldn't have privileged containers
- Ensure DMS Instances Are Not Publicly Accessible
- Ensure ECS containers should be limited to read-only access to root filesystems
- Ensure Encryption in Transit for DMS Endpoints for Redis OSS
- Ensure Auto Minor Version Upgrade Is Enabled for DMS Instances
- Ensure ECS Task Sets Do Not Automatically Assign Public IP Addresses
- Ensure S3 Glacier vaults have policies which allow access to everyone.
- Ensure the S3 bucket CloudTrail bucket requires MFA delete.
- Ensure there are no potential enumeration threats in CloudTrail.
- Ensure CloudTrail Insight is enabled.
- Ensure CloudTrail logging management events in All Regions.
- Ensure there are no potential LLM Jacking threats in CloudTrail.
- Ensure Enable Privacy Protection for for a Route53 Domain.
- Ensure Enable Transfer Lock for a Route53 Domain.
- Ensure Route53 Records contains dangling IPs.
- Ensure SSM Incidents is enabled with response plans.
- Ensure Inspector2 is enabled for Amazon EC2 instances, ECR container images and Lambda functions.
- Ensure Logging Is Enabled for DMS Replication Tasks
- Ensure IAM Authorization Is Enabled for DMS Endpoints for Neptune Databases
- Ensure EC2 Auto Scaling Groups Use EC2 Launch Templates
- Ensure Capacity Rebalancing Is Enabled for EC2 Auto Scaling Groups
- Ensure Inspector2 active findings exist.
- Ensure Direct Connect connections are redundant.
- Ensure Direct Connect virtual interface(s) are providing redundant connections.
- Ensure ACM Certificates use a secure key algorithm.
- Ensure GuardDuty RDS Protection is enabled.
- Ensure that GuardDuty Malware Protection for EC2 is enabled.
- Ensure There are High severity GuardDuty findings.
- Ensure GuardDuty is centrally managed.
- Ensure GuardDuty S3 Protection is enabled.
- Ensure Auto Scaling Groups Use ELB Health Checks
- Ensure EC2 Auto Scaling Group Uses MultipEnsure EC2 Auto Scaling Group Uses Multiple Availability Zonesle Availability Zones
- Ensure EC2 Auto Scaling Group Uses Multiple Instance Types and AZs
- Ensure no secrets are present in EC2 Auto Scaling Launch Configurations
- Ensure Auto Scaling group launch configurations require Instance Metadata Service Version 2 (IMDSv2)
- Ensure Amazon EC2 instances launched using Auto Scaling group launch configurations have Public IP addresses
- Ensure Network Firewall Policies Have at Least One Rule Group Associated
- Ensure All VPCs Have Network Firewall Enabled
- GuardDuty EKS Runtime Monitoring Should Be Enabled
- Ensure Default Action for Full Packets in Network Firewall is Set to Drop or Forward
- Ensure Default Action for Fragmented Packets is Set to Drop or Forward
- Ensure CloudFront Distributions Have Origin Failover Enabled
- Ensure EFS Access Points Should Enforce a Root Directory
- Ensure CloudFront Distributions Use Custom SSL/TLS Certificates
- Ensure Deletion Protection Safety Feature is Enabled for Amazon VPC Network Firewalls
- Ensure Network Firewall Logging is Enabled
- Ensure All Network Firewall Firewalls Are Deployed Across Multiple Availability Zones (AZs)
- Ensure CloudFront Distributions Do Not Point to Non-Existent S3 Origins Without Static Website Hosting
- Check if Internet-Facing Application Load Balancers Are Protected by AWS Shield Advanced
- Ensure Route 53 hosted zones are protected by AWS Shield Advanced
- Ensure Classic Load Balancers are protected by AWS Shield Advanced
- Ensure Elastic IP addresses with associations are protected by AWS Shield Advanced
- Ensure CloudFront Distributions Are Using SNI to Serve HTTPS Requests
- Ensure CloudFront distributions are protected by AWS Shield Advanced
- Ensure Global Accelerators are protected by AWS Shield Advanced
- Ensure Elastic Load Balancers have no insecure SSL ciphers enabled
- Ensure Elastic Load Balancer V2 (ELBv2) is configured across multiple Availability Zones (AZs)
- Ensure CloudFront Distributions Have a Default Root Object
- Ensure Elastic Load Balancers have deletion protection enabled
- Ensure CloudFront Distributions Are Using AWS WAF
- Ensure Network Load Balancers (NLB) have TLS termination enabled
- Ensure ELBV2 has listeners configured
- Ensure Elastic Load Balancers (ELB) Have Logging Enabled
- Ensure CloudFront Distributions with S3 Origin Use Origin Access Control (OAC)
- Ensure Application Load Balancer Has a WAF Web ACL Attached
- Ensure CloudFront Distributions Encrypt Traffic to Custom Origins
- Ensure the Application Load Balancer is Configured with Strictest Desync Mitigation Mode
- Ensure Cross-Zone Load Balancing is Enabled for Network Load Balancers (NLBs) and Gateway Load Balancers (GWLB)
- Ensure AWS KMS Keys Are Not Deleted Unintentionally
- Ensure No Security Groups Allow Ingress from 0.0.0.0/0 or ::/0 to Elasticsearch/Kibana Ports
- Check if There Are Unused KMS Customer Managed Keys (CMKs)
- Ensure AWS KMS Customer Managed Keys Are Not Multi-Region
- Ensure No EC2 Instances Allow Ingress from the Internet to TCP Port 389 or 636
- Ensure Public Access to EBS Snapshots Is Disabled
- Ensure Amazon Elasticsearch/OpenSearch Service Domains Should Have HTTPS Enforcement Enabled
- Ensure AWS Storage Gateway File Shares Are Encrypted with KMS CMK
- Ensure Directory Service Monitoring with CloudWatch Logs
- Ensure AWS Storage Gateway Gateways Are Hosted in a Fault-Tolerant Environment
- Ensure Sensitive Information Filters are Configured for Amazon Bedrock Guardrails
- Ensure Directory Service Manual Snapshots limit reached
- Ensure that Amazon Bedrock Model Invocation Logs are Encrypted with KMS
- Ensure Directory Service has SNS Notifications enabled
- Ensure that Guardrails are Enabled for Amazon Bedrock Agent Sessions
- Ensure Prompt Attack Filter is Configured at Highest Strength for Amazon Bedrock Guardrails
- Ensure that Model Invocation Logging is Enabled for Amazon Bedrock
- Ensure Multi-Factor Authentication (MFA) Using a RADIUS Server is Enabled in Directory Service
- Ensure Session Idle Disconnect Timeout is Set to 10 Minutes or Less
- Ensure Session Disconnect Timeout is Set to 5 Minutes or Less
- Ensure Default Internet Access from Your Amazon AppStream Fleet Streaming Instances Remains Unchecked
- Ensure User Maximum Session Duration is No Longer than 10 Hours
- Ensure that Your AWS EventBridge Event Bus is Not Exposed to Everyone
- Ensure EventBridge Event Buses Do Not Allow Unknown Cross-Account Access
- Ensure EventBridge Event Buses Do Not Allow Unknown Cross-Account Access
- Ensure EventBridge Global Endpoints Have Event Replication Enabled
- Ensure Security Hub Is Enabled and Its Standard Subscriptions Are Configured
- Ensure No Security Groups Allow Ingress from 0.0.0.0/0 or ::/0 to Telnet Port 23
- Ensure EC2 Client VPN Endpoints Have Client Connection Logging Enabled
- Ensure Amazon EC2 Paravirtual Virtualization Type Is Not Used
- Ensure No EC2 Instances Allow Ingress from the Internet to TCP Port 22(SSH)
- Ensure No Security Groups Allow Ingress from 0.0.0.0/0 or ::/0 to Postgres Port 5432
- Ensure there are no secrets in SSM Documents
- Ensure SSM Documents Are Not Set as Public
- Ensure EC2 Instances Managed by Systems Manager Are Compliant with Patching Requirements
- Ensure EC2 Instances Are Managed by Systems Manager
- Ensure SNS Subscriptions Do Not Use HTTP Endpoints
- Ensure SNS Topics Are Encrypted
- Ensure No EC2 Instances Allow Ingress from the Internet to TCP Ports 1433 or 1434 (SQL Server)
- Ensure Kafka Cluster Has Unrestricted Access Disabled
- Ensure RADIUS Server in Directory Service Uses the Recommended Security Protocol
- Ensure Kafka Cluster Encryption in Transit Is Enabled
- Ensure Mutual TLS Authentication Is Enabled for Kafka Clusters
- Ensure Kafka Clusters Are Not Exposed to the Public
- Ensure Directory Service LDAP Certificates Expiration Is Monitored and Managed
- Ensure MSK Connect Connectors Are Encrypted in Transit
- Ensure Unused Network Access Control Lists (NACLs) Are Removed
- Ensure Kafka Cluster Encryption at Rest Uses Customer Managed Keys (CMK)
- Ensure Enhanced Monitoring is Enabled for MSK (Kafka) Brokers
- Ensure MSK Clusters Use the Latest Version
- Ensure No EC2 Instances Allow Ingress from the Internet to TCP Ports 20 or 21 (FTP)
- Ensure Unassigned Elastic IPs Are Identified and Removed
- Ensure Amazon EFS Protects Sensitive Data with Encryption at Rest
- Ensure no security groups allow ingress from 0.0.0.0/0 or ::/0 to high risk ports
- Ensure Amazon EFS File Systems are Configured with Multi-AZ
- Ensure trust boundaries in VPC endpoint connections.
- Ensure Amazon SageMaker Notebook instances have direct internet access
- Ensure no Network ACLs allow ingress from 0.0.0.0/0 to SSH port 22
- Ensure CodeArtifact Internal Packages Do Not Allow External Public Source Publishing
- Check if Amazon SageMaker Notebook instances have direct internet access
- Ensure Amazon SageMaker Training jobs have volume and output with KMS encryption enabled
- Ensure Amazon SageMaker Training job have VPC settings configured
- Ensu Amazon SageMaker Models have network isolation enabled
- Ensure Amazon SageMaker Notebook instances have root access disabled
- Ensure all VPC has public and private subnets defined.
- Ensure all VPC has subnets in more than one availability zone
- EnsuAmazon EC2 should be configured to use VPC endpoints that are created for the Amazon EC2 service.
- Amazon EC2 should be configured to use VPC endpoints that are created for the Amazon EC2 service.
- Ensure Both VPN tunnels for an AWS Site-to-Site VPN connection should be up.
- Ensure no EC2 instances allow ingress from the internet to TCP port 139 or 445 (CIFS).
- Ensure Amazon VPC Interface Endpoints should have ENIs in more than one subnet.
- Ensure VPC Subnets Do Not Assign Public IP by Default
- Ensure ElastiCache Redis Cache Clusters Have Automatic Minor Upgrades Enabled
- Ensure ElastiCache Redis Cache Clusters Have Automatic Minor Upgrades Enabled
- Ensure ElastiCache Cluster is Not Using a Public Subnet
- Ensure ElastiCache Redis Clusters Have Automatic Failover Enabled
- Ensure Elasticache Redis cache clusters have at rest encryption enabled.
- Ensure Elasticache Redis replication groups of earlier versions should have Redis OSS AUTH enabled.
- Ensure Elasticache Redis cache cluster has Multi-AZ enabled.
- Ensure Config Recorder is Using Service-Linked AWS Config Role
- Ensure SageMaker endpoint production variants should have at least two initial instances
- Ensure Secrets Manager secrets are not publicly accessible
- Ensure Secrets Manager secret rotation is enabled
- Ensure secrets manager secrets are not unused
- Ensure Secrets should be rotated periodically
- Ensure ECR Registry has scan on push enabled
- Ensure ECR repositories should have tag immutability configured
- Ensure ECR repositories have lifecycle policies enabled
- EnsurResource Explorer Indexes Found
- Ensure Workspaces VPC are Deployed Following Best Practices Using 1 Public Subnet and 2 Private Subnets with a NAT Gateway Attached
- Ensure DynamoDB tables should not be accessible from other AWS accounts
- Ensure DynamoDB Accelerator (DAX) clusters are encrypted in transit
- Ensure DynamoDB table has encryption at rest enabled using CMK KMS
- Ensure DynamoDB tables automatically scale capacity with demand
- Ensure DynamoDB Accelerator (DAX) clusters have nodes in multiple availability zones
- Ensure that your Amazon WorkSpaces storage volumes are encrypted in order to meet security and compliance requirements.
- Ensure DynamoDB tables have deletion protection enabled
- Ensure DynamoDB tables are included in a backup plan
- EnDynamoDB DAX Clusters are encrypted at rest
- Ensure EKS Control Plane Logging is enabled for all required log types
- Ensure DynamoDB tables point-in-time recovery (PITR) is enabled
- Ensure AWS Organizations delegated administrators are trusted
- Ensure Kubernetes cluster runs on a supported Kubernetes version
- Ensure AWS Organization has tags policies enabled and attached
- Ensure EKS Clusters are not publicly accessible
- Ensure that AWS Organizations opt-out of AI services policy is enabled and disallow child-accounts to overwrite this policy
- Ensure AWS Regions are restricted with SCP policies
- Ensure Network Policy is Enabled and Set as Appropriate
- Ensure Kubernetes Secrets are encrypted using Customer Master Keys (CMKs)
- Ensure Clusters are created with Private Nodes
- Ensure account is part of an AWS Organizations
- Ensure DataSync tasks should have logging enabled
- Ensure for medium and high risks identified in workloads defined in the AWS Well-Architected Tool
- Ensure AWS WAFv2 WebACL logging is enabled
- Ensure API Gateway Public Endpoints Have Authorizers Configured
- Ensure API Gateway REST API Cache Data is Encrypted at Rest
- Ensure AWS WAFv2 WebACL has at least one rule or rule group
- Ensure API Gateway APIs and Methods Have Authorizers Configured
- Ensure AWS WAFv2 WebACL rule or rule group has Amazon CloudWatch metrics enabled
- Ensure Multi-Factor Authentication (MFA) is enabled for Amazon Cognito User Pools
- Ensure EBS Snapshot lifecycle policies are defined.
- Ensure Amazon Cognito User Pool should prevent user existence errors
- Ensure Cognito User Pool has password policy to require at least one lowercase letter
- Ensure that advanced security features are enabled for Amazon Cognito User Pools to block sign-in by users with suspected compromised credentials
- Ensure that the password policy for your Amazon Cognito user pool requires at least one symbol
- Ensure that token revocation is enabled for Amazon Cognito User Pools
- Ensure Macie automated sensitive data discovery is enabled.
- Ensure that all FMS policies inside an admin account are compliant
- Ensure AWS X-Ray Tracing is Enabled for API Gateway REST API Stages
- Check if API Gateway Stage has logging enabled.
- Ensure Elastic Beanstalk Environments Have Enhanced Health Reporting Enabled
- Ensure AWS AppSync GraphQL APIs should not be authenticated with API keys
- Ensure cognito user pools has advanced security enabled with full-function
- Ensure that the password policy for your user pool requires at least one uppercase letter
- Ensure Elastic Beanstalk Managed Platform Updates are Enabled
- Ensure that the user pool has a temporary password expiration period of 7 days or less
- Ensure that the password policy for your user pools require a minimum length of 14 or greater
- Ensure Elastic Beanstalk Environments Stream Logs to CloudWatch
- Ensure that the password policy for your user pool requires a number
- Ensure Cognito Identity Pool has guest access disabled
- Ensure self registration is disabled for Amazon Cognito User Pools
- Ensure that your Amazon Cognito user pool blocks potential malicious sign-in attempts
- Ensure cognito user pools deletion protection enabled to prevent accidental deletion
- Ensure AWS AppSync should have field-level logging enabled
- Ensure that Amazon Cognito User Pool is associated with a WAF Web ACL
- Ensure that CodeBuild projects have S3 or CloudWatch logging enabled
- Ensure Disaster Recovery Service(DRS) is enabled with jobs.
- Ensure CodeBuild projects do not contain secrets on plaintext environment variables
- Ensure CodeBuild project source repository URLs do not contain sensitive credentials
- Ensure CodeBuild Project has been invoked in the last 90 days
- Ensure S3 Logs for CodeBuild Projects are encrypted at rest
- Ensure CodeBuild Project uses a controlled buildspec
- Ensure CodeBuild report group exports are encrypted at rest
- Ensure DocumentDB Clusters have backup enabled
- Ensure DocumentDB Clusters has deletion protection enabled
- Ensure DocumentDB Cluster have Multi-AZ enabled
- Ensure DocumentDB manual cluster snapshot is public
- Ensure DocumentDB cluster storage is encrypted
- Enable DocumentDB clusters are using the log export feature
- Ensure that CDKToolkit stacks have a Bootstrap version of 21 or higher to mitigate security risks
- Ensure termination protection for Cloudformation Stacks Enabled
- EnsureService Catalog portfolios should be shared within an AWS organization only
- Ensure RDS instances are protected by a backup plan
- Ensure AWS Redshift Clusters Have Enhanced VPC Routing Enabled
- Ensu RDS instances has enhanced monitoring enabled
- Ensure AWS Redshift Clusters Are Encrypted at Rest
- Ensure Redshift clusters have Multi-AZ enabled.
- Ensure Redshift clusters are using the default database name.
- Ensure Redshift Clusters have automated snapshots enabled.
- Ensure Amazon Redshift clusters are using the default Admin username.
- Ensure for Redshift Automatic Version Upgrade
- Ensure connections to Amazon Redshift clusters are encrypted in transit.
- Ensure RDS clusters are protected by a backup plan
- Ensure that your Amazon RDS instances are not using the default master username
- Ensure RDS clusters storage is encrypted
- Ensure RDS instances are deployed within a VPC
- Ensure RDS DB instances have copy tags to snapshots enabled
- Ensure RDS Snapshots and Cluster Snapshots are public
- Ensure Kinesis streams should be encrypted at rest.
- Ensure Kinesis streams should have an adequate data retention period.
- Ensure Memory DB clusters have minor version upgrade enabled.
- Ensure AWS Lambda Functions Are Deployed Inside a VPC
- Ensure Lambda functions have resource-based policy set as Public.
- Ensure AWS Lambda Function VPC is deployed Across Multiple Availability Zones
- Ensure EC2 Transit Gateways Do Not Automatically Accept VPC Attachment Requests
- Ensure no security groups allow ingress from 0.0.0.0/0 or ::/0 to Kafka port 9092.
- Ensure No Secrets Are Hardcoded in EC2 Launch Templates
- Ensure Detailed Monitoring is Enabled for EC2 Instances
- Ensure that your Amazon RDS clusters are not using the default master username
- Ensure RDS clusters have deletion protection enabled
- Ensure RDS clusters have minor version upgrade enabled
- Ensure RDS clusters have IAM authentication enabled
- Ensu RDS instances have multi-AZ enabled
- Ensure RDS instance is using a supported engine version
- Ensure RDS instances enforce SSL/TLS encryption for client connections (Microsoft SQL Server, PostgreSQL, MySQL, MariaDB, Aurora PostgreSQL, and Aurora MySQL)
- Ensure RDS clusters have multi-AZ enabled
- Ensure RDS Security Group events are subscribed
- Ensure RDS instances are using non-default ports
- Ensure RDS instances have minor version upgrade enabled
- Ensure RDS instances have deletion protection enabled
- Ensure EC2 Launch Templates Do Not Assign Public IPs to Network Interfaces
- Ensure EC2 Instances Do Not Use Multiple Network Interfaces (ENIs) Unless Required
- Ensure RDS clusters are using non-default ports
- Ensure RDS Parameter Group events are subscribed
- Check if RDS Aurora MySQL Clusters have backtrack enabled
- Ensure RDS cluster is integrated with CloudWatch Logs
- Check if AWS Lambda Function VPC is deployed Across Multiple Availability Zones
- Ensure RDS DB clusters have copy tags to snapshots enabled
- Ensure RDS Instances events are subscribed
- Ensure RDS instances have IAM authentication enabled
- Ensure no EC2 instances allow ingress from the internet to TCP port 27017 or 27018 (MongoDB).
- Ensure RDS Cluster critical events are subscribed
- Ensure Elastic and Public IPs Are Not Indexed in Shodan
- Ensure that the SSL/TLS certificates configured for your Amazon RDS are not expired
- Ensure that SES identities are not publicly accessible
- Ensure Step Functions state machines should have logging enabled
- Ensure Security Groups Created by EC2 Launch Wizard Follow Least Privilege Principles
- Ensure Public Lambda Function URL
- Ensure Instance Metadata Service Version 2 (IMDSv2) is enforced for EC2 instances at the account level to protect against SSRF vulnerabilities.
- Ensure Lambda Function URL CORS configuration
- Ensure no security groups allow ingress from 0.0.0.0/0 or ::/0 to MySQL port 3306.
- Ensure EC2 Instances Do Not Have Unnecessary Public IPs
- Ensure security groups with more than 50 ingress or egress rules.
- Ensure no security groups allow ingress and egress from wide-open IP address with a mask between 0 and 24.
- Ensure EC2 Launch Templates Require IMDSv2 for Instance Metadata Access
- Ensure no security groups allow ingress from 0.0.0.0/0 or ::/0 to all ports.
- Ensure EC2 Instances Require IMDSv2 for Instance Metadata Access
- Ensure No EC2 Instances Allow Ingress from the Internet to TCP Port 3389 (RDP)
- Ensure no EC2 instances allow ingress from the internet to TCP port 23 (Telnet).
- Ensure no EC2 instances allow ingress from the internet to TCP port 11211 (Memcached)
- Ensure no security groups allow ingress from 0.0.0.0/0 or ::/0 to FTP ports 20 or 21.
- Ensure no EC2 instances allow ingress from the internet to TCP port 9092 (Kafka)
- Ensure EBS Snapshots Exist for EC2 Volumes
- Ensure Amazon ECS task definitions should have secure networking modes and user definitions
- Ensure centralized root credentials management is enabled
- Ensure No IAM Groups Have Administrator Access Policy
- Ensure IAM Inline Policies That Allow Full ":" Administrative Privileges Are Not Associated to IAM Identities
- Ensure IAM identities (users,groups,roles) have the AWSCloudShellFullAccess policy attached.
- Ensure IAM Inline Policies That Allow Full "kms:*" Privileges Are Not Created
- Ensure IAM Roles Do Not Have ReadOnlyAccess Access for External AWS Accounts
- Ensure No Security Groups Allow Ingress from 0.0.0.0/0 or ::/0 to Windows SQL Server Ports 1433 or 1434
- Ensure IAM Policies That Allow Full "kms:*" Privileges Are Not Created
- Ensure User Access Keys Unused Are Disabled
- Ensure no EC2 instances allow ingress from the internet to TCP port 6379 (Redis).
- Ensure Unused User Console Access Is Disabled
- Ensure IAM Policies That Allow Full "cloudtrail:*" Privileges Are Not Created
- Ensure No Network ACLs Allow Ingress from 0.0.0.0/0 to Any Port
- Ensure No Security Groups Allow Ingress from 0.0.0.0/0 or ::/0 to Windows SQL Server Ports 1433 or 1434
- Ensure No IAM Inline Policies Allow Actions That May Lead to Privilege Escalation
- Ensure no EC2 instances allow ingress from the internet to TCP port 6379 (Redis).
- Ensure IAM Users Have Two Active Access Keys
- Ensure IAM Customer-Managed Policies That Allow Full ":" Administrative Privileges Are Not Attached
- Ensure IAM Roles Do Not Have AdministratorAccess Policy Attached
- Ensure Public Access to EBS Snapshots Is Disabled
- Ensure No Security Groups Allow Ingress from 0.0.0.0/0 or ::/0 to Telnet Port 23
- Ensure EC2 Client VPN Endpoints Have Client Connection Logging Enabled
- Ensure Amazon EC2 Paravirtual Virtualization Type Is Not Used
- Ensure No EC2 Instances Allow Ingress from the Internet to Elasticsearch and Kibana Ports (TCP 9200, 9300, 5601)
- Ensure No EC2 Instances Allow Ingress from the Internet to TCP Port 88, 464, 749, or 750 (Kerberos)
- Ensure no EC2 instances allow ingress from the internet to TCP port 1521, 2483 or 2484 (Oracle).
- Ensure Amazon SageMaker Notebook instances have VPC settings configured
- Check if Amazon SageMaker Models have VPC settings configured
- Ensure Compute Instances Do Not Have Public IP Addresses (Automated)
- Check if Route53 Records contains dangling IPs.
- Ensure IAM Service Roles Prevent Against a Cross-Service Confused Deputy Attack
- Ensure Users Make Use of Temporary Credentials Assuming IAM Roles
- Ensure Amazon Elasticsearch/Opensearch Service domains have internal user database enabled
- Ensure a Security Audit Role Has Been Created to Conduct Security Audits
- Ensure there are no potential privilege escalation threats in CloudTrail.
- Ensure EFS Access Points Should Enforce a User Identity
- Ensure Amazon Elasticsearch/Opensearch Service domains have encryption at-rest enabled
- Ensure ECR image scan found vulnerabilities in the newest image version
- Ensure Amazon SageMaker Training jobs have intercontainer encryption enabled
- Ensure Amazon SageMaker Models have VPC settings configured
- Ensure Amazon Elasticsearch/Opensearch Service domains have fine grained access control enabled
- Ensure GuardDuty EKS Runtime Monitoring should be enabled
- Ensure GuardDuty Lambda Protection is enabled
- Ensure GuardDuty EKS Audit Log Monitoring Enabled
- Ensure Neptune DB clusters are configured to copy tags to snapshots
- Ensure Neptune Clusters Backup Retention Period
- Ensure the database does not have public mode enabled
- Ensure static IPs are allocated but not attached to any instance
- Ensure Neptune Clusters have audit cloudwatch logs enabled
- Ensure Neptune Clusters storage is encrypted at rest
- Ensure Elastic Load Balancers (ELBs) Have SSL Listeners
- Ensure Amazon SageMaker Training jobs have network isolation enabled
- Ensure EC2 Auto Scaling Group uses multiple Availability Zones
- Ensure Neptune Clusters have multi-AZ enabled
- Ensure Neptune Clusters have IAM authentication enabled
- Ensure NeptuneDB Manual Cluster Snapshot is Public
- Ensure Neptune DB Cluster Snapshots Are Encrypted At Rest
- Ensure Glue development endpoints have CloudWatch logs encryption enabled
- Ensure a log metric filter and alarm are in place for AWS Management Console authentication failures
- Ensure a log metric filter and alarm are are in place for changes to Network Access Control Lists (NACL)
- Ensure a log metric filter and alarm are in place for CloudTrail configuration changes
- Ensure a log metric filter and alarm are in place for security group changes
- Ensure a log metric filter and alarm are in place for root account usage
- Ensure a log metric filter and alarm are in place for AWS Config configuration changes
- Ensure a log metric filter and alarm are in place for IAM policy changes
- Ensure a log metric filter and alarm are in place for VPC changes
- Ensure a log metric filter and alarm are in place for unauthorized API calls
- Ensure a log metric filter and alarm are in place for the disabling or scheduled deletion of customer-created KMS CMKs
- Ensure a log metric filter and alarm exist for Management Console sign-in without MFA
- Ensure a log metric filter and alarm exist for S3 bucket policy changes
- Ensure a log metric filter and alarm exist for changes to network gateways
- Ensure Amazon Elasticsearch/Opensearch Service domains have logging enabled
- Ensure Amazon Elasticsearch/Opensearch Service domains have logging enabled
- Ensure Amazon Opensearch/Elasticsearch domains are not set as Public or have open policy access
- Ensure Route53 public hosted zones are logging queries to CloudWatch Logs
- Ensure checking for internet facing Elastic Load Balancers
- Ensure IAM Access Analyzer is enabled without findings
- Ensure IAM Access Analyzer is enabled
- Ensure publicly accessible Redshift clusters are checked
- Ensure Redshift cluster has audit logging enabled
- Ensure Trusted Advisor is checked for errors and warnings
- Ensure CloudTrail log file validation is enabled
- Ensure CloudTrail is enabled across all regions
- Ensure CloudTrail logs are encrypted at rest using KMS CMKs
- Ensure CloudTrail trails are integrated with CloudWatch Logs
- Ensure the S3 bucket CloudTrail logs is not publicly accessible
- Ensure S3 bucket access logging is enabled on the CloudTrail S3 bucket
- Ensure S3 buckets have Object-level logging for read events enabled in CloudTrail
- Ensure that Object-level logging for write events is enabled in CloudTrail for S3 buckets
- Ensure AWS Config is enabled in all regions
- Ensure internet facing Elastic Load Balancers are checked
- Ensure DocumentDB instances storage is encrypted
- Ensure VPCs are present in multiple regions
- Ensure routing tables for VPC peering have least access
- Ensure VPC Flow Logging is Enabled in all VPCs
- Ensure SNS topics have policy set as Public
- Ensure SQS queues have Server Side Encryption enabled
- Ensure SQS queues have policy set as Public
- Ensure secrets exist in ECS task definitions environment variables
- Ensure GuardDuty is enabled
- Ensure RDS instances client connections are encrypted (Microsoft SQL Server, PostgreSQL, MySQL, MariaDB, Aurora PostgreSQL, and Aurora MySQL)
- Ensure RDS instances have backup enabled
- Ensure RDS instances storage is encrypted
- Ensure there are no Public Accessible RDS instances.
- Ensure RDS instances are integrated with CloudWatch Logs
- Ensure that ECR image scan on push is enabled
- Check if ACM certificates have Certificate Transparency logging enabled
- Ensure ACM Certificates are about to expire in specific days or less
- Ensure S3 buckets have server access logging enabled
- Ensure S3 buckets have object versioning enabled
- Ensure S3 buckets have default encryption (SSE) enabled or use a bucket policy to enforce it
- Ensure that S3 buckets have policies which allow WRITE access
- Ensure there are no ECR repositories set as Public
- Ensure Amazon Macie is enabled
- Ensure S3 buckets have secure transport policy
- Ensure rotation for customer created KMS CMKs is enabled
- Ensure exposed KMS keys are checked
- Ensure a support role has been created to manage incidents with AWS Support.
- Ensure IAM AWS-Managed policies that allow full "*:*" administrative privileges are not attached
- Ensure access keys are rotated every 90 days or less
- Ensure there are SAML Providers then STS can be used
- Ensure IAM Service Roles prevent against a cross-service confused deputy attack
- Ensure that S3 buckets are not open to Everyone or Any AWS user
- Ensure IAM users have Hardware MFA enabled
- Ensure multi-factor authentication (MFA) is enabled for all IAM users that have a console password
- Ensure that the IAM password policy requires at least one symbol
- Ensure there are no EBS Snapshots set as Public
- Ensure CloudFront distributions have logging enabled
- Ensure CloudFront distributions have Field Level Encryption enabled
- Ensure geo restrictions are enabled in CloudFront distributions
- Ensure CloudFront distributions are set to HTTPS
- Ensure API Gateway Stage has a WAF ACL attached
- Ensure API Gateway endpoint is public or private
- Ensure API Gateway Stage has client certificate enabled to access your backend endpoint
- Ensure API Gateway V2 has configured authorizers
- Ensure that no Network ACLs permit ingress from 0.0.0.0/0 to Microsoft RDP port 3389.
- Ensure EBS Default Encryption is activated.
- Ensure no Security Groups are currently unused.
- Ensure there are no EC2 AMIs set as Public.
- Ensure no security groups allow ingress from 0.0.0.0/0 or ::/0 to Redis port 6379.
- Ensure to check for internet facing EC2 instances with Instance Profiles attached.
- Ensure no security groups allow ingress from 0.0.0.0/0 or ::/0 to any port.
- Ensure EBS snapshots are encrypted.
- Ensure no security groups allow ingress from 0.0.0.0/0 or ::/0 to MongoDB ports 27017 and 27018.
- Ensure EC2 Instances older than specific days are checked.
- Ensure IAM instance roles are used for AWS resource access from instances.
- Ensure there are no EBS Volumes unencrypted.
- Ensure no security groups allow ingress from 0.0.0.0/0 or ::/0 to SSH port 22.
- Ensure secrets are found in EC2 User Data.
- Ensure no security groups allow ingress from 0.0.0.0/0 or ::/0 to port 3389.
- Ensure the default security group for every VPC restricts all traffic.
- Ensure no security groups allow ingress from 0.0.0.0/0 or ::/0 to Oracle ports 1521 or 2483.
- Ensure no security groups allow ingress from 0.0.0.0/0 or ::/0 to Memcached port 11211.
- Ensure no security groups allow ingress from 0.0.0.0/0 or ::/0 to Cassandra ports 7199 or 9160 or 8888
- Ensure Lambda functions invoke API operations are being recorded by CloudTrail.
- Ensure secrets are found in Lambda functions variables.
- Ensure obsolete Lambda runtimes are found.
- Ensure secrets are found in Lambda functions code.
- Ensure no secrets are in CloudFormation outputs.
- Ensure EKS Control Plane Audit Logging is enabled for all log types
- Ensure access to the EKS Control Plane Endpoint is restricted.
- Ensure that EKS Clusters are configured with private endpoints enabled and public access disabled.
- Ensure the use of root accounts is avoided.
- Ensure no root account access key exists.
- Ensure IAM password policy requires minimum length of 14 or greater
- Ensure only hardware MFA is enabled for the root account.
- Ensure that the IAM password policy mandates at least one number.
- Ensure no Customer Managed IAM policies allow actions that may lead into Privilege Escalation
- Ensure that the IAM password policy prohibits password reuse, specifically 24 or greater.
- Ensure that IAM policies are attached only to groups or roles.
- Ensure that IAM password policy requires at least one lowercase letter.
- Ensure IAM password policy requires at least one uppercase letter
- Ensure MFA is enabled for the root account.
- Ensure that access keys are not set up during initial user setup for all IAM users that have a console password.
- Ensure that all the expired SSL/TLS certificates stored in AWS IAM are removed.
- Ensure IAM password policy expires passwords within 90 days or less.
- Ensure that users within groups holding AdministratorAccess policy have multi-factor authentication (MFA) tokens activated.
- Ensure that Lightsail instances are not publicly accessible
- Ensure Amazon Opensearch/Elasticsearch domains are not publicly accessible
- Ensure no EC2 instances allow ingress from the internet to TCP port 3306 (MySQL).
- Ensure Amazon EBS volumes should be protected by a backup plan.
- Ensure no EC2 instances allow ingress from the internet to TCP port 5432 (PostgreSQL)
- Ensure Elasticache Redis cache clusters have in transit encryption enabled.
- Ensure no secrets are in Lambda functions code.
- Ensure that RDS Snapshots and Cluster Snapshots are encrypted.