MongoDB Atlas project network access list configuration is evaluated for entries that allow access from anywhere (0.0.0.0/0, ::/0, 0.0.0.0, ::) or for missing access lists, instead of restricting connections to specific IPs or CIDRs.
Risk
Internet-wide access enables scanning, brute force, and credential stuffing against database endpoints. A successful compromise can cause data exfiltration (confidentiality), unauthorized writes or drops (integrity), and service disruption or lockout (availability).
prowler mongodbatlas --checks projects_network_access_list_exposed_to_internet
Recommendation
Apply least privilege: permit only required IPs/CIDRs or approved security groups; avoid 0.0.0.0/0 and ::/0. Prefer private connectivity (VPC peering or private endpoints) over public access. Use temporary entries for short-lived admin needs and review lists regularly.
Remediation
- In MongoDB Atlas, open your project and go to Security > Database & Network Access > IP Access List
- Delete any entries equal to 0.0.0.0/0, ::/0, 0.0.0.0, or ::
- If the list becomes empty, click Add IP Address and add a specific IP/CIDR or an AWS Security Group (for a peered VPC)
- Click Save
Source Code
Resource Type
NotDefined