MySQL test data, inside your network

What works today

Dedicated MySQL connector (PyMySQL): information_schema discovery, primary and foreign keys, row estimates, aggregate profiles and unbuffered streaming reads.

Password as a secret reference; TLS with certificate and host-name verification is the default (verify-ca, encrypt-only and disabled are explicit opt-outs).

Authentication: password (secret reference).

Known limitations

• Requires agent 0.2.0 or later; agent 0.1.0 does not include its driver.
• Password authentication only (IAM database authentication not yet tested).
• Tested against MySQL 8.4 LTS; Amazon RDS for MySQL and Aurora MySQL are compatibility profiles still to be tested.
• Spatial values are read and provisioned as WKT text; BIT values as unsigned integers.
• The conformance run used TLS without certificate verification against a self-signed test server; verified TLS against a trusted certificate is not yet part of the recorded evidence.

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.

Read-only proof

Proven before reading: SHOW GRANTS FOR CURRENT_USER(), with granted roles expanded, may list only SELECT, SHOW VIEW and USAGE; any write, DDL, administrative or grant privilege refuses the source, and every session runs as a read-only transaction.

Compatibility profiles

Managed variants of an engine are profiles of this connector, not separate connectors. A profile is marked tested only when its own conformance run passed.

• Amazon RDS for MySQL — not tested yet (roadmap only)
• Amazon Aurora MySQL-Compatible — not tested yet (roadmap only)

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.

Connector version 0.1.0, last verified 2026-09-30.

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

1. Use agent 0.2.0 or later (earlier agent images do not include the MySQL driver). The same connector reads MariaDB; set "flavor": "mariadb" to refuse any other server.
2. Create a dedicated user with SELECT and SHOW VIEW on the databases to read and nothing else (no write, DDL, administrative or grant privilege), ideally on a replica.
3. Store the connection document with the password as a secret reference. TLS with certificate and host-name verification (verify-full) is the default; weaker modes are explicit opt-outs.
4. 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.
5. Before reading, the agent proves the account is read-only from SHOW GRANTS (granted roles expanded) and refuses to continue if it is not; every session runs as a read-only transaction.

Example connection document, stored in your secret store and resolved by the agent locally (DataNivra only ever sees its reference):

{
  "kind": "MYSQL",
  "host": "shop-replica.db.example.internal",
  "user": "tdm_reader",
  "password_ref": "vault://tdm/shop-replica#password",
  "databases": ["shop"]
}

Next: install the agent, then follow the getting started guide.