SemanticFed
All use cases
Governance & SecurityCompliance Officer

Prove who queried what, and where it came from

A full audit trail plus end-to-end lineage across every federated source

Prove who queried what, and where it came from

Compliance teams need to answer two questions reliably: who accessed this data, and where did this number come from. Across many disconnected systems, both are painful.

SemanticFed is designed so every query is attributable to an actor and logged with the policy that applied, and every dataset carries lineage back through its virtual views to the physical sources. An access review reads as one audit trail. A data-subject request can be traced through the model.

Governance becomes evidence you can produce, not a story you have to reconstruct.

A pre-launch scenario describing the audit and lineage capabilities being built.

Do it yourself

Answer "who queried this?" and "where did this number come from?" from one place — the audit log plus the lineage in the knowledge graph.

0 / 7

  1. Open the Audit Logs to see every recorded query run.

    You should see: A chronological, attributable log of query runs loads.

    Open in app

Ready to make this your story?

Join the waitlistBrowse all use cases

Related scenarios

Data Governance Lead

Governance & Security

Enforce row- and column-level policy at the query edge

Define row filters, column masking, and access rules once in SemanticFed and enforce them on every federated query, regardless of where the data lives.

Row-level securityColumn maskingCentral policy+1
Read the scenario
Security Architect

Governance & Security

Keep data in place to honor residency rules

Query data where it lives so regulated data stays inside its residency boundary while still part of a unified model.

Data residencyQuery in placeCross-region model+1
Read the scenario