turbot/steampipe-mod-aws-compliance

Control: 7 Redshift Serverless namespaces should not use the default database name

Description

This control checks whether an Amazon Redshift Serverless namespace uses the default database name, dev. The control fails if the Redshift Serverless namespace uses the default database name, dev.

When creating an Amazon Redshift Serverless namespace, you should specify a unique, custom value for the database name and not use the default database name, which is dev. The default database name is public knowledge. By specifying a different database name, you can mitigate risks such as unauthorized users inadvertently gaining access to data in the namespace.

Remediation

You can't change the database name for an Amazon Redshift Serverless namespace after you create the namespace. You can, however, specify a custom database name for a Redshift Serverless namespace when you create the namespace. For information about creating a namespace, see Workgroups and namespaces in the Amazon Redshift Management Guide.

Usage

Run the control in your terminal:

powerpipe control run aws_compliance.control.foundational_security_redshiftserverless_7

Snapshot and share results via Turbot Pipes:

powerpipe login
powerpipe control run aws_compliance.control.foundational_security_redshiftserverless_7 --share

SQL

This control uses a named query:

select
namespace_arn as resource,
case
when db_name = 'dev' then 'alarm'
else 'ok'
end as status,
case
when db_name = 'dev' then title || ' uses default database name.'
else title || ' not uses default database name.'
end as reason
, region, account_id
from
aws_redshiftserverless_namespace;

Tags