Check ID:
Provider: AWS
Service:
Severity: MEDIUM
Categories:
Resource type:
dms_endpoint_mongodb_authentication_enabledProvider: AWS
Service:
dmsSeverity: MEDIUM
Categories:
identity-accessResource type:
AwsDmsEndpointWhat this check verifies
AWS DMS MongoDB endpoints use an authentication mechanism. Configuration expectsAuthType not no (e.g., password) with an authMechanism such as scram_sha_1 or mongodb_cr.
Risk
Without authentication, unauthenticated connections can access the source, degrading confidentiality and integrity. Adversaries could read or modify migrated documents, hijack CDC, inject data, or exfiltrate records during replication.Recommendation
Enforce strong authentication on MongoDB endpoints: setAuthType to password and use authMechanism like scram_sha_1. Apply least privilege database accounts, store secrets in Secrets Manager, and pair with TLS for defense in depth.
Remediation
- CLI
- Terraform
- Native IaC
- Dashboard steps
References
- https://docs.aws.amazon.com/dms/latest/userguide/CHAP_Source.MongoDB.html
- https://docs.aws.amazon.com/securityhub/latest/userguide/dms-controls.html#dms-11
Where this check fires
This check runs on every scheduled scan against your AWS account. Findings appear at Cloud Security → Findings filterable byCheck ID = dms_endpoint_mongodb_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 AWS checks