Prove lineage, ownership,and access. On demand

DataHub supports compliance readiness with column-level lineage, named ownership, access policies, and a versioned history of every change, captured automatically across the estate.

BCBS 239DORAGDPRCCPASOC 2Internal audit remediation
datahub · evidence request · EVD-2291live
Examiner request · Q3 stress report
"Where did the Tier 1 capital ratio on line 14 come from, who owns the inputs, and who could see them?"
5 / 5
evidence items
produced from metadata
0
chased by email
Lineage· source → report, column levelTraced
Ownership· technical, business, data stewardAssigned
Classification· sensitivity tag, propagatedTagged
Access· who, when, approved by whomLogged
Change history· versioned, point-in-timeRetained
The shape of answer an examiner accepts: exact source fields, exact transformations, exact aggregations. Illustrative only.
Trusted by modern data teams

The question isn't whether you have governance. It's whether you can evidence it

“We have a BCBS 239 finding and we cannot evidence lineage for our risk data.” Head of data risk

The lineage is real. It just can't be produced

It is encoded in the SQL that ran, but never captured anywhere an auditor can read. So one question means an engineer reverse-engineering a pipeline by hand, per field, per cycle. Most institutions can defend a fraction of the fields examiners ask about. The rest lives in tribal knowledge.

The cost: Remediation is measured in analyst-months, and it resets every reporting cycle because nothing was captured the first time.

“The auditor asked who owns this field and nobody could answer.” Chief data officer

“Who owns this field?” has no answer anyone will sign

Ownership was assigned once, in a spreadsheet, before two reorgs and a platform migration. The name on it has left. Nobody will attest to a definition they did not write, so accountability is the control that fails first, and it fails quietly until someone asks.

The cost: A governance control you cannot evidence is treated by an examiner as a control you do not have.

“We need to prove who has access to PII and when that access was granted.” Data governance lead

You can show access today. You can't show access last March

Pulling a current permissions list is straightforward. Proving who could see a PII column nine months ago, who approved it, and when it was revoked is a different question, and it is the one that gets asked. Access granted through a ticket queue leaves no durable record joined to the asset.

The cost: Point-in-time access evidence gets reconstructed under deadline, from systems that were never designed to retain it.

“DORA is in effect and we need to show operational resilience across our data flows.” Director of data governance

Remediation done by hand decays between cycles

A regulation that applies continuously cannot be answered by a one-off exercise. The finding closes: a team documents the critical fields, tags the sensitive ones, fills the gaps. Then new pipelines ship, schemas change, people move, and the estate drifts back out of compliance, because nothing about the fix was continuous.

The cost: You pay for the same remediation more than once, and the next finding lands on ground you thought you'd already covered.

Six triggers. Different names, one underlying demand

Basel Committee · 14 principlesRisk data aggregation & reportingBinding deadline: January 2016
What it asks for

Source-to-report traceability for risk data

Demonstrate how a reported figure was computed: the exact source fields, the exact transformations, the exact aggregations, across core banking, trading platforms and loan origination, through the warehouse, into the report.

  • Accuracy, integrity and completeness of risk data (P3, P4)
  • A single, consistent definition of each reported metric (P9)
  • Evidence of review and remedial action over time (P12, P13)
Where it breaks

The trace is reconstructed, not retained

Lineage gets rebuilt by hand for the fields the examiner names, in the weeks before the response is due. It is accurate on the day it is written, unversioned, and cannot answer "what did the pipeline look like in Q3?"

  • No point-in-time view of a prior reporting period
  • "Tier 1 Capital" defined differently in three places
What DataHub produces

Lineage that is column-level, cross-system, versioned and glossary-integrated

Captured automatically as data moves, so the trace is a standing artefact rather than a project. DataHub publishes a mapping of these four lineage properties against the 14 principles.

  • Column-level trace from source field to reported line
  • Versioned history for prior-period questions
  • Glossary terms bound to every instance of a metric

A regulated company without a deadline is not the audience for this page. If nothing is currently in force against you, the honest answer is that you have time to do this properly and shouldn't be rushed. If you have a finding, a date, or a regulation already applying to you, the rest of this page is about what you can put in front of the person asking.

Six capabilities. Each one produces an artefact, not a dashboard

Automated rather than assembled, which is what makes them survive between reporting cycles.

01 · Provenance Automated column-level lineage, as audit evidence A source-to-report trace for any field, on request.

Captured automatically across databases, transformation pipelines, BI tools and ML systems, derived from the SQL that actually ran rather than documentation someone maintained. Column level, so the trace resolves to the field an examiner named. Cross-system, so it never stops at one tool's edge.

02 · Accountability Ownership and stewardship, assigned and tracked “Who owns this field?” answered with a name, and a type.

Owners assigned and tracked automatically as the estate scales, with ownership types that match how accountability splits: Technical Owner, Business Owner, Data Steward, or your own. Automated alerts keep owners across quality issues, access requests and schema changes, so the name on the asset stays live.

03 · Access Policy-based access control, with an audit trail Who was granted what, by whom, on what justification.

Access Policies define who can do what to which resources, scoped by resource type, entity, domain or ownership. Access Workflows route each request to the right reviewer, statically or dynamically to entity, domain or data product owners, capture the business justification, and keep every request in one audit log.

04 · Classification Classification and sensitivity tagging that propagates Every copy of a regulated field, classified and findable.

A sensitivity tag or glossary term applied to a column propagates through column-level lineage automatically, so downstream copies inherit the classification instead of escaping it. Tags can sync into Snowflake so warehouse and catalog agree, and a tag change can trigger action through the Actions Framework.

05 · Point-in-time Versioned change history, so prior periods are answerable Point-in-time answers for a period that has already closed.

Metadata changes are versioned rather than overwritten, which is what turns lineage into evidence: an auditor's question is almost never about today. Ownership, classification, definitions and structure each carry a history, so what a field looked like when the report was filed does not rest on anyone's memory.

06 · Remediation Compliance Forms, so the gap gets closed by the people who know Remediation progress you can source and defend.

Define the assets in scope, the questions to answer, and the assignees responsible, filtered by ownership type where it matters. Forms land in the assignee's inbox as tasks, and analytics report which assets meet or violate each requirement, so progress is read from the estate rather than asserted in a deck.

What the auditor asks for, and where it comes from

Audit evidence checklist 4 questions · 4 sources

The artefact: a source-to-report trace naming the exact source fields, the exact transformations applied at each hop, and the exact aggregations that produced the final figure, across core systems, the warehouse and the reporting layer.

Column-level, cross-system lineage Automated SQL parsing of what ran

Checkout.com automated PII governance across 42+ internal teams

Customer story · Payments, 1,500+ employees

PII masking that fires on the tag, not on a ticket

Checkout.com serves global brands including the Financial Times, GE, Sony and Patreon. As it onboarded more than 42 internal teams, manual governance stopped scaling, and masking sensitive PII across systems became the harder half of the problem. Using DataHub's Actions Framework, tagging a column as PII now emits an event to Kafka that propagates masking into Snowflake and notifies the user for confirmation. Temporary PII access auto-expires. Every metadata change is logged and replicated to Snowflake, which is what turned governance activity into audit-ready record.

"The most important bit of why we use DataHub's Actions Framework is to allow us to make real-time changes as soon as an event happens in DataHub."
JC
John Claro
Data Engineer II, Checkout.com

What the implementation produced

Real-time PII masking propagated to Snowflake on tag
Temporary PII access with automatic expiration
All metadata changes logged and replicated for audit
Automated deprecation at 30 / 60 / 90 days of non-use

The stack it had to span

A real regulated payments estate, not a single-warehouse demo.

SnowflakeKafkadbtAirflowLookerLookML
20%
data governance team efficiency gain
IDC, The Business Value of DataHub Cloud, March 2026
75%
more datasets with mapped lineage
IDC, The Business Value of DataHub Cloud, March 2026
153%
more data assets with complete metadata
IDC, The Business Value of DataHub Cloud, March 2026
3,000+
organisations running DataHub
datahub.com

Sources: Checkout.com customer story, the IDC Business Value Solution Brief on DataHub Cloud (March 2026), and the DataHub data governance product page.

Two guides, if you'd rather read before you book

Primary guide · Banking & capital markets

BCBS 239 Compliance and Beyond

Maps directly to the 14 principles of BCBS 239, covers embedding governance, ownership and accountability into daily operations, and makes the case for treating compliance investment as the foundation for what comes after rather than a sunk cost. Written against the reality that a decade after publication, most banks are still not fully compliant, because of legacy systems, fragmented governance and inconsistent data quality.

Secondary guide · Audit readiness

From Compliance Gap to Audit-Ready: A Faster Path for Banks

Most institutions can defend a fraction of the fields examiners ask about. The rest lives in tribal knowledge and manual effort that cannot scale. This guide covers why compliance initiatives fail to produce defensible documentation, the three impediments behind it, and the FinServ Compliance QuickStart: a pre-seeded FIBO-aligned glossary, a Federal Reserve MDRM ingestor, an opinionated configuration, and a CDE Data Steward Agent.

Book your custom demo with DataHub

Share a few details about your goals, and we'll be in touch to schedule a personalised walkthrough tailored to your data environment, use cases, and roadmap.

We'll cover:

How DataHub helps teams discover, understand, maintain, and govern their data
Best practices for driving adoption across your organisation
How to get started fast, with cloud-native or on-prem deployment

Let's get you the answers and insights you need.

Self-hosted or cloud/Encrypted at rest and in transit/3,000+ organisations

Share a few details

A DataHub specialist reaches out within one business day. 30 minutes, no prep required.

Prefer to look around first?

Take the self-guided product tour
No prep and no data required
Technical, not a slide walkthrough
Open source or cloud, we'll say which fits