Check ID:
Provider: MongoDB Atlas
Service:
Severity: HIGH
Categories:
Resource type:
clusters_tls_enabledProvider: MongoDB Atlas
Service:
clustersSeverity: HIGH
Categories:
encryptionResource type:
NotDefinedWhat this check verifies
MongoDB Atlas clusters require TLS/SSL for client connections to encrypt data in transit (sslEnabled=true).
Risk
Without enforced TLS, traffic can be intercepted or altered, degrading confidentiality and integrity. Attackers can run man-in-the-middle attacks, steal credentials or session tokens, and inject/replay queries, leading to unauthorized data access.Recommendation
Enforce TLS 1.2+ for all connections and keep it mandatory (sslEnabled=true).
Apply zero trust and defense in depth: use CA-signed certificates, disable tlsInsecure and similar bypasses, rotate certificates, and restrict access via private networking or trusted IP ranges.
Remediation
- CLI
- Dashboard steps
References
- https://www.mongodb.com/docs/atlas/setup-cluster-security/#encryption-in-transit
- https://www.mongodb.com/docs/compass/connect/advanced-connection-options/tls-ssl-connection/
- https://www.mongodb.com/docs/manual/tutorial/configure-ssl-clients/
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_tls_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