Integrations · SaaS applications · Available now
ServiceNow test data, inside your network
ServiceNow connector: table discovery from sys_db_object and sys_dictionary (inherited fields included, sys_id as key, reference fields as relationships) and Table API reads with a pinned API version.
Available now SaaS applications
Shipped in the standard agent and backed by recorded conformance evidence.
What works today
ServiceNow connector: table discovery from sys_db_object and sys_dictionary (inherited fields included, sys_id as key, reference fields as relationships) and Table API reads with a pinned API version.
Basic credentials of an integration user, OAuth 2.0 client credentials or an access token, all as secret references. Optional incremental extraction by sys_updated_on. Records are processed inside your environment and never sent to DataNivra Cloud.
Authentication: basic integration user (secret reference); OAuth 2.0 client credentials (secret reference); access token (secret reference).
Known limitations
- Requires agent 0.4.2 or later: earlier agents cannot prove a ServiceNow integration user read-only on current releases (hidden role names, access-control-shortened pages).
- Verified against one real ServiceNow Personal Developer Instance (Australia release, Table API v2, basic integration user) with synthetic custom tables; other releases, OAuth on a real instance and large tables are untested.
- The integration user needs read access controls on sys_user_has_role, sys_user_role, sys_db_object, sys_dictionary and every configured table (see the setup steps); table write ACLs are not evaluated, the proof rests on snc_read_only.
- Currency fields are read as text, empty strings as nulls; password, image and attachment fields are not read.
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: the integration user's active roles must include snc_read_only, the platform role that blocks inserts, updates and deletes, and no admin, security_admin or maint role; anything else, a role query that fails, or a role whose name access controls hide (except the platform's auto-assigned script-writer prerequisite role) refuses the source. A Table API page that access controls shortened fails instead of returning a partial read.
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 |
|---|---|---|---|---|---|
| ServiceNow (Personal Developer Instance) | glide-australia-02-11-2026__patch7-09-17-2026 | managed-service | httpx 0.28.1 | basic (integration user) | 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
- Use agent 0.4.2 or later (earlier agents cannot prove a ServiceNow integration user read-only on current releases).
- Create a web-service-only integration user with the roles snc_read_only (blocks every insert, update and delete) and snc_platform_rest_api_access. Never admin, security_admin or maint.
- Give it read access to the catalog: data_classification_auditor reads sys_db_object and sys_dictionary. With security_admin elevated, create a role (for example dn_role_assignment_reader) with exactly two record/read ACLs, on sys_user_has_role and sys_user_role, so the agent can read the user’s own roles and their names. Check the Operation is read before saving.
- Create a role (for example dn_conformance_table_reader) with one record/read ACL per table to read, and add both roles to the integration user. Grant no create, write or delete ACL.
- Store the connection document with the password (or OAuth client secret) 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, the agent proves from the user’s roles that it holds snc_read_only and no administrative role, and refuses if a role name is hidden from it; a page shortened by access controls fails instead of returning a partial read. It sends GET requests only.
Example connection document, stored in your secret store and resolved by the agent locally (DataNivra only ever sees its reference):
{
"kind": "SERVICENOW",
"instance_url": "https://example.service-now.com",
"api_version": "v2",
"auth": "basic",
"username": "tdm.reader",
"password_ref": "vault://tdm/servicenow#password",
"integration_user": "tdm.reader",
"objects": {
"members": { "api_name": "u_members" },
"claims": { "api_name": "u_claims" }
}
}Next: install the agent, then follow the getting started guide.
All integrations · SaaS application test data management · Guides · Start free