Cortex CloudApplication Security
Redshift clusters are not using the default database name. misconfiguration detected in code
Rule Details
Cortex AppSec Rule ID
APPSEC_AWS_320
Category - Subcategory
Compute - Overprovisioned
Provider
AWS
Severity
MEDIUM
Framework
Terraform, Terraform Plan
Impact
This rule is checking to ensure that Redshift clusters are not using the default database name. Using the default database name in AWS Redshift clusters can pose a security risk as it can be easily guessed by malicious actors. They could potentially gain unauthorized access to your database if other security measures are weak or compromised. For enhanced security, it is recommended to use a unique database name that cannot be easily guessed.
How to Fix
Resource: aws_redshift_cluster
Arguments: database_name
To fix the issue, you need to ensure that your Redshift clusters are not using the default database name. You should specify a unique name for every Redshift cluster you create. [source,go]
resource "aws_redshift_cluster" "default" { cluster_identifier = "tf-redshift-cluster" database_name = "my_db" }
PreviousElasticsearch domains are not configured with a minimum of three dedicated master nodes misconfigura
NextRedshift clusters are not using enhanced VPC routing misconfiguration detected in code
Last updated
Was this helpful?
