AWS Redshift Audit - Security Checks
Checks Performed
- Amazon EMR Clusters Should Have Kerberos Enabled
- Clusters With High Disk Usage Should Be Scaled
- EMR Cluster Logging Should Be Enabled
- EMR Cluster Master Node Should Not Have Public IP
- EMR Clusters Should Be In VPC
- EMR In-Transit And At-Rest Encryption Should Be Enabled
- EMR Instances Should Use Latest Generation
- Idle Redshift Clusters Should Be Terminated
- Redshift Automated Snapshots Should Have Retention Period Enabled
- Redshift Cluster Audit Should Have Logging Enabled
- Redshift Cluster Nodes Should Be Of The Desired Type
- Redshift Cluster Should Not Be Publicly Accessible
- Redshift Cluster Should Not be Underutilized
- Redshift Cluster Should Not Use Default Master Username
- Redshift Clusters Should Allow Version Upgrade
- Redshift Clusters Should Be Encrypted
- Redshift Clusters Should Be Encrypted With KMS CMKs
- Redshift Clusters Should Be Launched Within a VPC
- Redshift Clusters Should Have Deferred Maintenance Enabled
- Redshift Clusters Should Not Use Default Port
- Redshift Clusters Should Use Latest Generation Of Nodes
- Redshift Nodes Limit
- Redshift Parameter Group Require SSL
- Redshift Reserved Node Lease Expiration In The Next 30 Days
- Redshift Reserved Node Lease Expiration In The Next 7 Days
- Redshift Reserved Node Recent Purchases Should Be Reviewed
- Redshift Reserved Node Should Not Have Status - Payment Pending
- Redshift Reserved Nodes Should Not Be Unused
- Redshift Reserved Nodes Should Not Have Status - Payment Failed
- Redshift User Activity Logging Should Be Enabled