MongoDB Atlas
Collect organization, project, cluster, database-user, and access-list inventory through the MongoDB Atlas API v1.0.
What this connector audits
Checks this connector runs once it's connected. This is the full list; we don't claim coverage beyond what's implemented.
- Database user inventory and role permissions
- Network IP access list and peering configurations
- Cluster and database configurations
Endpoints this template queries
The exact MongoDB Atlas API endpoints called once connected. All read-only GET requests unless noted.
- GET/orgs
- GET/groups
- GET/groups/{groupId}/clusters
- GET/groups/{groupId}/databaseUsers
- GET/groups/{groupId}/accessList
What we need
Field labels only. We never show secret values here. Credentials are encrypted at rest and used only to run the checks above.
- Base URL(prefilled: https://cloud.mongodb.com/api/atlas/v1.0)
- Endpoints (JSON)(prefilled: [ { "id": "orgs", "name": "Organizations", "path": "/orgs" }, { "id": "projects", "name": "Projects", "path": "/groups" }, { "id": "clusters", "name": "Clusters", "path": "/groups/{groupId}/clusters" }, { "id": "database-users", "name": "Database users", "path": "/groups/{groupId}/databaseUsers" }, { "id": "access-list", "name": "IP access lists", "path": "/groups/{groupId}/accessList" } ])
- Auth header name(prefilled: Authorization)
- Auth header value(secret credential)
Required
Optional
Which frameworks this evidence supports
MongoDB Atlas evidence feeds into controls for any framework you run that requires this check type; the same synced evidence can satisfy more than one framework's requirements instead of being collected per audit.
Don't see your system?
Tell us what you use and what it needs to prove. We'll follow up about adding a connector.
Wire in MongoDB Atlas evidence
Get a guided demo, or start by scanning any domain for free.