TL;DR
| Supported data types | 3rd party detection | Hunters detection | IOC search | Search | Table name | Log format | Collection method |
|---|---|---|---|---|---|---|---|
| MongoDB Atlas Audit Events | ✅ | ✅ | ✅ | mongodb_atlas_audit_events |
JSON | API, S3, GCP Bucket List, Azure Block Storage List |
Overview
MongoDB Atlas is a fully-managed cloud database service, and its Administration API exposes an organization-level activity/events feed that records significant administrative, security, and billing actions taken across an Atlas organization and its projects (groups). Each event documents who performed an action (user, API key, or service account), from which IP address, what type of action occurred (e.g., user added to a project, API key created, network access list modified, cluster created/deleted, authentication failures), and when it happened. This feed is highly valuable for security operations because it provides an audit trail of identity and access changes, network configuration changes, encryption/security configuration changes, and authentication failures within the Atlas control plane — key signals for detecting account compromise, privilege escalation, or unauthorized infrastructure changes. Integrating this data with Hunters allows these events to be correlated with other telemetry across your environment to surface threats originating from, or targeting, your Atlas organization.
Supported data types
MongoDB Atlas Audit Events
Table name: mongodb_atlas_audit_events
This data type contains the MongoDB Atlas activity feed of the organization and of each of its projects: identity and access changes (users, database users, API keys and service accounts), project membership and role changes, network access list modifications, cluster lifecycle events, Data Explorer activity, and billing-related activity. Each record captures the actor, the affected resource, the source IP address, and the event type, providing a clear audit trail for security investigations.
Expected format
Logs are expected in JSON format.
{"id":"66f1a2b3c4d5e6f7a8b9c0d7","groupId":"5f1a2b3c4d5e6f7a8b9c0d14","orgId":"5a0a1e7e0f2912c554080adc","created":"2024-06-01T17:12:40Z","eventTypeName":"API_KEY_ACCESS_LIST_ENTRY_ADDED","userId":"609f1b2c3d4e5f6a7b8c9d07","username":"gina.park@example.com","remoteAddress":"192.0.2.88","apiKeyId":"66f1a2b3c4d5e6f7a8b9c0a2","whitelistEntry":"192.0.2.88/32","isGlobalAdmin":false,"links":[{"rel":"self","href":"https://cloud.mongodb.com/api/atlas/v2/orgs/5a0a1e7e0f2912c554080adc/events/66f1a2b3c4d5e6f7a8b9c0d7"}]}
Send data to Hunters
Hunters supports the collection of MongoDB Atlas logs using API, S3 List, S3 Notifications, GCP Bucket List, and Azure Block Storage List.
To connect MongoDB Atlas logs:
Connect using S3
- Route MongoDB Atlas logs into an AWS S3 bucket.
- Once logs are in S3, follow the steps in this section.
Connect using Azure Block Storage List
- Route MongoDB Atlas logs into an Azure Storage container as block blobs.
- Once logs are in the container, follow the steps in this section.
Connect using GCP Bucket List
- Route MongoDB Atlas logs into a Google Cloud Storage bucket.
- Once logs are in the bucket, follow the steps in this section.
Connect using API
Hunters pulls the organization events feed (GET /api/atlas/v2/orgs/{orgId}/events) and the events feed of every project the service account can read (GET /api/atlas/v2/groups/{groupId}/events) from the MongoDB Atlas Administration API on a schedule, using an Atlas organization service account.
- In MongoDB Atlas, open your organization and go to Identity & Access > Applications > Service Accounts, then click Add new (or Create Service Account).
- Give the service account a name and description, and choose a client secret expiration.
- Under Organization Permissions, select Organization Read Only. This role covers the organization events and the events of every project. If you prefer narrower access, grant Organization Member and add the service account to each project with Project Read Only; Hunters then collects the events of those projects only.
- Click Create, then copy the Client ID and the Client Secret. The secret starts with
mdb_sa_sk_and Atlas shows it only once. - If your organization requires an IP access list for the Atlas Administration API (the default for organizations created in the Atlas UI), add Hunters' egress IP addresses to the service account's API Access List. If you skip this, Atlas rejects Hunters' requests with HTTP 403.
- Copy your Organization ID from Organization Settings.
- In the Hunters portal, connect the MongoDB Atlas data source with the Organization ID, Client ID and Client Secret, as described in this section.
For more details, see MongoDB's guide: Get Started with the Atlas Administration API.