Integrations · Databases · Available now
CockroachDB test data, inside your network
CockroachDB through the PostgreSQL connector, with its own compatibility record: catalog discovery, declared primary and foreign keys, row estimates from CockroachDB's table statistics, bounded aggregate profiles and server-side-cursor reads over verified TLS. PostgreSQL wire compatibility is never assumed: CockroachDB is detected and tested separately.
Available now Databases
Shipped in the standard agent and backed by recorded conformance evidence.
Before connecting, an administrator must run one check. CockroachDB does not show a user its own legacy role options, so the reader’s login cannot see them and the agent’s read-only proof does not cover them. CREATELOGIN, for example, lets a user change another non-admin user’s password.
Not visible to the agent: CREATELOGIN, CONTROLJOB, CANCELQUERY, CONTROLCHANGEFEED, MODIFYCLUSTERSETTING.
Run as an administrator:
SELECT username, options, member_of FROM [SHOW ROLES] WHERE username = 'tdm_reader';Expected: One row: tdm_reader | {} | {} — options must be empty. If the reader gets SELECT through roles (member_of not empty), run the same query for each of those roles: their options must be empty too.
Everything else is verified automatically before every read: read-only session, no SUPERUSER, CREATEROLE or CREATEDB, no admin membership, no write-capable system privilege, and only SELECT / USAGE / EXECUTE / CONNECT grants (no ownership, no grant option).
What works today
CockroachDB through the PostgreSQL connector, with its own compatibility record: catalog discovery, declared primary and foreign keys, row estimates from CockroachDB's table statistics, bounded aggregate profiles and server-side-cursor reads over verified TLS. PostgreSQL wire compatibility is never assumed: CockroachDB is detected and tested separately.
Served by the PostgreSQL connector, which detects CockroachDB from version() (set flavor="cockroachdb" to refuse any other server); evidence is recorded separately. sslmode defaults to verify-full; every session is read-only with a statement timeout.
Authentication: SQL user and password over TLS (secret reference).
Known limitations
- Administrator check before connecting: the reader's own login cannot see its legacy role options (CREATELOGIN, CONTROLJOB, CANCELQUERY, CONTROLCHANGEFEED, MODIFYCLUSTERSETTING), so the read-only proof does not cover them. An administrator runs SELECT username, options, member_of FROM [SHOW ROLES] WHERE username = 'tdm_reader'; once and expects empty options ({}) for the reader and for any role it is a member of. Everything else is verified automatically.
- Requires agent 0.4.2 or later: earlier agents cannot prove a CockroachDB user read-only and refuse the source (the driver, psycopg, ships in the standard agent image).
- Password authentication only (no client-certificate, GSSAPI or JWT authentication).
- Row estimates need table statistics (CockroachDB collects them automatically); without them the connector counts rows exactly.
- Byte-size estimates are not reported.
- Tested against a self-hosted CockroachDB 26.3 single node; CockroachDB Cloud (Basic, Standard, Advanced) and multi-region clusters 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: everything the PostgreSQL proof checks (read-only session; no SUPERUSER, CREATEROLE or CREATEDB; no INSERT, UPDATE, DELETE or TRUNCATE on any visible table; no CREATE on any schema or the database) plus CockroachDB's own model: no admin membership, no write-capable system privilege (inherited grants included) and no system grant other than VIEW privileges, and SHOW GRANTS (roles and public included) may hold only SELECT on relations, USAGE on schemas and types, EXECUTE on routines and CONNECT or TEMPORARY on the database, never WITH GRANT OPTION or ownership. Not covered: CockroachDB's legacy role options (CREATELOGIN, CONTROLJOB, CANCELQUERY, CONTROLCHANGEFEED, MODIFYCLUSTERSETTING) are not visible to the user's own login, so an administrator checks them once with SHOW ROLES.
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 |
|---|---|---|---|---|---|
| CockroachDB | 26.3.2 | real-engine | psycopg 3.3.6 | password (TLS verify-full) | 2026-10-13 |
Connector version 0.1.0, last verified 2026-10-13.
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
- Create a dedicated login role with SELECT on the schemas to read and nothing else, and make its sessions read-only (ALTER ROLE … SET default_transaction_read_only = on).
- Store the connection document in a secret store the agent can resolve, with the password as a secret reference.
- 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 a production source, the agent proves the role is read-only from the catalog and refuses to continue if it is not.
- The same connector reads CockroachDB (needs agent 0.4.2 or later): set "flavor": "cockroachdb" to refuse any other server. Before connecting, an administrator must run SHOW ROLES once and confirm the reader has no role options: the reader’s own login cannot see CREATELOGIN, CONTROLJOB, CANCELQUERY, CONTROLCHANGEFEED or MODIFYCLUSTERSETTING, so the agent cannot verify them (see the CockroachDB page).
Example connection document, stored in your secret store and resolved by the agent locally (DataNivra only ever sees its reference):
{
"kind": "POSTGRESQL",
"host": "claims-replica.db.example.internal",
"dbname": "claims",
"user": "tdm_reader",
"password_ref": "vault://tdm/claims-replica#password",
"sslmode": "verify-full",
"schemas": ["claims", "reference"]
}Next: install the agent, then follow the getting started guide.
All integrations · Database test data management · Guides · Start free