Connect your Data Governance
Data catalogs carry the metadata privacy programmes run on — what data exists, who owns it, why it is processed. TruSecure's data-governance connector pulls catalog metadata, so records like GDPR Art. 30 RoPA are drafted from the catalog and provenanced.
What the connector pulls
| Source system | What TruSecure pulls | Feeds governance |
|---|---|---|
| Data catalog | Datasets, systems of record, stewards | GDPR · records-of-processing support |
| Classification metadata | Sensitivity, retention rules, legal basis tags | Control Library · ISO 27701 alignment |
| Ownership | Data owners, stewards, delegated custodians | Governance workspace · named accountability |
| Retention state | Applicable schedules, disposition status | Risk Management · retention-gap entries |
Evidence produced from Data Governance data
One control test pulled from live Data Governance state — not a manual export, not a screenshot, but a verified query result with provenance:
- Control tested
- Records of processing current within 12 months
- Catalog source
- Collibra · 96 governed datasets
- Test
- re-perform · RoPA entries vs catalog change log
- Sample
- 96 entries · 91 current, 5 datasets changed without RoPA update
- Result
- fail · 5 entries redrafted from catalog metadata, sent to owners
- Evidence
- Catalog API query · timestamped 2026-08-22T10:26:48Z
- Export
- sealed · sha256:3c7f...e1b9
Setup and scope model
- Read-only, scoped permission
Connector requires read-only access to catalog metadata — schemas, ownership, classification. No write permissions, no ability to edit catalog entries.
- Data filtered by entity
Catalog domains scoped to the entity context; a shared catalog across group companies credits each entity's own domains.
- Continuous sync
RoPA drafts regenerate from catalog state, so processing records track the metadata instead of drifting from it.
Commercial packaging
Data Governance connectors are part of the paid TruSecure Fabric subscription. The connector itself, the continuous sync, the evidence provenance tracking, and the mapping to NIS2, DORA, ISO 27001, SOC 2 and other frameworks are all included — no per-connector fees, no usage tiers. Pricing is scoped in the conversation, not a price list.
How integration works
A demo with your actual Data Governance environment shown in preview mode — your data pulling into governance, feeding controls and evidence. Then a Resilience Sprint that configures the connector for production, scopes the entity context, and validates the first evidence pull. No self-serve checkout, no per-connector pricing.
TruSecure helps operationalize requirements and prepare evidence. Legal interpretation should be validated by qualified counsel.