Skip to main content
Connect your MongoDB database so Myrmex can audit its hardening and compliance, check its operational health, explore its collections, and — with approval — run queries and commands for you. Myrmex reaches the database over the native MongoDB protocol through a Collector on your network. Operations run live and on demand through the Integration Specialist agent — Myrmex reads only what you ask for and keeps none of your data on the Myrmex side.

​
What Myrmex Can Do

Compliance audit

Run a Security Posture audit and map findings to CIS, ISO 27001, NIST CSF, and BACEN frameworks.

Health checks

Review connections, replication lag, the oplog window, and cache usage.

Explore collections

List databases and collections so you can see what the instance holds.

Describe structure

Inspect a collection’s fields, indexes, and validation rules.

Sensitive-data scan

Scan collections and fields for personal or sensitive data that needs protection.

Run queries

Run read queries and commands any time; writes require your confirmation.

​
Before You Start

  • A Collector on a network that can reach the MongoDB host on its TCP port (default 27017). See Collector mode.
  • A dedicated database user for Myrmex (create it in Step 1).
  • The Auth Database is the authSource where the user is defined (default admin).

​
Step 1 — Create the Credential in MongoDB

Create a dedicated, least-privilege user for auditing. clusterMonitor grants read access to server status and configuration; readAnyDatabase lets Myrmex list collections and inspect structure.
Keep the account read-only for auditing. Add readWrite on the target database only if you want the agents to run write operations through Run queries.

​
Step 2 — Add the Integration in Myrmex

From the Directory, choose Add Integration → MongoDB, then fill in:

​
Connect

Click Connect to validate the login. The database then appears under Environment → Integrations alongside your other integrations, and you can start asking the AI about it in the Workspace.

​
Notes

  • Read-only by default. Auditing, health, exploration, and sensitive-data scans only need the read-only roles above. Add readWrite only if you want confirmation-gated Run queries writes.
  • Nothing is stored. Every operation runs in real time through the Collector; results return to your Workspace and no database data is retained on the Myrmex side.
  • Encryption in transit follows your server’s configuration; the posture audit flags an unencrypted listener.