Check ID:
Provider: MongoDB Atlas
Service:
Severity: CRITICAL
Categories:
Resource type:
clusters_authentication_enabledProvider: MongoDB Atlas
Service:
clustersSeverity: CRITICAL
Categories:
identity-accessResource type:
NotDefinedWhat this check verifies
MongoDB Atlas clusters enforce database authentication for client connections (authEnabled).
Identifies clusters where authentication is not required for access.
Risk
Without authentication, anyone with network reach can access the database, compromising confidentiality and integrity. Attackers can exfiltrate data, modify or delete records, and create backdoor users, leading to outages and data loss that impact availability.Recommendation
Enable and enforce database authentication on all clusters.- Prefer strong methods (X.509, OIDC, AWS IAM) over static passwords
- Grant least privilege roles and avoid shared accounts
- Rotate credentials/keys
- Combine with IP access lists or private endpoints for defense in depth
Remediation
- CLI
- Terraform
- Dashboard steps
atlas dbusers create —username <USERNAME> —password <PASSWORD> —role readWriteAnyDatabase@admin —projectId <PROJECT_ID>
References
- https://www.mongodb.com/docs/atlas/security/quick-start/
- https://www.mongodb.com/docs/atlas/security-ldaps-okta/
- https://www.mongodb.com/docs/atlas/security/config-db-auth/
- https://www.mongodb.com/docs/atlas/security-ldaps-onelogin/
Where this check fires
This check runs on every scheduled scan against your MongoDB Atlas account. Findings appear at Cloud Security → Findings filterable byCheck ID = clusters_authentication_enabled. To re-evaluate after a fix, hit Run now on the account’s schedule under Cloud Security → Schedules — the next scan re-checks this control and marks the finding fixed or keeps it persistent.
← Back to MongoDB Atlas checks