NoSQL database security hardening
High
Cross-cloud
General
cosmosdb-nosql-database-security-hardening
Applies to
Microsoft.DocumentDB/databaseAccountsAWS::DynamoDB::Table
What CGPulse checks
A resource passes this rule when disableLocalAuth must be set true OR sseEnabled must equal true. Anything else is reported as a finding with the evaluated property value attached as evidence.
How to fix it
Configure IAM-based authentication for DynamoDB to enforce scoped, auditable access. In AWS Console: IAM > configure fine-grained DynamoDB policies. See: https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/authentication-and-access-control.html
Compliance frameworks
Is your environment compliant with this rule?
CGPulse checks it — and 621 others — against your Azure and AWS accounts with read-only access.
Related Cross-cloud rules
- Block storage volumes must be encrypted
- Cache service security hardening
- Cache services must enforce TLS encryption in transit
- Container registry security hardening
- Database authentication must use managed identities
- Databases must not be publicly accessible
- IAM password policy must require minimum length of 14
- Key management service security hardening