Integrations · NoSQL · Available now
MongoDB test data, inside your network
MongoDB connector (pymongo): collection discovery, field shapes inferred from a bounded sample inside your network, _id or unique-index-backed business keys, document counts, aggregate profiles and bounded streaming reads with nested documents carried as JSON text.
Available now NoSQL
Shipped in the standard agent and backed by recorded conformance evidence.
MongoDB has no foreign keys. DataNivra cannot discover relationships from MongoDB: they come from an industry pack’s relationship mappings or relationships you declare. Without declared relationships, subsets do not follow relationships and the orphan check cannot cover them.
The console warns before a build that has none, and the certificate records RELATIONSHIPS_NOT_DECLARED for that source instead of reporting zero orphans as a check.
What works today
MongoDB connector (pymongo): collection discovery, field shapes inferred from a bounded sample inside your network, _id or unique-index-backed business keys, document counts, aggregate profiles and bounded streaming reads with nested documents carried as JSON text.
SCRAM user with only the read role on the selected databases; the password is a secret reference. TLS with certificate and host-name verification is the default (verify-ca and disabled are explicit opt-outs). Every operation carries maxTimeMS; reads use secondaryPreferred by default and aggregation pipelines can never contain $out or $merge.
Authentication: SCRAM-SHA-256 / SCRAM-SHA-1 username and password (secret reference).
Known limitations
- Requires agent 0.4.0 or later; earlier agent images do not include the pymongo driver.
- Fields are inferred from a bounded $sample per collection (sample_size); a later document whose field type differs stops the read with FIELD_TYPE_DRIFT. Fields outside the inferred columns are carried, never dropped, in one JSON column (_extra_fields).
- Nested documents and arrays are masked and provisioned as JSON text, not as nested fields.
- Only regular collections are read (no views or time-series collections).
- SCRAM password authentication only (no X.509, LDAP, Kerberos or AWS IAM authentication).
- MongoDB declares no relationships: they come from industry packs or explicit mappings. Business keys other than _id need a unique, non-partial index.
- Verified against MongoDB 8.0 (TLS verified) and 7.0 Community in Docker; MongoDB Atlas and Amazon DocumentDB are not yet tested.
Capability matrix
Each capability is tracked separately and shown at the level the recorded conformance evidence supports. A connector that only discovers metadata is never presented as equivalent to one that runs the whole workflow.
| Capability | Level |
|---|---|
| Discovery | Supported |
| Classification | Supported |
| Profiling | Supported |
| Masking | Supported |
| Deterministic masking | Supported |
| Entity-aware subsetting | Supported |
| Relationship preservation | Supported |
| Synthetic workflows | Supported |
| Certification | Supported |
| Provisioning | Supported |
| CI/CD | Supported |
| Evidence generation | Supported |
Read-only proof
Proven before reading: connectionStatus with showPrivileges returns the privileges MongoDB computed for the authenticated user; every action on every resource must be a read action (find, listCollections, listIndexes, collStats, dbStats, killCursors, listDatabases, ...). readWrite, admin and monitoring roles, and unauthenticated sessions, refuse the source.
Conformance evidence
DataNivra runs every connector through a common conformance kit on synthetic data: no write statements, proven read-only access, secret redaction, schema and relationship discovery, bounded streaming, cancellation, clear reason codes, egress canaries and no raw values in logs, then the discover, mask, subset, certify and provision workflow. The published status is computed from those results.
| Engine or service | Version | Environment | Driver | Authentication | Verified on |
|---|---|---|---|---|---|
| MongoDB | 7.0.43 | real-engine | pymongo 4.18.2 | SCRAM-SHA-256 (plaintext, explicit tls: disabled) | 2026-10-08 |
| MongoDB | 8.0.32 | real-engine | pymongo 4.18.2 | SCRAM-SHA-256 (TLS, certificate and host name verified) | 2026-10-08 |
Connector version 0.1.0, last verified 2026-10-08.
What crosses the boundary
Connectors run inside the agent in your network. Only metadata, aggregates and evidence reach DataNivra Cloud:
- Schema, table and column names and data types (for file sets, operator-declared or opaque table names — never data-derived file names).
- Aggregates such as row-count estimates, null and distinct ratios; counts from 1 to 10 are reported as 10 (small-cell protection).
- Classification findings (which column looks like which kind of sensitive data) and relationship metadata.
- Evidence metadata: checksums, gate outcomes, engine and policy versions, and templated error codes.
Never sent:
- Any cell value, row, sample, minimum/maximum or top-k value — masked or not.
- Credentials, connection strings or resolved secret values: DataNivra stores only the secret reference.
- Free text copied from your data, or exception messages that contain values.
See the customer-resident architecture and how to verify these claims yourself.
Setup outline
- Use agent 0.4.0 or later: the standard agent image includes the MongoDB driver (pymongo).
- Create a dedicated user holding only the built-in read role on the databases to read (no readWrite, admin, user-administration or monitoring role), ideally against a secondary.
- Store the connection document with the password as a secret reference. TLS with certificate and host-name verification (verify-full) is the default; verify-ca and disabled are explicit opt-outs. Declare business keys in key_fields only where a unique index backs them.
- In the console, register the source with the secret reference of that document (for example vault://tdm/source-connection) and the agent that can reach it, then run discovery.
- Before reading, the agent proves the user is read-only from connectionStatus (the privileges MongoDB computed for the user) and refuses to continue if any non-read action is granted. Field shapes come from a bounded sample read inside your network.
Example connection document, stored in your secret store and resolved by the agent locally (DataNivra only ever sees its reference):
{
"kind": "MONGODB",
"hosts": ["claims-rs0.db.example.internal:27017"],
"replica_set": "rs0",
"databases": ["enrollment", "claims"],
"user": "tdm_reader",
"password_ref": "vault://tdm/claims-mongo#password",
"key_fields": { "enrollment.members": ["member_id"] }
}Next: install the agent, then follow the getting started guide.
All integrations · NoSQL test data management · Guides · Start free