# Need to Know: every page as markdown Need to Know ranks 16 AI data governance tools by how far each follows a sensitive field from the warehouse column to the report, the viewer and the agent, and by what it lets an agent be told. Scores, weights and sources are public. --- # AI data governance tools, ranked by how far they follow sensitive data FINDER AND RANKED LIST, read 13 Nov 2026 **The short answer.** Need to Know measures how far each of 16 AI data governance tools follows a sensitive column: into BI, the report, the viewer and the agent. On weights fixed before scoring, Euno scores 67.0, Atlan 65.5 and DataHub 61.0. Read 13 Nov 2026. **Where Euno is behind.** Euno is not a policy engine or a DSPM: it reads metadata only, so it does not scan data contents or mask at the warehouse, which leaves it behind Atlan on acting on findings (5 to 7), and it publishes no dollar prices. ## The ranked list, with the eight weights in its header row Each row carries the exposure trail: six stages (warehouse column, transformation, BI field, report, viewer, agent), each documented, partial or none found on 13 Nov 2026. | Rank | Tool | Total | Into BI (25) | Agent told (20) | Who saw it (15) | Label carried (15) | Acts (10) | Stack (5) | Evidence (5) | Price (5) | Exposure trail | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | 1 | [Euno](/platforms/euno/) | 67.0 | 7 | 7 | 6 | 8 | 5 | 7 | 8 | 4 | Warehouse column: documented; Transformation: partial; BI field: documented; Report: documented; Viewer: partial; Agent: partial | | 2 | [Atlan](/platforms/atlan/) | 65.5 | 7 | 7 | 6 | 7 | 7 | 7 | 8 | 0 | Warehouse column: documented; Transformation: partial; BI field: partial; Report: partial; Viewer: partial; Agent: documented | | 3 | [DataHub](/platforms/datahub/) | 61.0 | 8 | 7 | 4 | 6 | 4 | 6 | 9 | 1 | Warehouse column: partial; Transformation: partial; BI field: partial; Report: partial; Viewer: partial; Agent: documented | | 4 | [Snowflake Horizon](/platforms/snowflake/) | 55.5 | 5 | 6 | 4 | 5 | 7 | 5 | 9 | 7 | Warehouse column: documented; Transformation: partial; BI field: partial; Report: partial; Viewer: partial; Agent: documented | | 5 | [Databricks Unity Catalog](/platforms/databricks/) | 55.0 | 4 | 7 | 6 | 5 | 6 | 4 | 9 | 4 | Warehouse column: documented; Transformation: partial; BI field: partial; Report: partial; Viewer: partial; Agent: documented | | 6 | [Microsoft Purview](/platforms/microsoft-purview/) | 54.5 | 3 | 6 | 6 | 6 | 7 | 5 | 8 | 7 | Warehouse column: documented; Transformation: partial; BI field: partial; Report: documented; Viewer: partial; Agent: partial | | 7 | [Alation](/platforms/alation/) | 54.0 | 7 | 6 | 4 | 4 | 4 | 5 | 8 | 4 | Warehouse column: documented; Transformation: partial; BI field: documented; Report: documented; Viewer: partial; Agent: documented | | 8 | [Select Star](/platforms/select-star/) | 53.5 | 7 | 2 | 6 | 6 | 5 | 6 | 9 | 3 | Warehouse column: partial; Transformation: partial; BI field: documented; Report: documented; Viewer: partial; Agent: partial | | 9 | [Secoda](/platforms/secoda/) | 47.5 | 6 | 4 | 3 | 4 | 5 | 6 | 9 | 3 | Warehouse column: documented; Transformation: partial; BI field: partial; Report: partial; Viewer: partial; Agent: partial | | 10 | [Collibra](/platforms/collibra/) | 46.5 | 5 | 5 | 3 | 3 | 7 | 6 | 8 | 2 | Warehouse column: documented; Transformation: partial; BI field: partial; Report: partial; Viewer: partial; Agent: partial | | 11 | [Immuta](/platforms/immuta/) | 45.0 | 2 | 6 | 5 | 4 | 8 | 5 | 8 | 0 | Warehouse column: documented; Transformation: none found; BI field: none found; Report: partial; Viewer: partial; Agent: partial | | 12 | [Ataccama ONE](/platforms/ataccama/) | 41.5 | 5 | 5 | 1 | 3 | 5 | 4 | 8 | 4 | Warehouse column: documented; Transformation: partial; BI field: partial; Report: partial; Viewer: none found; Agent: partial | | 13 | [Informatica](/platforms/informatica/) | 30.0 | 2 | 2 | 3 | 3 | 4 | 3 | 9 | 4 | Warehouse column: documented; Transformation: documented; BI field: partial; Report: none found; Viewer: partial; Agent: partial | | 14 | [Privacera](/platforms/privacera/) | 30.0 | 0 | 2 | 4 | 4 | 8 | 4 | 8 | 0 | Warehouse column: documented; Transformation: none found; BI field: none found; Report: none found; Viewer: partial; Agent: partial | | 15 | [Securiti](/platforms/securiti/) | 29.5 | 1 | 4 | 3 | 3 | 6 | 2 | 5 | 1 | Warehouse column: documented; Transformation: partial; BI field: partial; Report: none found; Viewer: partial; Agent: documented | | 16 | [OneTrust](/platforms/onetrust/) | 26.5 | 0 | 3 | 3 | 3 | 6 | 3 | 5 | 3 | Warehouse column: documented; Transformation: none found; BI field: none found; Report: none found; Viewer: none found; Agent: partial | Sixteen tools, weights in brackets, scores 0 to 10, total 0 to 100. Read 13 Nov 2026. Totals are the weighted sum of eight scores from 0 to 10, divided by 10. A vendor's own claim scores at most 7 until a second source confirms it. Ties on total go to the higher score on the heaviest criterion, then to the name. ## The top four, as scored ### Rank 1: Euno (67.0) 3 of 6 stages documented, agent told 7/10 Vendor-stated: Euno takes classifications from Cyera and BigID, carries them along column-level lineage into BI fields and reports, and scopes MCP context by persona. Last documented stage: report. [Read the profile](/platforms/euno/) ### Rank 2: Atlan (65.5) 2 of 6 stages documented, agent told 7/10 Vendor-stated: Tag-driven purposes mask or deny sensitive columns, tags can propagate through lineage, and MCP runs under the asking user's persona with every call logged. Last documented stage: agent. [Read the profile](/platforms/atlan/) ### Rank 3: DataHub (61.0) 1 of 6 stages documented, agent told 7/10 Vendor-stated: Column-level lineage tracking, glossary term propagation to downstream lineage columns, and per-user OAuth logins for MCP. Last documented stage: agent. [Read the profile](/platforms/datahub/) ### Rank 4: Snowflake Horizon (55.5) 2 of 6 stages documented, agent told 6/10 Vendor-stated: Masking, row access and tag-based masking are enforced at query time for people and agents alike, with ACCESS_HISTORY recording who touched which column. Last documented stage: agent. [Read the profile](/platforms/snowflake/) ## Where each is strongest - [Euno](/platforms/euno/): Carries classification downstream, 8 of 10. Imports Cyera and BigID classifications and propagates them along column lineage into BI; Cyera lists the integration independently. - [Atlan](/platforms/atlan/): Follows sensitive data into BI, 7 of 10. Column-level lineage documented for Tableau, Looker and Power BI with stated gaps (Tableau flows and embedded, Power BI partial SQL sources). - [DataHub](/platforms/datahub/): Follows sensitive data into BI, 8 of 10. Column lineage from Snowflake through dbt into Looker, Power BI and Tableau is documented, and dbt Labs independently describes column lineage to downstream dashboards; Tableau needs a high role. - [Snowflake Horizon](/platforms/snowflake/): Acts on it, 7 of 10. Dynamic masking, row access and tag-based masking policies are documented as enforced at query time (some Enterprise Edition). - [Databricks Unity Catalog](/platforms/databricks/): Controls what an agent is told, 7 of 10. Row filters and masks enforce per user in Genie, OAuth calls run as the signed-in user and a PII guardrail is in Beta; one agent MCP bypasses the gateway. - [Microsoft Purview](/platforms/microsoft-purview/): Acts on it, 7 of 10. Protection policies, DLP and endpoint blocking enforce on labeled items, but not on Power BI reports or dashboards, and have scale limits. - [Alation](/platforms/alation/): Follows sensitive data into BI, 7 of 10. Column-level lineage from warehouse columns to Tableau report fields, Power BI and Looker, plus dbt extraction, is documented; vendor docs only, Power BI with stated limitations. - [Select Star](/platforms/select-star/): Follows sensitive data into BI, 7 of 10. Column-level lineage from warehouse through SQL parsing into Looker, Tableau, Sigma and Power BI is vendor-documented; press quotes only the CEO on lineage, so capped at 7. - [Secoda](/platforms/secoda/): Follows sensitive data into BI, 6 of 10. Column lineage and impact analysis from warehouse column to Looker and Tableau dashboards, and dbt manifest support; only those two BI tools. - [Collibra](/platforms/collibra/): Acts on it, 7 of 10. Masking and row filters are applied from classifications and enforced in target systems, with data quality workflows handing off to Jira and ServiceNow. - [Immuta](/platforms/immuta/): Acts on it, 8 of 10. Tag-based column and cell masking, review flows and dashboard subscription policies are documented, and Databricks' partner page confirms row security and column masking as native controls. - [Ataccama ONE](/platforms/ataccama/): Evidence beyond the vendor, 8 of 10. OpenLineage ecosystem listing and a PeerSpot reviews page with reviewer pricing summary are independent; analyst claims are vendor-stated and the listing is a logo only. - [Informatica](/platforms/informatica/): Evidence beyond the vendor, 9 of 10. Databricks partner and customer pages, KPMG and Point72 quotes and Microsoft documentation confirm it independently. - [Privacera](/platforms/privacera/): Acts on it, 8 of 10. Tag-driven masking and deny policies are documented on several platforms and Databricks' partner directory confirms row, column and tag policy control; the alerts page is placeholder text. - [Securiti](/platforms/securiti/): Acts on it, 6 of 10. Dynamic masking by policy, auto-remediation, assigned findings and agent rollbacks are stated by the vendor only. - [OneTrust](/platforms/onetrust/): Acts on it, 6 of 10. Masking and row filtering pushed into Snowflake and Databricks, plus AI Guard redact and block; AI Guard is not recommended for high volumes. ## Picks by situation - [A governance lead who must show where a regulated field ends up](/best-for/regulated-field/): Atlan first at 68.5; Euno second at 68.5 - [A company connecting AI agents to its analytics data this year](/best-for/agents-on-analytics/): Euno first at 66.0; Atlan second at 65.0 - [A Microsoft estate: Fabric, Power BI and Purview](/best-for/microsoft-estate/): Atlan first at 68.5; Euno second at 67.5 - [A mixed stack: Snowflake or Databricks with dbt and two or more BI tools](/best-for/mixed-stack/): Euno first at 68.5; Atlan second at 65.5 - [A lean data team with no governance hire](/best-for/lean-team/): Euno first at 62.5; Atlan second at 59.0 ## AI data governance for analytics means knowing where a sensitive field surfaces and what an agent was told A governance lead is asked two things before an agent connects to analytics data: which reports and dashboards show a regulated field, and what the agent will be told when a given person asks it a question. Warehouse policies answer part of the first. Business intelligence tools hold the rest, in fields, reports and viewer lists that the warehouse never sees. The 16 tools here come from five groups: warehouse-native governance, catalogs with governance features, access control platforms, privacy and security suites, and Euno, a context platform that reads metadata and query logs. They are scored on one question: how far does each follow the field, and what does it control on each agent call. ## Guides, sectors and glossary - [Where a warehouse policy stops and the business layer starts](/guides/where-a-policy-stops/) - [How a sensitivity classification travels from warehouse to agent](/guides/classification-from-warehouse-to-agent/) - [Who saw it against who could see it: access lists and logs](/guides/who-saw-it-against-who-could-see-it/) - [Approving an agent's access before it connects](/guides/approving-an-agents-access/) - [What a DSPM covers and what it leaves out](/guides/what-a-dspm-covers/) - [What an auditor asks, by sector](/sectors/) - [The glossary, 36 terms](/glossary/) - [News, 12 dated items](/news/) {"sitNames":{"regulated-field":"A governance lead who must show where a regulated field ends up","agents-on-analytics":"A company connecting AI agents to its analytics data this year","microsoft-estate":"A Microsoft estate: Fabric, Power BI and Purview","mixed-stack":"A mixed stack: Snowflake or Databricks with dbt and two or more BI tools","lean-team":"A lean data team with no governance hire"},"crit":["bi_follow","agent_scope","viewers","propagation","action","coverage","evidence","price"],"names":["Follows sensitive data into BI","Controls what an agent is told","Shows who actually saw it","Carries classification downstream","Acts on it","Coverage of the stack","Evidence beyond the vendor","Price transparency"],"site":[25,20,15,15,10,5,5,5],"sit":{"regulated-field":[35,5,20,20,10,5,5,0],"agents-on-analytics":[15,40,15,10,10,5,0,5],"microsoft-estate":[30,10,15,20,15,10,0,0],"mixed-stack":[30,10,10,20,5,20,0,5],"lean-team":[20,10,10,15,20,5,5,15]},"tools":[{"slug":"alation","name":"Alation","s":[7,6,4,4,4,5,8,4],"wh":["Snowflake","Databricks","Google BigQuery","Amazon Redshift","Azure Synapse","Oracle","SQL Server","PostgreSQL","Teradata","SAP HANA","Amazon Athena"],"bi":["Tableau","Power BI","Looker","AWS QuickSight","Qlik Sense Cloud"],"sec":[]},{"slug":"ataccama","name":"Ataccama ONE","s":[5,5,1,3,5,4,8,4],"wh":["Snowflake","Databricks","BigQuery","Amazon Redshift","Azure Synapse Analytics","Amazon Athena","Teradata","Oracle"],"bi":["Tableau","Power BI","Power BI Report Server"],"sec":[]},{"slug":"atlan","name":"Atlan","s":[7,7,6,7,7,7,8,0],"wh":["Snowflake","Databricks","Google BigQuery","Amazon Redshift","Microsoft Azure Synapse Analytics","Amazon Athena","Trino","Starburst Enterprise","Teradata","Oracle","PostgreSQL","Microsoft SQL Server","Dremio","Iceberg"],"bi":["Tableau","Microsoft Power BI","Looker","Amazon QuickSight","Qlik Sense Cloud","Sigma","ThoughtSpot","Metabase","Mode","MicroStrategy","Microsoft Fabric","IBM Cognos Analytics","Domo","SAP Analytics Cloud"],"sec":["BigID","Cyera","ALTR","Immuta"]},{"slug":"collibra","name":"Collibra","s":[5,5,3,3,7,6,8,2],"wh":["Snowflake","Databricks Unity Catalog","Google BigQuery","Amazon Redshift","Azure Synapse Analytics","Azure SQL Server","Microsoft SQL Server","Oracle","PostgreSQL","MySQL","Teradata","SAP HANA"],"bi":["Tableau","Power BI","Looker","Qlik","Sigma","ThoughtSpot","Strategy","SSRS-PBRS"],"sec":["Okta","Microsoft Entra ID"]},{"slug":"databricks","name":"Databricks Unity Catalog","s":[4,7,6,5,6,4,9,4],"wh":["Databricks SQL warehouses","Snowflake","BigQuery","AWS Glue","MySQL","PostgreSQL","Salesforce"],"bi":["Tableau","Power BI","Sigma","Databricks AI/BI dashboards"],"sec":[]},{"slug":"datahub","name":"DataHub","s":[8,7,4,6,4,6,9,1],"wh":["Snowflake","BigQuery","Databricks","Redshift"],"bi":["Tableau","Power BI","Looker","Preset"],"sec":[]},{"slug":"euno","name":"Euno","s":[7,7,6,8,5,7,8,4],"wh":["Snowflake","BigQuery","Databricks","Redshift (private preview)","MySQL","SQL Server"],"bi":["Tableau","Looker","Power BI","ThoughtSpot","Sigma","Omni","Cube Core","Salesforce","Hex"],"sec":["Cyera","BigID","Microsoft Purview","Monte Carlo","Elementary","Okta","Google Workspace"]},{"slug":"immuta","name":"Immuta","s":[2,6,5,4,8,5,8,0],"wh":["Snowflake","Databricks Unity Catalog","Databricks Spark","Google BigQuery","Amazon Redshift","Amazon Athena","AWS Lake Formation","Amazon S3","Starburst","Trino","Azure Synapse Analytics","Oracle","SQL Server","Teradata","MySQL","MariaDB","PostgreSQL"],"bi":["Tableau","Power BI"],"sec":["Alation","Atlan","Collibra","Microsoft Purview"]},{"slug":"informatica","name":"Informatica","s":[2,2,3,3,4,3,9,4],"wh":["Snowflake","Databricks (Unity Catalog)","Amazon Redshift","Salesforce Data 360"],"bi":["Tableau","Power BI"],"sec":[]},{"slug":"microsoft-purview","name":"Microsoft Purview","s":[3,6,6,6,7,5,8,7],"wh":["Snowflake","Azure Synapse Analytics","Azure SQL Database","Azure Databricks Unity Catalog","Azure Databricks Hive Metastore","Google BigQuery","Amazon Redshift","Oracle","Teradata","SQL Server"],"bi":["Power BI","Looker"],"sec":["Microsoft Purview Information Protection","Microsoft Purview DLP","Microsoft Defender for Cloud Apps"]},{"slug":"onetrust","name":"OneTrust","s":[0,3,3,3,6,3,5,3],"wh":["Snowflake","Databricks Unity Catalog","Amazon Redshift","Amazon Athena","Amazon RDS for SQL Server","Google BigQuery","Azure Databricks","Teradata"],"bi":[],"sec":["Palo Alto Networks"]},{"slug":"privacera","name":"Privacera","s":[0,2,4,4,8,4,8,0],"wh":["Snowflake","Databricks Unity Catalog","Databricks SQL","Google BigQuery","AWS Redshift","AWS Athena","Azure Synapse","Trino","Starburst","Dremio","Oracle","Microsoft SQL Server","PostgreSQL","MySQL","Vertica"],"bi":[],"sec":["Collibra","Okta","Azure AD","LDAP","Apache Ranger"]},{"slug":"secoda","name":"Secoda","s":[6,4,3,4,5,6,9,3],"wh":["Snowflake","BigQuery","Databricks","Redshift","Azure Synapse","ClickHouse","MotherDuck","Apache Hive"],"bi":["Tableau","Looker","Looker Studio","Power BI","Metabase","Mode","Sigma","ThoughtSpot","QuickSight","Superset","Hex","Omni","MicroStrategy One"],"sec":["Cyera"]},{"slug":"securiti","name":"Securiti","s":[1,4,3,3,6,2,5,1],"wh":["Snowflake","Google BigQuery","Databricks"],"bi":["Tableau"],"sec":["Microsoft security center (sensitivity labels)"]},{"slug":"select-star","name":"Select Star","s":[7,2,6,6,5,6,9,3],"wh":["Snowflake","Databricks","BigQuery","Amazon Redshift","PostgreSQL","Microsoft SQL Server (beta)","MySQL (beta)","Oracle (beta)","Salesforce (beta)","IBM Db2 (beta)","AWS Glue"],"bi":["Tableau","Microsoft Power BI","Looker","Looker Studio","Mode","Sigma","Sisense / Periscope","Metabase","ThoughtSpot","Amazon QuickSight","Hex","Salesforce CRM Analytics (beta)"],"sec":[]},{"slug":"snowflake","name":"Snowflake Horizon","s":[5,6,4,5,7,5,9,7],"wh":["Snowflake","Amazon Redshift","BigQuery","Databricks","IBM Db2","MySQL","Oracle","PostgreSQL","SQL Server"],"bi":["Amazon QuickSight","Hex","Looker","Metabase","Microsoft Power BI","Omni","Sigma","Tableau Cloud","Tableau Server","ThoughtSpot"],"sec":[]}]}(function(){let D=JSON.parse(document.getElementById('nk-finder-data').textContent);function finderRank(D, a) { let picks = []; if (a.stack === 'microsoft') picks.push('microsoft-estate'); else if (a.stack === 'mixed') picks.push('mixed-stack'); if (a.regulated === 'yes') picks.push('regulated-field'); if (a.agents === 'yes') picks.push('agents-on-analytics'); if (a.owner === 'data-team') picks.push('lean-team'); let w = D.crit.map(function (_, i) { return picks.length ? picks.reduce(function (t, k) { return t + D.sit[k][i]; }, 0) / picks.length : D.site[i]; }); let heavy = 0; w.forEach(function (x, i) { if (x > w[heavy]) heavy = i; }); let rows = D.tools.map(function (t) { let total = t.s.reduce(function (acc, x, i) { return acc + x * w[i]; }, 0) / 10; return { t: t, total: Math.round(total * 10) / 10 }; }); rows.sort(function (x, y) { return y.total - x.total || y.t.s[heavy] - x.t.s[heavy] || (x.t.name 0 && (w[i] >= 10 ? 1 : 0) * 1e6 + d > (best >= 0 ? (w[best] >= 10 ? 1 : 0) * 1e6 + bd : 0)) { bd = d; best = i; } }); let top = D.crit.map(function (_, i) { return i; }).sort(function (i, j) { return r.t.s[j] - r.t.s[i] || w[j] - w[i]; })[0]; let why = best >= 0 ? 'Beats ' + nx.t.name + ' on ' + D.names[best] + ' (' + r.t.s[best] + ' to ' + nx.t.s[best] + ' at weight ' + Math.round(w[best]) + ').' : 'Its top score under your weights is ' + D.names[top] + ', ' + r.t.s[top] + ' of 10.'; if (r.total === nx.total) why += ' Tied with ' + nx.t.name + ' at ' + r.total.toFixed(1) + '; the tie goes to the higher score on ' + D.names[heavy] + ', then the name.'; let notes = []; if (a.stack === 'microsoft') notes.push(r.t.bi.some(function (b) { return /power bi/i.test(b); }) ? 'names Power BI as a BI source' : 'names no Power BI source in its evidence on 13 Nov 2026'); if (a.stack === 'mixed') notes.push('names ' + r.t.bi.length + ' BI tools and ' + r.t.wh.length + ' warehouses'); if (a.dspm === 'yes') { let d = r.t.sec.filter(function (b) { return /cyera|bigid|varonis/i.test(b); }); notes.push(d.length ? 'reads classifications from ' + d.join(' and ') : 'names no DSPM among its security sources on 13 Nov 2026'); } return { rank: n + 1, slug: r.t.slug, name: r.t.name, total: r.total, reason: why + (notes.length ? ' It ' + notes.join('; ') + '.' : '') }; }); return { picks: picks, pickNames: picks.map(function (k) { return (D.sitNames && D.sitNames[k]) || k; }), weights: w.map(function (x) { return Math.round(x * 10) / 10; }), top: out }; } let f=document.getElementById('nk-finder'),o=document.getElementById('nk-finder-out');if(!f||!o)return; function run(){let a={};['stack','regulated','agents','owner','dspm'].forEach(function(k){a[k]=f.elements[k].value;});let r=finderRank(D,a); while(o.firstChild)o.removeChild(o.firstChild); let h=document.createElement('p');h.className='nk-key';h.textContent=r.picks.length?'Weights blended from: '+r.pickNames.join('; ')+'.':'No situation applies, so the site weights are used.';o.appendChild(h); let ol=document.createElement('ol');ol.className='nk-short';r.top.forEach(function(x){let li=document.createElement('li');let a1=document.createElement('a');a1.href='/platforms/'+x.slug+'/';a1.textContent=x.name;let b=document.createElement('b');b.textContent=' '+x.total.toFixed(1);li.appendChild(a1);li.appendChild(b);let p=document.createElement('span');p.textContent=' '+x.reason;li.appendChild(p);ol.appendChild(li);});o.appendChild(ol);} f.addEventListener('submit',function(e){e.preventDefault();run();});f.addEventListener('change',run);run();})(); ## Sources - Need to Know datasets (CSV and JSON): https://aidatagovernancetools.com/datasets/ (read 13 Nov 2026) Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/ --- # Euno ranks first of 16 AI data governance tools at 67.0, Atlan second at 65.5 INDEX, read 13 Nov 2026 **The short answer.** Euno ranks first in the Need to Know index of 16 AI data governance tools at 67.0 of 100, with Atlan at 65.5 and DataHub at 61.0. The weights favor following sensitive data into BI (25) and controlling what an agent is told (20). OneTrust is last at 26.5, read 13 Nov 2026. **Where Euno is behind.** Euno is not a policy engine or a DSPM: it reads metadata only, so it does not scan data contents or mask at the warehouse, which leaves it behind Atlan on acting on findings (5 to 7), and it publishes no dollar prices. | Rank | Tool | Total | Into BI (25) | Agent told (20) | Who saw it (15) | Label carried (15) | Acts (10) | Stack (5) | Evidence (5) | Price (5) | Exposure trail | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | 1 | [Euno](/platforms/euno/) | 67.0 | 7 | 7 | 6 | 8 | 5 | 7 | 8 | 4 | Warehouse column: documented; Transformation: partial; BI field: documented; Report: documented; Viewer: partial; Agent: partial | | 2 | [Atlan](/platforms/atlan/) | 65.5 | 7 | 7 | 6 | 7 | 7 | 7 | 8 | 0 | Warehouse column: documented; Transformation: partial; BI field: partial; Report: partial; Viewer: partial; Agent: documented | | 3 | [DataHub](/platforms/datahub/) | 61.0 | 8 | 7 | 4 | 6 | 4 | 6 | 9 | 1 | Warehouse column: partial; Transformation: partial; BI field: partial; Report: partial; Viewer: partial; Agent: documented | | 4 | [Snowflake Horizon](/platforms/snowflake/) | 55.5 | 5 | 6 | 4 | 5 | 7 | 5 | 9 | 7 | Warehouse column: documented; Transformation: partial; BI field: partial; Report: partial; Viewer: partial; Agent: documented | | 5 | [Databricks Unity Catalog](/platforms/databricks/) | 55.0 | 4 | 7 | 6 | 5 | 6 | 4 | 9 | 4 | Warehouse column: documented; Transformation: partial; BI field: partial; Report: partial; Viewer: partial; Agent: documented | | 6 | [Microsoft Purview](/platforms/microsoft-purview/) | 54.5 | 3 | 6 | 6 | 6 | 7 | 5 | 8 | 7 | Warehouse column: documented; Transformation: partial; BI field: partial; Report: documented; Viewer: partial; Agent: partial | | 7 | [Alation](/platforms/alation/) | 54.0 | 7 | 6 | 4 | 4 | 4 | 5 | 8 | 4 | Warehouse column: documented; Transformation: partial; BI field: documented; Report: documented; Viewer: partial; Agent: documented | | 8 | [Select Star](/platforms/select-star/) | 53.5 | 7 | 2 | 6 | 6 | 5 | 6 | 9 | 3 | Warehouse column: partial; Transformation: partial; BI field: documented; Report: documented; Viewer: partial; Agent: partial | | 9 | [Secoda](/platforms/secoda/) | 47.5 | 6 | 4 | 3 | 4 | 5 | 6 | 9 | 3 | Warehouse column: documented; Transformation: partial; BI field: partial; Report: partial; Viewer: partial; Agent: partial | | 10 | [Collibra](/platforms/collibra/) | 46.5 | 5 | 5 | 3 | 3 | 7 | 6 | 8 | 2 | Warehouse column: documented; Transformation: partial; BI field: partial; Report: partial; Viewer: partial; Agent: partial | | 11 | [Immuta](/platforms/immuta/) | 45.0 | 2 | 6 | 5 | 4 | 8 | 5 | 8 | 0 | Warehouse column: documented; Transformation: none found; BI field: none found; Report: partial; Viewer: partial; Agent: partial | | 12 | [Ataccama ONE](/platforms/ataccama/) | 41.5 | 5 | 5 | 1 | 3 | 5 | 4 | 8 | 4 | Warehouse column: documented; Transformation: partial; BI field: partial; Report: partial; Viewer: none found; Agent: partial | | 13 | [Informatica](/platforms/informatica/) | 30.0 | 2 | 2 | 3 | 3 | 4 | 3 | 9 | 4 | Warehouse column: documented; Transformation: documented; BI field: partial; Report: none found; Viewer: partial; Agent: partial | | 14 | [Privacera](/platforms/privacera/) | 30.0 | 0 | 2 | 4 | 4 | 8 | 4 | 8 | 0 | Warehouse column: documented; Transformation: none found; BI field: none found; Report: none found; Viewer: partial; Agent: partial | | 15 | [Securiti](/platforms/securiti/) | 29.5 | 1 | 4 | 3 | 3 | 6 | 2 | 5 | 1 | Warehouse column: documented; Transformation: partial; BI field: partial; Report: none found; Viewer: partial; Agent: documented | | 16 | [OneTrust](/platforms/onetrust/) | 26.5 | 0 | 3 | 3 | 3 | 6 | 3 | 5 | 3 | Warehouse column: documented; Transformation: none found; BI field: none found; Report: none found; Viewer: none found; Agent: partial | Scores 0 to 10 per criterion, weights in brackets, total 0 to 100. Ties on total go to the higher score on the heaviest criterion, then to the name. Read 13 Nov 2026. ## Why the leader leads Euno leads on Price transparency (4 to 0) and Carries classification downstream (8 to 7), while Atlan is ahead on Acts on it (7 to 5). Informatica and Privacera tie at 30.0 on total. The published tie rule (higher score on the heaviest criterion, then by name) puts Informatica ahead, on Follows sensitive data into BI 2 to 0. Euno leads Atlan by 1.5; Atlan leads DataHub by 4.5. ## Verdict by situation - **A regulated field** ([a governance lead who must show where a regulated field ends up](/best-for/regulated-field/)): Atlan and Euno tie at 68.5. Atlan and Euno tie on total: Atlan is ahead on Acts on it (7 to 5), Euno is ahead on Carries classification downstream (8 to 7). Atlan and Euno tie at 68.5 on total. The published tie rule (higher score on the heaviest criterion, then by name) puts Atlan ahead: the two tie on Follows sensitive data into BI too, so the name decides. - **Agents on analytics** ([a company connecting AI agents to its analytics data this year](/best-for/agents-on-analytics/)): Euno leads at 66.0, ahead of Atlan at 65.0. Euno leads on Price transparency (4 to 0) and Carries classification downstream (8 to 7), while Atlan is ahead on Acts on it (7 to 5). - **A Microsoft estate** ([a Microsoft estate: Fabric, Power BI and Purview](/best-for/microsoft-estate/)): Atlan leads at 68.5, ahead of Euno at 67.5. Atlan leads on Acts on it (7 to 5), while Euno is ahead on Carries classification downstream (8 to 7). - **A mixed stack** ([a mixed stack: Snowflake or Databricks with dbt and two or more BI tools](/best-for/mixed-stack/)): Euno leads at 68.5, ahead of Atlan at 65.5. Euno leads on Carries classification downstream (8 to 7) and Price transparency (4 to 0), while Atlan is ahead on Acts on it (7 to 5). - **A lean team** ([a lean data team with no governance hire](/best-for/lean-team/)): Euno leads at 62.5, ahead of Atlan at 59.0. Euno leads on Price transparency (4 to 0) and Carries classification downstream (8 to 7), while Atlan is ahead on Acts on it (7 to 5). ## Every platform profile - [1. Euno](/platforms/euno/): 67.0; AI context platform for enterprise data (metadata graph with rule-based labels and an MCP server) - [2. Atlan](/platforms/atlan/): 65.5; data catalog, metadata and governance platform, now marketed as a context layer for AI - [3. DataHub](/platforms/datahub/): 61.0; open source data catalog and metadata platform with a managed Cloud edition - [4. Snowflake Horizon](/platforms/snowflake/): 55.5; data platform's built-in catalog, governance and context layer - [5. Databricks Unity Catalog](/platforms/databricks/): 55.0; lakehouse data catalog and governance layer (built into the Databricks platform, with an open source core) - [6. Microsoft Purview](/platforms/microsoft-purview/): 54.5; Microsoft data security and compliance suite (sensitivity labels, DLP, DSPM for AI) plus a retiring data catalog and Data Map - [7. Alation](/platforms/alation/): 54.0; data catalog and data intelligence platform with governance, data quality and AI agents - [8. Select Star](/platforms/select-star/): 53.5; data catalog, column-level lineage and metadata platform (acquired by Snowflake) - [9. Secoda](/platforms/secoda/): 47.5; data catalog, governance and AI analytics platform, now part of Atlassian - [10. Collibra](/platforms/collibra/): 46.5; data governance platform: catalog, lineage, data quality, data access and AI governance - [11. Immuta](/platforms/immuta/): 45.0; data access control and authorization platform (policy engine with sensitive data tagging) - [12. Ataccama ONE](/platforms/ataccama/): 41.5; data quality, catalog and observability platform with master data management - [13. Informatica](/platforms/informatica/): 30.0; enterprise data catalog, governance, quality and access management platform (IDMC), now part of Salesforce - [14. Privacera](/platforms/privacera/): 30.0; data security platform: sensitive data discovery, tag-based access control and masking (Apache Ranger based), plus AI agent governance - [15. Securiti](/platforms/securiti/): 29.5; data security posture management and AI data governance platform - [16. OneTrust](/platforms/onetrust/): 26.5; privacy, AI governance and data use governance platform ## Sources - https://documentation.alation.com/en/latest/governance/SnowflakeTags/index.md: https://documentation.alation.com/en/latest/governance/SnowflakeTags/index.md (read 13 Nov 2026) - https://docs.ataccama.com/one/latest/data-quality/rules.html: https://docs.ataccama.com/one/latest/data-quality/rules.html (read 13 Nov 2026) - https://docs.atlan.com/llms/governance/tags/what-are-tags/llms.txt: https://docs.atlan.com/llms/governance/tags/what-are-tags/llms.txt (read 13 Nov 2026) - https://www.collibra.com/products/data-catalog: https://www.collibra.com/products/data-catalog (read 13 Nov 2026) - https://docs.databricks.com/aws/en/data-governance/unity-catalog/data-classification: https://docs.databricks.com/aws/en/data-governance/unity-catalog/data-classification (read 13 Nov 2026) - https://docs.datahub.com/docs/metadata-ingestion/docs/dev_guides/classification: https://docs.datahub.com/docs/metadata-ingestion/docs/dev_guides/classification (read 13 Nov 2026) - https://docs.euno.ai/sources/data-security/cyera-integration/cyera-integration-use-cases.md: https://docs.euno.ai/sources/data-security/cyera-integration/cyera-integration-use-cases.md (read 13 Nov 2026) - https://documentation.immuta.com/saas/configuration/tags/data-discovery.md: https://documentation.immuta.com/saas/configuration/tags/data-discovery.md (read 13 Nov 2026) - https://www.informatica.com/about-us/news/news-releases/2024/02/20240229-informatica-launches-cloud-data-access-management-industrys-first-ai-powered-solution-for-automating-data-access-policy-enforcement-at-scale.html: https://www.informatica.com/about-us/news/news-releases/2024/02/20240229-informatica-launches-cloud-data-access-management-industrys-first-ai-powered-solution-for-automating-data-access-policy-enforcement-at-scale.html (read 13 Nov 2026) - https://learn.microsoft.com/purview/data-map-classification: https://learn.microsoft.com/purview/data-map-classification (read 13 Nov 2026) - https://www.onetrust.com/solutions/data-use-governance/: https://www.onetrust.com/solutions/data-use-governance/ (read 13 Nov 2026) - https://docs.privacera.com/data-security/user-guide/discovery/scanning/classification/tags.html: https://docs.privacera.com/data-security/user-guide/discovery/scanning/classification/tags.html (read 13 Nov 2026) - https://docs.secoda.co/resource-and-metadata-management/tags/auto-pii-tagging.md: https://docs.secoda.co/resource-and-metadata-management/tags/auto-pii-tagging.md (read 13 Nov 2026) - https://securiti.ai/products/data-discovery/: https://securiti.ai/products/data-discovery/ (read 13 Nov 2026) - https://web.archive.org/web/2026/https://docs.selectstar.com/data-management/automated-pii-detection-beta: https://web.archive.org/web/2026/https://docs.selectstar.com/data-management/automated-pii-detection-beta (read 13 Nov 2026) - https://docs.snowflake.com/en/user-guide/classify-intro.md: https://docs.snowflake.com/en/user-guide/classify-intro.md (read 13 Nov 2026) Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/index/ --- # Weights fixed first, evidence second, scores last, and the scorer never knew the names METHOD, read 13 Nov 2026 **The short answer.** Eight criteria and their weights were committed on 13 Nov 2026, before any vendor was scored. A subagent scored every tool from the evidence files without being told which tool is the client, and a second reviewed those scores blind. A vendor claim earns at most 7 of 10 until a second source confirms it. Need to Know ranks tools by one question: which show where sensitive data surfaces, in which reports, to which viewers and to which agents, and control what an agent is told. The eight criteria below turn that question into scores, and the weights are the ones a governance lead in a regulated company would set before looking at any vendor. The weights were written to a file in the repository first. The first score was committed after it, and the file has not changed since. The scores, the weights and the ranked views on this site are checked against that history on every build, and a build that disagrees does not ship. ## The criteria and their weights | Criterion | What is scored, with evidence | Weight | | --- | --- | --- | | Follows sensitive data into BI | From a warehouse column through transformation to the BI field and the report, across BI tools, as documented | 25 | | Controls what an agent is told | Context and access scoped to the person asking and applied on each agent call | 20 | | Shows who actually saw it | Viewers per report and per agent, from usage or access logs | 15 | | Carries classification downstream | Takes sensitivity labels from where they already exist (the warehouse, a classifier, a security tool) and propagates them along lineage | 15 | | Acts on it | Alerts, tickets, blocking or masking | 10 | | Coverage of the stack | Warehouses, transformation, BI and security tools, as documented | 5 | | Evidence beyond the vendor | Named customers, analyst coverage, partner pages | 5 | | Price transparency | Published prices or a published pricing model | 5 | Weights fixed 13 Nov 2026, before the first score, and unchanged since. ## What each score means - **0:** none found on the read date - **7:** the most a vendor claim or vendor documentation alone can earn: detailed, specific, covering the whole criterion - **1-3:** mentioned, partial, or limited to one system or one level - **4-6:** documented and working, with gaps the documentation shows - **8-10:** detailed and confirmed by a second source (third-party write-up, or observed directly in public code, schema or release record) ## The rules every score follows - Every vendor is scored 0 to 10 on every criterion, whole numbers, from the evidence file only. - A vendor claim scores at most 7 until a second source confirms it (kind third-party or observed). - None found scores 0 and is written "none found on" the read date, never as a missing feature. - Breadth facts (module counts, integration counts, headcount, funding) carry at most 10 percent of any ranking; integration counts inform coverage only through the systems they name. - The total is the weighted sum of the scores divided by 10 (0 to 100 scale, published to one decimal). - Ties break on the higher score on the heaviest criterion, then by name. - Once the first score exists, no weight and no criterion changes. A score changes only when a sourced fact changes, logged with the fact. ## How ties are broken Tied totals are broken by the higher score on the heaviest criterion, then by the tool name. Where two criteria share the top weight, as Follows sensitive data into BI and Acts on it do in the lean team situation (20 each), the heaviest is the first in the published criteria order, which is Follows sensitive data into BI for the site weights. ## The five situations and their own weights Each situation page ranks the same scores under weights a buyer in that situation would use. These were fixed and committed with the site weights, before any score. | Situation | Into BI | Agent told | Who saw it | Label carried | Acts | Stack | Evidence | Price | | --- | --- | --- | --- | --- | --- | --- | --- | --- | | [A governance lead who must show where a regulated field ends up](/best-for/regulated-field/) | 35 | 5 | 20 | 20 | 10 | 5 | 5 | 0 | | [A company connecting AI agents to its analytics data this year](/best-for/agents-on-analytics/) | 15 | 40 | 15 | 10 | 10 | 5 | 0 | 5 | | [A Microsoft estate: Fabric, Power BI and Purview](/best-for/microsoft-estate/) | 30 | 10 | 15 | 20 | 15 | 10 | 0 | 0 | | [A mixed stack: Snowflake or Databricks with dbt and two or more BI tools](/best-for/mixed-stack/) | 30 | 10 | 10 | 20 | 5 | 20 | 0 | 5 | | [A lean data team with no governance hire](/best-for/lean-team/) | 20 | 10 | 10 | 15 | 20 | 5 | 5 | 15 | Situation weights, each summing to 100. Column order is the published criteria order. - **A regulated field:** An auditor asks for the path of the field into each report and the people who saw it, with its classification carried along. - **Agents on analytics:** Before an agent connects, someone must control what it is told for each person it acts for, and see what it was given. - **A Microsoft estate:** In a Microsoft estate sensitivity labels already exist; the question is how far they travel into Power BI and what happens when they do. - **A mixed stack:** Across several BI tools, the value is in following a column through dbt into every BI tool in use, with the label carried. - **A lean team:** With no governance hire, the tool has to act on its own findings and the cost has to be knowable up front. ## How the scoring was kept blind Each vendor was researched to the same depth: product pages, documentation, release notes, a trust or security page and at least two third-party sources, every fact stored with its quote, its source URL and the date it was read. A second pass re-read six quotes per vendor and re-searched every none-found fact. A subagent was then given only the weights, a scoring guide and an anonymized evidence packet, and was not told which vendor is the client. A second subagent with fresh context reviewed every cell the same way. Each cell cites the facts it rests on, and a script checks that a score above 7 cites a fact from a second source. ## What the scores do not cover The packets kept customer names and product categories as the vendors publish them, so a reader who knows the market could guess some vendors. The scorers were told not to try and could not browse. A score is a reading of public documentation on 13 Nov 2026. It is not a test of a running product, and a tool can do more than its documentation says. Where nothing was found the cell reads none found on that date, and it scores 0. Breadth facts such as integration counts, headcount and funding carry at most 10 percent of any ranking. Euno's pricing page and home page describe two pricing models and neither gives a dollar price, so price transparency is scored on what each page says. ## Sources - Need to Know scores, CSV: https://aidatagovernancetools.com/datasets/need-to-know-scores.csv (read 13 Nov 2026) - Need to Know evidence, CSV: https://aidatagovernancetools.com/datasets/need-to-know-evidence.csv (read 13 Nov 2026) Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/method/ --- # Euno for AI data governance: rank 1 of 16, at 67.0 of 100 PLATFORM PROFILE, read 13 Nov 2026 **The short answer.** Euno ranks 1 of 16 on the Need to Know index at 67.0 of 100, read 13 Nov 2026. Its best criterion is Carries classification downstream at 8 of 10, and its weakest is Price transparency at 4. The exposure map records 3 of six stages as documented and 3 as partial. **Where Euno is behind.** Euno is not a policy engine or a DSPM: it reads metadata only, so it does not scan data contents or mask at the warehouse, which leaves it behind Atlan on acting on findings (5 to 7), and it publishes no dollar prices. - **Category:** AI context platform for enterprise data (metadata graph with rule-based labels and an MCP server) - **Status:** Exists under this name on 13 Nov 2026 (euno.ai serves "Euno: The AI Context Platform for Enterprise Data"; docs.euno.ai is live; Series A announced September 9, 2026; Gartner Cool Vendor release September 2, 2026). - **Exposure trail:** Warehouse column: documented; Transformation: partial; BI field: documented; Report: documented; Viewer: partial; Agent: partial - **Warehouses named:** Snowflake, BigQuery, Databricks, Redshift (private preview), MySQL, SQL Server - **BI tools named:** Tableau, Looker, Power BI, ThoughtSpot, Sigma, Omni, Cube Core, Salesforce, Hex - **Security tools named:** Cyera, BigID, Microsoft Purview, Monte Carlo, Elementary, Okta, Google Workspace - **Rank and total:** 1 of 16, 67.0 of 100 3 of 6 stages documented, 3 partial ## Euno on the eight criteria | Criterion | Weight | Score | Why | | --- | --- | --- | --- | | Follows sensitive data into BI | 25 | 7 | Documents warehouse classifications traced through column lineage to Tableau, Looker and Power BI fields and reports; all vendor-stated. | | Controls what an agent is told | 20 | 7 | Personas define what data and actions are available to an agent over MCP, enforced automatically; vendor documentation only. | | Shows who actually saw it | 15 | 6 | Distinct users per Tableau and Power BI resource, resolved behind shared accounts, but a per-agent log was none found on 2026-11-13. | | Carries classification downstream | 15 | 8 | Imports Cyera and BigID classifications and propagates them along column lineage into BI; Cyera lists the integration independently. | | Acts on it | 10 | 5 | Alerts, tickets and recommendations are documented, but masking or blocking was none found on 2026-11-13 (metadata only). | | Coverage of the stack | 5 | 7 | Warehouses, dbt, nine BI tools and security tools Cyera, BigID and Purview are named; some catalogs are absent. | | Evidence beyond the vendor | 5 | 8 | A dbt Labs post on a named customer and a Cyera partner listing confirm it independently. | | Price transparency | 5 | 4 | Pricing is based on assets managed and agent context consumption, with unlimited users; no dollar amount was found. | Blind scores for Euno, 0 to 10. A vendor claim scores at most 7 until a second source confirms it. ## Where Euno is strongest Vendor-stated: Euno takes classifications from Cyera and BigID, carries them along column-level lineage into BI fields and reports, and scopes MCP context by persona. ## Where Euno falls short Euno is not a policy engine or a DSPM: it reads metadata only and does not query table contents, no masking or access blocking was found in its docs, and it publishes no dollar prices. ## Euno along the exposure trail | Stage | Reading | Evidence | | --- | --- | --- | | [Warehouse column](/exposure-map/column/) | documented | Euno docs say Euno maps Cyera classifications onto Snowflake and BigQuery resources and traces them forward through column-level lineage. [Source](https://docs.euno.ai/sources/data-security/cyera-integration/cyera-integration-use-cases.md?utm_source=aidatagovernancetools.com&utm_medium=referral&utm_campaign=platform), read 13 Nov 2026. | | [Transformation](/exposure-map/transformation/) | partial | Euno docs describe a Propagated Boolean tag that carries a value such as contains_pii along a direction of lineage. [Source](https://docs.euno.ai/using-euno/metadata-activation/metadata-tags.md?utm_source=aidatagovernancetools.com&utm_medium=referral&utm_campaign=platform), read 13 Nov 2026. | | [BI field](/exposure-map/bi-field/) | documented | Euno docs say BigID classifications do not automatically appear on Looker, Tableau or Power BI assets, and that Euno propagates them to downstream fields and reports. [Source](https://docs.euno.ai/sources/data-security/bigid-integration/bigid-integration-use-cases.md?utm_source=aidatagovernancetools.com&utm_medium=referral&utm_campaign=platform), read 13 Nov 2026. | | [Report](/exposure-map/report/) | documented | Euno docs say Cyera classifies sensitive data in the warehouse and Euno propagates those classifications through column-level lineage into BI fields, dashboards and reports. [Source](https://docs.euno.ai/sources/data-security/cyera-integration/cyera-integration-use-cases.md?utm_source=aidatagovernancetools.com&utm_medium=referral&utm_campaign=platform), read 13 Nov 2026. | | [Viewer](/exposure-map/viewer/) | partial | Euno docs say Tableau impression records give counts and distinct users per resource over 14, 30 and 60 days. [Source](https://docs.euno.ai/using-euno/usage-optimization/tableau-usage-data.md?utm_source=aidatagovernancetools.com&utm_medium=referral&utm_campaign=platform), read 13 Nov 2026. | | [Agent](/exposure-map/agent/) | partial | Euno docs say Euno MCP uses the active persona to determine what data and actions are available. [Source](https://docs.euno.ai/ai/mcp-setup.md?utm_source=aidatagovernancetools.com&utm_medium=referral&utm_campaign=platform), read 13 Nov 2026. | Documented, partial or none found on the read date. Vendor claims are the vendor's. ## Euno in each situation | Situation | Rank | Total | Leader | | --- | --- | --- | --- | | [A regulated field](/best-for/regulated-field/) | 2 | 68.5 | Atlan 68.5 | | [Agents on analytics](/best-for/agents-on-analytics/) | 1 | 66.0 | Euno 66.0 | | [A Microsoft estate](/best-for/microsoft-estate/) | 2 | 67.5 | Atlan 68.5 | | [A mixed stack](/best-for/mixed-stack/) | 1 | 68.5 | Euno 68.5 | | [A lean team](/best-for/lean-team/) | 1 | 62.5 | Euno 62.5 | Each situation ranks the same scores under its own published weights. ## The evidence on Euno, fact by fact - **euno-01** (Profile, Euno's own claim): Euno docs describe Euno as a metadata management platform that powers governance automation and provides automated context for AI. [Source](https://docs.euno.ai/?utm_source=aidatagovernancetools.com&utm_medium=referral&utm_campaign=platform), read 13 Nov 2026. - **euno-02** (Profile, Euno's own claim): Euno says on its home page FAQ that it is an enterprise context platform for AI agents and that it is not a data catalog. [Source](https://euno.ai/?utm_source=aidatagovernancetools.com&utm_medium=referral&utm_campaign=platform), read 13 Nov 2026. - **euno-03** (Profile, Euno's own claim): Euno says it was founded in 2023, is based in San Francisco and Tel Aviv, and is backed by N47, 10D and data and security founders. [Source](https://euno.ai/blog/euno-raises-series-a?utm_source=aidatagovernancetools.com&utm_medium=referral&utm_campaign=platform), read 13 Nov 2026. - **euno-04** (Profile, Euno's own claim): Euno says in a September 9, 2026 wire release that it raised a $23 million Series A led by N47, with existing investor 10D participating. [Source](https://www.prnewswire.com/news-releases/euno-raises-23-million-series-a-to-build-the-ai-context-brain-for-the-enterprise-302872947.html), read 13 Nov 2026. - **euno-05** (Profile, Euno's own claim): Euno says it was named a Cool Vendor in the 2026 Gartner Coolest Vendor Innovations in Data Management report (Gartner publication dated 29 July 2026, cited by Euno); Gartner's own page was not readable on 2026-11-13. [Source](https://euno.ai/blog/euno-named-as-a-gartner-cool-vendor-2026?utm_source=aidatagovernancetools.com&utm_medium=referral&utm_campaign=platform), read 13 Nov 2026. - **euno-06** (Profile, Euno's own claim): Euno docs FAQ say Euno reads metadata and query logs and does not query the data in tables. [Source](https://docs.euno.ai/support-resources/faq.md?utm_source=aidatagovernancetools.com&utm_medium=referral&utm_campaign=platform), read 13 Nov 2026. - **euno-07** (Profile, none-found): None found on 2026-11-13: a trust, security or compliance certification page (SOC 2, ISO 27001) on euno.ai; euno.ai/security, /trust and /trust-center returned 404 and the terms were absent from the pages read, in euno.ai and docs.euno.ai. Searched: https://euno.ai/, read 13 Nov 2026. - **euno-08** (Profile, Euno's own claim): Euno says Active metadata Tags let a team define rules that label assets as gold layer, PII free, governed, highly used or AI-ready, and that the tags update as the data model changes. [Source](https://euno.ai/product/automated-labeling?utm_source=aidatagovernancetools.com&utm_medium=referral&utm_campaign=platform), read 13 Nov 2026. - **euno-09** (Profile, Euno's own claim): Euno docs list active tag types that calculate values from rules (categorical from EQL conditions, live boolean, propagated boolean, AI select, Liquid template, coalesce); fixed tags are values a person sets. [Source](https://docs.euno.ai/using-euno/metadata-activation/metadata-tags.md?utm_source=aidatagovernancetools.com&utm_medium=referral&utm_campaign=platform), read 13 Nov 2026. - **euno-10** (Profile, Euno's own claim): Euno's own AlphaSense write-up gives example rules: mark a Tableau asset trusted when it queries only gold-layer dbt models, or flag anything depending on a PII column upstream as not AI-ready. [Source](https://euno.ai/blog/alphasense-x-euno-dbt-summit-26?utm_source=aidatagovernancetools.com&utm_medium=referral&utm_campaign=platform), read 13 Nov 2026. - **euno-11** (Profile, Euno's own claim): Euno docs say Monte Carlo remains the source of truth for alerts, and Euno shows active alerts on tables, columns and dbt resources. [Source](https://docs.euno.ai/sources/data-observability/monte-carlo.md?utm_source=aidatagovernancetools.com&utm_medium=referral&utm_campaign=platform), read 13 Nov 2026. - **euno-12** (Profile, Euno's own claim): Euno docs say Elementary remains the source of truth for incidents, and Euno shows open and acknowledged incidents from dbt tests on resources. [Source](https://docs.euno.ai/sources/data-observability/elementary-integration.md?utm_source=aidatagovernancetools.com&utm_medium=referral&utm_campaign=platform), read 13 Nov 2026. - **euno-13** (Profile, Euno's own claim): Euno says it detects conflicting definitions of a metric and connects the relevant owners to resolve them; governed definitions are glossary entries a person maintains. [Source](https://euno.ai/use-cases/governance-automations?utm_source=aidatagovernancetools.com&utm_medium=referral&utm_campaign=platform), read 13 Nov 2026. - **euno-14** (Profile, none-found): None found on 2026-11-13: a data quality or health test that Euno runs itself on table contents (the FAQ says Euno does not query data; health comes from the Monte Carlo and Elementary integrations), in docs.euno.ai FAQ and sources. Searched: https://docs.euno.ai/support-resources/faq.md, read 13 Nov 2026. - **euno-15** (Profile, Euno's own claim): Euno docs say the standard MCP connection uses OAuth and lets Cursor, Claude, ChatGPT and other MCP clients explore the data model. [Source](https://docs.euno.ai/ai/mcp-setup.md?utm_source=aidatagovernancetools.com&utm_medium=referral&utm_campaign=platform), read 13 Nov 2026. - **euno-16** (Profile, Euno's own claim): Euno docs say Euno MCP uses the active persona to determine what data and actions are available. [Source](https://docs.euno.ai/ai/mcp-setup.md?utm_source=aidatagovernancetools.com&utm_medium=referral&utm_campaign=platform), read 13 Nov 2026. - **euno-17** (Profile, Euno's own claim): Euno docs describe a Push proactively option that always includes a tag in API responses to AI agents. [Source](https://docs.euno.ai/using-euno/metadata-activation/metadata-tags.md?utm_source=aidatagovernancetools.com&utm_medium=referral&utm_campaign=platform), read 13 Nov 2026. - **euno-18** (Profile, Euno's own claim): Euno says it generates live column-level lineage from warehouse to BI, stitched with usage, ownership and logic. [Source](https://euno.ai/?utm_source=aidatagovernancetools.com&utm_medium=referral&utm_campaign=platform), read 13 Nov 2026. - **euno-19** (Profile, Euno's own claim): Euno says active tags are live and update automatically as the data model changes. [Source](https://euno.ai/product/automated-labeling?utm_source=aidatagovernancetools.com&utm_medium=referral&utm_campaign=platform), read 13 Nov 2026. - **euno-20** (Profile, Euno's own claim): Euno docs say workflows run automatically on a daily schedule and notify by email, Slack or webhook when EQL results meet a condition. [Source](https://docs.euno.ai/using-euno/metadata-activation/workflows.md?utm_source=aidatagovernancetools.com&utm_medium=referral&utm_campaign=platform), read 13 Nov 2026. - **euno-21** (Evidence beyond the vendor, third-party): dbt Labs published a post on 2026-10-26 saying AlphaSense rebuilt a legacy dashboard model as a governed star schema of 13 models in about 15 prompts in one session, using Euno for context. [Source](https://www.getdbt.com/blog/alphasense-dbt-ai-context-data-rebuild.md), read 13 Nov 2026. - **euno-22** (Evidence beyond the vendor, third-party): Cyera lists Euno as a partner integration in its integrations directory. [Source](https://www.cyera.com/integrations), read 13 Nov 2026. - **euno-23** (Evidence beyond the vendor, observed): The public GitHub organization euno-ai holds a Terraform provider (MIT), a Terraform module for Snowflake Intelligence (MIT) and a Postman collection for the Euno API. [Source](https://api.github.com/orgs/euno-ai/repos), read 13 Nov 2026. - **euno-24** (Evidence beyond the vendor, Euno's own claim): Euno says in its wire release that its customers include AlphaSense and Zayo Group (vendor statement). [Source](https://www.prnewswire.com/news-releases/euno-raises-23-million-series-a-to-build-the-ai-context-brain-for-the-enterprise-302872947.html), read 13 Nov 2026. - **euno-25** (Evidence beyond the vendor, none-found): None found on 2026-11-13: a Gartner Peer Insights page, a cloud marketplace listing with a price, or a dbt partner directory entry for Euno (the Gartner report page returned HTTP 403; getdbt.com/partners does not list Euno), in gartner.com and getdbt.com/partners. Searched: https://euno.ai/blog/euno-named-as-a-gartner-cool-vendor-2026, read 13 Nov 2026. - **euno-26** (Price transparency, Euno's own claim): Euno's home page says pricing is based on AI agent context consumption, not user seats. [Source](https://euno.ai/?utm_source=aidatagovernancetools.com&utm_medium=referral&utm_campaign=platform), read 13 Nov 2026. - **euno-27** (Price transparency, Euno's own claim): Euno's pricing page says users and AI agents are unlimited and the customer pays for the data assets managed. [Source](https://euno.ai/pricing?utm_source=aidatagovernancetools.com&utm_medium=referral&utm_campaign=platform), read 13 Nov 2026. - **euno-28** (Price transparency, none-found): None found on 2026-11-13: a dollar price for any plan; the Start tier says Request pricing and the other tiers say Book a demo, in euno.ai/pricing. Searched: https://euno.ai/pricing, read 13 Nov 2026. - **euno-29** (Shows who actually saw it, Euno's own claim): Euno docs say Tableau impression records give counts and distinct users per resource over 14, 30 and 60 days. [Source](https://docs.euno.ai/using-euno/usage-optimization/tableau-usage-data.md?utm_source=aidatagovernancetools.com&utm_medium=referral&utm_campaign=platform), read 13 Nov 2026. - **euno-30** (Shows who actually saw it, Euno's own claim): Euno docs say Power BI impressions are collected from the Fabric user activity log for reports, dashboards and semantic models, with distinct users over 14, 30 and 60 days. [Source](https://docs.euno.ai/using-euno/usage-optimization/power-bi-usage-data.md?utm_source=aidatagovernancetools.com&utm_medium=referral&utm_campaign=platform), read 13 Nov 2026. - **euno-31** (Shows who actually saw it, Euno's own claim): Euno docs say shared BI service accounts hide who accessed sensitive data, and that Euno resolves the individuals behind BI access and usage events. [Source](https://docs.euno.ai/sources/data-security/cyera-integration/cyera-integration-use-cases.md?utm_source=aidatagovernancetools.com&utm_medium=referral&utm_campaign=platform), read 13 Nov 2026. - **euno-32** (Shows who actually saw it, none-found): None found on 2026-11-13: a documented per-agent log of which agent was served which sensitive field, in docs.euno.ai MCP, audit log and AI pages. Searched: https://docs.euno.ai/ai/mcp-setup.md, read 13 Nov 2026. - **euno-33** (Controls what an agent is told, Euno's own claim): Euno docs say personas define what a user can see and do and personalize how Euno responds when used as the context layer for another agent over MCP. [Source](https://docs.euno.ai/setup-configuration/personas.md?utm_source=aidatagovernancetools.com&utm_medium=referral&utm_campaign=platform), read 13 Nov 2026. - **euno-34** (Controls what an agent is told, Euno's own claim): Euno says persona-based access decides who receives which context, enforced automatically. [Source](https://euno.ai/?utm_source=aidatagovernancetools.com&utm_medium=referral&utm_campaign=platform), read 13 Nov 2026. - **euno-35** (Carries classification downstream, Euno's own claim): Euno docs describe a Propagated Boolean tag that carries a value such as contains_pii along a direction of lineage. [Source](https://docs.euno.ai/using-euno/metadata-activation/metadata-tags.md?utm_source=aidatagovernancetools.com&utm_medium=referral&utm_campaign=platform), read 13 Nov 2026. - **euno-36** (Carries classification downstream, Euno's own claim): Euno docs say Cyera classifies sensitive data in the warehouse and Euno propagates those classifications through column-level lineage into BI fields, dashboards and reports. [Source](https://docs.euno.ai/sources/data-security/cyera-integration/cyera-integration-use-cases.md?utm_source=aidatagovernancetools.com&utm_medium=referral&utm_campaign=platform), read 13 Nov 2026. - **euno-37** (Carries classification downstream, Euno's own claim): Euno docs say BigID classifications do not automatically appear on Looker, Tableau or Power BI assets, and that Euno propagates them to downstream fields and reports. [Source](https://docs.euno.ai/sources/data-security/bigid-integration/bigid-integration-use-cases.md?utm_source=aidatagovernancetools.com&utm_medium=referral&utm_campaign=platform), read 13 Nov 2026. - **euno-38** (Follows sensitive data into BI, Euno's own claim): Euno says PII exposure tracking maps sensitive data propagation into the business layer and tracks access and actual exposure through reports, dashboards and AI agents. [Source](https://euno.ai/?utm_source=aidatagovernancetools.com&utm_medium=referral&utm_campaign=platform), read 13 Nov 2026. - **euno-39** (Follows sensitive data into BI, Euno's own claim): Euno says it propagates DSPM classifications such as PII and PCI from warehouse columns to BI fields, reports and dashboards (vendor blog, April 20, 2026). [Source](https://euno.ai/blog/euno-is-officially-live-on-cyeras-integrations?utm_source=aidatagovernancetools.com&utm_medium=referral&utm_campaign=platform), read 13 Nov 2026. - **euno-40** (Follows sensitive data into BI, Euno's own claim): Euno docs say Euno maps Cyera classifications onto Snowflake and BigQuery resources and traces them forward through column-level lineage. [Source](https://docs.euno.ai/sources/data-security/cyera-integration/cyera-integration-use-cases.md?utm_source=aidatagovernancetools.com&utm_medium=referral&utm_campaign=platform), read 13 Nov 2026. - **euno-41** (Acts on it, Euno's own claim): Euno says governance workflows track metadata changes and trigger notifications, tickets and recommendations for deprecation. [Source](https://euno.ai/?utm_source=aidatagovernancetools.com&utm_medium=referral&utm_campaign=platform), read 13 Nov 2026. - **euno-42** (Acts on it, Euno's own claim): Euno docs say that when sensitive data flows into a dashboard or report, Euno generates real-time alerts so security teams can enforce access policies in BI. [Source](https://docs.euno.ai/sources/data-security/cyera-integration/cyera-integration-use-cases.md?utm_source=aidatagovernancetools.com&utm_medium=referral&utm_campaign=platform), read 13 Nov 2026. - **euno-43** (Acts on it, none-found): None found on 2026-11-13: a documented feature that masks data or blocks warehouse access (docs describe observing masking policies and sending alerts; the FAQ says Euno reads metadata only), in docs.euno.ai workflows, integrations and FAQ. Searched: https://docs.euno.ai/support-resources/faq.md, read 13 Nov 2026. - **euno-44** (Coverage of the stack, Euno's own claim): Euno docs say the Purview integration discovers Purview DLP policies and links them to Power BI resources. [Source](https://docs.euno.ai/sources/data-security/microsoft-purview-integration.md?utm_source=aidatagovernancetools.com&utm_medium=referral&utm_campaign=platform), read 13 Nov 2026. - **euno-45** (Coverage of the stack, none-found): None found on 2026-11-13: a Euno source integration for Collibra, Atlan, Alation, Qlik Sense or MicroStrategy, in docs.euno.ai/sources. Searched: https://docs.euno.ai/sources.md, read 13 Nov 2026. - **euno-46** (Evidence beyond the vendor, observed): The public PyPI registry lists an open source Python package "euno" (version 0.6.2, 6 releases, latest uploaded 2026-07-28) that describes itself as a CLI library for a Euno instance, with the source repository in the euno-ai GitHub organization. [Source](https://pypi.org/pypi/euno/json), read 13 Nov 2026. - **euno-47** (Evidence beyond the vendor, observed): The public Terraform Registry lists a community provider euno-ai/euno (version 0.1.0, published 2025-10-04, 585 downloads) whose docs cover dbt Core, Fivetran, Hex and Snowflake integration resources. [Source](https://registry.terraform.io/v1/providers/euno-ai/euno), read 13 Nov 2026. ## Compare Euno - [Euno vs Microsoft Purview](/compare/euno-vs-microsoft-purview/) - [Euno vs Immuta](/compare/euno-vs-immuta/) - [Euno vs Privacera](/compare/euno-vs-privacera/) - [Euno vs Securiti](/compare/euno-vs-securiti/) - [Euno vs OneTrust](/compare/euno-vs-onetrust/) - [The full index](/index/) ## Sources - https://docs.euno.ai/: https://docs.euno.ai/ (read 13 Nov 2026) - https://euno.ai/: https://euno.ai/ (read 13 Nov 2026) - https://euno.ai/blog/euno-raises-series-a: https://euno.ai/blog/euno-raises-series-a (read 13 Nov 2026) - https://www.prnewswire.com/news-releases/euno-raises-23-million-series-a-to-build-the-ai-context-brain-for-the-enterprise-302872947.html: https://www.prnewswire.com/news-releases/euno-raises-23-million-series-a-to-build-the-ai-context-brain-for-the-enterprise-302872947.html (read 13 Nov 2026) - https://euno.ai/blog/euno-named-as-a-gartner-cool-vendor-2026: https://euno.ai/blog/euno-named-as-a-gartner-cool-vendor-2026 (read 13 Nov 2026) - https://docs.euno.ai/support-resources/faq.md: https://docs.euno.ai/support-resources/faq.md (read 13 Nov 2026) - https://euno.ai/product/automated-labeling: https://euno.ai/product/automated-labeling (read 13 Nov 2026) - https://docs.euno.ai/using-euno/metadata-activation/metadata-tags.md: https://docs.euno.ai/using-euno/metadata-activation/metadata-tags.md (read 13 Nov 2026) - https://euno.ai/blog/alphasense-x-euno-dbt-summit-26: https://euno.ai/blog/alphasense-x-euno-dbt-summit-26 (read 13 Nov 2026) - https://docs.euno.ai/sources/data-observability/monte-carlo.md: https://docs.euno.ai/sources/data-observability/monte-carlo.md (read 13 Nov 2026) - https://docs.euno.ai/sources/data-observability/elementary-integration.md: https://docs.euno.ai/sources/data-observability/elementary-integration.md (read 13 Nov 2026) - https://euno.ai/use-cases/governance-automations: https://euno.ai/use-cases/governance-automations (read 13 Nov 2026) - https://docs.euno.ai/ai/mcp-setup.md: https://docs.euno.ai/ai/mcp-setup.md (read 13 Nov 2026) - https://docs.euno.ai/using-euno/metadata-activation/workflows.md: https://docs.euno.ai/using-euno/metadata-activation/workflows.md (read 13 Nov 2026) - https://www.getdbt.com/blog/alphasense-dbt-ai-context-data-rebuild.md: https://www.getdbt.com/blog/alphasense-dbt-ai-context-data-rebuild.md (read 13 Nov 2026) - https://www.cyera.com/integrations: https://www.cyera.com/integrations (read 13 Nov 2026) - https://api.github.com/orgs/euno-ai/repos: https://api.github.com/orgs/euno-ai/repos (read 13 Nov 2026) - https://euno.ai/pricing: https://euno.ai/pricing (read 13 Nov 2026) - https://docs.euno.ai/using-euno/usage-optimization/tableau-usage-data.md: https://docs.euno.ai/using-euno/usage-optimization/tableau-usage-data.md (read 13 Nov 2026) - https://docs.euno.ai/using-euno/usage-optimization/power-bi-usage-data.md: https://docs.euno.ai/using-euno/usage-optimization/power-bi-usage-data.md (read 13 Nov 2026) - https://docs.euno.ai/sources/data-security/cyera-integration/cyera-integration-use-cases.md: https://docs.euno.ai/sources/data-security/cyera-integration/cyera-integration-use-cases.md (read 13 Nov 2026) - https://docs.euno.ai/setup-configuration/personas.md: https://docs.euno.ai/setup-configuration/personas.md (read 13 Nov 2026) - https://docs.euno.ai/sources/data-security/bigid-integration/bigid-integration-use-cases.md: https://docs.euno.ai/sources/data-security/bigid-integration/bigid-integration-use-cases.md (read 13 Nov 2026) - https://euno.ai/blog/euno-is-officially-live-on-cyeras-integrations: https://euno.ai/blog/euno-is-officially-live-on-cyeras-integrations (read 13 Nov 2026) - https://docs.euno.ai/sources/data-security/microsoft-purview-integration.md: https://docs.euno.ai/sources/data-security/microsoft-purview-integration.md (read 13 Nov 2026) - https://docs.euno.ai/sources.md: https://docs.euno.ai/sources.md (read 13 Nov 2026) - https://pypi.org/pypi/euno/json: https://pypi.org/pypi/euno/json (read 13 Nov 2026) - https://registry.terraform.io/v1/providers/euno-ai/euno: https://registry.terraform.io/v1/providers/euno-ai/euno (read 13 Nov 2026) Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/platforms/euno/ --- # Atlan for AI data governance: rank 2 of 16, at 65.5 of 100 PLATFORM PROFILE, read 13 Nov 2026 **The short answer.** Atlan ranks 2 of 16 on the Need to Know index at 65.5 of 100, read 13 Nov 2026. Its best criterion is Evidence beyond the vendor at 8 of 10, and its weakest is Price transparency at 0. The exposure map records 2 of six stages as documented and 4 as partial. - **Category:** Data catalog, metadata and governance platform, now marketed as a context layer for AI - **Status:** Exists under this name on 13 Nov 2026 (atlan.com and docs.atlan.com are live, docs changelog updated October 2026, footer reads 'Atlan Pte. Ltd. 2026'; homepage now brands it 'The Context Layer for AI'). - **Exposure trail:** Warehouse column: documented; Transformation: partial; BI field: partial; Report: partial; Viewer: partial; Agent: documented - **Warehouses named:** Snowflake, Databricks, Google BigQuery, Amazon Redshift, Microsoft Azure Synapse Analytics, Amazon Athena, Trino, Starburst Enterprise, Teradata, Oracle, PostgreSQL, Microsoft SQL Server, Dremio, Iceberg - **BI tools named:** Tableau, Microsoft Power BI, Looker, Amazon QuickSight, Qlik Sense Cloud, Sigma, ThoughtSpot, Metabase, Mode, MicroStrategy, Microsoft Fabric, IBM Cognos Analytics, Domo, SAP Analytics Cloud - **Security tools named:** BigID, Cyera, ALTR, Immuta - **Rank and total:** 2 of 16, 65.5 of 100 2 of 6 stages documented, 4 partial ## Atlan on the eight criteria | Criterion | Weight | Score | Why | | --- | --- | --- | --- | | Follows sensitive data into BI | 25 | 7 | Column-level lineage documented for Tableau, Looker and Power BI with stated gaps (Tableau flows and embedded, Power BI partial SQL sources). | | Controls what an agent is told | 20 | 7 | MCP forwards the caller identity so persona, role and domain policies apply on each tool call; service tokens carry one persona. | | Shows who actually saw it | 15 | 6 | Power BI usage, queried-by usernames and logged MCP calls exist, but Tableau unique viewers are unsupported and popularity is bounded to supported sources. | | Carries classification downstream | 15 | 7 | Imports source tags and Cyera classifications and propagates tags along lineage, though propagation is off by default and docs conflict. | | Acts on it | 10 | 7 | Tag-driven policies can mask or deny queries, and data quality failures alert to Slack, Teams, Jira or ServiceNow. | | Coverage of the stack | 5 | 7 | Wide warehouses, dbt, many BI tools and security tools BigID, Cyera and ALTR are named. | | Evidence beyond the vendor | 5 | 8 | Soda, a data observability vendor and Dagster document integrations independently; no analyst page was readable. | | Price transparency | 5 | 0 | No published price, plan table or pricing model was found on 2026-11-13; pricing redirects to sales. | Blind scores for Atlan, 0 to 10. A vendor claim scores at most 7 until a second source confirms it. ## Where Atlan is strongest Vendor-stated: Tag-driven purposes mask or deny sensitive columns, tags can propagate through lineage, and MCP runs under the asking user's persona with every call logged. ## Where Atlan falls short No built-in PII detector was found in the docs, tag propagation is off by default, and Tableau unique-viewer counts are not supported. ## Atlan along the exposure trail | Stage | Reading | Evidence | | --- | --- | --- | | [Warehouse column](/exposure-map/column/) | documented | Atlan says it crawls and syncs tags from source systems (AWS Glue, Confluent Kafka, Databricks, dbt, BigQuery, Snowflake) so they show up in Atlan. [Source](https://docs.atlan.com/llms/governance/tags/what-are-tags/llms.txt), read 13 Nov 2026. | | [Transformation](/exposure-map/transformation/) | partial | When attaching a tag, a user can allow propagation to child and downstream assets through lineage. [Source](https://docs.atlan.com/llms/governance/tags/attach-a-tag/llms.txt), read 13 Nov 2026. | | [BI field](/exposure-map/bi-field/) | partial | Atlan says it captures column-level lineage automatically across warehouses, pipelines and BI tools. [Source](https://docs.atlan.com/product/capabilities/lineage/concepts/what-is-column-level-lineage), read 13 Nov 2026. | | [Report](/exposure-map/report/) | partial | The Metadata Propagator can be restricted by asset type to keep metadata out of report-level assets, which implies it can reach them when not restricted. [Source](https://docs.atlan.com/product/capabilities/lineage/how-tos/propagate-metadata-through-lineage), read 13 Nov 2026. | | [Viewer](/exposure-map/viewer/) | partial | Atlan computes a popularity score from distinct users and read queries over the last 30 days for supported sources. [Source](https://docs.atlan.com/llms/catalog/usage-and-popularity/interpret-usage-metrics/llms.txt), read 13 Nov 2026. | | [Agent](/exposure-map/agent/) | documented | Atlan says MCP forwards the caller's identity so the same persona, role and domain policies as the UI apply to every tool call. [Source](https://docs.atlan.com/product/capabilities/atlan-ai/references/mcp-security), read 13 Nov 2026. | Documented, partial or none found on the read date. Vendor claims are the vendor's. ## Atlan in each situation | Situation | Rank | Total | Leader | | --- | --- | --- | --- | | [A regulated field](/best-for/regulated-field/) | 1 | 68.5 | Atlan 68.5 | | [Agents on analytics](/best-for/agents-on-analytics/) | 2 | 65.0 | Euno 66.0 | | [A Microsoft estate](/best-for/microsoft-estate/) | 1 | 68.5 | Atlan 68.5 | | [A mixed stack](/best-for/mixed-stack/) | 2 | 65.5 | Euno 68.5 | | [A lean team](/best-for/lean-team/) | 2 | 59.0 | Euno 62.5 | Each situation ranks the same scores under its own published weights. ## The evidence on Atlan, fact by fact - **atlan-01** (Profile, Atlan's own claim): Atlan says it launched publicly in 2020 as the context layer for data. [Source](https://atlan.com/about/), read 13 Nov 2026. - **atlan-02** (Profile, Atlan's own claim): Atlan's docs describe it as a data catalog and governance platform. [Source](https://docs.atlan.com/llms.txt), read 13 Nov 2026. - **atlan-03** (Profile, Atlan's own claim): Atlan says playbooks are rule-based automations that update asset metadata in bulk. [Source](https://docs.atlan.com/llms/governance/playbooks/set-up-playbooks/llms.txt), read 13 Nov 2026. - **atlan-04** (Profile, Atlan's own claim): A playbook action can set an asset's certificate to Verified, Draft, Deprecated or No certificate. [Source](https://docs.atlan.com/llms/governance/playbooks/set-up-playbooks/llms.txt), read 13 Nov 2026. - **atlan-05** (Profile, Atlan's own claim): A playbook can be scheduled to run hourly, daily, weekly or monthly. [Source](https://docs.atlan.com/llms/governance/playbooks/set-up-playbooks/llms.txt), read 13 Nov 2026. - **atlan-06** (Carries classification downstream, Atlan's own claim): Atlan says tag propagation to downstream assets is disabled by default and is chosen per tag as Hierarchy & lineage, Hierarchy only, or No propagation. [Source](https://docs.atlan.com/llms/governance/tags/attach-a-tag/llms.txt), read 13 Nov 2026. - **atlan-07** (Carries classification downstream, Atlan's own claim): When attaching a tag, a user can allow propagation to child and downstream assets through lineage. [Source](https://docs.atlan.com/llms/governance/tags/attach-a-tag/llms.txt), read 13 Nov 2026. - **atlan-08** (Carries classification downstream, Atlan's own claim): Atlan's docs vocabulary says a Classification propagates downstream through lineage by default, which differs from the tag page that says propagation is off by default. [Source](https://docs.atlan.com/llms.txt), read 13 Nov 2026. - **atlan-09** (Carries classification downstream, Atlan's own claim): Atlan's Metadata Propagator app pushes owners, certificates, tags and custom metadata from upstream assets to downstream dependents along existing lineage. [Source](https://docs.atlan.com/product/capabilities/lineage/how-tos/propagate-metadata-through-lineage), read 13 Nov 2026. - **atlan-10** (Profile, Atlan's own claim): Atlan says it crawls and syncs tags from source systems (AWS Glue, Confluent Kafka, Databricks, dbt, BigQuery, Snowflake) so they show up in Atlan. [Source](https://docs.atlan.com/llms/governance/tags/what-are-tags/llms.txt), read 13 Nov 2026. - **atlan-11** (Carries classification downstream, Atlan's own claim): Atlan's Cyera connector imports Cyera-discovered classifications onto Atlan assets. [Source](https://docs.atlan.com/data/product-change-log/llms.txt), read 13 Nov 2026. - **atlan-12** (Carries classification downstream, none-found): None found on 2026-11-13: a built-in classifier in Atlan that scans column values and flags PII automatically, in the docs index (docs.atlan.com/llms.txt) and the governance index. Searched: https://docs.atlan.com/llms.txt, read 13 Nov 2026. - **atlan-13** (Acts on it, Atlan's own claim): Atlan purposes apply policies to every asset carrying a tag, so a PII tag can trigger masking or deny query. [Source](https://docs.atlan.com/llms/governance/access-control/what-are-purposes/llms.txt), read 13 Nov 2026. - **atlan-14** (Acts on it, Atlan's own claim): Atlan data policies can apply column-level masking such as hashing, redaction or showing only the last four characters. [Source](https://docs.atlan.com/llms/governance/access-control/data-policy/llms.txt), read 13 Nov 2026. - **atlan-15** (Profile, Atlan's own claim): Atlan says Data Quality Studio is its native module for defining, monitoring and enforcing data quality expectations. [Source](https://docs.atlan.com/llms/governance/data-quality/data-quality-studio/llms.txt), read 13 Nov 2026. - **atlan-16** (Coverage of the stack, Atlan's own claim): Data Quality Studio rules run in the customer's warehouse (BigQuery, Databricks, Snowflake) rather than in Atlan. [Source](https://docs.atlan.com/llms/governance/data-quality/data-quality-studio/llms.txt), read 13 Nov 2026. - **atlan-17** (Profile, Atlan's own claim): Atlan's anomaly detection watches row count and freshness on a Snowflake table without manual thresholds. [Source](https://docs.atlan.com/llms/governance/data-quality/llms.txt), read 13 Nov 2026. - **atlan-18** (Acts on it, Atlan's own claim): Data quality rule failures can send alerts to Slack, Microsoft Teams, Jira or ServiceNow. [Source](https://docs.atlan.com/llms/governance/data-quality/configure-alerts/llms.txt), read 13 Nov 2026. - **atlan-19** (Acts on it, Atlan's own claim): An Atlan app propagates data-quality and pipeline alerts downstream through lineage and keeps announcements in sync as incidents are created or resolved. [Source](https://docs.atlan.com/llms/catalog/lineage/alert-propagation/llms.txt), read 13 Nov 2026. - **atlan-20** (Shows who actually saw it, Atlan's own claim): Atlan computes a popularity score from distinct users and read queries over the last 30 days for supported sources. [Source](https://docs.atlan.com/llms/catalog/usage-and-popularity/interpret-usage-metrics/llms.txt), read 13 Nov 2026. - **atlan-21** (Shows who actually saw it, Atlan's own claim): For Tableau, Atlan does not support unique-viewer counts, Tableau Server or JWT bearer authentication in popularity metrics. [Source](https://docs.atlan.com/llms/catalog/usage-and-popularity/interpret-usage-metrics/llms.txt), read 13 Nov 2026. - **atlan-22** (Shows who actually saw it, Atlan's own claim): A Power BI miner reads activity events to produce usage metrics for Power BI assets and can exclude named users. [Source](https://docs.atlan.com/llms/connectors/microsoft-power-bi/mine-microsoft-power-bi/llms.txt), read 13 Nov 2026. - **atlan-23** (Shows who actually saw it, Atlan's own claim): Atlan MCP can return the source-system usernames that recently or most often queried an asset. [Source](https://docs.atlan.com/llms/platform/atlan-mcp-overview/mcp-asset-attributes/llms.txt), read 13 Nov 2026. - **atlan-24** (Profile, Atlan's own claim): Atlan says MCP can return certificate status, owners, tags, glossary terms and data quality rule counts for an asset. [Source](https://docs.atlan.com/llms/platform/atlan-mcp-overview/mcp-asset-attributes/llms.txt), read 13 Nov 2026. - **atlan-25** (Profile, Atlan's own claim): Atlan MCP returns freshness fields such as when rows last changed (for some connectors such as Snowflake) and when the source last updated. [Source](https://docs.atlan.com/llms/platform/atlan-mcp-overview/mcp-asset-attributes/llms.txt), read 13 Nov 2026. - **atlan-26** (Profile, Atlan's own claim): Atlan says its MCP server exposes 41 tools in nine categories, each marked Read, Write or Admin. [Source](https://docs.atlan.com/llms/platform/atlan-mcp-overview/mcp-tools/llms.txt), read 13 Nov 2026. - **atlan-27** (Profile, Atlan's own claim): Atlan MCP ranks search results by semantic relevance, trust signals and usage; the page describes ranking, not exclusion of uncertified assets. [Source](https://docs.atlan.com/llms/platform/atlan-mcp-overview/mcp-search-quality/llms.txt), read 13 Nov 2026. - **atlan-28** (Controls what an agent is told, Atlan's own claim): Atlan says MCP forwards the caller's identity so the same persona, role and domain policies as the UI apply to every tool call. [Source](https://docs.atlan.com/product/capabilities/atlan-ai/references/mcp-security), read 13 Nov 2026. - **atlan-29** (Controls what an agent is told, Atlan's own claim): With OAuth, each MCP tool call runs with the signed-in user's identity and Atlan permissions. [Source](https://docs.atlan.com/product/capabilities/atlan-ai/references/mcp-security), read 13 Nov 2026. - **atlan-30** (Controls what an agent is told, Atlan's own claim): A service-account MCP token must carry exactly one persona, which becomes the scope for that agent. [Source](https://docs.atlan.com/product/capabilities/atlan-ai/references/mcp-security), read 13 Nov 2026. - **atlan-31** (Shows who actually saw it, Atlan's own claim): Atlan says every MCP tool call is logged with tool, client, model, tenant and duration, and access denials are logged with reasons. [Source](https://docs.atlan.com/product/capabilities/atlan-ai/references/mcp-security), read 13 Nov 2026. - **atlan-32** (Shows who actually saw it, Atlan's own claim): Atlan says it helps show what governed context an agent used and whether the agent was allowed to access it through MCP, and pairs with an LLM observability tool. [Source](https://docs.atlan.com/llms/platform/agents/monitor-your-ai-agents-with-atlan/llms.txt), read 13 Nov 2026. - **atlan-33** (Follows sensitive data into BI, Atlan's own claim): Atlan says it captures column-level lineage automatically across warehouses, pipelines and BI tools. [Source](https://docs.atlan.com/product/capabilities/lineage/concepts/what-is-column-level-lineage), read 13 Nov 2026. - **atlan-34** (Follows sensitive data into BI, Atlan's own claim): For Tableau, Atlan documents column-level lineage from datasource to worksheet and worksheet to dashboard. [Source](https://docs.atlan.com/llms/connectors/tableau/what-does-atlan-crawl-from-tableau/llms.txt), read 13 Nov 2026. - **atlan-35** (Follows sensitive data into BI, Atlan's own claim): Tableau lineage is not supported for flows, metrics and embedded dashboards. [Source](https://docs.atlan.com/llms/connectors/tableau/what-does-atlan-crawl-from-tableau/llms.txt), read 13 Nov 2026. - **atlan-36** (Follows sensitive data into BI, Atlan's own claim): For Looker, Atlan documents field-level lineage for views, explores, looks, tiles and dashboards. [Source](https://docs.atlan.com/llms/connectors/looker/what-does-atlan-crawl-from-looker/llms.txt), read 13 Nov 2026. - **atlan-37** (Follows sensitive data into BI, Atlan's own claim): For Power BI, Atlan documents measure lineage down to a page and dataflow lineage from only some SQL sources. [Source](https://docs.atlan.com/llms/connectors/microsoft-power-bi/what-does-atlan-crawl-from-microsoft-power-bi/llms.txt), read 13 Nov 2026. - **atlan-38** (Carries classification downstream, Atlan's own claim): The Metadata Propagator can be restricted by asset type to keep metadata out of report-level assets, which implies it can reach them when not restricted. [Source](https://docs.atlan.com/product/capabilities/lineage/how-tos/propagate-metadata-through-lineage), read 13 Nov 2026. - **atlan-39** (Profile, Atlan's own claim): Atlan added a Cube semantic-layer connector that brings cubes, measures and dimensions into the catalog with lineage. [Source](https://docs.atlan.com/data/product-change-log/llms.txt), read 13 Nov 2026. - **atlan-40** (Profile, Atlan's own claim): Atlan documents a business glossary for standardizing terms and definitions, which a person curates. [Source](https://docs.atlan.com/llms/governance/llms.txt), read 13 Nov 2026. - **atlan-41** (Price transparency, none-found): None found on 2026-11-13: a published price, plan table or pricing model, in https://atlan.com/pricing/ (the page redirects to a talk-to-sales form). Searched: https://atlan.com/pricing/, read 13 Nov 2026. - **atlan-42** (Evidence beyond the vendor, third-party): Soda's own documentation lists an Atlan integration that shows Soda check results in Atlan assets and lineage (partner page, independent of Atlan). [Source](https://docs.soda.io/integrations/atlan), read 13 Nov 2026. - **atlan-43** (Evidence beyond the vendor, observed): The public atlanhq/agent-toolkit repository's README says the local Atlan MCP server is deprecated in favor of the hosted one. [Source](https://raw.githubusercontent.com/atlanhq/agent-toolkit/main/README.md), read 13 Nov 2026. - **atlan-44** (Evidence beyond the vendor, none-found): None found on 2026-11-13: an analyst page naming Atlan (Gartner Peer Insights, Forrester, IDC, GigaOm) that could be read; Gartner Peer Insights returned an access block to automated fetch, in the Gartner Peer Insights metadata management page. Searched: https://www.gartner.com/reviews/market/metadata-management-solutions/vendor/atlan/product/atlan, read 13 Nov 2026. - **atlan-45** (Profile, Atlan's own claim): Atlan's docs index lists about 116 connector entries across BI, warehouses, ETL, quality and privacy categories. [Source](https://atlan.com/connectors/), read 13 Nov 2026. - **atlan-46** (Evidence beyond the vendor, third-party): Monte Carlo, a data observability vendor, documents an Atlan integration that surfaces Monte Carlo incidents on Atlan assets. [Source](https://docs.getmontecarlo.com/docs/atlan), read 13 Nov 2026. - **atlan-47** (Evidence beyond the vendor, third-party): Dagster, an orchestration vendor, documents an Atlan integration in its own docs that sends Dagster event metadata to Atlan. [Source](https://docs.dagster.io/integrations/libraries/atlan), read 13 Nov 2026. ## Compare Atlan - [The full index](/index/) ## Sources - https://atlan.com/about/: https://atlan.com/about/ (read 13 Nov 2026) - https://docs.atlan.com/llms.txt: https://docs.atlan.com/llms.txt (read 13 Nov 2026) - https://docs.atlan.com/llms/governance/playbooks/set-up-playbooks/llms.txt: https://docs.atlan.com/llms/governance/playbooks/set-up-playbooks/llms.txt (read 13 Nov 2026) - https://docs.atlan.com/llms/governance/tags/attach-a-tag/llms.txt: https://docs.atlan.com/llms/governance/tags/attach-a-tag/llms.txt (read 13 Nov 2026) - https://docs.atlan.com/product/capabilities/lineage/how-tos/propagate-metadata-through-lineage: https://docs.atlan.com/product/capabilities/lineage/how-tos/propagate-metadata-through-lineage (read 13 Nov 2026) - https://docs.atlan.com/llms/governance/tags/what-are-tags/llms.txt: https://docs.atlan.com/llms/governance/tags/what-are-tags/llms.txt (read 13 Nov 2026) - https://docs.atlan.com/data/product-change-log/llms.txt: https://docs.atlan.com/data/product-change-log/llms.txt (read 13 Nov 2026) - https://docs.atlan.com/llms/governance/access-control/what-are-purposes/llms.txt: https://docs.atlan.com/llms/governance/access-control/what-are-purposes/llms.txt (read 13 Nov 2026) - https://docs.atlan.com/llms/governance/access-control/data-policy/llms.txt: https://docs.atlan.com/llms/governance/access-control/data-policy/llms.txt (read 13 Nov 2026) - https://docs.atlan.com/llms/governance/data-quality/data-quality-studio/llms.txt: https://docs.atlan.com/llms/governance/data-quality/data-quality-studio/llms.txt (read 13 Nov 2026) - https://docs.atlan.com/llms/governance/data-quality/llms.txt: https://docs.atlan.com/llms/governance/data-quality/llms.txt (read 13 Nov 2026) - https://docs.atlan.com/llms/governance/data-quality/configure-alerts/llms.txt: https://docs.atlan.com/llms/governance/data-quality/configure-alerts/llms.txt (read 13 Nov 2026) - https://docs.atlan.com/llms/catalog/lineage/alert-propagation/llms.txt: https://docs.atlan.com/llms/catalog/lineage/alert-propagation/llms.txt (read 13 Nov 2026) - https://docs.atlan.com/llms/catalog/usage-and-popularity/interpret-usage-metrics/llms.txt: https://docs.atlan.com/llms/catalog/usage-and-popularity/interpret-usage-metrics/llms.txt (read 13 Nov 2026) - https://docs.atlan.com/llms/connectors/microsoft-power-bi/mine-microsoft-power-bi/llms.txt: https://docs.atlan.com/llms/connectors/microsoft-power-bi/mine-microsoft-power-bi/llms.txt (read 13 Nov 2026) - https://docs.atlan.com/llms/platform/atlan-mcp-overview/mcp-asset-attributes/llms.txt: https://docs.atlan.com/llms/platform/atlan-mcp-overview/mcp-asset-attributes/llms.txt (read 13 Nov 2026) - https://docs.atlan.com/llms/platform/atlan-mcp-overview/mcp-tools/llms.txt: https://docs.atlan.com/llms/platform/atlan-mcp-overview/mcp-tools/llms.txt (read 13 Nov 2026) - https://docs.atlan.com/llms/platform/atlan-mcp-overview/mcp-search-quality/llms.txt: https://docs.atlan.com/llms/platform/atlan-mcp-overview/mcp-search-quality/llms.txt (read 13 Nov 2026) - https://docs.atlan.com/product/capabilities/atlan-ai/references/mcp-security: https://docs.atlan.com/product/capabilities/atlan-ai/references/mcp-security (read 13 Nov 2026) - https://docs.atlan.com/llms/platform/agents/monitor-your-ai-agents-with-atlan/llms.txt: https://docs.atlan.com/llms/platform/agents/monitor-your-ai-agents-with-atlan/llms.txt (read 13 Nov 2026) - https://docs.atlan.com/product/capabilities/lineage/concepts/what-is-column-level-lineage: https://docs.atlan.com/product/capabilities/lineage/concepts/what-is-column-level-lineage (read 13 Nov 2026) - https://docs.atlan.com/llms/connectors/tableau/what-does-atlan-crawl-from-tableau/llms.txt: https://docs.atlan.com/llms/connectors/tableau/what-does-atlan-crawl-from-tableau/llms.txt (read 13 Nov 2026) - https://docs.atlan.com/llms/connectors/looker/what-does-atlan-crawl-from-looker/llms.txt: https://docs.atlan.com/llms/connectors/looker/what-does-atlan-crawl-from-looker/llms.txt (read 13 Nov 2026) - https://docs.atlan.com/llms/connectors/microsoft-power-bi/what-does-atlan-crawl-from-microsoft-power-bi/llms.txt: https://docs.atlan.com/llms/connectors/microsoft-power-bi/what-does-atlan-crawl-from-microsoft-power-bi/llms.txt (read 13 Nov 2026) - https://docs.atlan.com/llms/governance/llms.txt: https://docs.atlan.com/llms/governance/llms.txt (read 13 Nov 2026) - https://atlan.com/pricing/: https://atlan.com/pricing/ (read 13 Nov 2026) - https://docs.soda.io/integrations/atlan: https://docs.soda.io/integrations/atlan (read 13 Nov 2026) - https://raw.githubusercontent.com/atlanhq/agent-toolkit/main/README.md: https://raw.githubusercontent.com/atlanhq/agent-toolkit/main/README.md (read 13 Nov 2026) - https://www.gartner.com/reviews/market/metadata-management-solutions/vendor/atlan/product/atlan: https://www.gartner.com/reviews/market/metadata-management-solutions/vendor/atlan/product/atlan (read 13 Nov 2026) - https://atlan.com/connectors/: https://atlan.com/connectors/ (read 13 Nov 2026) - https://docs.getmontecarlo.com/docs/atlan: https://docs.getmontecarlo.com/docs/atlan (read 13 Nov 2026) - https://docs.dagster.io/integrations/libraries/atlan: https://docs.dagster.io/integrations/libraries/atlan (read 13 Nov 2026) Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/platforms/atlan/ --- # DataHub for AI data governance: rank 3 of 16, at 61.0 of 100 PLATFORM PROFILE, read 13 Nov 2026 **The short answer.** DataHub ranks 3 of 16 on the Need to Know index at 61.0 of 100, read 13 Nov 2026. Its best criterion is Evidence beyond the vendor at 9 of 10, and its weakest is Price transparency at 1. The exposure map records 1 of six stages as documented and 5 as partial. - **Category:** Open source data catalog and metadata platform with a managed Cloud edition - **Status:** Exists under this name on 13 Nov 2026 (datahub.com and docs.datahub.com live; open source DataHub by DataHub Inc, formerly Acryl Data; the company page and Series B press release say 'DataHub, by Acryl Data'; security page still says Acryl; GitHub repo pushed 13 Nov 2026). - **Exposure trail:** Warehouse column: partial; Transformation: partial; BI field: partial; Report: partial; Viewer: partial; Agent: documented - **Warehouses named:** Snowflake, BigQuery, Databricks, Redshift - **BI tools named:** Tableau, Power BI, Looker, Preset - **Security tools named:** none found on 13 Nov 2026 - **Rank and total:** 3 of 16, 61.0 of 100 1 of 6 stages documented, 5 partial ## DataHub on the eight criteria | Criterion | Weight | Score | Why | | --- | --- | --- | --- | | Follows sensitive data into BI | 25 | 8 | Column lineage from Snowflake through dbt into Looker, Power BI and Tableau is documented, and dbt Labs independently describes column lineage to downstream dashboards; Tableau needs a high role. | | Controls what an agent is told | 20 | 7 | Per-user OAuth tokens keep permissions and audit identity per user, confirmed in the public README; scoped MCP servers are per use case and need an add-on. | | Shows who actually saw it | 15 | 4 | Looker historical usage and per-user audit attribution exist, but viewer lists for Power BI or Tableau reports were none found on 2026-11-13. | | Carries classification downstream | 15 | 6 | Term and tag propagation along column lineage with a BigID connector (alpha), but datasets only, Public Beta, and the built-in PII classifier was removed. | | Acts on it | 10 | 4 | Metadata tests apply labels automatically and incidents can block pipelines, but access workflows are Private Beta and no masking is shown. | | Coverage of the stack | 5 | 6 | Generally available Snowflake, BigQuery, Databricks, dbt, Looker, Tableau and Power BI connectors; security coverage is only an alpha BigID connector. | | Evidence beyond the vendor | 5 | 9 | Airflow and dbt Labs list it, and public repository, PyPI and Docker Hub records show active, widely used code. | | Price transparency | 5 | 1 | Cloud is sold through sales with no price list found on 2026-11-13; only the free Core edition is stated. | Blind scores for DataHub, 0 to 10. A vendor claim scores at most 7 until a second source confirms it. ## Where DataHub is strongest Vendor-stated: Column-level lineage tracking, glossary term propagation to downstream lineage columns, and per-user OAuth logins for MCP. ## Where DataHub falls short The built-in PII classifier was removed from ingestion, asset-level term propagation skips dashboards and charts, and Cloud pricing is not public. ## DataHub along the exposure trail | Stage | Reading | Evidence | | --- | --- | --- | | [Warehouse column](/exposure-map/column/) | partial | DataHub docs say the built-in PII classifier was removed from ingestion; no classifier is registered by default. [Source](https://docs.datahub.com/docs/metadata-ingestion/docs/dev_guides/classification), read 13 Nov 2026. | | [Transformation](/exposure-map/transformation/) | partial | DataHub docs say column-level lineage tracks each specific column, shown inside table-level lineage. [Source](https://docs.datahub.com/docs/features/feature-guides/lineage), read 13 Nov 2026. | | [BI field](/exposure-map/bi-field/) | partial | The Looker source docs list column-level lineage as enabled by default. [Source](https://docs.datahub.com/docs/generated/ingestion/sources/looker), read 13 Nov 2026. | | [Report](/exposure-map/report/) | partial | DataHub docs limit asset-level glossary term propagation to datasets; charts, dashboards, pipelines and tasks are excluded. [Source](https://docs.datahub.com/docs/automations/glossary-term-propagation), read 13 Nov 2026. | | [Viewer](/exposure-map/viewer/) | partial | The Looker source docs say it can pull historical dashboard usage from Looker system activity. [Source](https://docs.datahub.com/docs/generated/ingestion/sources/looker), read 13 Nov 2026. | | [Agent](/exposure-map/agent/) | documented | DataHub docs say Cloud admins can create scoped MCP servers with their own URL, hidden tools, custom instructions and a saved View; this needs the Context add-on. [Source](https://docs.datahub.com/docs/features/feature-guides/scoped-mcp-servers), read 13 Nov 2026. | Documented, partial or none found on the read date. Vendor claims are the vendor's. ## DataHub in each situation | Situation | Rank | Total | Leader | | --- | --- | --- | --- | | [A regulated field](/best-for/regulated-field/) | 3 | 63.0 | Atlan 68.5 | | [Agents on analytics](/best-for/agents-on-analytics/) | 3 | 59.5 | Euno 66.0 | | [A Microsoft estate](/best-for/microsoft-estate/) | 3 | 61.0 | Atlan 68.5 | | [A mixed stack](/best-for/mixed-stack/) | 3 | 61.5 | Euno 68.5 | | [A lean team](/best-for/lean-team/) | 5 | 53.0 | Euno 62.5 | Each situation ranks the same scores under its own published weights. ## The evidence on DataHub, fact by fact - **datahub-01** (Profile, DataHub's own claim): DataHub docs say Metadata Tests apply their actions (tags, terms, owners, domains) continuously as the set of matching assets changes, with no person marking each asset. [Source](https://docs.datahub.com/docs/tests/metadata-tests), read 13 Nov 2026. - **datahub-02** (Profile, DataHub's own claim): DataHub docs say a Metadata Test action can add or remove classification labels as assets move in and out of compliance with a rule. [Source](https://docs.datahub.com/docs/tests/metadata-tests), read 13 Nov 2026. - **datahub-03** (Profile, DataHub's own claim): DataHub docs say Glossary Term Propagation copies classification labels to downstream columns and assets along lineage and siblings. [Source](https://docs.datahub.com/docs/automations/glossary-term-propagation), read 13 Nov 2026. - **datahub-04** (Profile, DataHub's own claim): The glossary term propagation page labels the feature as Public Beta in DataHub Cloud, available through a Cloud representative. [Source](https://docs.datahub.com/docs/automations/glossary-term-propagation), read 13 Nov 2026. - **datahub-05** (Carries classification downstream, DataHub's own claim): DataHub docs limit asset-level glossary term propagation to datasets; charts, dashboards, pipelines and tasks are excluded. [Source](https://docs.datahub.com/docs/automations/glossary-term-propagation), read 13 Nov 2026. - **datahub-06** (Carries classification downstream, DataHub's own claim): DataHub docs say column-level term propagation covers all downstream lineage columns and sibling columns, and a chosen subset of terms (for example only sensitive ones) can be selected. [Source](https://docs.datahub.com/docs/automations/glossary-term-propagation), read 13 Nov 2026. - **datahub-07** (Carries classification downstream, DataHub's own claim): DataHub docs describe a Cloud-only automation that syncs DataHub terms, tags and descriptions back to Snowflake tables and columns (Public Beta). [Source](https://docs.datahub.com/docs/automations/snowflake-metadata-sync), read 13 Nov 2026. - **datahub-08** (Carries classification downstream, DataHub's own claim): The DataHub Actions framework includes a Tag Sync (Tag Propagation) action that propagates tags from an asset to downstream datasets, filtered by tag prefix, but only to datasets and not to dashboards or charts. [Source](https://docs.datahub.com/docs/datahub-actions/src/datahub_actions/plugin/action/tag), read 13 Nov 2026. - **datahub-09** (Profile, DataHub's own claim): DataHub docs say documentation propagation sends column descriptions to downstream and sibling columns by column-level lineage; it is on by default in open source and Public Beta in Cloud. [Source](https://docs.datahub.com/docs/automations/docs-propagation), read 13 Nov 2026. - **datahub-10** (Profile, DataHub's own claim): DataHub docs say Metadata Test conditions can read technical signals such as usage and size that DataHub extracts, varying by integration. [Source](https://docs.datahub.com/docs/tests/metadata-tests), read 13 Nov 2026. - **datahub-11** (Profile, DataHub's own claim): DataHub docs give example Metadata Test rules that require an owner, a description or a classification term on heavily queried assets. [Source](https://docs.datahub.com/docs/tests/metadata-tests), read 13 Nov 2026. - **datahub-12** (Profile, DataHub's own claim): DataHub docs say Metadata Tests are re-evaluated when an asset changes and at least once every day. [Source](https://docs.datahub.com/docs/tests/metadata-tests), read 13 Nov 2026. - **datahub-13** (Profile, DataHub's own claim): DataHub Cloud assertions can run a SQL check on a schedule against Snowflake, Redshift, BigQuery and Databricks, or evaluate ingested metadata (freshness, volume, schema). [Source](https://docs.datahub.com/docs/managed-datahub/observe/assertions), read 13 Nov 2026. - **datahub-14** (Profile, DataHub's own claim): DataHub docs say Custom SQL and Column Value assertions need a live warehouse connection, so they do not work from ingested metadata alone. [Source](https://docs.datahub.com/docs/managed-datahub/observe/assertions), read 13 Nov 2026. - **datahub-15** (Acts on it, DataHub's own claim): DataHub docs say incidents can be used to block data pipelines whose inputs have active issues. [Source](https://docs.datahub.com/docs/incidents/incidents), read 13 Nov 2026. - **datahub-16** (Profile, DataHub's own claim): DataHub docs say its MCP Server gives AI agents direct access to DataHub metadata. [Source](https://docs.datahub.com/docs/features/feature-guides/mcp), read 13 Nov 2026. - **datahub-17** (Profile, DataHub's own claim): DataHub docs say the MCP server returns usage stats, ownership, documentation, tags, glossary terms and quality signals for an asset. [Source](https://docs.datahub.com/docs/features/feature-guides/mcp), read 13 Nov 2026. - **datahub-18** (Controls what an agent is told, DataHub's own claim): DataHub docs say DataHub Cloud MCP uses OAuth2 so each user connects with a personal login, with tokens scoped to that user. [Source](https://docs.datahub.com/docs/features/feature-guides/mcp), read 13 Nov 2026. - **datahub-19** (Controls what an agent is told, DataHub's own claim): DataHub docs say a shared self-hosted MCP deployment keeps permissions, search results and audit attribution per user. [Source](https://docs.datahub.com/docs/features/feature-guides/mcp), read 13 Nov 2026. - **datahub-20** (Controls what an agent is told, DataHub's own claim): DataHub docs say Cloud admins can create scoped MCP servers with their own URL, hidden tools, custom instructions and a saved View; this needs the Context add-on. [Source](https://docs.datahub.com/docs/features/feature-guides/scoped-mcp-servers), read 13 Nov 2026. - **datahub-21** (Acts on it, DataHub's own claim): DataHub docs say MCP mutation tools (add tags and terms, owners, description) are off unless TOOLS_IS_MUTATION_ENABLED is set. [Source](https://docs.datahub.com/docs/features/feature-guides/mcp), read 13 Nov 2026. - **datahub-22** (Controls what an agent is told, observed): The public mcp-server-datahub README says the HTTP server has no server-wide token and each client sends its own DataHub token so permissions and audit identity stay per user. [Source](https://raw.githubusercontent.com/acryldata/mcp-server-datahub/main/README.md), read 13 Nov 2026. - **datahub-23** (Coverage of the stack, DataHub's own claim): DataHub says its integrations page covers 150+ data and AI systems, including 23 BI tools. [Source](https://docs.datahub.com/integrations), read 13 Nov 2026. - **datahub-24** (Follows sensitive data into BI, DataHub's own claim): DataHub docs show data flowing from Snowflake tables through dbt into Looker views and explores in its lineage view. [Source](https://docs.datahub.com/docs/features/feature-guides/lineage), read 13 Nov 2026. - **datahub-25** (Follows sensitive data into BI, DataHub's own claim): DataHub docs say column-level lineage tracks each specific column, shown inside table-level lineage. [Source](https://docs.datahub.com/docs/features/feature-guides/lineage), read 13 Nov 2026. - **datahub-26** (Follows sensitive data into BI, DataHub's own claim): The Looker source docs list column-level lineage as enabled by default. [Source](https://docs.datahub.com/docs/generated/ingestion/sources/looker), read 13 Nov 2026. - **datahub-27** (Follows sensitive data into BI, DataHub's own claim): The Power BI source docs list column-level lineage as enabled by default. [Source](https://docs.datahub.com/docs/generated/ingestion/sources/powerbi), read 13 Nov 2026. - **datahub-28** (Follows sensitive data into BI, DataHub's own claim): The Tableau source docs say a site role below Site Administrator Explorer limits data source field metadata and so column-level lineage. [Source](https://docs.datahub.com/docs/generated/ingestion/sources/tableau), read 13 Nov 2026. - **datahub-29** (Shows who actually saw it, DataHub's own claim): The Looker source docs say it can pull historical dashboard usage from Looker system activity. [Source](https://docs.datahub.com/docs/generated/ingestion/sources/looker), read 13 Nov 2026. - **datahub-30** (Shows who actually saw it, none-found): None found on 2026-11-13: per-agent viewer or per-report viewer lists for Power BI or Tableau, in the DataHub docs for BI sources and usage. Searched: https://docs.datahub.com/docs/features/dataset-usage-and-query-history, read 13 Nov 2026. - **datahub-31** (Carries classification downstream, DataHub's own claim): DataHub docs say the built-in PII classifier was removed from ingestion; no classifier is registered by default. [Source](https://docs.datahub.com/docs/metadata-ingestion/docs/dev_guides/classification), read 13 Nov 2026. - **datahub-32** (Profile, DataHub's own claim): DataHub says on its governance page that AI-powered PII classification is part of DataHub Cloud workflows. [Source](https://datahub.com/products/data-governance/), read 13 Nov 2026. - **datahub-33** (Profile, DataHub's own claim): DataHub lists GA connectors for Snowflake, BigQuery, Databricks, dbt, Looker, Tableau and Power BI on its integrations page. [Source](https://docs.datahub.com/integrations), read 13 Nov 2026. - **datahub-34** (Carries classification downstream, DataHub's own claim): DataHub lists a BigID connector (labeled Alpha) that enriches DataHub datasets with BigID classification: glossary terms, tags and risk scores. [Source](https://docs.datahub.com/integrations), read 13 Nov 2026. - **datahub-35** (Profile, DataHub's own claim): DataHub says its governance workflows track certification status in real time and flag non-compliant assets. [Source](https://datahub.com/products/data-governance/), read 13 Nov 2026. - **datahub-36** (Acts on it, DataHub's own claim): DataHub docs list Access Workflows (approval routing for data access requests) as Private Beta. [Source](https://docs.datahub.com/docs/managed-datahub/workflows/access-workflows), read 13 Nov 2026. - **datahub-37** (Price transparency, DataHub's own claim): DataHub says DataHub Cloud pricing is scoped to use case and sold through sales; Core is free. [Source](https://datahub.com/products/cloud-vs-core/), read 13 Nov 2026. - **datahub-38** (Price transparency, none-found): None found on 2026-11-13: a public price list or pricing page for DataHub Cloud, at datahub.com/pricing (returns Page Not Found) and in the Core vs Cloud page. Searched: https://datahub.com/pricing, read 13 Nov 2026. - **datahub-39** (Evidence beyond the vendor, observed): The public datahub-project/datahub repository is Apache-2.0 licensed with about 12,981 stars, last pushed 2026-11-13, latest tag v1.9.0rc5 (GitHub API). [Source](https://api.github.com/repos/datahub-project/datahub), read 13 Nov 2026. - **datahub-40** (Evidence beyond the vendor, observed): The acryldata/mcp-server-datahub repository is Apache-2.0, last pushed 2026-11-09, latest release v0.8.0 on 2026-10-21 (GitHub API). [Source](https://api.github.com/repos/acryldata/mcp-server-datahub), read 13 Nov 2026. - **datahub-41** (Evidence beyond the vendor, observed): PyPI lists acryl-datahub version 1.7.0.20 uploaded 2026-11-12, source linked to datahub-project/datahub. [Source](https://pypi.org/pypi/acryl-datahub/json), read 13 Nov 2026. - **datahub-42** (Profile, DataHub's own claim): DataHub announced a $35 million Series B led by Bessemer Venture Partners on May 21, 2025, as "DataHub, by Acryl Data". [Source](https://datahub.com/news/series-b-announcement/), read 13 Nov 2026. - **datahub-43** (Profile, DataHub's own claim): DataHub says it has 3000+ organizations, 3M+ monthly PyPI downloads and 16,000+ community members, and is headquartered in Palo Alto. [Source](https://datahub.com/company/), read 13 Nov 2026. - **datahub-44** (Profile, DataHub's own claim): DataHub says Metrics & Semantic Models, in Beta, is a catalog of metric definitions with owner, description and calculation, and with synonyms and instructions meant for agents. [Source](https://docs.datahub.com/docs/features/feature-guides/metrics-and-semantic-models), read 13 Nov 2026. - **datahub-45** (Profile, DataHub's own claim): DataHub docs say the MCP server includes a tool to set lifecycle stage (proposed, approved, deprecated) on assets and terms, which a person or agent applies. [Source](https://docs.datahub.com/docs/features/feature-guides/mcp), read 13 Nov 2026. - **datahub-46** (Evidence beyond the vendor, third-party): Apache Airflow lists DataHub on its ecosystem page as a metadata platform that can collect lineage and other metadata from Airflow. [Source](https://airflow.apache.org/ecosystem/), read 13 Nov 2026. - **datahub-47** (Evidence beyond the vendor, third-party): dbt Labs lists "Acryl Data" (DataHub Cloud's former company name) on its integrations page for viewing dbt models, docs, test results and column-level lineage. [Source](https://www.getdbt.com/product/integrations), read 13 Nov 2026. - **datahub-48** (Evidence beyond the vendor, observed): Docker Hub shows the acryldata/datahub-gms image as active with more than 5.9 million pulls and an update on the read date. [Source](https://hub.docker.com/v2/repositories/acryldata/datahub-gms), read 13 Nov 2026. - **datahub-49** (Evidence beyond the vendor, observed): Artifact Hub lists a public DataHub Helm chart under the Data processing category. [Source](https://artifacthub.io/api/v1/packages/helm/datahub/datahub), read 13 Nov 2026. ## Compare DataHub - [The full index](/index/) ## Sources - https://docs.datahub.com/docs/tests/metadata-tests: https://docs.datahub.com/docs/tests/metadata-tests (read 13 Nov 2026) - https://docs.datahub.com/docs/automations/glossary-term-propagation: https://docs.datahub.com/docs/automations/glossary-term-propagation (read 13 Nov 2026) - https://docs.datahub.com/docs/automations/snowflake-metadata-sync: https://docs.datahub.com/docs/automations/snowflake-metadata-sync (read 13 Nov 2026) - https://docs.datahub.com/docs/datahub-actions/src/datahub_actions/plugin/action/tag: https://docs.datahub.com/docs/datahub-actions/src/datahub_actions/plugin/action/tag (read 13 Nov 2026) - https://docs.datahub.com/docs/automations/docs-propagation: https://docs.datahub.com/docs/automations/docs-propagation (read 13 Nov 2026) - https://docs.datahub.com/docs/managed-datahub/observe/assertions: https://docs.datahub.com/docs/managed-datahub/observe/assertions (read 13 Nov 2026) - https://docs.datahub.com/docs/incidents/incidents: https://docs.datahub.com/docs/incidents/incidents (read 13 Nov 2026) - https://docs.datahub.com/docs/features/feature-guides/mcp: https://docs.datahub.com/docs/features/feature-guides/mcp (read 13 Nov 2026) - https://docs.datahub.com/docs/features/feature-guides/scoped-mcp-servers: https://docs.datahub.com/docs/features/feature-guides/scoped-mcp-servers (read 13 Nov 2026) - https://raw.githubusercontent.com/acryldata/mcp-server-datahub/main/README.md: https://raw.githubusercontent.com/acryldata/mcp-server-datahub/main/README.md (read 13 Nov 2026) - https://docs.datahub.com/integrations: https://docs.datahub.com/integrations (read 13 Nov 2026) - https://docs.datahub.com/docs/features/feature-guides/lineage: https://docs.datahub.com/docs/features/feature-guides/lineage (read 13 Nov 2026) - https://docs.datahub.com/docs/generated/ingestion/sources/looker: https://docs.datahub.com/docs/generated/ingestion/sources/looker (read 13 Nov 2026) - https://docs.datahub.com/docs/generated/ingestion/sources/powerbi: https://docs.datahub.com/docs/generated/ingestion/sources/powerbi (read 13 Nov 2026) - https://docs.datahub.com/docs/generated/ingestion/sources/tableau: https://docs.datahub.com/docs/generated/ingestion/sources/tableau (read 13 Nov 2026) - https://docs.datahub.com/docs/features/dataset-usage-and-query-history: https://docs.datahub.com/docs/features/dataset-usage-and-query-history (read 13 Nov 2026) - https://docs.datahub.com/docs/metadata-ingestion/docs/dev_guides/classification: https://docs.datahub.com/docs/metadata-ingestion/docs/dev_guides/classification (read 13 Nov 2026) - https://datahub.com/products/data-governance/: https://datahub.com/products/data-governance/ (read 13 Nov 2026) - https://docs.datahub.com/docs/managed-datahub/workflows/access-workflows: https://docs.datahub.com/docs/managed-datahub/workflows/access-workflows (read 13 Nov 2026) - https://datahub.com/products/cloud-vs-core/: https://datahub.com/products/cloud-vs-core/ (read 13 Nov 2026) - https://datahub.com/pricing: https://datahub.com/pricing (read 13 Nov 2026) - https://api.github.com/repos/datahub-project/datahub: https://api.github.com/repos/datahub-project/datahub (read 13 Nov 2026) - https://api.github.com/repos/acryldata/mcp-server-datahub: https://api.github.com/repos/acryldata/mcp-server-datahub (read 13 Nov 2026) - https://pypi.org/pypi/acryl-datahub/json: https://pypi.org/pypi/acryl-datahub/json (read 13 Nov 2026) - https://datahub.com/news/series-b-announcement/: https://datahub.com/news/series-b-announcement/ (read 13 Nov 2026) - https://datahub.com/company/: https://datahub.com/company/ (read 13 Nov 2026) - https://docs.datahub.com/docs/features/feature-guides/metrics-and-semantic-models: https://docs.datahub.com/docs/features/feature-guides/metrics-and-semantic-models (read 13 Nov 2026) - https://airflow.apache.org/ecosystem/: https://airflow.apache.org/ecosystem/ (read 13 Nov 2026) - https://www.getdbt.com/product/integrations: https://www.getdbt.com/product/integrations (read 13 Nov 2026) - https://hub.docker.com/v2/repositories/acryldata/datahub-gms: https://hub.docker.com/v2/repositories/acryldata/datahub-gms (read 13 Nov 2026) - https://artifacthub.io/api/v1/packages/helm/datahub/datahub: https://artifacthub.io/api/v1/packages/helm/datahub/datahub (read 13 Nov 2026) Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/platforms/datahub/ --- # Snowflake Horizon for AI data governance: rank 4 of 16, at 55.5 of 100 PLATFORM PROFILE, read 13 Nov 2026 **The short answer.** Snowflake Horizon ranks 4 of 16 on the Need to Know index at 55.5 of 100, read 13 Nov 2026. Its best criterion is Evidence beyond the vendor at 9 of 10, and its weakest is Shows who actually saw it at 4. The exposure map records 2 of six stages as documented and 4 as partial. - **Category:** Data platform's built-in catalog, governance and context layer - **Status:** Exists under this name on 13 Nov 2026 (docs.snowflake.com has a Snowflake Horizon Catalog page and Horizon Context page, and the snowflake.com Horizon Catalog page loads via a web.archive.org copy; Select Star's home page says it is now a part of Snowflake, and Snowflake docs read do not describe how Select Star relates to Horizon). - **Exposure trail:** Warehouse column: documented; Transformation: partial; BI field: partial; Report: partial; Viewer: partial; Agent: documented - **Warehouses named:** Snowflake, Amazon Redshift, BigQuery, Databricks, IBM Db2, MySQL, Oracle, PostgreSQL, SQL Server - **BI tools named:** Amazon QuickSight, Hex, Looker, Metabase, Microsoft Power BI, Omni, Sigma, Tableau Cloud, Tableau Server, ThoughtSpot - **Security tools named:** none found on 13 Nov 2026 - **Rank and total:** 4 of 16, 55.5 of 100 2 of 6 stages documented, 4 partial ## Snowflake Horizon on the eight criteria | Criterion | Weight | Score | Why | | --- | --- | --- | --- | | Follows sensitive data into BI | 25 | 5 | Column-level lineage for Tableau, Power BI and OpenLineage dbt feeds, but connectors are marked Preview and tags are not carried onto BI fields. | | Controls what an agent is told | 20 | 6 | Agent queries enforce role, masking and row-access policies in the engine, with tool-level grants; metadata access is managed separately. | | Shows who actually saw it | 15 | 4 | ACCESS_HISTORY records object and column access by user; BI connectors show popularity, not named viewers per report or agent. | | Carries classification downstream | 15 | 5 | Tags propagate along dependencies and lineage with removal, within the platform; external classifier import was none found. | | Acts on it | 10 | 7 | Dynamic masking, row access and tag-based masking policies are documented as enforced at query time (some Enterprise Edition). | | Coverage of the stack | 5 | 5 | Nine BI tools, dbt and several databases are named; no security tool integrations are listed. | | Evidence beyond the vendor | 5 | 9 | dbt Labs, Microsoft Learn and Tableau documentation plus a public repository independently confirm it. | | Price transparency | 5 | 7 | Dollar credit prices are published per edition and region, with feature multipliers; prices show only after region selection. | Blind scores for Snowflake Horizon, 0 to 10. A vendor claim scores at most 7 until a second source confirms it. ## Where Snowflake Horizon is strongest Vendor-stated: Masking, row access and tag-based masking are enforced at query time for people and agents alike, with ACCESS_HISTORY recording who touched which column. ## Where Snowflake Horizon falls short Tag propagation is documented within Snowflake objects, BI lineage comes from connectors marked Preview on one page, and only popularity, not named viewers, is documented for BI reports. ## Snowflake Horizon along the exposure trail | Stage | Reading | Evidence | | --- | --- | --- | | [Warehouse column](/exposure-map/column/) | documented | Snowflake says its classification feature automatically discovers sensitive data and makes it easy to apply tags and masking policies. [Source](https://docs.snowflake.com/en/user-guide/classify-intro.md), read 13 Nov 2026. | | [Transformation](/exposure-map/transformation/) | partial | Snowflake documents automatic tag propagation: a tag set on a source object is assigned to target objects such as views and tables created from it (Enterprise Edition or higher). [Source](https://docs.snowflake.com/en/user-guide/object-tagging/propagation.md), read 13 Nov 2026. | | [BI field](/exposure-map/bi-field/) | partial | The Tableau connector reads workbooks, data sources, fields and lineage through Tableau's REST and Metadata APIs. [Source](https://docs.snowflake.com/en/user-guide/snowflake-horizon/connectors/tableau), read 13 Nov 2026. | | [Report](/exposure-map/report/) | partial | The Tableau connector reads workbooks, data sources, fields and lineage through Tableau's REST and Metadata APIs. [Source](https://docs.snowflake.com/en/user-guide/snowflake-horizon/connectors/tableau), read 13 Nov 2026. | | [Viewer](/exposure-map/viewer/) | partial | Snowflake documents ACCESS_HISTORY, a view of object and column access by user, kept for 365 days (Enterprise Edition). [Source](https://docs.snowflake.com/en/sql-reference/account-usage/access_history.md), read 13 Nov 2026. | | [Agent](/exposure-map/agent/) | documented | Snowflake says that when an AI agent queries data, the role's access control, masking and row-access policies are enforced in the query engine, and metadata access is managed separately. [Source](https://docs.snowflake.com/en/user-guide/snowflake-horizon/horizon-context.md), read 13 Nov 2026. | Documented, partial or none found on the read date. Vendor claims are the vendor's. ## Snowflake Horizon in each situation | Situation | Rank | Total | Leader | | --- | --- | --- | --- | | [A regulated field](/best-for/regulated-field/) | 6 | 52.5 | Atlan 68.5 | | [Agents on analytics](/best-for/agents-on-analytics/) | 6 | 55.5 | Euno 66.0 | | [A Microsoft estate](/best-for/microsoft-estate/) | 5 | 52.5 | Atlan 68.5 | | [A mixed stack](/best-for/mixed-stack/) | 6 | 52.0 | Euno 68.5 | | [A lean team](/best-for/lean-team/) | 3 | 59.0 | Euno 62.5 | Each situation ranks the same scores under its own published weights. ## The evidence on Snowflake Horizon, fact by fact - **snowflake-01** (Profile, Snowflake Horizon's own claim): Snowflake says Horizon Catalog is its catalog for data inside and outside Snowflake; the docs describe it as the home of governance, lineage, quality, classification and AI guardrails. [Source](https://docs.snowflake.com/en/user-guide/snowflake-horizon.md), read 13 Nov 2026. - **snowflake-02** (Profile, Snowflake Horizon's own claim): Select Star, the data catalog company Snowflake acquired, states on its own home page that it is now part of Snowflake; the Horizon Catalog documentation pages read here do not mention Select Star or say how its product relates to Horizon. [Source](https://www.selectstar.com/), read 13 Nov 2026. - **snowflake-03** (Profile, none-found): None found on 2026-11-13: Select Star, or how it relates to Horizon Catalog, on the Horizon Catalog and Horizon Context documentation pages, in docs.snowflake.com (snowflake-horizon and horizon-context pages). Searched: https://docs.snowflake.com/en/user-guide/snowflake-horizon.md, read 13 Nov 2026. - **snowflake-04** (Coverage of the stack, Snowflake Horizon's own claim): Snowflake documents Horizon Catalog connectors for nine BI tools (QuickSight, Hex, Looker, Metabase, Power BI, Omni, Sigma, Tableau, ThoughtSpot), eight databases and dbt, collecting metadata, lineage and popularity. [Source](https://docs.snowflake.com/en/user-guide/snowflake-horizon/connectors.md), read 13 Nov 2026. - **snowflake-05** (Profile, Snowflake Horizon's own claim): Snowflake lists regulatory certifications on its compliance page, including SOC 2 Type II, ISO-27001, HITRUST CSF, PCI DSS and FedRAMP. [Source](https://docs.snowflake.com/en/user-guide/intro-compliance.md), read 13 Nov 2026. - **snowflake-06** (Profile, Snowflake Horizon's own claim): Snowflake release notes dated Nov 4, 2026 list new background runs and supplementary tools for agents in the Snowflake-managed MCP server. [Source](https://docs.snowflake.com/en/release-notes/new-features), read 13 Nov 2026. - **snowflake-07** (Profile, Snowflake Horizon's own claim): Snowflake says its classification feature automatically discovers sensitive data and makes it easy to apply tags and masking policies. [Source](https://docs.snowflake.com/en/user-guide/classify-intro.md), read 13 Nov 2026. - **snowflake-08** (Profile, Snowflake Horizon's own claim): Snowflake documents automatic tag propagation: a tag set on a source object is assigned to target objects such as views and tables created from it (Enterprise Edition or higher). [Source](https://docs.snowflake.com/en/user-guide/object-tagging/propagation.md), read 13 Nov 2026. - **snowflake-09** (Profile, Snowflake Horizon's own claim): Snowflake documents that a masking policy attached to a tag is applied automatically to columns when classification applies that tag. [Source](https://docs.snowflake.com/en/user-guide/classify-intro.md), read 13 Nov 2026. - **snowflake-10** (Profile, Snowflake Horizon's own claim): In the Horizon Context example, a data steward applies the CERTIFICATION_STATUS tag by hand; the page describes a person setting CERTIFIED or DEPRECATED, not a rule. [Source](https://docs.snowflake.com/en/user-guide/snowflake-horizon/horizon-context.md), read 13 Nov 2026. - **snowflake-11** (Profile, none-found): None found on 2026-11-13: a rule or policy that sets or withdraws CERTIFICATION_STATUS (certified/deprecated) automatically from quality, usage or lineage signals, in the Horizon Context, Snowflake-provided tags and data quality documentation pages. Searched: https://docs.snowflake.com/en/user-guide/snowflake-horizon/horizon-context.md, read 13 Nov 2026. - **snowflake-12** (Profile, Snowflake Horizon's own claim): Snowflake says Horizon Context collects metadata, enriches it with business meaning and serves it to people, BI tools and AI agents; it names structural, operational (freshness, quality), semantic and behavioral (popularity) layers. [Source](https://docs.snowflake.com/en/user-guide/snowflake-horizon/horizon-context.md), read 13 Nov 2026. - **snowflake-13** (Profile, Snowflake Horizon's own claim): Snowflake documents data metric functions (DMFs) that measure attributes such as NULL counts and update frequency; DMFs and expectations make up data quality checks (Enterprise Edition). [Source](https://docs.snowflake.com/en/user-guide/data-quality-intro.md), read 13 Nov 2026. - **snowflake-14** (Profile, Snowflake Horizon's own claim): Snowflake documents semantic views as schema-level objects holding business metrics, entities and relationships, usable by Cortex Agents. [Source](https://docs.snowflake.com/en/user-guide/views-semantic/overview.md), read 13 Nov 2026. - **snowflake-15** (Profile, Snowflake Horizon's own claim): Snowflake documents that data quality checks run on a schedule, by default once an hour. [Source](https://docs.snowflake.com/en/user-guide/data-quality-intro.md), read 13 Nov 2026. - **snowflake-16** (Profile, Snowflake Horizon's own claim): Snowflake documents that its classification Autopilot reclassifies objects on a 30 day cadence. [Source](https://docs.snowflake.com/en/user-guide/classify-intro.md), read 13 Nov 2026. - **snowflake-17** (Profile, Snowflake Horizon's own claim): For object-dependency propagation Snowflake documents that a tag removed from the source is removed from the target, so the label is withdrawn when the source changes. [Source](https://docs.snowflake.com/en/user-guide/object-tagging/propagation.md), read 13 Nov 2026. - **snowflake-18** (Profile, Snowflake Horizon's own claim): Snowflake documents a limit: tags applied through data movement (CTAS, INSERT, MERGE, COPY INTO) are not continuously updated afterward. [Source](https://docs.snowflake.com/en/user-guide/object-tagging/propagation.md), read 13 Nov 2026. - **snowflake-19** (Profile, Snowflake Horizon's own claim): Snowflake says its managed MCP server lets AI agents retrieve data from Snowflake accounts and can serve Cortex Analyst, Cortex Search and Cortex Agents as tools. [Source](https://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-agents-mcp.md), read 13 Nov 2026. - **snowflake-20** (Profile, Snowflake Horizon's own claim): Snowflake says agents that retrieve context from the catalog get the certification tag as a machine-readable trust signal. [Source](https://docs.snowflake.com/en/user-guide/snowflake-horizon/horizon-context.md), read 13 Nov 2026. - **snowflake-21** (Profile, none-found): None found on 2026-11-13: a documented MCP tool or filter that returns certification, quality or sensitivity labels to an agent as a readiness check (as opposed to querying data or running Cortex services), in the Snowflake-managed MCP server documentation. Searched: https://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-agents-mcp.md, read 13 Nov 2026. - **snowflake-22** (Profile, none-found): None found on 2026-11-13: CERTIFICATION_STATUS or sensitivity tags carried onto dbt models or BI dashboards and fields (tags are documented on Snowflake objects), in the Horizon Context, object tagging and BI connector documentation. Searched: https://docs.snowflake.com/en/user-guide/snowflake-horizon/horizon-context.md, read 13 Nov 2026. - **snowflake-23** (Follows sensitive data into BI, Snowflake Horizon's own claim): Snowflake says it stitches lineage from Snowflake query history, external query logs, BI systems and OpenLineage feeds into one column-level graph. [Source](https://docs.snowflake.com/en/user-guide/snowflake-horizon/horizon-context.md), read 13 Nov 2026. - **snowflake-24** (Follows sensitive data into BI, Snowflake Horizon's own claim): The Tableau connector reads workbooks, data sources, fields and lineage through Tableau's REST and Metadata APIs. [Source](https://docs.snowflake.com/en/user-guide/snowflake-horizon/connectors/tableau), read 13 Nov 2026. - **snowflake-25** (Follows sensitive data into BI, Snowflake Horizon's own claim): The Power BI connector setup says report metadata is ingested to generate column-level lineage. [Source](https://docs.snowflake.com/en/user-guide/snowflake-horizon/connectors/powerbi), read 13 Nov 2026. - **snowflake-26** (Follows sensitive data into BI, Snowflake Horizon's own claim): The Horizon Context page marks the metadata connectors (PostgreSQL, SQL Server, Tableau, Power BI, dbt) as Preview, while the connectors page says Available to all accounts. [Source](https://docs.snowflake.com/en/user-guide/snowflake-horizon/horizon-context.md), read 13 Nov 2026. - **snowflake-27** (Carries classification downstream, Snowflake Horizon's own claim): Snowflake's lineage view flags upstream and downstream columns missing a tag or holding a different tag value and helps a person apply or fix them. [Source](https://docs.snowflake.com/en/user-guide/ui-snowsight-lineage.md), read 13 Nov 2026. - **snowflake-28** (Carries classification downstream, none-found): None found on 2026-11-13: importing sensitivity labels from an external classifier or security tool (for example BigID, Immuta) and propagating them along lineage, in the sensitive data classification and tag propagation documentation. Searched: https://docs.snowflake.com/en/user-guide/classify-intro.md, read 13 Nov 2026. - **snowflake-29** (Shows who actually saw it, Snowflake Horizon's own claim): Snowflake documents ACCESS_HISTORY, a view of object and column access by user, kept for 365 days (Enterprise Edition). [Source](https://docs.snowflake.com/en/sql-reference/account-usage/access_history.md), read 13 Nov 2026. - **snowflake-30** (Shows who actually saw it, Snowflake Horizon's own claim): The Tableau connector collects view and workbook usage and popularity; the page describes popularity, not a list of named viewers per report. [Source](https://docs.snowflake.com/en/user-guide/snowflake-horizon/connectors/tableau), read 13 Nov 2026. - **snowflake-31** (Shows who actually saw it, none-found): None found on 2026-11-13: named viewers per BI report or per AI agent response, in the ACCESS_HISTORY, lineage and BI connector documentation. Searched: https://docs.snowflake.com/en/sql-reference/account-usage/access_history.md, read 13 Nov 2026. - **snowflake-32** (Controls what an agent is told, Snowflake Horizon's own claim): Snowflake says that when an AI agent queries data, the role's access control, masking and row-access policies are enforced in the query engine, and metadata access is managed separately. [Source](https://docs.snowflake.com/en/user-guide/snowflake-horizon/horizon-context.md), read 13 Nov 2026. - **snowflake-33** (Controls what an agent is told, Snowflake Horizon's own claim): Snowflake documents RBAC for the managed MCP server and its tools. [Source](https://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-agents-mcp.md), read 13 Nov 2026. - **snowflake-34** (Controls what an agent is told, Snowflake Horizon's own claim): Snowflake documents that access to the MCP server does not grant access to tools; each tool needs its own grant. [Source](https://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-agents-mcp.md), read 13 Nov 2026. - **snowflake-35** (Controls what an agent is told, Snowflake Horizon's own claim): Snowflake warns that exposing SYSTEM_EXECUTE_SQL on an MCP server lets the client bypass the agent's semantic views and verified queries. [Source](https://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-agents-mcp.md), read 13 Nov 2026. - **snowflake-36** (Controls what an agent is told, Snowflake Horizon's own claim): Snowflake's marketing page says AI Guardrails detect, redact and block PII in agent outputs. [Source](https://web.archive.org/web/2026/https://www.snowflake.com/en/product/features/horizon/), read 13 Nov 2026. - **snowflake-37** (Controls what an agent is told, Snowflake Horizon's own claim): The Cortex AI Guardrails documentation page lists prompt injection and jailbreak protections; the page read does not describe PII redaction. [Source](https://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-ai-guardrails.md), read 13 Nov 2026. - **snowflake-38** (Acts on it, Snowflake Horizon's own claim): Snowflake documents Dynamic Data Masking, which masks column data at query time by policy. [Source](https://docs.snowflake.com/en/user-guide/security-column-intro.md), read 13 Nov 2026. - **snowflake-39** (Acts on it, Snowflake Horizon's own claim): Snowflake documents row access policies for row-level security (Enterprise Edition). [Source](https://docs.snowflake.com/en/user-guide/security-row-intro.md), read 13 Nov 2026. - **snowflake-40** (Acts on it, Snowflake Horizon's own claim): Snowflake documents tag-based masking: a masking policy set on a tag protects every tagged column of a matching data type. [Source](https://docs.snowflake.com/en/user-guide/tag-based-masking-policies.md), read 13 Nov 2026. - **snowflake-41** (Evidence beyond the vendor, third-party): dbt Labs publishes a partner page for Snowflake, describing the two as used together for governance and lineage. [Source](https://www.dbt.com/partners/snowflake), read 13 Nov 2026. - **snowflake-42** (Evidence beyond the vendor, Snowflake Horizon's own claim): Snowflake's Horizon page features a Merkle customer story with a 64% faster data development cycle (vendor-published). [Source](https://web.archive.org/web/2026/https://www.snowflake.com/en/product/features/horizon/), read 13 Nov 2026. - **snowflake-43** (Evidence beyond the vendor, observed): The public Snowflake-Labs/mcp repository (Apache-2.0, 302 stars, last release v.1.4.2 on 2026-05-15 per the GitHub API) says its community MCP server is no longer supported; users are pointed to the official Snowflake MCP Server. [Source](https://github.com/Snowflake-Labs/mcp), read 13 Nov 2026. - **snowflake-44** (Price transparency, Snowflake Horizon's own claim): Snowflake says its pricing is consumption-based; the archived pricing page lists Standard, Enterprise and Business Critical editions and shows prices only after a platform and region are selected. [Source](https://web.archive.org/web/2026/https://www.snowflake.com/en/pricing-options/), read 13 Nov 2026. - **snowflake-45** (Price transparency, Snowflake Horizon's own claim): Snowflake's Service Consumption Table (effective November 9, 2026; the snowflake.com copy returned HTTP 403, so this is the web.archive.org copy) lists On Demand Platform Credit prices in USD per edition: for AWS US East (Northern Virginia), $2.00 Standard, $3.00 Enterprise, $4.00 Business Critical and $6.00 VPS. [Source](https://web.archive.org/web/2026/https://www.snowflake.com/legal-files/CreditConsumptionTable.pdf), read 13 Nov 2026. - **snowflake-46** (Price transparency, Snowflake Horizon's own claim): Snowflake's Service Consumption Table lists Sensitive Data Classification as a serverless feature billed in Platform Credits with a Snowflake-managed compute multiplier of 0.9 and a cloud services multiplier of 1. [Source](https://web.archive.org/web/2026/https://www.snowflake.com/legal-files/CreditConsumptionTable.pdf), read 13 Nov 2026. - **snowflake-47** (Price transparency, Snowflake Horizon's own claim): Snowflake's Service Consumption Table lists Data Quality Monitoring as a serverless feature with a Snowflake-managed compute multiplier of 2 and a cloud services multiplier of 1. [Source](https://web.archive.org/web/2026/https://www.snowflake.com/legal-files/CreditConsumptionTable.pdf), read 13 Nov 2026. - **snowflake-48** (Price transparency, Snowflake Horizon's own claim): Snowflake's Service Consumption Table lists Cortex Tools, the calls by which Snowflake-managed and third-party agents reach Snowflake endpoints, at 0 AI Credits per 1,000 tool calls. [Source](https://web.archive.org/web/2026/https://www.snowflake.com/legal-files/CreditConsumptionTable.pdf), read 13 Nov 2026. - **snowflake-49** (Controls what an agent is told, Snowflake Horizon's own claim): Snowflake's September 2, 2026 release note says data lineage now shows which data a Cortex Agent can reach through the tools declared in its specification, but only for agents created or committed after the change. [Source](https://docs.snowflake.com/en/release-notes/2026/other/2026-09-02-cortex-agent-lineage), read 13 Nov 2026. - **snowflake-50** (Profile, Snowflake Horizon's own claim): Snowflake's September 3, 2026 release note says external lineage is generally available and takes OpenLineage events from tools such as dbt and Apache Airflow into the Snowflake lineage graph, including column lineage; it says nothing about carrying tags or certification onto those external objects. [Source](https://docs.snowflake.com/en/release-notes/2026/other/2026-09-03-external-lineage-ga), read 13 Nov 2026. - **snowflake-51** (Coverage of the stack, third-party): Microsoft Learn documents how to register and scan Snowflake in Microsoft Purview and says the scan fetches static lineage among tables, views, streams and stored procedures. [Source](https://learn.microsoft.com/en-us/purview/register-scan-snowflake), read 13 Nov 2026. - **snowflake-52** (Coverage of the stack, third-party): Microsoft Learn lists static lineage as part of the Purview Snowflake scan, with limits for stored procedures written in Java, Python and Scala. [Source](https://learn.microsoft.com/en-us/purview/register-scan-snowflake), read 13 Nov 2026. - **snowflake-53** (Profile, third-party): Tableau's own help documents a native Snowflake connector for Tableau Cloud, Desktop, Prep and Server. [Source](https://help.tableau.com/current/pro/desktop/en-us/examples_snowflake.htm), read 13 Nov 2026. ## Compare Snowflake Horizon - [The full index](/index/) ## Sources - https://docs.snowflake.com/en/user-guide/snowflake-horizon.md: https://docs.snowflake.com/en/user-guide/snowflake-horizon.md (read 13 Nov 2026) - https://www.selectstar.com/: https://www.selectstar.com/ (read 13 Nov 2026) - https://docs.snowflake.com/en/user-guide/snowflake-horizon/connectors.md: https://docs.snowflake.com/en/user-guide/snowflake-horizon/connectors.md (read 13 Nov 2026) - https://docs.snowflake.com/en/user-guide/intro-compliance.md: https://docs.snowflake.com/en/user-guide/intro-compliance.md (read 13 Nov 2026) - https://docs.snowflake.com/en/release-notes/new-features: https://docs.snowflake.com/en/release-notes/new-features (read 13 Nov 2026) - https://docs.snowflake.com/en/user-guide/classify-intro.md: https://docs.snowflake.com/en/user-guide/classify-intro.md (read 13 Nov 2026) - https://docs.snowflake.com/en/user-guide/object-tagging/propagation.md: https://docs.snowflake.com/en/user-guide/object-tagging/propagation.md (read 13 Nov 2026) - https://docs.snowflake.com/en/user-guide/snowflake-horizon/horizon-context.md: https://docs.snowflake.com/en/user-guide/snowflake-horizon/horizon-context.md (read 13 Nov 2026) - https://docs.snowflake.com/en/user-guide/data-quality-intro.md: https://docs.snowflake.com/en/user-guide/data-quality-intro.md (read 13 Nov 2026) - https://docs.snowflake.com/en/user-guide/views-semantic/overview.md: https://docs.snowflake.com/en/user-guide/views-semantic/overview.md (read 13 Nov 2026) - https://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-agents-mcp.md: https://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-agents-mcp.md (read 13 Nov 2026) - https://docs.snowflake.com/en/user-guide/snowflake-horizon/connectors/tableau: https://docs.snowflake.com/en/user-guide/snowflake-horizon/connectors/tableau (read 13 Nov 2026) - https://docs.snowflake.com/en/user-guide/snowflake-horizon/connectors/powerbi: https://docs.snowflake.com/en/user-guide/snowflake-horizon/connectors/powerbi (read 13 Nov 2026) - https://docs.snowflake.com/en/user-guide/ui-snowsight-lineage.md: https://docs.snowflake.com/en/user-guide/ui-snowsight-lineage.md (read 13 Nov 2026) - https://docs.snowflake.com/en/sql-reference/account-usage/access_history.md: https://docs.snowflake.com/en/sql-reference/account-usage/access_history.md (read 13 Nov 2026) - https://web.archive.org/web/2026/https://www.snowflake.com/en/product/features/horizon/: https://web.archive.org/web/2026/https://www.snowflake.com/en/product/features/horizon/ (read 13 Nov 2026) - https://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-ai-guardrails.md: https://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-ai-guardrails.md (read 13 Nov 2026) - https://docs.snowflake.com/en/user-guide/security-column-intro.md: https://docs.snowflake.com/en/user-guide/security-column-intro.md (read 13 Nov 2026) - https://docs.snowflake.com/en/user-guide/security-row-intro.md: https://docs.snowflake.com/en/user-guide/security-row-intro.md (read 13 Nov 2026) - https://docs.snowflake.com/en/user-guide/tag-based-masking-policies.md: https://docs.snowflake.com/en/user-guide/tag-based-masking-policies.md (read 13 Nov 2026) - https://www.dbt.com/partners/snowflake: https://www.dbt.com/partners/snowflake (read 13 Nov 2026) - https://github.com/Snowflake-Labs/mcp: https://github.com/Snowflake-Labs/mcp (read 13 Nov 2026) - https://web.archive.org/web/2026/https://www.snowflake.com/en/pricing-options/: https://web.archive.org/web/2026/https://www.snowflake.com/en/pricing-options/ (read 13 Nov 2026) - https://web.archive.org/web/2026/https://www.snowflake.com/legal-files/CreditConsumptionTable.pdf: https://web.archive.org/web/2026/https://www.snowflake.com/legal-files/CreditConsumptionTable.pdf (read 13 Nov 2026) - https://docs.snowflake.com/en/release-notes/2026/other/2026-09-02-cortex-agent-lineage: https://docs.snowflake.com/en/release-notes/2026/other/2026-09-02-cortex-agent-lineage (read 13 Nov 2026) - https://docs.snowflake.com/en/release-notes/2026/other/2026-09-03-external-lineage-ga: https://docs.snowflake.com/en/release-notes/2026/other/2026-09-03-external-lineage-ga (read 13 Nov 2026) - https://learn.microsoft.com/en-us/purview/register-scan-snowflake: https://learn.microsoft.com/en-us/purview/register-scan-snowflake (read 13 Nov 2026) - https://help.tableau.com/current/pro/desktop/en-us/examples_snowflake.htm: https://help.tableau.com/current/pro/desktop/en-us/examples_snowflake.htm (read 13 Nov 2026) Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/platforms/snowflake/ --- # Databricks Unity Catalog for AI data governance: rank 5 of 16, at 55.0 of 100 PLATFORM PROFILE, read 13 Nov 2026 **The short answer.** Databricks Unity Catalog ranks 5 of 16 on the Need to Know index at 55.0 of 100, read 13 Nov 2026. Its best criterion is Evidence beyond the vendor at 9 of 10, and its weakest is Follows sensitive data into BI at 4. The exposure map records 2 of six stages as documented and 4 as partial. - **Category:** Lakehouse data catalog and governance layer (built into the Databricks platform, with an open source core) - **Status:** Exists under this name on 13 Nov 2026 (databricks.com/product/unity-catalog is titled "UNITY CATALOG Open and unified governance for data and AI"; docs.databricks.com pages last updated Nov 2026; open source repo unitycatalog/unitycatalog pushed 13 Nov 2026). Related surfaces have been renamed: Lakehouse Monitoring is now "data profiling" inside "Data quality monitoring", and agent traffic is governed through "Unity Gateway". - **Exposure trail:** Warehouse column: documented; Transformation: partial; BI field: partial; Report: partial; Viewer: partial; Agent: documented - **Warehouses named:** Databricks SQL warehouses, Snowflake, BigQuery, AWS Glue, MySQL, PostgreSQL, Salesforce - **BI tools named:** Tableau, Power BI, Sigma, Databricks AI/BI dashboards - **Security tools named:** none found on 13 Nov 2026 - **Rank and total:** 5 of 16, 55.0 of 100 2 of 6 stages documented, 4 partial ## Databricks Unity Catalog on the eight criteria | Criterion | Weight | Score | Why | | --- | --- | --- | --- | | Follows sensitive data into BI | 25 | 4 | Own AI/BI dashboards appear in column lineage, but Tableau and Power BI need manual registration; automatic harvesting was none found on 2026-11-13. | | Controls what an agent is told | 20 | 7 | Row filters and masks enforce per user in Genie, OAuth calls run as the signed-in user and a PII guardrail is in Beta; one agent MCP bypasses the gateway. | | Shows who actually saw it | 15 | 6 | Dashboard view events, MCP tool calls and query history are logged by user, but Tableau and Power BI viewers were none found on 2026-11-13. | | Carries classification downstream | 15 | 5 | Own classifier tags columns and Beta propagation copies tags along lineage to derived tables, off by default; external security tool labels were none found. | | Acts on it | 10 | 6 | Column mask and row filter policies tie to classification tags with a masking form from detections, but ABAC policies are Beta and no alerts or tickets are shown. | | Coverage of the stack | 5 | 4 | Snowflake, BigQuery and Glue federate, dbt and three BI tools appear, Purview scans read tags; no third-party security tool integration was found. | | Evidence beyond the vendor | 5 | 9 | AWS Marketplace listing, dbt Labs documentation, Microsoft Learn and Tableau help independently document the product. | | Price transparency | 5 | 4 | Pay-as-you-go per-second model with committed-use discounts is published; governance feature DBU rates could not be read. | Blind scores for Databricks Unity Catalog, 0 to 10. A vendor claim scores at most 7 until a second source confirms it. ## Where Databricks Unity Catalog is strongest Vendor-stated: Automatic PII classification feeds governed tags, tag propagation (Beta) along lineage applies matching ABAC policies to derived columns, and Genie enforces row filters and column masks per user. ## Where Databricks Unity Catalog falls short BI reach beyond Databricks dashboards depends on manually registered external lineage for Tableau and Power BI, and no viewer log for those reports was found. ## Databricks Unity Catalog along the exposure trail | Stage | Reading | Evidence | | --- | --- | --- | | [Warehouse column](/exposure-map/column/) | documented | Databricks says Data Classification automatically tags columns with class.* governed tags when automatic tagging is enabled, and tags all existing and future detections. [Source](https://docs.databricks.com/aws/en/data-governance/unity-catalog/data-classification), read 13 Nov 2026. | | [Transformation](/exposure-map/transformation/) | partial | Databricks says Unity Catalog captures runtime lineage to the column level for tables, jobs, notebooks, dashboards, models and external assets, with some limits. [Source](https://docs.databricks.com/aws/en/data-governance/unity-catalog/data-lineage), read 13 Nov 2026. | | [BI field](/exposure-map/bi-field/) | partial | Databricks says external assets such as Tableau or Power BI dashboards can be registered as external metadata objects and linked into the lineage graph. [Source](https://docs.databricks.com/aws/en/data-governance/unity-catalog/external-lineage), read 13 Nov 2026. | | [Report](/exposure-map/report/) | partial | Databricks says external assets such as Tableau or Power BI dashboards can be registered as external metadata objects and linked into the lineage graph. [Source](https://docs.databricks.com/aws/en/data-governance/unity-catalog/external-lineage), read 13 Nov 2026. | | [Viewer](/exposure-map/viewer/) | partial | Databricks logs AI/BI dashboard view events in the audit log, including a user accessing the published version of a dashboard. [Source](https://docs.databricks.com/aws/en/admin/account-settings/audit-logs), read 13 Nov 2026. | | [Agent](/exposure-map/agent/) | documented | Databricks says row filters and column masks defined in Unity Catalog are enforced per user automatically in a Genie Agent, regardless of how it is shared. [Source](https://docs.databricks.com/aws/en/genie/set-up), read 13 Nov 2026. | Documented, partial or none found on the read date. Vendor claims are the vendor's. ## Databricks Unity Catalog in each situation | Situation | Rank | Total | Leader | | --- | --- | --- | --- | | [A regulated field](/best-for/regulated-field/) | 7 | 52.0 | Atlan 68.5 | | [Agents on analytics](/best-for/agents-on-analytics/) | 4 | 58.0 | Euno 66.0 | | [A Microsoft estate](/best-for/microsoft-estate/) | 8 | 51.0 | Atlan 68.5 | | [A mixed stack](/best-for/mixed-stack/) | 9 | 48.0 | Euno 68.5 | | [A lean team](/best-for/lean-team/) | 7 | 53.0 | Euno 62.5 | Each situation ranks the same scores under its own published weights. ## The evidence on Databricks Unity Catalog, fact by fact - **databricks-01** (Profile, Databricks Unity Catalog's own claim): Databricks says tag automations (Beta) assign or remove governed tags on tables, columns and volumes from rules you define, and that runs update tags as data and metadata change. [Source](https://docs.databricks.com/aws/en/admin/governed-tags/automate-tag-assignment), read 13 Nov 2026. - **databricks-02** (Profile, Databricks Unity Catalog's own claim): Databricks documents certifying a table by rule: owner is a named principal, the table has a description, and it had more than 100 read queries in 30 days, then the system.certification_status tag is set to certified. [Source](https://docs.databricks.com/aws/en/admin/governed-tags/automate-tag-assignment), read 13 Nov 2026. - **databricks-03** (Profile, Databricks Unity Catalog's own claim): Databricks says system.certification_status marks an asset as certified or deprecated, with a check mark in Catalog Explorer, and that this can be automated at scale. [Source](https://docs.databricks.com/aws/en/admin/governed-tags/), read 13 Nov 2026. - **databricks-04** (Profile, Databricks Unity Catalog's own claim): Databricks says Data Classification automatically tags columns with class.* governed tags when automatic tagging is enabled, and tags all existing and future detections. [Source](https://docs.databricks.com/aws/en/data-governance/unity-catalog/data-classification), read 13 Nov 2026. - **databricks-05** (Profile, Databricks Unity Catalog's own claim): Databricks lists the tag automation feature as Beta, with deterministic rules evaluated against metadata, and separate from the AI-based Data Classification. [Source](https://docs.databricks.com/aws/en/admin/governed-tags/), read 13 Nov 2026. - **databricks-06** (Profile, Databricks Unity Catalog's own claim): Databricks documents tag automation conditions that read tags, descriptions, names, owner, dates, and the governed tags on direct upstream sources in lineage. [Source](https://docs.databricks.com/aws/en/admin/governed-tags/automate-tag-assignment), read 13 Nov 2026. - **databricks-07** (Profile, Databricks Unity Catalog's own claim): Databricks says the Insights tab shows table usage over 30 days and frequent queries, users, dashboards, notebooks and joined tables, and shows relative popularity of tables and columns. [Source](https://docs.databricks.com/aws/en/discover/table-insights), read 13 Nov 2026. - **databricks-08** (Profile, Databricks Unity Catalog's own claim): Databricks says anomaly detection monitors tables for freshness and completeness using per-table models built from commit history and row counts. [Source](https://docs.databricks.com/aws/en/data-quality-monitoring/), read 13 Nov 2026. - **databricks-09** (Profile, Databricks Unity Catalog's own claim): Databricks stores data quality monitoring results (freshness, completeness, incidents with downstream impact) in a system table. [Source](https://docs.databricks.com/aws/en/admin/system-tables/), read 13 Nov 2026. - **databricks-10** (Profile, Databricks Unity Catalog's own claim): Databricks says Unity Catalog captures runtime lineage to the column level for tables, jobs, notebooks, dashboards, models and external assets, with some limits. [Source](https://docs.databricks.com/aws/en/data-governance/unity-catalog/data-lineage), read 13 Nov 2026. - **databricks-11** (Profile, Databricks Unity Catalog's own claim): Databricks documents managed MCPs in system.ai (including a Genie One MCP and a Databricks SQL MCP) that are Unity Catalog securables invoked through Unity Gateway, with grants and policies. [Source](https://docs.databricks.com/aws/en/agents/mcp-tools/built-in-mcp-services), read 13 Nov 2026. - **databricks-12** (Profile, Databricks Unity Catalog's own claim): Databricks says the Genie One MCP resolves metric definitions and table relationships through Genie Ontology, a governed semantic layer. [Source](https://docs.databricks.com/aws/en/agents/mcp-tools/built-in-mcp-services), read 13 Nov 2026. - **databricks-13** (Profile, Databricks Unity Catalog's own claim): Databricks says the Genie Agent MCP bypasses Unity Gateway and relies on permissions on the Genie Agent and its data. [Source](https://docs.databricks.com/aws/en/agents/mcp-tools/built-in-mcp-services), read 13 Nov 2026. - **databricks-14** (Profile, none-found): None found on 2026-11-13: a documented way for an MCP agent to filter or be served assets by system.certification_status or other readiness tags at query time, in Databricks docs for managed MCP servers, governed tags and tag automation. Searched: https://docs.databricks.com/aws/en/agents/mcp-tools/built-in-mcp-services, read 13 Nov 2026. - **databricks-15** (Profile, Databricks Unity Catalog's own claim): Databricks says tags can be applied to tables, columns, volumes, views, functions, models, and also to dashboards, Genie Agents, Databricks apps and notebooks. [Source](https://docs.databricks.com/aws/en/database-objects/tags), read 13 Nov 2026. - **databricks-16** (Profile, Databricks Unity Catalog's own claim): Databricks says tagging of external metadata objects (the objects that stand for assets outside Databricks, such as BI dashboards) is in Public Preview. [Source](https://docs.databricks.com/aws/en/database-objects/tags), read 13 Nov 2026. - **databricks-17** (Profile, third-party): dbt Labs documents a databricks_tags config in dbt-databricks (version 1.11 or higher) that applies Unity Catalog tags to materialized views and streaming tables. [Source](https://docs.getdbt.com/reference/resource-configs/databricks-configs), read 13 Nov 2026. - **databricks-18** (Profile, Databricks Unity Catalog's own claim): Databricks says automations run on demand or on a recurring schedule, and a dry run records matched assets before any tag is assigned. [Source](https://docs.databricks.com/aws/en/admin/governed-tags/automate-tag-assignment), read 13 Nov 2026. - **databricks-19** (Profile, Databricks Unity Catalog's own claim): Databricks says new tables and columns are typically classified within 24 hours, and a full scan can be triggered at any time. [Source](https://docs.databricks.com/aws/en/data-governance/unity-catalog/data-classification), read 13 Nov 2026. - **databricks-20** (Evidence beyond the vendor, third-party): AWS Marketplace lists the Databricks Data Intelligence Platform as a SaaS product sold by Databricks, Inc., with a 4.6 rating from 1429 reviews shown on the listing. [Source](https://aws.amazon.com/marketplace/pp/prodview-wtyi5lgtce6n6), read 13 Nov 2026. - **databricks-21** (Evidence beyond the vendor, observed): The public GitHub repository for open source Unity Catalog describes the project as a sandbox project with LF AI and Data Foundation. [Source](https://github.com/unitycatalog/unitycatalog), read 13 Nov 2026. - **databricks-22** (Price transparency, Databricks Unity Catalog's own claim): Databricks says it uses a pay-as-you-go model billed per second with no up-front costs, and offers committed-use discounts. [Source](https://www.databricks.com/product/pricing), read 13 Nov 2026. - **databricks-23** (Price transparency, Databricks Unity Catalog's own claim): Databricks says Data Classification has its own billing and points readers to the pricing page; usage can be queried from system.billing.usage. [Source](https://docs.databricks.com/aws/en/data-governance/unity-catalog/data-classification), read 13 Nov 2026. - **databricks-24** (Price transparency, third-party): The AWS Marketplace listing points to the Databricks pricing page for per-product DBU rates. [Source](https://aws.amazon.com/marketplace/pp/prodview-wtyi5lgtce6n6), read 13 Nov 2026. - **databricks-25** (Price transparency, none-found): None found on 2026-11-13: a DBU rate for Data Classification, tag automation, or Unity Catalog governance features as readable text, in the Databricks pricing pages (rate tables load by script and showed "Loading..."). Searched: https://www.databricks.com/product/pricing, read 13 Nov 2026. - **databricks-26** (Follows sensitive data into BI, Databricks Unity Catalog's own claim): Databricks says external assets such as Tableau or Power BI dashboards can be registered as external metadata objects and linked into the lineage graph. [Source](https://docs.databricks.com/aws/en/data-governance/unity-catalog/external-lineage), read 13 Nov 2026. - **databricks-27** (Follows sensitive data into BI, Databricks Unity Catalog's own claim): Databricks says external metadata objects can have column names entered so column-level mapping to a Unity Catalog object is possible. [Source](https://docs.databricks.com/aws/en/data-governance/unity-catalog/external-lineage), read 13 Nov 2026. - **databricks-28** (Follows sensitive data into BI, Databricks Unity Catalog's own claim): Databricks shows Databricks AI/BI dashboards as downstream consumers on a table's Lineage tab. [Source](https://docs.databricks.com/aws/en/data-governance/unity-catalog/data-lineage), read 13 Nov 2026. - **databricks-29** (Follows sensitive data into BI, none-found): None found on 2026-11-13: automatic harvesting of Tableau or Power BI field and report lineage into Unity Catalog without manual registration, in Databricks external lineage and lineage documentation. Searched: https://docs.databricks.com/aws/en/data-governance/unity-catalog/external-lineage, read 13 Nov 2026. - **databricks-30** (Controls what an agent is told, Databricks Unity Catalog's own claim): Databricks says row filters and column masks defined in Unity Catalog are enforced per user automatically in a Genie Agent, regardless of how it is shared. [Source](https://docs.databricks.com/aws/en/genie/set-up), read 13 Nov 2026. - **databricks-31** (Controls what an agent is told, Databricks Unity Catalog's own claim): Databricks says MCP clients authenticate with a Databricks token that identifies a user or service principal, and OAuth user-to-machine calls the MCP as the signed-in user. [Source](https://docs.databricks.com/aws/en/agents/mcp-tools/authentication-networking), read 13 Nov 2026. - **databricks-32** (Controls what an agent is told, Databricks Unity Catalog's own claim): Databricks documents a Sensitive Data Detection guardrail (Beta) on MCPs that can block calls containing PII in tool arguments and results, by classification tag. [Source](https://docs.databricks.com/aws/en/ai-gateway/govern-mcp-service), read 13 Nov 2026. - **databricks-33** (Controls what an agent is told, Databricks Unity Catalog's own claim): Databricks documents a custom policy function that denies a tool when the acting agent has a specific OAuth client ID and the call is on behalf of a user. [Source](https://docs.databricks.com/aws/en/ai-gateway/govern-mcp-service), read 13 Nov 2026. - **databricks-34** (Shows who actually saw it, Databricks Unity Catalog's own claim): Databricks logs AI/BI dashboard view events in the audit log, including a user accessing the published version of a dashboard. [Source](https://docs.databricks.com/aws/en/admin/account-settings/audit-logs), read 13 Nov 2026. - **databricks-35** (Shows who actually saw it, Databricks Unity Catalog's own claim): Databricks logs Genie One MCP tool calls in the audit log (one event per tool call). [Source](https://docs.databricks.com/aws/en/admin/account-settings/audit-logs), read 13 Nov 2026. - **databricks-36** (Shows who actually saw it, Databricks Unity Catalog's own claim): Databricks documents a query history system table with a column recording who ran each statement. [Source](https://docs.databricks.com/aws/en/admin/system-tables/query-history), read 13 Nov 2026. - **databricks-37** (Shows who actually saw it, none-found): None found on 2026-11-13: viewer logs for Tableau or Power BI reports built on Databricks tables, in Databricks system tables, audit log and lineage documentation. Searched: https://docs.databricks.com/aws/en/admin/system-tables/, read 13 Nov 2026. - **databricks-38** (Carries classification downstream, Databricks Unity Catalog's own claim): Databricks says tag propagation (Beta) copies a governed tag from a source table or column to derived tables and views using lineage, when supported operations run on serverless compute. [Source](https://docs.databricks.com/aws/en/admin/governed-tags/tag-propagation), read 13 Nov 2026. - **databricks-39** (Carries classification downstream, Databricks Unity Catalog's own claim): Databricks says propagation is off by default and enabled per governed tag, and uses a default value when sources conflict. [Source](https://docs.databricks.com/aws/en/admin/governed-tags/tag-propagation), read 13 Nov 2026. - **databricks-40** (Carries classification downstream, Databricks Unity Catalog's own claim): Databricks says a propagated tag makes an existing matching ABAC policy, such as a column mask, apply to the derived column. [Source](https://docs.databricks.com/aws/en/admin/governed-tags/tag-propagation), read 13 Nov 2026. - **databricks-41** (Acts on it, Databricks Unity Catalog's own claim): Databricks says ABAC policies are attached at catalog, schema or table level, evaluated dynamically, and support row filter and column mask policies, with GRANT and DENY policies (Beta). [Source](https://docs.databricks.com/aws/en/data-governance/unity-catalog/abac/), read 13 Nov 2026. - **databricks-42** (Acts on it, Databricks Unity Catalog's own claim): Databricks says a Data Classification result can be turned into a masking policy: the form is pre-filled to mask columns with the reviewed classification tag. [Source](https://docs.databricks.com/aws/en/data-governance/unity-catalog/data-classification), read 13 Nov 2026. - **databricks-43** (Coverage of the stack, Databricks Unity Catalog's own claim): Databricks says Unity Catalog is open source under the Linux Foundation and federates Snowflake, BigQuery and AWS Glue without moving data. [Source](https://www.databricks.com/product/unity-catalog), read 13 Nov 2026. - **databricks-44** (Coverage of the stack, none-found): None found on 2026-11-13: a named integration with a third-party security tool (for example BigID) that feeds sensitivity labels into Unity Catalog tags, in the Databricks Data Classification, governed tags and ABAC documentation. Searched: https://docs.databricks.com/aws/en/data-governance/unity-catalog/data-classification, read 13 Nov 2026. - **databricks-45** (Profile, Databricks Unity Catalog's own claim): Databricks says the Unity Catalog metric view lets users define a metric once and group by any available field at query time. [Source](https://docs.databricks.com/aws/en/uc-semantics/metric-views/), read 13 Nov 2026. - **databricks-46** (Coverage of the stack, third-party): Microsoft Learn documents how to register Azure Databricks and interact with Azure Databricks Unity Catalog in Microsoft Purview. [Source](https://learn.microsoft.com/en-us/purview/register-scan-azure-databricks-unity-catalog), read 13 Nov 2026. - **databricks-47** (Coverage of the stack, third-party): Microsoft Learn says a Purview scan of Unity Catalog reads Unity Catalog tags into Purview properties and fetches lineage between tables, views and columns during notebook runs. [Source](https://learn.microsoft.com/en-us/purview/register-scan-azure-databricks-unity-catalog), read 13 Nov 2026. - **databricks-48** (Profile, third-party): Tableau's own help documents a native Databricks connector for Tableau Cloud, Desktop, Prep and Server. [Source](https://help.tableau.com/current/pro/desktop/en-us/examples_databricks.htm), read 13 Nov 2026. ## Compare Databricks Unity Catalog - [Databricks Unity Catalog vs Immuta](/compare/databricks-vs-immuta/) - [The full index](/index/) ## Sources - https://docs.databricks.com/aws/en/admin/governed-tags/automate-tag-assignment: https://docs.databricks.com/aws/en/admin/governed-tags/automate-tag-assignment (read 13 Nov 2026) - https://docs.databricks.com/aws/en/admin/governed-tags/: https://docs.databricks.com/aws/en/admin/governed-tags/ (read 13 Nov 2026) - https://docs.databricks.com/aws/en/data-governance/unity-catalog/data-classification: https://docs.databricks.com/aws/en/data-governance/unity-catalog/data-classification (read 13 Nov 2026) - https://docs.databricks.com/aws/en/discover/table-insights: https://docs.databricks.com/aws/en/discover/table-insights (read 13 Nov 2026) - https://docs.databricks.com/aws/en/data-quality-monitoring/: https://docs.databricks.com/aws/en/data-quality-monitoring/ (read 13 Nov 2026) - https://docs.databricks.com/aws/en/admin/system-tables/: https://docs.databricks.com/aws/en/admin/system-tables/ (read 13 Nov 2026) - https://docs.databricks.com/aws/en/data-governance/unity-catalog/data-lineage: https://docs.databricks.com/aws/en/data-governance/unity-catalog/data-lineage (read 13 Nov 2026) - https://docs.databricks.com/aws/en/agents/mcp-tools/built-in-mcp-services: https://docs.databricks.com/aws/en/agents/mcp-tools/built-in-mcp-services (read 13 Nov 2026) - https://docs.databricks.com/aws/en/database-objects/tags: https://docs.databricks.com/aws/en/database-objects/tags (read 13 Nov 2026) - https://docs.getdbt.com/reference/resource-configs/databricks-configs: https://docs.getdbt.com/reference/resource-configs/databricks-configs (read 13 Nov 2026) - https://aws.amazon.com/marketplace/pp/prodview-wtyi5lgtce6n6: https://aws.amazon.com/marketplace/pp/prodview-wtyi5lgtce6n6 (read 13 Nov 2026) - https://github.com/unitycatalog/unitycatalog: https://github.com/unitycatalog/unitycatalog (read 13 Nov 2026) - https://www.databricks.com/product/pricing: https://www.databricks.com/product/pricing (read 13 Nov 2026) - https://docs.databricks.com/aws/en/data-governance/unity-catalog/external-lineage: https://docs.databricks.com/aws/en/data-governance/unity-catalog/external-lineage (read 13 Nov 2026) - https://docs.databricks.com/aws/en/genie/set-up: https://docs.databricks.com/aws/en/genie/set-up (read 13 Nov 2026) - https://docs.databricks.com/aws/en/agents/mcp-tools/authentication-networking: https://docs.databricks.com/aws/en/agents/mcp-tools/authentication-networking (read 13 Nov 2026) - https://docs.databricks.com/aws/en/ai-gateway/govern-mcp-service: https://docs.databricks.com/aws/en/ai-gateway/govern-mcp-service (read 13 Nov 2026) - https://docs.databricks.com/aws/en/admin/account-settings/audit-logs: https://docs.databricks.com/aws/en/admin/account-settings/audit-logs (read 13 Nov 2026) - https://docs.databricks.com/aws/en/admin/system-tables/query-history: https://docs.databricks.com/aws/en/admin/system-tables/query-history (read 13 Nov 2026) - https://docs.databricks.com/aws/en/admin/governed-tags/tag-propagation: https://docs.databricks.com/aws/en/admin/governed-tags/tag-propagation (read 13 Nov 2026) - https://docs.databricks.com/aws/en/data-governance/unity-catalog/abac/: https://docs.databricks.com/aws/en/data-governance/unity-catalog/abac/ (read 13 Nov 2026) - https://www.databricks.com/product/unity-catalog: https://www.databricks.com/product/unity-catalog (read 13 Nov 2026) - https://docs.databricks.com/aws/en/uc-semantics/metric-views/: https://docs.databricks.com/aws/en/uc-semantics/metric-views/ (read 13 Nov 2026) - https://learn.microsoft.com/en-us/purview/register-scan-azure-databricks-unity-catalog: https://learn.microsoft.com/en-us/purview/register-scan-azure-databricks-unity-catalog (read 13 Nov 2026) - https://help.tableau.com/current/pro/desktop/en-us/examples_databricks.htm: https://help.tableau.com/current/pro/desktop/en-us/examples_databricks.htm (read 13 Nov 2026) Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/platforms/databricks/ --- # Microsoft Purview for AI data governance: rank 6 of 16, at 54.5 of 100 PLATFORM PROFILE, read 13 Nov 2026 **The short answer.** Microsoft Purview ranks 6 of 16 on the Need to Know index at 54.5 of 100, read 13 Nov 2026. Its best criterion is Evidence beyond the vendor at 8 of 10, and its weakest is Follows sensitive data into BI at 3. The exposure map records 2 of six stages as documented and 4 as partial. - **Category:** Microsoft data security and compliance suite (sensitivity labels, DLP, DSPM for AI) plus a retiring data catalog and Data Map - **Status:** Exists under this name on 13 Nov 2026 (Learn docs and Microsoft Security blog); Purview Data Governance (Unified Catalog, Data Map, Data Quality) is being retired in favor of Microsoft Fabric with support ending Nov. 12, 2027, while Purview data security (Information Protection, DLP, DSPM for AI) continues. - **Exposure trail:** Warehouse column: documented; Transformation: partial; BI field: partial; Report: documented; Viewer: partial; Agent: partial - **Warehouses named:** Snowflake, Azure Synapse Analytics, Azure SQL Database, Azure Databricks Unity Catalog, Azure Databricks Hive Metastore, Google BigQuery, Amazon Redshift, Oracle, Teradata, SQL Server - **BI tools named:** Power BI, Looker - **Security tools named:** Microsoft Purview Information Protection, Microsoft Purview DLP, Microsoft Defender for Cloud Apps - **Rank and total:** 6 of 16, 54.5 of 100 2 of 6 stages documented, 4 partial ## Microsoft Purview on the eight criteria | Criterion | Weight | Score | Why | | --- | --- | --- | --- | | Follows sensitive data into BI | 25 | 3 | Power BI lineage is limited to four source types and column detail only from Azure SQL; Snowflake to BI and Tableau were none found. | | Controls what an agent is told | 20 | 6 | Supported AI apps and the Fabric IQ MCP respect user permissions, row and object level security; coverage is limited to supported apps. | | Shows who actually saw it | 15 | 6 | Power BI activity log shows who acted on which item, AI events and an agents dashboard exist, with 60-minute lag and no catalog viewer list. | | Carries classification downstream | 15 | 6 | Labels from three source types flow to Power BI items and downstream, with an 80-item limit and consent default mode. | | Acts on it | 10 | 7 | Protection policies, DLP and endpoint blocking enforce on labeled items, but not on Power BI reports or dashboards, and have scale limits. | | Coverage of the stack | 5 | 5 | Many warehouses, Power BI, Looker and Microsoft security tools, but no dbt and no Tableau scan was found. | | Evidence beyond the vendor | 5 | 8 | PeerSpot reports 60 reviews and a second-place ranking; an archived accelerator and a community SDK exist in public records. | | Price transparency | 5 | 7 | Dollar prices per governed asset and per processing unit are published in two places, but Fabric governance is bundled and not separately priced. | Blind scores for Microsoft Purview, 0 to 10. A vendor claim scores at most 7 until a second source confirms it. ## Where Microsoft Purview is strongest Vendor-stated: Sensitivity labels carry from Azure SQL and Synapse into Power BI semantic models, then downstream to reports and dashboards, with the Power BI activity log and AI interaction events recording who and which AI app touched labeled data. ## Where Microsoft Purview falls short Label inheritance from data sources covers only Excel, Azure Synapse and Azure SQL Database, column-level Power BI lineage only Azure SQL, Tableau has no listed capability, and the governance catalog is in maintenance mode until Nov. 12, 2027. ## Microsoft Purview along the exposure trail | Stage | Reading | Evidence | | --- | --- | --- | | [Warehouse column](/exposure-map/column/) | documented | Microsoft says Data Map classifies assets automatically during scans with more than 200 built-in classifications plus custom ones. [Source](https://learn.microsoft.com/purview/data-map-classification), read 13 Nov 2026. | | [Transformation](/exposure-map/transformation/) | partial | Microsoft documents that scanning Snowflake brings in tables, views, streams and stored procedures with static lineage between them. [Source](https://learn.microsoft.com/purview/register-scan-snowflake), read 13 Nov 2026. | | [BI field](/exposure-map/bi-field/) | partial | Microsoft says column-level lineage and transformation detail inside Power BI datasets are captured only when Azure SQL Database is the source. [Source](https://learn.microsoft.com/purview/how-to-lineage-powerbi), read 13 Nov 2026. | | [Report](/exposure-map/report/) | documented | Microsoft says a Power BI scan fetches static lineage between workspaces, dashboards, reports, datasets, dataflows, datamarts and external data source assets. [Source](https://learn.microsoft.com/purview/register-scan-power-bi-tenant), read 13 Nov 2026. | | [Viewer](/exposure-map/viewer/) | partial | Microsoft says the Power BI activity log records who took what action on which item, exposed through the ActivityEvents REST API. [Source](https://learn.microsoft.com/power-bi/enterprise/service-admin-auditing), read 13 Nov 2026. | | [Agent](/exposure-map/agent/) | partial | Microsoft says supported AI apps use existing access controls so data is never returned to a user, or used by the LLM, if that user lacks access. [Source](https://learn.microsoft.com/purview/ai-microsoft-purview), read 13 Nov 2026. | Documented, partial or none found on the read date. Vendor claims are the vendor's. ## Microsoft Purview in each situation | Situation | Rank | Total | Leader | | --- | --- | --- | --- | | [A regulated field](/best-for/regulated-field/) | 8 | 51.0 | Atlan 68.5 | | [Agents on analytics](/best-for/agents-on-analytics/) | 5 | 56.5 | Euno 66.0 | | [A Microsoft estate](/best-for/microsoft-estate/) | 7 | 51.5 | Atlan 68.5 | | [A mixed stack](/best-for/mixed-stack/) | 7 | 50.0 | Euno 68.5 | | [A lean team](/best-for/lean-team/) | 4 | 58.0 | Euno 62.5 | Each situation ranks the same scores under its own published weights. ## The evidence on Microsoft Purview, fact by fact - **microsoft-purview-01** (Profile, Microsoft Purview's own claim): Microsoft says Purview Data Governance will be retired and that Microsoft Fabric is now its data governance solution, with support ending Nov. 12, 2027. [Source](https://techcommunity.microsoft.com/blog/microsoft-security-blog/a-next-step-in-the-evolution-of-the-microsoft-data-governance-strategy/4572227), read 13 Nov 2026. - **microsoft-purview-02** (Profile, Microsoft Purview's own claim): Microsoft says the Purview brand stays focused on data security and compliance (classifying, labeling, protecting data, DLP, AI), while governance moves to Fabric. [Source](https://techcommunity.microsoft.com/blog/microsoft-security-blog/a-next-step-in-the-evolution-of-the-microsoft-data-governance-strategy/4572227), read 13 Nov 2026. - **microsoft-purview-03** (Profile, Microsoft Purview's own claim): Microsoft's Learn banner on Unified Catalog pages says new accounts can no longer be created and existing capabilities stay in maintenance mode through November 12, 2027. [Source](https://learn.microsoft.com/purview/unified-catalog-data-quality), read 13 Nov 2026. - **microsoft-purview-04** (Profile, Microsoft Purview's own claim): Microsoft's what's-new page says the new version of Data Security Posture Management is generally available, while partner solutions for non-Microsoft sources and the Data Security Posture Agent remain in preview. [Source](https://learn.microsoft.com/purview/whats-new), read 13 Nov 2026. - **microsoft-purview-05** (Carries classification downstream, Microsoft Purview's own claim): Microsoft documents that Power BI semantic models inherit sensitivity labels from only three source types: Excel on OneDrive or SharePoint, Azure Synapse Analytics, and Azure SQL Database. [Source](https://learn.microsoft.com/power-bi/enterprise/service-security-sensitivity-label-inheritance-from-data-sources), read 13 Nov 2026. - **microsoft-purview-06** (Carries classification downstream, Microsoft Purview's own claim): Microsoft says labels in Azure SQL and Synapse are applied through a two-step Purview flow, and the inheritance tenant setting must be on in Power BI. [Source](https://learn.microsoft.com/power-bi/enterprise/service-security-sensitivity-label-inheritance-from-data-sources), read 13 Nov 2026. - **microsoft-purview-07** (Carries classification downstream, Microsoft Purview's own claim): Microsoft documents downstream inheritance: a label applied to a semantic model or report flows to dependent semantic models, reports and dashboards, shown in lineage view. [Source](https://learn.microsoft.com/power-bi/enterprise/service-security-sensitivity-label-downstream-inheritance), read 13 Nov 2026. - **microsoft-purview-08** (Carries classification downstream, Microsoft Purview's own claim): Microsoft documents limits: downstream inheritance stops entirely above 80 downstream items, and never overwrites manual labels or applies a less restrictive label. [Source](https://learn.microsoft.com/power-bi/enterprise/service-security-sensitivity-label-downstream-inheritance), read 13 Nov 2026. - **microsoft-purview-09** (Carries classification downstream, Microsoft Purview's own claim): Microsoft says labels inherited from data sources propagate downstream only when fully automated downstream inheritance mode is enabled; the default mode asks the user for consent. [Source](https://learn.microsoft.com/power-bi/enterprise/service-security-sensitivity-label-downstream-inheritance), read 13 Nov 2026. - **microsoft-purview-10** (Carries classification downstream, Microsoft Purview's own claim): Microsoft says new Power BI reports and dashboards automatically inherit the label of the parent semantic model or report. [Source](https://learn.microsoft.com/power-bi/enterprise/service-security-sensitivity-label-overview), read 13 Nov 2026. - **microsoft-purview-11** (Carries classification downstream, Microsoft Purview's own claim): Microsoft says applying Purview sensitivity labels to Data Map assets (scanned data sources) is in preview and uses pay-as-you-go billing. [Source](https://learn.microsoft.com/purview/how-to-automatically-label-your-content), read 13 Nov 2026. - **microsoft-purview-12** (Coverage of the stack, Microsoft Purview's own claim): Microsoft says Data Map classifies assets automatically during scans with more than 200 built-in classifications plus custom ones. [Source](https://learn.microsoft.com/purview/data-map-classification), read 13 Nov 2026. - **microsoft-purview-13** (Follows sensitive data into BI, Microsoft Purview's own claim): Microsoft says Purview captures lineage between Power BI artifacts and external data assets, but only four source types are supported for that link: Azure SQL Database, Blob Storage, ADLS Gen1 and Gen2. [Source](https://learn.microsoft.com/purview/how-to-lineage-powerbi), read 13 Nov 2026. - **microsoft-purview-14** (Follows sensitive data into BI, Microsoft Purview's own claim): Microsoft says column-level lineage and transformation detail inside Power BI datasets are captured only when Azure SQL Database is the source. [Source](https://learn.microsoft.com/purview/how-to-lineage-powerbi), read 13 Nov 2026. - **microsoft-purview-15** (Follows sensitive data into BI, Microsoft Purview's own claim): Microsoft says a Power BI scan fetches static lineage between workspaces, dashboards, reports, datasets, dataflows, datamarts and external data source assets. [Source](https://learn.microsoft.com/purview/register-scan-power-bi-tenant), read 13 Nov 2026. - **microsoft-purview-16** (Shows who actually saw it, none-found): None found on 2026-11-13: a per-report viewer list inside the Purview catalog for scanned Power BI items, in the Power BI lineage page (the page covers inventory, lineage and search; viewer events are in the Power BI activity log instead). Searched: https://learn.microsoft.com/purview/, read 13 Nov 2026. - **microsoft-purview-17** (Coverage of the stack, Microsoft Purview's own claim): Microsoft documents that scanning Snowflake brings in tables, views, streams and stored procedures with static lineage between them. [Source](https://learn.microsoft.com/purview/register-scan-snowflake), read 13 Nov 2026. - **microsoft-purview-18** (Follows sensitive data into BI, none-found): None found on 2026-11-13: lineage from a Snowflake column to a Power BI or Tableau field, in the Snowflake scan page (lineage is described only among Snowflake tables, views, streams and stored procedures). Searched: https://learn.microsoft.com/purview/, read 13 Nov 2026. - **microsoft-purview-19** (Coverage of the stack, none-found): None found on 2026-11-13: dbt as a scannable source or transformation connector, in the Data Map connector list (Azure Data Factory and Synapse pipelines appear as lineage sources, dbt does not). Searched: https://learn.microsoft.com/purview/, read 13 Nov 2026. - **microsoft-purview-20** (Coverage of the stack, Microsoft Purview's own claim): Microsoft documents that the Azure Databricks Unity Catalog scan reads Unity Catalog tags and fetches table, view and column lineage from notebook runs. [Source](https://learn.microsoft.com/purview/register-scan-azure-databricks-unity-catalog), read 13 Nov 2026. - **microsoft-purview-21** (Coverage of the stack, Microsoft Purview's own claim): Microsoft documents limits for Databricks: lineage is not supported for external tables or in the China region. [Source](https://learn.microsoft.com/purview/register-scan-azure-databricks-unity-catalog), read 13 Nov 2026. - **microsoft-purview-22** (Coverage of the stack, Microsoft Purview's own claim): Microsoft's connector table has columns for automatic classification, sensitivity labels on Data Map assets, policies, lineage and live view, per data source. [Source](https://learn.microsoft.com/purview/microsoft-purview-connector-overview), read 13 Nov 2026. - **microsoft-purview-23** (Coverage of the stack, Microsoft Purview's own claim): Microsoft's what's-new page says auto-labeling policies now cover non-Microsoft connected apps such as Box and Google Workspace through Defender for Cloud Apps connectors. [Source](https://learn.microsoft.com/purview/whats-new), read 13 Nov 2026. - **microsoft-purview-24** (Coverage of the stack, none-found): None found on 2026-11-13: a Tableau scan with lineage or classification, in the Data Map connector list (Tableau appears in the table with no classification, label, policy, lineage or live view capability, and no Tableau scan page was found). Searched: https://learn.microsoft.com/purview/, read 13 Nov 2026. - **microsoft-purview-25** (Shows who actually saw it, Microsoft Purview's own claim): Microsoft says the Power BI activity log records who took what action on which item, exposed through the ActivityEvents REST API. [Source](https://learn.microsoft.com/power-bi/enterprise/service-admin-auditing), read 13 Nov 2026. - **microsoft-purview-26** (Shows who actually saw it, Microsoft Purview's own claim): Microsoft documents lag and paging limits: events can arrive up to 60 minutes late and the API returns one day of data per request. [Source](https://learn.microsoft.com/power-bi/enterprise/service-admin-auditing), read 13 Nov 2026. - **microsoft-purview-27** (Shows who actually saw it, Microsoft Purview's own claim): Microsoft says AI interaction events flow into the unified audit log and Activity explorer, including which files with sensitivity labels were accessed. [Source](https://learn.microsoft.com/purview/ai-microsoft-purview), read 13 Nov 2026. - **microsoft-purview-28** (Shows who actually saw it, Microsoft Purview's own claim): Microsoft says DSPM has an Apps and agents page whose dashboard shows how agents and their apps are used across the organization. [Source](https://learn.microsoft.com/purview/ai-agents), read 13 Nov 2026. - **microsoft-purview-29** (Shows who actually saw it, Microsoft Purview's own claim): Microsoft says Purview support for Copilot in Fabric starts with Copilot for Power BI (all prompts and text responses), with other Fabric Copilots and Fabric Data Agent in preview. [Source](https://learn.microsoft.com/purview/ai-copilot-fabric), read 13 Nov 2026. - **microsoft-purview-30** (Controls what an agent is told, Microsoft Purview's own claim): Microsoft says supported AI apps use existing access controls so data is never returned to a user, or used by the LLM, if that user lacks access. [Source](https://learn.microsoft.com/purview/ai-microsoft-purview), read 13 Nov 2026. - **microsoft-purview-31** (Controls what an agent is told, Microsoft Purview's own claim): Microsoft says encrypted labeled content is returned by AI apps only if the user holds the EXTRACT usage right as well as VIEW. [Source](https://learn.microsoft.com/purview/ai-microsoft-purview), read 13 Nov 2026. - **microsoft-purview-32** (Controls what an agent is told, Microsoft Purview's own claim): Microsoft says the Fabric IQ MCP endpoint answers questions over Power BI models and respects permissions, row-level security and object-level security. [Source](https://learn.microsoft.com/power-bi/developer/mcp/mcp-servers-overview), read 13 Nov 2026. - **microsoft-purview-33** (Controls what an agent is told, Microsoft Purview's own claim): Microsoft says the Power BI Authoring MCP server can read and write semantic models (including security roles) and is not meant for consumption; its hosted option is in preview. [Source](https://learn.microsoft.com/power-bi/developer/mcp/mcp-servers-overview), read 13 Nov 2026. - **microsoft-purview-34** (Acts on it, Microsoft Purview's own claim): Microsoft documents protection policies that tie a sensitivity label to an allow-list of users and groups and block everyone else from labeled Fabric items. [Source](https://learn.microsoft.com/fabric/governance/protection-policies-overview), read 13 Nov 2026. - **microsoft-purview-35** (Acts on it, Microsoft Purview's own claim): Microsoft documents limits: protection policies cover native Fabric items and Power BI semantic models, but not Power BI reports or dashboards. [Source](https://learn.microsoft.com/fabric/governance/protection-policies-overview), read 13 Nov 2026. - **microsoft-purview-36** (Acts on it, Microsoft Purview's own claim): Microsoft documents scale and timing limits: up to 50 policies, 100 users or groups per policy, no guests, and up to 24 hours before a new policy takes effect. [Source](https://learn.microsoft.com/fabric/governance/protection-policies-overview), read 13 Nov 2026. - **microsoft-purview-37** (Acts on it, Microsoft Purview's own claim): Microsoft documents DLP for Fabric and Power BI that can attach policy tips, alert admins and restrict access to items with sensitive content. [Source](https://learn.microsoft.com/purview/dlp-powerbi-get-started), read 13 Nov 2026. - **microsoft-purview-38** (Acts on it, Microsoft Purview's own claim): Microsoft says Endpoint DLP on onboarded Windows computers can warn or block sensitive data being pasted into third-party generative AI sites in a browser. [Source](https://learn.microsoft.com/purview/ai-microsoft-purview), read 13 Nov 2026. - **microsoft-purview-39** (Acts on it, Microsoft Purview's own claim): Microsoft says Unified Catalog data quality runs no-code or low-code rules, including AI-generated rules, at column level and can send notifications; the page carries the retirement banner. [Source](https://learn.microsoft.com/purview/unified-catalog-data-quality), read 13 Nov 2026. - **microsoft-purview-40** (Evidence beyond the vendor, third-party): PeerSpot (third-party review site) reports 60 reviews and an average 7.6 out of 10 for Microsoft Purview Data Governance, ranked #2 in Data Governance tools. [Source](https://www.peerspot.com/products/microsoft-purview-reviews), read 13 Nov 2026. - **microsoft-purview-41** (Price transparency, Microsoft Purview's own claim): Microsoft's Azure pricing page says Unified Catalog bills per governed asset per day, with a worked example of 200 governed assets costing $100 for 30 days. [Source](https://azure.microsoft.com/en-us/pricing/details/purview/), read 13 Nov 2026. - **microsoft-purview-42** (Price transparency, Microsoft Purview's own claim): Microsoft's Azure pricing page says data management rules and quality scans bill in Data Governance Processing Units, with an example of 2 DGPU costing $30 per day. [Source](https://azure.microsoft.com/en-us/pricing/details/purview/), read 13 Nov 2026. - **microsoft-purview-43** (Price transparency, Microsoft Purview's own claim): Microsoft says managing Copilot in Fabric AI interactions with Purview requires enabling pay-as-you-go billing. [Source](https://learn.microsoft.com/purview/ai-copilot-fabric), read 13 Nov 2026. - **microsoft-purview-44** (Price transparency, Microsoft Purview's own claim): Microsoft says the Fabric replacement for governance is included in Fabric capacity rather than billed through separate meters. [Source](https://techcommunity.microsoft.com/blog/microsoft-security-blog/a-next-step-in-the-evolution-of-the-microsoft-data-governance-strategy/4572227), read 13 Nov 2026. - **microsoft-purview-45** (Evidence beyond the vendor, observed): GitHub shows the Microsoft Purview-ADB-Lineage-Solution-Accelerator (Databricks lineage into Purview) is archived, MIT licensed, 93 stars, last pushed 2024-04-12, latest release 2.3.1 on 2023-03-13. [Source](https://github.com/microsoft/Purview-ADB-Lineage-Solution-Accelerator), read 13 Nov 2026. - **microsoft-purview-46** (Evidence beyond the vendor, observed): The PyPI record of PyApacheAtlas, an SDK published by an individual developer rather than Microsoft, describes working with the Azure Purview APIs for bulk loading, custom lineage and column mappings; the latest release on the record is 0.16.0 (Dec 2023). [Source](https://pypi.org/pypi/pyapacheatlas/json), read 13 Nov 2026. - **microsoft-purview-47** (Price transparency, Microsoft Purview's own claim): Microsoft's public Azure retail prices API lists Purview Data Governance meters in East US with effective start 2026-11-01: Data Management Basic $15, Standard $60 and Advanced $240 per Data Governance Processing Unit, and Data Catalog Standard $0.0165 per asset per day. [Source](https://prices.azure.com/api/retail/prices?$filter=serviceName eq 'Microsoft Purview' and armRegionName eq 'eastus' and contains(meterName,'Governance')), read 13 Nov 2026. ## Compare Microsoft Purview - [Euno vs Microsoft Purview](/compare/euno-vs-microsoft-purview/) - [Collibra vs Microsoft Purview](/compare/collibra-vs-microsoft-purview/) - [Informatica vs Microsoft Purview](/compare/informatica-vs-microsoft-purview/) - [Alternatives to Microsoft Purview](/alternatives/microsoft-purview/) - [The full index](/index/) ## Sources - https://techcommunity.microsoft.com/blog/microsoft-security-blog/a-next-step-in-the-evolution-of-the-microsoft-data-governance-strategy/4572227: https://techcommunity.microsoft.com/blog/microsoft-security-blog/a-next-step-in-the-evolution-of-the-microsoft-data-governance-strategy/4572227 (read 13 Nov 2026) - https://learn.microsoft.com/purview/unified-catalog-data-quality: https://learn.microsoft.com/purview/unified-catalog-data-quality (read 13 Nov 2026) - https://learn.microsoft.com/purview/whats-new: https://learn.microsoft.com/purview/whats-new (read 13 Nov 2026) - https://learn.microsoft.com/power-bi/enterprise/service-security-sensitivity-label-inheritance-from-data-sources: https://learn.microsoft.com/power-bi/enterprise/service-security-sensitivity-label-inheritance-from-data-sources (read 13 Nov 2026) - https://learn.microsoft.com/power-bi/enterprise/service-security-sensitivity-label-downstream-inheritance: https://learn.microsoft.com/power-bi/enterprise/service-security-sensitivity-label-downstream-inheritance (read 13 Nov 2026) - https://learn.microsoft.com/power-bi/enterprise/service-security-sensitivity-label-overview: https://learn.microsoft.com/power-bi/enterprise/service-security-sensitivity-label-overview (read 13 Nov 2026) - https://learn.microsoft.com/purview/how-to-automatically-label-your-content: https://learn.microsoft.com/purview/how-to-automatically-label-your-content (read 13 Nov 2026) - https://learn.microsoft.com/purview/data-map-classification: https://learn.microsoft.com/purview/data-map-classification (read 13 Nov 2026) - https://learn.microsoft.com/purview/how-to-lineage-powerbi: https://learn.microsoft.com/purview/how-to-lineage-powerbi (read 13 Nov 2026) - https://learn.microsoft.com/purview/register-scan-power-bi-tenant: https://learn.microsoft.com/purview/register-scan-power-bi-tenant (read 13 Nov 2026) - https://learn.microsoft.com/purview/: https://learn.microsoft.com/purview/ (read 13 Nov 2026) - https://learn.microsoft.com/purview/register-scan-snowflake: https://learn.microsoft.com/purview/register-scan-snowflake (read 13 Nov 2026) - https://learn.microsoft.com/purview/register-scan-azure-databricks-unity-catalog: https://learn.microsoft.com/purview/register-scan-azure-databricks-unity-catalog (read 13 Nov 2026) - https://learn.microsoft.com/purview/microsoft-purview-connector-overview: https://learn.microsoft.com/purview/microsoft-purview-connector-overview (read 13 Nov 2026) - https://learn.microsoft.com/power-bi/enterprise/service-admin-auditing: https://learn.microsoft.com/power-bi/enterprise/service-admin-auditing (read 13 Nov 2026) - https://learn.microsoft.com/purview/ai-microsoft-purview: https://learn.microsoft.com/purview/ai-microsoft-purview (read 13 Nov 2026) - https://learn.microsoft.com/purview/ai-agents: https://learn.microsoft.com/purview/ai-agents (read 13 Nov 2026) - https://learn.microsoft.com/purview/ai-copilot-fabric: https://learn.microsoft.com/purview/ai-copilot-fabric (read 13 Nov 2026) - https://learn.microsoft.com/power-bi/developer/mcp/mcp-servers-overview: https://learn.microsoft.com/power-bi/developer/mcp/mcp-servers-overview (read 13 Nov 2026) - https://learn.microsoft.com/fabric/governance/protection-policies-overview: https://learn.microsoft.com/fabric/governance/protection-policies-overview (read 13 Nov 2026) - https://learn.microsoft.com/purview/dlp-powerbi-get-started: https://learn.microsoft.com/purview/dlp-powerbi-get-started (read 13 Nov 2026) - https://www.peerspot.com/products/microsoft-purview-reviews: https://www.peerspot.com/products/microsoft-purview-reviews (read 13 Nov 2026) - https://azure.microsoft.com/en-us/pricing/details/purview/: https://azure.microsoft.com/en-us/pricing/details/purview/ (read 13 Nov 2026) - https://github.com/microsoft/Purview-ADB-Lineage-Solution-Accelerator: https://github.com/microsoft/Purview-ADB-Lineage-Solution-Accelerator (read 13 Nov 2026) - https://pypi.org/pypi/pyapacheatlas/json: https://pypi.org/pypi/pyapacheatlas/json (read 13 Nov 2026) - https://prices.azure.com/api/retail/prices?$filter=serviceName eq 'Microsoft Purview' and armRegionName eq 'eastus' and contains(meterName,'Governance'): https://prices.azure.com/api/retail/prices?$filter=serviceName eq 'Microsoft Purview' and armRegionName eq 'eastus' and contains(meterName,'Governance') (read 13 Nov 2026) Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/platforms/microsoft-purview/ --- # Alation for AI data governance: rank 7 of 16, at 54.0 of 100 PLATFORM PROFILE, read 13 Nov 2026 **The short answer.** Alation ranks 7 of 16 on the Need to Know index at 54.0 of 100, read 13 Nov 2026. Its best criterion is Evidence beyond the vendor at 8 of 10, and its weakest is Shows who actually saw it at 4. The exposure map records 4 of six stages as documented and 2 as partial. - **Category:** Data catalog and data intelligence platform with governance, data quality and AI agents - **Status:** Exists under this name on 13 Nov 2026 (alation.com serves the product as Alation, branded the Alation Intelligence Operating System; docs at documentation.alation.com; release notes dated November 4, 2026). - **Exposure trail:** Warehouse column: documented; Transformation: partial; BI field: documented; Report: documented; Viewer: partial; Agent: documented - **Warehouses named:** Snowflake, Databricks, Google BigQuery, Amazon Redshift, Azure Synapse, Oracle, SQL Server, PostgreSQL, Teradata, SAP HANA, Amazon Athena - **BI tools named:** Tableau, Power BI, Looker, AWS QuickSight, Qlik Sense Cloud - **Security tools named:** none found on 13 Nov 2026 - **Rank and total:** 7 of 16, 54.0 of 100 4 of 6 stages documented, 2 partial ## Alation on the eight criteria | Criterion | Weight | Score | Why | | --- | --- | --- | --- | | Follows sensitive data into BI | 25 | 7 | Column-level lineage from warehouse columns to Tableau report fields, Power BI and Looker, plus dbt extraction, is documented; vendor docs only, Power BI with stated limitations. | | Controls what an agent is told | 20 | 6 | MCP and API calls act as the asking user with different results per user, but service-account apps use a fixed role and MCP does not enforce tool approvals. | | Shows who actually saw it | 15 | 4 | Query-log top users and per-user agent tool-call counts exist, but Tableau view counts do not name viewers and no per-report viewer list is shown. | | Carries classification downstream | 15 | 4 | Snowflake tags are imported and custom fields copy up and down the hierarchy, but sensitivity propagation along lineage was none found on 2026-11-13. | | Acts on it | 10 | 4 | Data quality webhooks reach PagerDuty, Jira and Slack, and masked samples show only for Snowflake policies; no blocking or masking authored here. | | Coverage of the stack | 5 | 5 | Many warehouses, dbt and four BI tools are named, but no security or classification tool integration was found on 2026-11-13. | | Evidence beyond the vendor | 5 | 8 | Databricks Partner Connect and a PeerSpot review are independent confirmations, plus a vendor-published named customer story. | | Price transparency | 5 | 4 | A consumption-unit pricing model with published unit rates per tool call is documented, but no dollar price per unit; the pricing page is a contact form. | Blind scores for Alation, 0 to 10. A vendor claim scores at most 7 until a second source confirms it. ## Where Alation is strongest Vendor-stated: Agent calls run with the caller's identity and role, and column-level lineage is documented for Tableau, Power BI and Looker. ## Where Alation falls short No documented propagation of sensitivity labels along lineage into BI fields, no per-viewer report log, and MCP tool restrictions are left to each client. ## Alation along the exposure trail | Stage | Reading | Evidence | | --- | --- | --- | | [Warehouse column](/exposure-map/column/) | documented | Alation docs say Snowflake tags can be brought into Alation to track sensitive data and used as search filters; tags must be created in Snowflake first. [Source](https://documentation.alation.com/en/latest/governance/SnowflakeTags/index.md), read 13 Nov 2026. | | [Transformation](/exposure-map/transformation/) | partial | Alation docs describe lineage extraction for dbt Cloud and dbt Core through the dbt Gen2 connector. [Source](https://documentation.alation.com/en/latest/OpenConnectorFramework/ELTConnectors/dbtOCFConnector/dbtOCFConnectorConfigLineage.md), read 13 Nov 2026. | | [BI field](/exposure-map/bi-field/) | documented | Alation docs say Tableau lineage can show links from warehouse table columns to BI report fields in Tableau views (column-level lineage on by default from 2024.1.5). [Source](https://documentation.alation.com/en/latest/OpenConnectorFramework/BIConnectors/TableauOCFConnector/TableauServerandOnlineConnectorConfigureLineage.md), read 13 Nov 2026. | | [Report](/exposure-map/report/) | documented | Alation docs describe cross-source and column-level lineage for the Power BI Scanner connector, with supported expressions and limitations. [Source](https://documentation.alation.com/en/latest/OpenConnectorFramework/BIConnectors/PowerBIScannerOCFConnector/PowerBIScannerConnectorConfigLineage.md), read 13 Nov 2026. | | [Viewer](/exposure-map/viewer/) | partial | Alation docs say Tableau report popularity comes from Tableau view counts, which count views but do not name viewers. [Source](https://documentation.alation.com/en/latest/OpenConnectorFramework/BIConnectors/TableauOCFConnector/TableauOCFPopularity.md), read 13 Nov 2026. | | [Agent](/exposure-map/agent/) | documented | Alation docs say agents and tools hold no data permissions of their own and act as the caller on each run. [Source](https://documentation.alation.com/en/latest/agentstudio/security/identity-and-permissions.md), read 13 Nov 2026. | Documented, partial or none found on the read date. Vendor claims are the vendor's. ## Alation in each situation | Situation | Rank | Total | Leader | | --- | --- | --- | --- | | [A regulated field](/best-for/regulated-field/) | 5 | 54.0 | Atlan 68.5 | | [Agents on analytics](/best-for/agents-on-analytics/) | 7 | 53.0 | Euno 66.0 | | [A Microsoft estate](/best-for/microsoft-estate/) | 6 | 52.0 | Atlan 68.5 | | [A mixed stack](/best-for/mixed-stack/) | 5 | 53.0 | Euno 68.5 | | [A lean team](/best-for/lean-team/) | 8 | 50.5 | Euno 62.5 | Each situation ranks the same scores under its own published weights. ## The evidence on Alation, fact by fact - **alation-01** (Profile, Alation's own claim): Alation says it was founded in 2012 by four founders to connect people with questions to the data that has the answers (our-story page dates it 2012, Redwood City). [Source](https://www.alation.com/our-story/), read 13 Nov 2026. - **alation-02** (Profile, Alation's own claim): Alation says its catalog connects to 120+ sources without moving data. [Source](https://www.alation.com/aios/catalog/), read 13 Nov 2026. - **alation-03** (Profile, Alation's own claim): Alation lists named pre-built connectors across warehouse, transformation (dbt, Fivetran) and BI (Tableau, Power BI, Looker) layers, and says it has 100+ more. [Source](https://www.alation.com/aios/connectors-and-sdks/), read 13 Nov 2026. - **alation-04** (Profile, Alation's own claim): Alation now brands its platform the Alation Intelligence Operating System (AIOS), with the product still named Alation. [Source](https://www.alation.com/pricing/), read 13 Nov 2026. - **alation-05** (Profile, Alation's own claim): Alation says it holds ISO 27001:2022 certification for the whole company and its products. [Source](https://www.alation.com/legal/security/), read 13 Nov 2026. - **alation-06** (Profile, Alation's own claim): Alation docs say Curation Automation lets users define rules that curate large volumes of assets from one hub (rules can be scheduled and cover RDBMS, BI and filesystem sources); it applies from version 2026.2.1.0. [Source](https://documentation.alation.com/en/latest/governance/OutcomeBasedGovernance/CurationAutomation/index.md), read 13 Nov 2026. - **alation-07** (Profile, Alation's own claim): Alation docs say each curation field has an auto-apply confidence threshold (50% to 80%, default 75%) and AI suggestions below it are not applied, so the rule decides without a person marking each asset only above that threshold. [Source](https://documentation.alation.com/en/latest/governance/OutcomeBasedGovernance/CurationAutomation/CurationAutomationFAQ.md), read 13 Nov 2026. - **alation-08** (Profile, Alation's own claim): Alation docs describe the three trust flags (Endorsement, Important Info, Deprecation) as set by users on an object; the doc describes no rule that sets an Endorsement. [Source](https://documentation.alation.com/en/latest/governance/UseTrustFlags/index.md), read 13 Nov 2026. - **alation-09** (Profile, Alation's own claim): Alation docs say trust flags can be applied in bulk to all members of a catalog set, and conditional sets group objects by name-matching rules. [Source](https://documentation.alation.com/en/latest/governance/CatalogSets/ManageCatalogSets.md), read 13 Nov 2026. - **alation-10** (Profile, Alation's own claim): Alation says its governance agents propose descriptions, stewards, classifications and quality rules, but nothing commits until a human approves (with a confidence score and preview). [Source](https://www.alation.com/solutions/agentic-data-governance/), read 13 Nov 2026. - **alation-11** (Profile, Alation's own claim): Alation says DQ Pilot drafts quality monitors from catalog metadata, lineage and usage, and stewards review and approve the rules. [Source](https://www.alation.com/product/data-quality/), read 13 Nov 2026. - **alation-12** (Profile, Alation's own claim): Alation docs say popularity is computed from query ingestion (accounts and counts of use) and from Compose usage. [Source](https://docs.alation.com/en/latest/OpenConnectorFramework/DiscoverMetadata/DataPopularity.html), read 13 Nov 2026. - **alation-13** (Profile, Alation's own claim): Alation says agents reach the catalog over MCP and API with the same governed context people see, including quality scores and trust signals. [Source](https://www.alation.com/aios/catalog/), read 13 Nov 2026. - **alation-14** (Profile, Alation's own claim): Alation docs list built-in agent tools for catalog search, lineage and data quality scores, and the MCP server exposes them to connected clients. [Source](https://documentation.alation.com/en/latest/agentstudio/build/tools/get-dq-scores-tool.md), read 13 Nov 2026. - **alation-15** (Profile, Alation's own claim): Alation docs say the Alation-hosted MCP server is only available to Alation Cloud Service customers. [Source](https://documentation.alation.com/en/latest/agentstudio/integrations/mcp/quick-start.md), read 13 Nov 2026. - **alation-16** (Profile, observed): The public Alation AI Agent SDK repository shows a first stable release of the SDK, LangChain and MCP packages. [Source](https://github.com/Alation/alation-ai-agent-sdk/releases), read 13 Nov 2026. - **alation-17** (Controls what an agent is told, Alation's own claim): Alation docs say agents and tools hold no data permissions of their own and act as the caller on each run. [Source](https://documentation.alation.com/en/latest/agentstudio/security/identity-and-permissions.md), read 13 Nov 2026. - **alation-18** (Controls what an agent is told, Alation's own claim): Alation docs say two users on the same MCP server can see different tool lists and results because every request carries the user's identity. [Source](https://documentation.alation.com/en/latest/agentstudio/integrations/mcp/using-the-mcp-server.md), read 13 Nov 2026. - **alation-19** (Controls what an agent is told, Alation's own claim): Alation docs say a machine-to-machine OAuth app acts with the role set at creation, independent of any user, so a service-account agent is scoped to that role and not to the asking person. [Source](https://documentation.alation.com/en/latest/agentstudio/security/identity-and-permissions.md), read 13 Nov 2026. - **alation-20** (Controls what an agent is told, Alation's own claim): Alation docs say tool approvals are not enforced over MCP and each client must enforce its own tool restrictions. [Source](https://documentation.alation.com/en/latest/agentstudio/integrations/mcp/using-the-mcp-server.md), read 13 Nov 2026. - **alation-21** (Controls what an agent is told, Alation's own claim): Alation says access and masking rules attach to the metric definition and apply the same way to a person or an agent (marketing page; Policy Center docs separately show masking only for Snowflake data policies). [Source](https://www.alation.com/solutions/governed-ai-bi/), read 13 Nov 2026. - **alation-22** (Profile, Alation's own claim): Alation docs say trust flags apply to BI objects (servers, reports, datasources, folders and columns) as well as RDBMS, file system and document objects. [Source](https://documentation.alation.com/en/latest/governance/UseTrustFlags/index.md), read 13 Nov 2026. - **alation-23** (Profile, Alation's own claim): Alation says Semantic Model Mastering writes governed metric definitions back into Snowflake and Databricks semantic layers. [Source](https://www.alation.com/solutions/governed-ai-bi/), read 13 Nov 2026. - **alation-24** (Profile, Alation's own claim): Alation docs say a deprecation on a table or BI object puts an Important Info flag on lineage-connected tables and BI objects, and removing the deprecation removes the propagated flags; the flag is a copy and new children do not get it. [Source](https://documentation.alation.com/en/latest/governance/UseTrustFlags/index.md), read 13 Nov 2026. - **alation-25** (Profile, Alation's own claim): Alation docs say Data Quality monitors can run on an internal schedule or be run from pipelines through the Data Quality SDK. [Source](https://documentation.alation.com/en/latest/AlationDataQuality/index.md), read 13 Nov 2026. - **alation-26** (Profile, Alation's own claim): Alation says version-aware lineage closes stale links automatically and monitors surface missing links. [Source](https://www.alation.com/product/data-lineage/), read 13 Nov 2026. - **alation-27** (Evidence beyond the vendor, third-party): Databricks Partner Connect lists Alation as a partner integration for finding, understanding and trusting lakehouse data. [Source](https://www.databricks.com/partnerconnect), read 13 Nov 2026. - **alation-28** (Evidence beyond the vendor, third-party): A GE Healthcare reviewer on PeerSpot gives a positive account of Alation Data Catalog pricing, setup and licensing discussions. [Source](https://www.peerspot.com/products/alation-pricing), read 13 Nov 2026. - **alation-29** (Evidence beyond the vendor, Alation's own claim): Alation cites Brambles (named customer) on its governance page; this is a vendor-published story. [Source](https://www.alation.com/solutions/agentic-data-governance/), read 13 Nov 2026. - **alation-30** (Price transparency, none-found): None found on 2026-11-13: a published price list or plan prices, in https://www.alation.com/pricing/ (page is a contact form titled Start a Conversation). Searched: https://www.alation.com/pricing/, read 13 Nov 2026. - **alation-31** (Price transparency, Alation's own claim): Alation docs say AI products are sold as a pool of Alation Consumption Units (ACUs) instead of seats or tiers; the docs show ACU rates (for example 0.25 ACU per Agent Studio tool call) but no dollar price per ACU. [Source](https://documentation.alation.com/en/latest/admins/admin-settings-acs/consumption/index.md), read 13 Nov 2026. - **alation-32** (Follows sensitive data into BI, Alation's own claim): Alation docs say Tableau lineage can show links from warehouse table columns to BI report fields in Tableau views (column-level lineage on by default from 2024.1.5). [Source](https://documentation.alation.com/en/latest/OpenConnectorFramework/BIConnectors/TableauOCFConnector/TableauServerandOnlineConnectorConfigureLineage.md), read 13 Nov 2026. - **alation-33** (Follows sensitive data into BI, Alation's own claim): Alation docs describe cross-source and column-level lineage for the Power BI Scanner connector, with supported expressions and limitations. [Source](https://documentation.alation.com/en/latest/OpenConnectorFramework/BIConnectors/PowerBIScannerOCFConnector/PowerBIScannerConnectorConfigLineage.md), read 13 Nov 2026. - **alation-34** (Follows sensitive data into BI, Alation's own claim): Alation docs describe cross-system and column-level lineage between Looker and supported RDBMS sources. [Source](https://documentation.alation.com/en/latest/OpenConnectorFramework/BIConnectors/Looker/LookerConfigureLineage.md), read 13 Nov 2026. - **alation-35** (Follows sensitive data into BI, Alation's own claim): Alation docs describe lineage extraction for dbt Cloud and dbt Core through the dbt Gen2 connector. [Source](https://documentation.alation.com/en/latest/OpenConnectorFramework/ELTConnectors/dbtOCFConnector/dbtOCFConnectorConfigLineage.md), read 13 Nov 2026. - **alation-36** (Carries classification downstream, Alation's own claim): Alation docs say curation propagation copies a curated custom-field value (for example Sensitive) up or down the catalog hierarchy (schema, table, column); the docs describe the hierarchy, not lineage, for this feature. [Source](https://documentation.alation.com/en/latest/governance/OutcomeBasedGovernance/CurationPropagation/index.md), read 13 Nov 2026. - **alation-37** (Carries classification downstream, Alation's own claim): Alation docs say Snowflake tags can be brought into Alation to track sensitive data and used as search filters; tags must be created in Snowflake first. [Source](https://documentation.alation.com/en/latest/governance/SnowflakeTags/index.md), read 13 Nov 2026. - **alation-38** (Carries classification downstream, Alation's own claim): Alation says its curation agents classify sensitive data using catalog context, source comments and reference documentation, with a confidence score. [Source](https://www.alation.com/solutions/agentic-data-governance/), read 13 Nov 2026. - **alation-39** (Carries classification downstream, none-found): None found on 2026-11-13: a feature that carries a sensitivity or PII label along column-level lineage into BI fields, in the Curation Propagation, Snowflake Tags and Curation Automation docs (hierarchy and tag import are described; lineage propagation is described only for deprecation flags). Searched: https://documentation.alation.com/en/latest/governance/OutcomeBasedGovernance/CurationPropagation/index.md, read 13 Nov 2026. - **alation-40** (Acts on it, Alation's own claim): Alation docs say Data Quality webhooks send check and anomaly state changes to systems such as PagerDuty, Jira and Slack. [Source](https://documentation.alation.com/en/latest/AlationDataQuality/WebhooksChecksAnomalies.md), read 13 Nov 2026. - **alation-41** (Acts on it, Alation's own claim): Alation docs say the Policy Center can show masked values in data samples to authorized users only (Snowflake data policies are extracted, not authored in Alation). [Source](https://docs.alation.com/en/latest/steward/PolicyCenter/index.html), read 13 Nov 2026. - **alation-42** (Coverage of the stack, none-found): None found on 2026-11-13: named integrations with security or classification tools such as BigID, Immuta, Securiti or Varonis, in the documentation.alation.com llms.txt index and connector pages. Searched: https://documentation.alation.com/llms.txt, read 13 Nov 2026. - **alation-43** (Shows who actually saw it, Alation's own claim): Alation docs say Tableau report popularity comes from Tableau view counts, which count views but do not name viewers. [Source](https://documentation.alation.com/en/latest/OpenConnectorFramework/BIConnectors/TableauOCFConnector/TableauOCFPopularity.md), read 13 Nov 2026. - **alation-44** (Shows who actually saw it, Alation's own claim): Alation docs say query log ingestion adds popularity and top users to catalog pages (database query activity, not report viewers). [Source](https://documentation.alation.com/en/latest/OpenConnectorFramework/DiscoverMetadata/ConfigureQueryLogIngestion.md), read 13 Nov 2026. - **alation-45** (Shows who actually saw it, Alation's own claim): Alation docs say each Agent Studio tool call is attributed to an identity (user, Slack-linked user, or system account), and the Usage page shows per-user tool call counts. [Source](https://documentation.alation.com/en/latest/agentstudio/security/observability/usage.md), read 13 Nov 2026. - **alation-46** (Evidence beyond the vendor, observed): The public PyPI registry lists alation-ai-agent-sdk 1.0.0 as a Python library for AI agents to read Alation catalog metadata, and records the 1.0.0 upload on 2026-10-26. [Source](https://pypi.org/project/alation-ai-agent-sdk/), read 13 Nov 2026. ## Compare Alation - [The full index](/index/) ## Sources - https://www.alation.com/our-story/: https://www.alation.com/our-story/ (read 13 Nov 2026) - https://www.alation.com/aios/catalog/: https://www.alation.com/aios/catalog/ (read 13 Nov 2026) - https://www.alation.com/aios/connectors-and-sdks/: https://www.alation.com/aios/connectors-and-sdks/ (read 13 Nov 2026) - https://www.alation.com/pricing/: https://www.alation.com/pricing/ (read 13 Nov 2026) - https://www.alation.com/legal/security/: https://www.alation.com/legal/security/ (read 13 Nov 2026) - https://documentation.alation.com/en/latest/governance/OutcomeBasedGovernance/CurationAutomation/index.md: https://documentation.alation.com/en/latest/governance/OutcomeBasedGovernance/CurationAutomation/index.md (read 13 Nov 2026) - https://documentation.alation.com/en/latest/governance/OutcomeBasedGovernance/CurationAutomation/CurationAutomationFAQ.md: https://documentation.alation.com/en/latest/governance/OutcomeBasedGovernance/CurationAutomation/CurationAutomationFAQ.md (read 13 Nov 2026) - https://documentation.alation.com/en/latest/governance/UseTrustFlags/index.md: https://documentation.alation.com/en/latest/governance/UseTrustFlags/index.md (read 13 Nov 2026) - https://documentation.alation.com/en/latest/governance/CatalogSets/ManageCatalogSets.md: https://documentation.alation.com/en/latest/governance/CatalogSets/ManageCatalogSets.md (read 13 Nov 2026) - https://www.alation.com/solutions/agentic-data-governance/: https://www.alation.com/solutions/agentic-data-governance/ (read 13 Nov 2026) - https://www.alation.com/product/data-quality/: https://www.alation.com/product/data-quality/ (read 13 Nov 2026) - https://docs.alation.com/en/latest/OpenConnectorFramework/DiscoverMetadata/DataPopularity.html: https://docs.alation.com/en/latest/OpenConnectorFramework/DiscoverMetadata/DataPopularity.html (read 13 Nov 2026) - https://documentation.alation.com/en/latest/agentstudio/build/tools/get-dq-scores-tool.md: https://documentation.alation.com/en/latest/agentstudio/build/tools/get-dq-scores-tool.md (read 13 Nov 2026) - https://documentation.alation.com/en/latest/agentstudio/integrations/mcp/quick-start.md: https://documentation.alation.com/en/latest/agentstudio/integrations/mcp/quick-start.md (read 13 Nov 2026) - https://github.com/Alation/alation-ai-agent-sdk/releases: https://github.com/Alation/alation-ai-agent-sdk/releases (read 13 Nov 2026) - https://documentation.alation.com/en/latest/agentstudio/security/identity-and-permissions.md: https://documentation.alation.com/en/latest/agentstudio/security/identity-and-permissions.md (read 13 Nov 2026) - https://documentation.alation.com/en/latest/agentstudio/integrations/mcp/using-the-mcp-server.md: https://documentation.alation.com/en/latest/agentstudio/integrations/mcp/using-the-mcp-server.md (read 13 Nov 2026) - https://www.alation.com/solutions/governed-ai-bi/: https://www.alation.com/solutions/governed-ai-bi/ (read 13 Nov 2026) - https://documentation.alation.com/en/latest/AlationDataQuality/index.md: https://documentation.alation.com/en/latest/AlationDataQuality/index.md (read 13 Nov 2026) - https://www.alation.com/product/data-lineage/: https://www.alation.com/product/data-lineage/ (read 13 Nov 2026) - https://www.databricks.com/partnerconnect: https://www.databricks.com/partnerconnect (read 13 Nov 2026) - https://www.peerspot.com/products/alation-pricing: https://www.peerspot.com/products/alation-pricing (read 13 Nov 2026) - https://documentation.alation.com/en/latest/admins/admin-settings-acs/consumption/index.md: https://documentation.alation.com/en/latest/admins/admin-settings-acs/consumption/index.md (read 13 Nov 2026) - https://documentation.alation.com/en/latest/OpenConnectorFramework/BIConnectors/TableauOCFConnector/TableauServerandOnlineConnectorConfigureLineage.md: https://documentation.alation.com/en/latest/OpenConnectorFramework/BIConnectors/TableauOCFConnector/TableauServerandOnlineConnectorConfigureLineage.md (read 13 Nov 2026) - https://documentation.alation.com/en/latest/OpenConnectorFramework/BIConnectors/PowerBIScannerOCFConnector/PowerBIScannerConnectorConfigLineage.md: https://documentation.alation.com/en/latest/OpenConnectorFramework/BIConnectors/PowerBIScannerOCFConnector/PowerBIScannerConnectorConfigLineage.md (read 13 Nov 2026) - https://documentation.alation.com/en/latest/OpenConnectorFramework/BIConnectors/Looker/LookerConfigureLineage.md: https://documentation.alation.com/en/latest/OpenConnectorFramework/BIConnectors/Looker/LookerConfigureLineage.md (read 13 Nov 2026) - https://documentation.alation.com/en/latest/OpenConnectorFramework/ELTConnectors/dbtOCFConnector/dbtOCFConnectorConfigLineage.md: https://documentation.alation.com/en/latest/OpenConnectorFramework/ELTConnectors/dbtOCFConnector/dbtOCFConnectorConfigLineage.md (read 13 Nov 2026) - https://documentation.alation.com/en/latest/governance/OutcomeBasedGovernance/CurationPropagation/index.md: https://documentation.alation.com/en/latest/governance/OutcomeBasedGovernance/CurationPropagation/index.md (read 13 Nov 2026) - https://documentation.alation.com/en/latest/governance/SnowflakeTags/index.md: https://documentation.alation.com/en/latest/governance/SnowflakeTags/index.md (read 13 Nov 2026) - https://documentation.alation.com/en/latest/AlationDataQuality/WebhooksChecksAnomalies.md: https://documentation.alation.com/en/latest/AlationDataQuality/WebhooksChecksAnomalies.md (read 13 Nov 2026) - https://docs.alation.com/en/latest/steward/PolicyCenter/index.html: https://docs.alation.com/en/latest/steward/PolicyCenter/index.html (read 13 Nov 2026) - https://documentation.alation.com/llms.txt: https://documentation.alation.com/llms.txt (read 13 Nov 2026) - https://documentation.alation.com/en/latest/OpenConnectorFramework/BIConnectors/TableauOCFConnector/TableauOCFPopularity.md: https://documentation.alation.com/en/latest/OpenConnectorFramework/BIConnectors/TableauOCFConnector/TableauOCFPopularity.md (read 13 Nov 2026) - https://documentation.alation.com/en/latest/OpenConnectorFramework/DiscoverMetadata/ConfigureQueryLogIngestion.md: https://documentation.alation.com/en/latest/OpenConnectorFramework/DiscoverMetadata/ConfigureQueryLogIngestion.md (read 13 Nov 2026) - https://documentation.alation.com/en/latest/agentstudio/security/observability/usage.md: https://documentation.alation.com/en/latest/agentstudio/security/observability/usage.md (read 13 Nov 2026) - https://pypi.org/project/alation-ai-agent-sdk/: https://pypi.org/project/alation-ai-agent-sdk/ (read 13 Nov 2026) Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/platforms/alation/ --- # Select Star for AI data governance: rank 8 of 16, at 53.5 of 100 PLATFORM PROFILE, read 13 Nov 2026 **The short answer.** Select Star ranks 8 of 16 on the Need to Know index at 53.5 of 100, read 13 Nov 2026. Its best criterion is Evidence beyond the vendor at 9 of 10, and its weakest is Controls what an agent is told at 2. The exposure map records 2 of six stages as documented and 4 as partial. - **Category:** Data catalog, column-level lineage and metadata platform (acquired by Snowflake) - **Status:** Exists under this name on 13 Nov 2026: selectstar.com home page shows 'Select Star is now a part of Snowflake' and the CEO post dated 24 Nov 2025 says Snowflake announced plans to acquire it; docs.selectstar.com did not resolve (HTTP 404), so docs were read from web.archive.org snapshots (2026). - **Exposure trail:** Warehouse column: partial; Transformation: partial; BI field: documented; Report: documented; Viewer: partial; Agent: partial - **Warehouses named:** Snowflake, Databricks, BigQuery, Amazon Redshift, PostgreSQL, Microsoft SQL Server (beta), MySQL (beta), Oracle (beta), Salesforce (beta), IBM Db2 (beta), AWS Glue - **BI tools named:** Tableau, Microsoft Power BI, Looker, Looker Studio, Mode, Sigma, Sisense / Periscope, Metabase, ThoughtSpot, Amazon QuickSight, Hex, Salesforce CRM Analytics (beta) - **Security tools named:** none found on 13 Nov 2026 - **Rank and total:** 8 of 16, 53.5 of 100 2 of 6 stages documented, 4 partial ## Select Star on the eight criteria | Criterion | Weight | Score | Why | | --- | --- | --- | --- | | Follows sensitive data into BI | 25 | 7 | Column-level lineage from warehouse through SQL parsing into Looker, Tableau, Sigma and Power BI is vendor-documented; press quotes only the CEO on lineage, so capped at 7. | | Controls what an agent is told | 20 | 2 | MCP uses a long-lived API token and Ask AI sees all assets by default; per-asker filtering was none found on 2026-11-13. | | Shows who actually saw it | 15 | 6 | Top users per table and per dashboard from query history and views; no agent log found, and BI-tool viewers are not listed. | | Carries classification downstream | 15 | 6 | PII tags are suggested along lineage with dbt tag sync and Snowflake write-back, but rules are name-based and need a person to confirm. | | Acts on it | 10 | 5 | PII masking in its own UI and downstream integrations plus notifications; tickets and access blocking were none found. | | Coverage of the stack | 5 | 6 | Many warehouses, dbt, Airflow and twelve BI tools, with several in beta; security tool label import was none found. | | Evidence beyond the vendor | 5 | 9 | Press, a partner announcement, an observability roundup and an open catalog list independently describe the product. | | Price transparency | 5 | 3 | Usage-based plans sized by sources, users and tables are described on an archived page; no dollar amounts, and the page is gone. | Blind scores for Select Star, 0 to 10. A vendor claim scores at most 7 until a second source confirms it. ## Where Select Star is strongest Vendor-stated: Documents column-level lineage from source views to Looker and Sigma assets, lineage and provenance for Tableau and Power BI, and top users per dashboard. ## Where Select Star falls short MCP and Ask AI access is instance-wide (token, scoped by source or folder), the docs show three roles and no per-asker filtering on agent calls, and PII rules match column names daily. ## Select Star along the exposure trail | Stage | Reading | Evidence | | --- | --- | --- | | [Warehouse column](/exposure-map/column/) | partial | Select Star docs say PII rules are regular expressions matched against column names and run once a day after metadata sync (name-based, not a scan of values). [Source](https://web.archive.org/web/2026/https://docs.selectstar.com/data-management/automated-pii-detection-beta), read 13 Nov 2026. | | [Transformation](/exposure-map/transformation/) | partial | Select Star docs say lineage is built by parsing SQL statements that ran in the source, which is how warehouse and transformation steps are linked. [Source](https://web.archive.org/web/20260715110406/https://docs.selectstar.com/llms-full.txt), read 13 Nov 2026. | | [BI field](/exposure-map/bi-field/) | documented | Select Star says its Looker integration gives column-level lineage from source views down to LookML views, explores and dashboards. [Source](https://www.selectstar.com/integrations/looker), read 13 Nov 2026. | | [Report](/exposure-map/report/) | documented | Select Star docs describe a Downstream Dashboards lineage view that lists every dependent dashboard with its top user and popularity. [Source](https://web.archive.org/web/20260715110406/https://docs.selectstar.com/llms-full.txt), read 13 Nov 2026. | | [Viewer](/exposure-map/viewer/) | partial | Select Star docs say a table's Top Users split into table users by query count and dashboard users by views or queries of directly downstream dashboards. [Source](https://web.archive.org/web/20260715110406/https://docs.selectstar.com/llms-full.txt), read 13 Nov 2026. | | [Agent](/exposure-map/agent/) | partial | Select Star docs say the Ask AI chatbot sees all data assets by default, and admins can narrow it by data source, schema or folder for the whole instance. [Source](https://web.archive.org/web/20260715110406/https://docs.selectstar.com/llms-full.txt), read 13 Nov 2026. | Documented, partial or none found on the read date. Vendor claims are the vendor's. ## Select Star in each situation | Situation | Rank | Total | Leader | | --- | --- | --- | --- | | [A regulated field](/best-for/regulated-field/) | 4 | 62.0 | Atlan 68.5 | | [Agents on analytics](/best-for/agents-on-analytics/) | 11 | 43.0 | Euno 66.0 | | [A Microsoft estate](/best-for/microsoft-estate/) | 4 | 57.5 | Atlan 68.5 | | [A mixed stack](/best-for/mixed-stack/) | 4 | 57.0 | Euno 68.5 | | [A lean team](/best-for/lean-team/) | 6 | 53.0 | Euno 62.5 | Each situation ranks the same scores under its own published weights. ## The evidence on Select Star, fact by fact - **select-star-01** (Profile, Select Star's own claim): Select Star's home page says Select Star is now part of Snowflake. [Source](https://www.selectstar.com/), read 13 Nov 2026. - **select-star-02** (Profile, Select Star's own claim): The Select Star CEO wrote on 2025-11-24 that Snowflake announced plans to acquire the Select Star platform (announced, per this post; the home page now says it is part of Snowflake). [Source](https://www.selectstar.com/resources/snowflake-acquire-select-star), read 13 Nov 2026. - **select-star-03** (Follows sensitive data into BI, Select Star's own claim): Select Star says its lineage tracks data models and BI dashboards with provenance back to source systems. [Source](https://www.selectstar.com/product/data-lineage), read 13 Nov 2026. - **select-star-04** (Follows sensitive data into BI, Select Star's own claim): Select Star docs say lineage is built by parsing SQL statements that ran in the source, which is how warehouse and transformation steps are linked. [Source](https://web.archive.org/web/20260715110406/https://docs.selectstar.com/llms-full.txt), read 13 Nov 2026. - **select-star-05** (Follows sensitive data into BI, Select Star's own claim): Select Star docs describe a Downstream Dashboards lineage view that lists every dependent dashboard with its top user and popularity. [Source](https://web.archive.org/web/20260715110406/https://docs.selectstar.com/llms-full.txt), read 13 Nov 2026. - **select-star-06** (Follows sensitive data into BI, Select Star's own claim): Select Star says its Looker integration gives column-level lineage from source views down to LookML views, explores and dashboards. [Source](https://www.selectstar.com/integrations/looker), read 13 Nov 2026. - **select-star-07** (Follows sensitive data into BI, Select Star's own claim): Select Star says its Tableau integration tracks data models and Tableau dashboards, and their provenance, back to source systems. [Source](https://www.selectstar.com/integrations/tableau), read 13 Nov 2026. - **select-star-08** (Follows sensitive data into BI, Select Star's own claim): Select Star says its Sigma integration gives column-level lineage from source views to workbooks and elements. [Source](https://www.selectstar.com/integrations), read 13 Nov 2026. - **select-star-09** (Follows sensitive data into BI, Select Star's own claim): Select Star docs say connecting Power BI enables metadata, lineage and popularity for Power BI (setup needs Entra ID and Fabric admin access). [Source](https://web.archive.org/web/20260715110406/https://docs.selectstar.com/llms-full.txt), read 13 Nov 2026. - **select-star-10** (Follows sensitive data into BI, Select Star's own claim): Select Star docs say lineage refreshes about every 24 hours, and lineage is removed only when a new DDL statement is detected. [Source](https://web.archive.org/web/20260715110406/https://docs.selectstar.com/llms-full.txt), read 13 Nov 2026. - **select-star-11** (Carries classification downstream, Select Star's own claim): Select Star says its lineage powers automation that propagates PII classification tags. [Source](https://www.selectstar.com/product/data-lineage), read 13 Nov 2026. - **select-star-12** (Carries classification downstream, Select Star's own claim): Select Star's Data Access Control page says it tags PII automatically and propagates tags to related assets. [Source](https://www.selectstar.com/product/data-access-control), read 13 Nov 2026. - **select-star-13** (Carries classification downstream, Select Star's own claim): Select Star docs say tags are suggested (shown grey) from fields where data passes AS IS up or downstream, not applied as final tags without a person. [Source](https://web.archive.org/web/20260715110406/https://docs.selectstar.com/llms-full.txt), read 13 Nov 2026. - **select-star-14** (Carries classification downstream, Select Star's own claim): Select Star docs say PII rules are regular expressions matched against column names and run once a day after metadata sync (name-based, not a scan of values). [Source](https://web.archive.org/web/2026/https://docs.selectstar.com/data-management/automated-pii-detection-beta), read 13 Nov 2026. - **select-star-15** (Carries classification downstream, Select Star's own claim): Select Star docs say dbt tags are synced into Select Star and can be matched to Select Star tags, with PII tags linked as an example. [Source](https://web.archive.org/web/20260715110406/https://docs.selectstar.com/llms-full.txt), read 13 Nov 2026. - **select-star-16** (Carries classification downstream, Select Star's own claim): Select Star docs say Snowflake Tag Sync writes Select Star status and category tags, including suggested tags, back to Snowflake tables and columns. [Source](https://web.archive.org/web/20260715110406/https://docs.selectstar.com/llms-full.txt), read 13 Nov 2026. - **select-star-17** (Acts on it, Select Star's own claim): Select Star docs say a PII tag removes the value in memory from SQL queries that expose it, inside Select Star. [Source](https://web.archive.org/web/2026/https://docs.selectstar.com/data-management/sensitive-pii-data), read 13 Nov 2026. - **select-star-18** (Acts on it, Select Star's own claim): Select Star says PII-tagged fields are masked by default in its UI and downstream integrations, visible only to authorized roles. [Source](https://www.selectstar.com/product/data-access-control), read 13 Nov 2026. - **select-star-19** (Acts on it, Select Star's own claim): Select Star docs say downstream notifications can reach table users, dashboard users and owners when an update or breaking change is coming. [Source](https://web.archive.org/web/20260715110406/https://docs.selectstar.com/llms-full.txt), read 13 Nov 2026. - **select-star-20** (Acts on it, Select Star's own claim): Select Star docs describe AI Agents (private beta) that run daily to add or remove tags, assign owners and manage collections by natural-language rule; lineage filters only test whether lineage exists. [Source](https://web.archive.org/web/20260715110406/https://docs.selectstar.com/llms-full.txt), read 13 Nov 2026. - **select-star-21** (Acts on it, none-found): None found on 2026-11-13: ticket creation (for example Jira or ServiceNow) or blocking of data access on a sensitive column, in the Select Star docs integrations list (Slack is the only platform app listed besides search and notifications). Searched: https://web.archive.org/web/20260715110406/https://docs.selectstar.com/llms-full.txt, read 13 Nov 2026. - **select-star-22** (Shows who actually saw it, Select Star's own claim): Select Star docs say popularity is computed from query history: what is used, what is not, and who uses it. [Source](https://web.archive.org/web/20260715110406/https://docs.selectstar.com/llms-full.txt), read 13 Nov 2026. - **select-star-23** (Shows who actually saw it, Select Star's own claim): Select Star docs say a table's Top Users split into table users by query count and dashboard users by views or queries of directly downstream dashboards. [Source](https://web.archive.org/web/20260715110406/https://docs.selectstar.com/llms-full.txt), read 13 Nov 2026. - **select-star-24** (Shows who actually saw it, Select Star's own claim): Select Star docs say dashboard popularity is the number of views over 30 to 90 days, with a Top Users tab for each dashboard. [Source](https://web.archive.org/web/20260715110406/https://docs.selectstar.com/llms-full.txt), read 13 Nov 2026. - **select-star-25** (Shows who actually saw it, Select Star's own claim): Select Star docs say the top 25 users by dashboard views or queries can be notified; this is the closest documented list of who sees a report. [Source](https://web.archive.org/web/20260715110406/https://docs.selectstar.com/llms-full.txt), read 13 Nov 2026. - **select-star-26** (Shows who actually saw it, Select Star's own claim): Select Star docs say its own admin analytics cover only actions inside Select Star (activity log with CSV export), not who viewed a report in the BI tool. [Source](https://web.archive.org/web/20260715110406/https://docs.selectstar.com/llms-full.txt), read 13 Nov 2026. - **select-star-27** (Shows who actually saw it, none-found): None found on 2026-11-13: a log or report of which AI agent or MCP client called which asset and what it received, in the Select Star MCP Server and AI Agents docs. Searched: https://web.archive.org/web/20260715110406/https://docs.selectstar.com/llms-full.txt, read 13 Nov 2026. - **select-star-28** (Controls what an agent is told, Select Star's own claim): Select Star says its MCP Server gives agents descriptions, tags, owners and popularity scores for search, lineage and semantic models. [Source](https://www.selectstar.com/product/mcp-for-data), read 13 Nov 2026. - **select-star-29** (Controls what an agent is told, Select Star's own claim): Select Star docs list seven MCP tools, including metadata search and lineage traversal, authenticated with a Select Star API token in the request header. [Source](https://web.archive.org/web/20260715110406/https://docs.selectstar.com/llms-full.txt), read 13 Nov 2026. - **select-star-30** (Controls what an agent is told, Select Star's own claim): Select Star docs say API tokens have no expiration and are created in Account Settings, so the MCP connection uses a long-lived token. [Source](https://web.archive.org/web/2026/https://docs.selectstar.com/select-star-api/authentication), read 13 Nov 2026. - **select-star-31** (Controls what an agent is told, Select Star's own claim): Select Star docs say the Ask AI chatbot sees all data assets by default, and admins can narrow it by data source, schema or folder for the whole instance. [Source](https://web.archive.org/web/20260715110406/https://docs.selectstar.com/llms-full.txt), read 13 Nov 2026. - **select-star-32** (Controls what an agent is told, Select Star's own claim): Select Star docs say that in-app all users see the same metadata descriptions and query history (no per-person view). [Source](https://web.archive.org/web/2026/https://docs.selectstar.com/data-management/sensitive-pii-data), read 13 Nov 2026. - **select-star-33** (Controls what an agent is told, Select Star's own claim): Select Star docs say Ask AI sends metadata to OpenAI and Anthropic but not queries scrubbed under PII tags. [Source](https://web.archive.org/web/20260715110406/https://docs.selectstar.com/llms-full.txt), read 13 Nov 2026. - **select-star-34** (Controls what an agent is told, Select Star's own claim): Select Star docs define three roles (Viewer, Data Manager, Admin), while its marketing page claims role and attribute based access control. [Source](https://web.archive.org/web/2026/https://docs.selectstar.com/user-management/user-roles), read 13 Nov 2026. - **select-star-35** (Controls what an agent is told, Select Star's own claim): Select Star's Data Access Control page claims role-based and attribute-based view and edit permissions using classification tags. [Source](https://www.selectstar.com/product/data-access-control), read 13 Nov 2026. - **select-star-36** (Controls what an agent is told, none-found): None found on 2026-11-13: documentation that MCP tool results are filtered to the permissions of the person asking on each call, in the Select Star MCP Server docs. Searched: https://web.archive.org/web/20260715110406/https://docs.selectstar.com/llms-full.txt, read 13 Nov 2026. - **select-star-37** (Coverage of the stack, Select Star's own claim): Select Star docs say it connects to warehouses and BI tools to fetch metadata, query history and activity logs. [Source](https://web.archive.org/web/20260715110406/https://docs.selectstar.com/llms-full.txt), read 13 Nov 2026. - **select-star-38** (Coverage of the stack, none-found): None found on 2026-11-13: an integration that reads sensitivity labels from a security or classification tool (for example BigID, Securiti, Purview), in the Select Star docs integrations list. Searched: https://web.archive.org/web/20260715110406/https://docs.selectstar.com/llms-full.txt, read 13 Nov 2026. - **select-star-39** (Evidence beyond the vendor, third-party): Monte Carlo (a partner) announced an integration that shows Monte Carlo monitors on Select Star table pages. [Source](https://montecarlo.ai/blog-select-star-integration), read 13 Nov 2026. - **select-star-40** (Evidence beyond the vendor, third-party): Monte Carlo's data catalog roundup describes Select Star as automating lineage, ERDs and documentation or tag propagation. [Source](https://montecarlo.ai/blog-data-catalog-tools), read 13 Nov 2026. - **select-star-41** (Evidence beyond the vendor, observed): The public GitHub organization selectstar lists five repositories, none of them the catalog product (for example django-db-comments), so the code gives no evidence of product behavior. [Source](https://api.github.com/orgs/selectstar/repos?per_page=100), read 13 Nov 2026. - **select-star-42** (Evidence beyond the vendor, none-found): None found on 2026-11-13: a readable analyst page (Gartner Peer Insights, G2) or cloud marketplace listing naming Select Star, Snowflake's own press release returned HTTP 403 and the others were not reachable or not found. Searched: https://www.selectstar.com/, read 13 Nov 2026. - **select-star-43** (Price transparency, Select Star's own claim): Select Star's archived pricing page (2025-11-11) calls its pricing usage-based; plans are Growth and Enterprise sized by data sources, users and tables, with no dollar amounts. [Source](https://web.archive.org/web/20251111111859/https://www.selectstar.com/pricing), read 13 Nov 2026. - **select-star-44** (Price transparency, Select Star's own claim): Select Star's archived pricing FAQ says extra tables or users can be bought as overage after the base plan. [Source](https://web.archive.org/web/20251111111859/https://www.selectstar.com/pricing), read 13 Nov 2026. - **select-star-45** (Price transparency, none-found): None found on 2026-11-13: a current pricing page with prices, https://www.selectstar.com/pricing now returns the home page; the last archived pricing page (2025-11-11) shows no dollar amounts. Searched: https://www.selectstar.com/, read 13 Nov 2026. - **select-star-46** (Evidence beyond the vendor, third-party): TechCrunch (press, Jan 2023) reports that Select Star's platform reads metadata and logs from named warehouses and BI tools and that its CEO says it detects PII and builds column-level lineage. [Source](https://techcrunch.com/2023/01/31/select-star-closes-15m-round-to-add-context-to-disparate-data/), read 13 Nov 2026. - **select-star-47** (Evidence beyond the vendor, observed): The public open-source awesome-data-catalogs list on GitHub (Open Data Discovery project) describes Select Star and marks column-level lineage as supported. [Source](https://raw.githubusercontent.com/opendatadiscovery/awesome-data-catalogs/main/README.md), read 13 Nov 2026. ## Compare Select Star - [The full index](/index/) ## Sources - https://www.selectstar.com/: https://www.selectstar.com/ (read 13 Nov 2026) - https://www.selectstar.com/resources/snowflake-acquire-select-star: https://www.selectstar.com/resources/snowflake-acquire-select-star (read 13 Nov 2026) - https://www.selectstar.com/product/data-lineage: https://www.selectstar.com/product/data-lineage (read 13 Nov 2026) - https://web.archive.org/web/20260715110406/https://docs.selectstar.com/llms-full.txt: https://web.archive.org/web/20260715110406/https://docs.selectstar.com/llms-full.txt (read 13 Nov 2026) - https://www.selectstar.com/integrations/looker: https://www.selectstar.com/integrations/looker (read 13 Nov 2026) - https://www.selectstar.com/integrations/tableau: https://www.selectstar.com/integrations/tableau (read 13 Nov 2026) - https://www.selectstar.com/integrations: https://www.selectstar.com/integrations (read 13 Nov 2026) - https://www.selectstar.com/product/data-access-control: https://www.selectstar.com/product/data-access-control (read 13 Nov 2026) - https://web.archive.org/web/2026/https://docs.selectstar.com/data-management/automated-pii-detection-beta: https://web.archive.org/web/2026/https://docs.selectstar.com/data-management/automated-pii-detection-beta (read 13 Nov 2026) - https://web.archive.org/web/2026/https://docs.selectstar.com/data-management/sensitive-pii-data: https://web.archive.org/web/2026/https://docs.selectstar.com/data-management/sensitive-pii-data (read 13 Nov 2026) - https://www.selectstar.com/product/mcp-for-data: https://www.selectstar.com/product/mcp-for-data (read 13 Nov 2026) - https://web.archive.org/web/2026/https://docs.selectstar.com/select-star-api/authentication: https://web.archive.org/web/2026/https://docs.selectstar.com/select-star-api/authentication (read 13 Nov 2026) - https://web.archive.org/web/2026/https://docs.selectstar.com/user-management/user-roles: https://web.archive.org/web/2026/https://docs.selectstar.com/user-management/user-roles (read 13 Nov 2026) - https://montecarlo.ai/blog-select-star-integration: https://montecarlo.ai/blog-select-star-integration (read 13 Nov 2026) - https://montecarlo.ai/blog-data-catalog-tools: https://montecarlo.ai/blog-data-catalog-tools (read 13 Nov 2026) - https://api.github.com/orgs/selectstar/repos?per_page=100: https://api.github.com/orgs/selectstar/repos?per_page=100 (read 13 Nov 2026) - https://web.archive.org/web/20251111111859/https://www.selectstar.com/pricing: https://web.archive.org/web/20251111111859/https://www.selectstar.com/pricing (read 13 Nov 2026) - https://techcrunch.com/2023/01/31/select-star-closes-15m-round-to-add-context-to-disparate-data/: https://techcrunch.com/2023/01/31/select-star-closes-15m-round-to-add-context-to-disparate-data/ (read 13 Nov 2026) - https://raw.githubusercontent.com/opendatadiscovery/awesome-data-catalogs/main/README.md: https://raw.githubusercontent.com/opendatadiscovery/awesome-data-catalogs/main/README.md (read 13 Nov 2026) Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/platforms/select-star/ --- # Secoda for AI data governance: rank 9 of 16, at 47.5 of 100 PLATFORM PROFILE, read 13 Nov 2026 **The short answer.** Secoda ranks 9 of 16 on the Need to Know index at 47.5 of 100, read 13 Nov 2026. Its best criterion is Evidence beyond the vendor at 9 of 10, and its weakest is Shows who actually saw it at 3. The exposure map records 1 of six stages as documented and 5 as partial. - **Category:** Data catalog, governance and AI analytics platform, now part of Atlassian - **Status:** Exists under this name on 13 Nov 2026: secoda.co and docs.secoda.co are live under the Secoda name, and Secoda's own blog post 'Atlassian acquires Secoda' says Secoda has been acquired by Atlassian and customers' experience will not change for now (secoda-40, secoda-41, secoda-42). - **Exposure trail:** Warehouse column: documented; Transformation: partial; BI field: partial; Report: partial; Viewer: partial; Agent: partial - **Warehouses named:** Snowflake, BigQuery, Databricks, Redshift, Azure Synapse, ClickHouse, MotherDuck, Apache Hive - **BI tools named:** Tableau, Looker, Looker Studio, Power BI, Metabase, Mode, Sigma, ThoughtSpot, QuickSight, Superset, Hex, Omni, MicroStrategy One - **Security tools named:** Cyera - **Rank and total:** 9 of 16, 47.5 of 100 1 of 6 stages documented, 5 partial ## Secoda on the eight criteria | Criterion | Weight | Score | Why | | --- | --- | --- | --- | | Follows sensitive data into BI | 25 | 6 | Column lineage and impact analysis from warehouse column to Looker and Tableau dashboards, and dbt manifest support; only those two BI tools. | | Controls what an agent is told | 20 | 4 | Docs say operations respect access controls and team permissions, but the MCP server forwards one API token per tool call. | | Shows who actually saw it | 15 | 3 | Resource pages show query counts, frequent users and Power BI view counts; per-viewer lists were none found on 2026-11-13. | | Carries classification downstream | 15 | 4 | Retrieves Cyera sensitivity tags and propagates metadata up to four levels, but own PII detection is keyword-based and lineage is not named. | | Acts on it | 10 | 5 | Policy issues link to Jira and automations tag classifications; PII is left out of previews, and no masking or blocking is shown. | | Coverage of the stack | 5 | 6 | Warehouses, dbt, thirteen BI tools and Cyera are named; few other security tools. | | Evidence beyond the vendor | 5 | 9 | Diginomica and TechCrunch name customers and integrations, and a data observability vendor lists it as a catalog integration. | | Price transparency | 5 | 3 | Three plans with feature lists are published but no dollar amounts; the page says contact us. | Blind scores for Secoda, 0 to 10. A vendor claim scores at most 7 until a second source confirms it. ## Where Secoda is strongest Vendor-stated: Column-level lineage runs from warehouse column to Tableau or Looker dashboards, PII is found by column-name keywords, Cyera sensitivity tags are ingested, and PII columns are kept out of previews. ## Where Secoda falls short Column-level lineage into BI is documented only for Looker and Tableau, and no per-viewer report log or per-agent record of sensitive columns was found. ## Secoda along the exposure trail | Stage | Reading | Evidence | | --- | --- | --- | | [Warehouse column](/exposure-map/column/) | documented | Secoda docs say PII is found by matching column-name keywords, which an admin can customize. [Source](https://docs.secoda.co/resource-and-metadata-management/tags/auto-pii-tagging.md), read 13 Nov 2026. | | [Transformation](/exposure-map/transformation/) | partial | Secoda docs say lineage is built automatically from SQL queries, and dbt's manifest.json is used to widen coverage. [Source](https://docs.secoda.co/features/data-lineage.md), read 13 Nov 2026. | | [BI field](/exposure-map/bi-field/) | partial | Secoda docs say column-level lineage into BI tools is currently supported only for Looker and Tableau. [Source](https://docs.secoda.co/features/data-lineage.md), read 13 Nov 2026. | | [Report](/exposure-map/report/) | partial | Secoda docs say a user can run impact analysis from a warehouse column to the affected dashboard or chart, for Looker and Tableau only. [Source](https://docs.secoda.co/features/data-lineage.md), read 13 Nov 2026. | | [Viewer](/exposure-map/viewer/) | partial | Secoda docs say a catalog resource shows the number of queries run and its frequent users. [Source](https://docs.secoda.co/features/popularity.md), read 13 Nov 2026. | | [Agent](/exposure-map/agent/) | partial | Secoda docs say its AI follows team-based permissions: a user asking about a team they are not in gets no results. [Source](https://docs.secoda.co/features/ai-assistant/security.md), read 13 Nov 2026. | Documented, partial or none found on the read date. Vendor claims are the vendor's. ## Secoda in each situation | Situation | Rank | Total | Leader | | --- | --- | --- | --- | | [A regulated field](/best-for/regulated-field/) | 9 | 49.5 | Atlan 68.5 | | [Agents on analytics](/best-for/agents-on-analytics/) | 10 | 43.0 | Euno 66.0 | | [A Microsoft estate](/best-for/microsoft-estate/) | 9 | 48.0 | Atlan 68.5 | | [A mixed stack](/best-for/mixed-stack/) | 8 | 49.0 | Euno 68.5 | | [A lean team](/best-for/lean-team/) | 9 | 47.0 | Euno 62.5 | Each situation ranks the same scores under its own published weights. ## The evidence on Secoda, fact by fact - **secoda-01** (Profile, Secoda's own claim): Secoda docs describe a rule-based automation that tags a resource Verified once it has both a complete description and an owner. [Source](https://docs.secoda.co/features/automations/automations-use-cases.md), read 13 Nov 2026. - **secoda-02** (Profile, Secoda's own claim): Secoda docs say Automations are rule-based, can update PII, tags, owners, descriptions and status, and can use AI to generate descriptions, tags and classification. [Source](https://docs.secoda.co/features/automations.md), read 13 Nov 2026. - **secoda-03** (Profile, Secoda's own claim): Secoda docs say an Automation can act on a table's Data Quality Score, for example marking a table Published and Verified when its score is Good. [Source](https://docs.secoda.co/features/data-quality-score.md), read 13 Nov 2026. - **secoda-04** (Profile, Secoda's own claim): Secoda docs say the Verified tag is a stamp of approval that influences search ranking and signals approval by stakeholders (a status a person can also set). [Source](https://docs.secoda.co/resource-and-metadata-management/tags/verified-tag.md), read 13 Nov 2026. - **secoda-05** (Profile, Secoda's own claim): Secoda docs say the Data Quality Score is built from stewardship, usability, freshness and accuracy, and accuracy reads Secoda Monitors or dbt, Monte Carlo and Great Expectations test results. [Source](https://docs.secoda.co/features/data-quality-score.md), read 13 Nov 2026. - **secoda-06** (Profile, Secoda's own claim): Secoda docs say the Data Quality Score checks that data freshness is within the expected period. [Source](https://docs.secoda.co/features/data-quality-score.md), read 13 Nov 2026. - **secoda-07** (Profile, Secoda's own claim): Secoda docs define popularity as queries or views in the last 24 hours, pulled from the source system. [Source](https://docs.secoda.co/features/popularity.md), read 13 Nov 2026. - **secoda-08** (Profile, Secoda's own claim): Secoda docs say its MCP server gives AI tools access to the catalog and that operations respect existing governance and access controls. [Source](https://docs.secoda.co/features/ai-assistant/secoda-mcp-server.md), read 13 Nov 2026. - **secoda-09** (Profile, Secoda's own claim): Secoda docs list the MCP tools: asset search, SQL, entity retrieval, lineage, glossary and charts; none is named for filtering by Verified status or quality score. [Source](https://docs.secoda.co/features/ai-assistant/secoda-mcp-server.md), read 13 Nov 2026. - **secoda-10** (Profile, observed): The Secoda MCP server code forwards a single API token as a bearer credential to the Secoda API on each tool call. [Source](https://raw.githubusercontent.com/secoda/secoda-mcp/main/server.py), read 13 Nov 2026. - **secoda-11** (Profile, Secoda's own claim): The secoda-mcp README says the API token needed by the MCP server can be generated by an admin at the Secoda API settings page. [Source](https://raw.githubusercontent.com/secoda/secoda-mcp/main/README.md), read 13 Nov 2026. - **secoda-12** (Profile, Secoda's own claim): Secoda docs say its AI follows team-based permissions: a user asking about a team they are not in gets no results. [Source](https://docs.secoda.co/features/ai-assistant/security.md), read 13 Nov 2026. - **secoda-13** (Profile, Secoda's own claim): Secoda docs say its scheduled AI agents are read-only and only analyze and report. [Source](https://docs.secoda.co/features/ai-assistant/secoda-ai-agents.md), read 13 Nov 2026. - **secoda-14** (Profile, Secoda's own claim): Secoda docs say column-level lineage into BI tools is currently supported only for Looker and Tableau. [Source](https://docs.secoda.co/features/data-lineage.md), read 13 Nov 2026. - **secoda-15** (Profile, Secoda's own claim): Secoda docs list Tableau lineage from Tableau fields to columns in other sources and from datasources to workbooks, sheets and dashboards. [Source](https://docs.secoda.co/integrations/data-visualization-tools/tableau-integration/metadata-extracted.md), read 13 Nov 2026. - **secoda-16** (Profile, Secoda's own claim): Secoda docs say dbt is a secondary integration that adds metadata to warehouse tables already connected. [Source](https://docs.secoda.co/integrations/data-transformation-tools/readme-1/dbt/metadata-extracted.md), read 13 Nov 2026. - **secoda-17** (Profile, Secoda's own claim): Secoda docs say an Automation can run on an hourly, daily or weekly schedule or a cron expression, and can also fire on schema changes. [Source](https://docs.secoda.co/features/automations.md), read 13 Nov 2026. - **secoda-18** (Profile, Secoda's own claim): Secoda docs say a policy issue is removed from the active list automatically once the resource complies. [Source](https://docs.secoda.co/features/policies.md), read 13 Nov 2026. - **secoda-19** (Profile, Secoda's own claim): Secoda docs say monitors alert when a freshness or other measure leaves its expected range, with automatic thresholds that take days to learn. [Source](https://docs.secoda.co/features/monitoring.md), read 13 Nov 2026. - **secoda-20** (Evidence beyond the vendor, third-party): Diginomica, a trade publication, reports Atlassian bought Secoda and names enterprise customers. [Source](https://diginomica.com/atlassian-acquires-secoda-democratize-enterprise-data-analysis-business-teams), read 13 Nov 2026. - **secoda-21** (Evidence beyond the vendor, observed): The public secoda-mcp GitHub repository describes the MCP server as built with FastMCP and carries an MIT license (created May 2025, last pushed January 2026 per the GitHub API). [Source](https://raw.githubusercontent.com/secoda/secoda-mcp/main/README.md), read 13 Nov 2026. - **secoda-22** (Evidence beyond the vendor, observed): A January 2026 commit in the secoda-mcp repository is signed off with an atlassian.com email address. [Source](https://github.com/secoda/secoda-mcp/commit/a3e32e9eb68355216929b51c48fcb8d22e621959), read 13 Nov 2026. - **secoda-23** (Price transparency, Secoda's own claim): Secoda's pricing page shows three plans (Core, Premium, Enterprise) with feature lists and no dollar amounts. [Source](https://www.secoda.co/pricing), read 13 Nov 2026. - **secoda-24** (Price transparency, none-found): None found on 2026-11-13: a published dollar price or per-seat price, in https://www.secoda.co/pricing (plans list features only; the page offers Contact us). Searched: https://www.secoda.co/pricing, read 13 Nov 2026. - **secoda-25** (Follows sensitive data into BI, Secoda's own claim): Secoda docs say a user can run impact analysis from a warehouse column to the affected dashboard or chart, for Looker and Tableau only. [Source](https://docs.secoda.co/features/data-lineage.md), read 13 Nov 2026. - **secoda-26** (Follows sensitive data into BI, Secoda's own claim): Secoda docs say lineage is built automatically from SQL queries, and dbt's manifest.json is used to widen coverage. [Source](https://docs.secoda.co/features/data-lineage.md), read 13 Nov 2026. - **secoda-27** (Controls what an agent is told, Secoda's own claim): Secoda docs say Run SQL for the AI needs an admin toggle and the asking user's query access on that integration. [Source](https://docs.secoda.co/features/ai-assistant/security.md), read 13 Nov 2026. - **secoda-28** (Controls what an agent is told, Secoda's own claim): Secoda docs say columns marked PII are left out of table Previews. [Source](https://docs.secoda.co/resource-and-metadata-management/tags/auto-pii-tagging.md), read 13 Nov 2026. - **secoda-29** (Shows who actually saw it, Secoda's own claim): Secoda docs say a catalog resource shows the number of queries run and its frequent users. [Source](https://docs.secoda.co/features/popularity.md), read 13 Nov 2026. - **secoda-30** (Shows who actually saw it, Secoda's own claim): Secoda's Power BI page lists report usage as a number of views extracted from Power BI. [Source](https://docs.secoda.co/integrations/data-visualization-tools/power-bi/metadata-extracted.md), read 13 Nov 2026. - **secoda-31** (Shows who actually saw it, none-found): None found on 2026-11-13: a per-viewer list of who opened each report in the source BI tool, or a log of which agent received which sensitive column, in https://docs.secoda.co/ (only counts and frequent users). Searched: https://docs.secoda.co/, read 13 Nov 2026. - **secoda-32** (Carries classification downstream, Secoda's own claim): Secoda docs say the Cyera integration retrieves sensitivity tags and tags matching resources in Secoda with the same classifications. [Source](https://docs.secoda.co/integrations/data-quality-tools/cyera.md), read 13 Nov 2026. - **secoda-33** (Carries classification downstream, Secoda's own claim): Secoda docs say an Automation can propagate metadata to child, parent or same-name resources, up to four levels. [Source](https://docs.secoda.co/features/automations.md), read 13 Nov 2026. - **secoda-34** (Carries classification downstream, Secoda's own claim): Secoda docs say PII is found by matching column-name keywords, which an admin can customize. [Source](https://docs.secoda.co/resource-and-metadata-management/tags/auto-pii-tagging.md), read 13 Nov 2026. - **secoda-35** (Acts on it, Secoda's own claim): Secoda docs say policy issues can be assigned and linked to a Jira ticket or external task. [Source](https://docs.secoda.co/features/policies.md), read 13 Nov 2026. - **secoda-36** (Acts on it, Secoda's own claim): Secoda docs give classification tagging (PII, PHI, Confidential) as an example policy, with non-compliant resources surfaced as issues. [Source](https://docs.secoda.co/features/policies.md), read 13 Nov 2026. - **secoda-37** (Acts on it, Secoda's own claim): Secoda's pricing page puts PII scanning and Policies in Premium and Access request management in Enterprise. [Source](https://www.secoda.co/pricing), read 13 Nov 2026. - **secoda-38** (Coverage of the stack, third-party): Diginomica says Secoda connects to sources and BI tools from Snowflake, BigQuery and MySQL to Tableau and Looker. [Source](https://diginomica.com/atlassian-acquires-secoda-democratize-enterprise-data-analysis-business-teams), read 13 Nov 2026. - **secoda-39** (Coverage of the stack, Secoda's own claim): Secoda's docs index lists data quality integrations Cyera, Dataplex, Great Expectations, Monte Carlo and Soda. [Source](https://docs.secoda.co/llms.txt), read 13 Nov 2026. - **secoda-40** (Profile, Secoda's own claim): Secoda's own blog says Secoda has been acquired by Atlassian and existing customers' experience will not change. [Source](https://www.secoda.co/blog/atlassian-acquires-secoda), read 13 Nov 2026. - **secoda-41** (Profile, Secoda's own claim): Secoda's blog says customers' experience will not change for now and infrastructure will migrate to Atlassian's cloud platform with timelines published in advance. [Source](https://www.secoda.co/blog/atlassian-acquires-secoda), read 13 Nov 2026. - **secoda-42** (Profile, Secoda's own claim): Secoda's homepage still operates under the Secoda name and banners the Atlassian acquisition. [Source](https://www.secoda.co/), read 13 Nov 2026. - **secoda-43** (Profile, Secoda's own claim): Secoda's changelog dates the MCP server launch to v8.12.0 on May 29, 2025. [Source](https://docs.secoda.co/changelog.md), read 13 Nov 2026. - **secoda-44** (Profile, Secoda's own claim): Secoda's changelog says v8.19.0 added AI Agents and an AI Automation block. [Source](https://docs.secoda.co/changelog.md), read 13 Nov 2026. - **secoda-45** (Evidence beyond the vendor, third-party): TechCrunch (2023) reports Secoda's funding round and names customers, including Remitly, Too Good to Go, Babylist and Y Combinator. [Source](https://techcrunch.com/2023/09/21/secoda-secures-16m-to-expand-its-data-cataloging-platform/), read 13 Nov 2026. - **secoda-46** (Evidence beyond the vendor, third-party): TechCrunch (2023) reports Secoda raised $14 million led by Craft Ventures, bringing total raised to $16 million at that date. [Source](https://techcrunch.com/2023/09/21/secoda-secures-16m-to-expand-its-data-cataloging-platform/), read 13 Nov 2026. - **secoda-47** (Coverage of the stack, third-party): Monte Carlo's integrations page lists Secoda as a catalog integration that surfaces Monte Carlo health signals in Secoda. [Source](https://www.montecarlodata.com/integrations/), read 13 Nov 2026. ## Compare Secoda - [The full index](/index/) ## Sources - https://docs.secoda.co/features/automations/automations-use-cases.md: https://docs.secoda.co/features/automations/automations-use-cases.md (read 13 Nov 2026) - https://docs.secoda.co/features/automations.md: https://docs.secoda.co/features/automations.md (read 13 Nov 2026) - https://docs.secoda.co/features/data-quality-score.md: https://docs.secoda.co/features/data-quality-score.md (read 13 Nov 2026) - https://docs.secoda.co/resource-and-metadata-management/tags/verified-tag.md: https://docs.secoda.co/resource-and-metadata-management/tags/verified-tag.md (read 13 Nov 2026) - https://docs.secoda.co/features/popularity.md: https://docs.secoda.co/features/popularity.md (read 13 Nov 2026) - https://docs.secoda.co/features/ai-assistant/secoda-mcp-server.md: https://docs.secoda.co/features/ai-assistant/secoda-mcp-server.md (read 13 Nov 2026) - https://raw.githubusercontent.com/secoda/secoda-mcp/main/server.py: https://raw.githubusercontent.com/secoda/secoda-mcp/main/server.py (read 13 Nov 2026) - https://raw.githubusercontent.com/secoda/secoda-mcp/main/README.md: https://raw.githubusercontent.com/secoda/secoda-mcp/main/README.md (read 13 Nov 2026) - https://docs.secoda.co/features/ai-assistant/security.md: https://docs.secoda.co/features/ai-assistant/security.md (read 13 Nov 2026) - https://docs.secoda.co/features/ai-assistant/secoda-ai-agents.md: https://docs.secoda.co/features/ai-assistant/secoda-ai-agents.md (read 13 Nov 2026) - https://docs.secoda.co/features/data-lineage.md: https://docs.secoda.co/features/data-lineage.md (read 13 Nov 2026) - https://docs.secoda.co/integrations/data-visualization-tools/tableau-integration/metadata-extracted.md: https://docs.secoda.co/integrations/data-visualization-tools/tableau-integration/metadata-extracted.md (read 13 Nov 2026) - https://docs.secoda.co/integrations/data-transformation-tools/readme-1/dbt/metadata-extracted.md: https://docs.secoda.co/integrations/data-transformation-tools/readme-1/dbt/metadata-extracted.md (read 13 Nov 2026) - https://docs.secoda.co/features/policies.md: https://docs.secoda.co/features/policies.md (read 13 Nov 2026) - https://docs.secoda.co/features/monitoring.md: https://docs.secoda.co/features/monitoring.md (read 13 Nov 2026) - https://diginomica.com/atlassian-acquires-secoda-democratize-enterprise-data-analysis-business-teams: https://diginomica.com/atlassian-acquires-secoda-democratize-enterprise-data-analysis-business-teams (read 13 Nov 2026) - https://github.com/secoda/secoda-mcp/commit/a3e32e9eb68355216929b51c48fcb8d22e621959: https://github.com/secoda/secoda-mcp/commit/a3e32e9eb68355216929b51c48fcb8d22e621959 (read 13 Nov 2026) - https://www.secoda.co/pricing: https://www.secoda.co/pricing (read 13 Nov 2026) - https://docs.secoda.co/resource-and-metadata-management/tags/auto-pii-tagging.md: https://docs.secoda.co/resource-and-metadata-management/tags/auto-pii-tagging.md (read 13 Nov 2026) - https://docs.secoda.co/integrations/data-visualization-tools/power-bi/metadata-extracted.md: https://docs.secoda.co/integrations/data-visualization-tools/power-bi/metadata-extracted.md (read 13 Nov 2026) - https://docs.secoda.co/: https://docs.secoda.co/ (read 13 Nov 2026) - https://docs.secoda.co/integrations/data-quality-tools/cyera.md: https://docs.secoda.co/integrations/data-quality-tools/cyera.md (read 13 Nov 2026) - https://docs.secoda.co/llms.txt: https://docs.secoda.co/llms.txt (read 13 Nov 2026) - https://www.secoda.co/blog/atlassian-acquires-secoda: https://www.secoda.co/blog/atlassian-acquires-secoda (read 13 Nov 2026) - https://www.secoda.co/: https://www.secoda.co/ (read 13 Nov 2026) - https://docs.secoda.co/changelog.md: https://docs.secoda.co/changelog.md (read 13 Nov 2026) - https://techcrunch.com/2023/09/21/secoda-secures-16m-to-expand-its-data-cataloging-platform/: https://techcrunch.com/2023/09/21/secoda-secures-16m-to-expand-its-data-cataloging-platform/ (read 13 Nov 2026) - https://www.montecarlodata.com/integrations/: https://www.montecarlodata.com/integrations/ (read 13 Nov 2026) Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/platforms/secoda/ --- # Collibra for AI data governance: rank 10 of 16, at 46.5 of 100 PLATFORM PROFILE, read 13 Nov 2026 **The short answer.** Collibra ranks 10 of 16 on the Need to Know index at 46.5 of 100, read 13 Nov 2026. Its best criterion is Evidence beyond the vendor at 8 of 10, and its weakest is Price transparency at 2. The exposure map records 1 of six stages as documented and 5 as partial. - **Category:** Data governance platform: catalog, lineage, data quality, data access and AI governance - **Status:** Exists under this name on 13 Nov 2026 (collibra.com homepage titled "The Enterprise AI Control Plane", docs release notes dated November 5, 2026, trust center and press releases through October 2026; acquisitions Raito, Deasy Labs and trail ML folded into the platform). - **Exposure trail:** Warehouse column: documented; Transformation: partial; BI field: partial; Report: partial; Viewer: partial; Agent: partial - **Warehouses named:** Snowflake, Databricks Unity Catalog, Google BigQuery, Amazon Redshift, Azure Synapse Analytics, Azure SQL Server, Microsoft SQL Server, Oracle, PostgreSQL, MySQL, Teradata, SAP HANA - **BI tools named:** Tableau, Power BI, Looker, Qlik, Sigma, ThoughtSpot, Strategy, SSRS-PBRS - **Security tools named:** Okta, Microsoft Entra ID - **Rank and total:** 10 of 16, 46.5 of 100 1 of 6 stages documented, 5 partial ## Collibra on the eight criteria | Criterion | Weight | Score | Why | | --- | --- | --- | --- | | Follows sensitive data into BI | 25 | 5 | Lineage sources span warehouses, dbt and many BI tools to report level, but column lineage is not generated for SQL-created tables. | | Controls what an agent is told | 20 | 5 | MCP tools use the authenticated user scopes and existing permissions, while guardian agents are a newly launched preview product. | | Shows who actually saw it | 15 | 3 | Lineage claims an access audit trail and a preview protect log covers source access, but no viewers per report or agent were found. | | Carries classification downstream | 15 | 3 | Automated classification and imported tags drive access policies, but automatic propagation along lineage was none found on 2026-11-13. | | Acts on it | 10 | 7 | Masking and row filters are applied from classifications and enforced in target systems, with data quality workflows handing off to Jira and ServiceNow. | | Coverage of the stack | 5 | 6 | Wide warehouses, dbt and eight BI tools are named; security tools are limited to identity providers Okta and Entra ID. | | Evidence beyond the vendor | 5 | 8 | Another company's open source policy engine lists it as a supported catalog and an independent connector exists on PyPI; analyst and customer claims are vendor-stated. | | Price transparency | 5 | 2 | Only a note that some tools use Units and one server is commercial; no pricing page or model was found on 2026-11-13. | Blind scores for Collibra, 0 to 10. A vendor claim scores at most 7 until a second source confirms it. ## Where Collibra is strongest Data Access applies masking and row filters on Snowflake, Databricks and BigQuery from data classifications, backed by lineage to reports and an MCP server that runs under user scopes. ## Where Collibra falls short No documented automatic propagation of classification along lineage, no viewers per BI report or agent, and the MCP column search cannot filter by classification tag. ## Collibra along the exposure trail | Stage | Reading | Evidence | | --- | --- | --- | | [Warehouse column](/exposure-map/column/) | documented | Collibra says automated classification labels data, including PII and PHI, and that it can generate descriptions for assets. [Source](https://www.collibra.com/products/data-catalog), read 13 Nov 2026. | | [Transformation](/exposure-map/transformation/) | partial | Collibra docs list the adapters that dbt lineage supports (including Snowflake, Databricks, Postgres, BigQuery, Redshift); the page does not mention snapshot nodes. [Source](https://web.archive.org/web/20260421071225/https://productresources.collibra.com/docs/collibra/latest/Content/CollibraDataLineage/DataSources/dbtCore/ref_dbt-core-supported-transformations.htm), read 13 Nov 2026. | | [BI field](/exposure-map/bi-field/) | partial | Collibra docs list supported lineage sources including warehouses (Snowflake, Databricks Unity Catalog, BigQuery), dbt and Looker, Power BI, Qlik, Sigma, Tableau and ThoughtSpot; the docs state column-level lineage is not generated for tables created by SQL statements. [Source](https://productresources.collibra.com/docs/collibra/latest/Content/CollibraDataLineage/ref_technical-lineage-supported-data-sources.htm), read 13 Nov 2026. | | [Report](/exposure-map/report/) | partial | Collibra says its lineage traces root causes and downstream impacts at table, column and report level. [Source](https://www.collibra.com/products/data-lineage), read 13 Nov 2026. | | [Viewer](/exposure-map/viewer/) | partial | Collibra docs say Usage Analytics shows behavioral data about users and popular resources inside Collibra; the page does not mention BI reports. [Source](https://productresources.collibra.com/docs/collibra/latest/Content/UsageAnalytics/to_usage-analytics.htm), read 13 Nov 2026. | | [Agent](/exposure-map/agent/) | partial | The chip README says tools work with the default scopes of any authenticated Collibra user, and a permission error means the connecting user lacks a scope such as dgc.ai-copilot or dgc.classify. [Source](https://github.com/collibra/chip), read 13 Nov 2026. | Documented, partial or none found on the read date. Vendor claims are the vendor's. ## Collibra in each situation | Situation | Rank | Total | Leader | | --- | --- | --- | --- | | [A regulated field](/best-for/regulated-field/) | 10 | 46.0 | Atlan 68.5 | | [Agents on analytics](/best-for/agents-on-analytics/) | 9 | 46.0 | Euno 66.0 | | [A Microsoft estate](/best-for/microsoft-estate/) | 10 | 47.0 | Atlan 68.5 | | [A mixed stack](/best-for/mixed-stack/) | 10 | 45.5 | Euno 68.5 | | [A lean team](/best-for/lean-team/) | 10 | 46.5 | Euno 62.5 | Each situation ranks the same scores under its own published weights. ## The evidence on Collibra, fact by fact - **collibra-01** (Profile, Collibra's own claim): Collibra says it positions itself as an enterprise AI control plane for context and control across sources, models and agents. [Source](https://www.collibra.com/), read 13 Nov 2026. - **collibra-02** (Profile, Collibra's own claim): Collibra announced it acquired Raito, a data access governance company, which underlies the Data Access product (masking and filtering). [Source](https://www.prnewswire.com/news-releases/collibra-announces-the-acquisition-of-raito-and-new-powerful-advancements-in-unified-governance-for-data-and-ai-across-every-data-citizen-302472460.html), read 13 Nov 2026. - **collibra-03** (Profile, Collibra's own claim): Collibra lists its compliance attestations on its trust center, including SOC 2, ISO 27001, ISO 42001 and FedRAMP. [Source](https://www.collibra.com/company/trust-center), read 13 Nov 2026. - **collibra-04** (Profile, Collibra's own claim): Collibra docs say workflows start automatically on events such as asset creation or an attribute value change, so a status or label change can be rule-driven, but the page does not describe certification workflows. [Source](https://developer.collibra.com/workflows/workflow-documentation/Content/Workflows/ref_what-is-a-workflow.htm), read 13 Nov 2026. - **collibra-05** (Profile, Collibra's own claim): Collibra says on its catalog page that teams can certify trustworthy data and surface Data Quality & Observability metrics; the page does not say certification is set by rule. [Source](https://www.collibra.com/products/data-catalog), read 13 Nov 2026. - **collibra-06** (Profile, none-found): None found on 2026-11-13: a documented certified, endorsed or approved-for-AI status that a rule sets and re-sets automatically, in the Collibra documentation home, catalog page and workflow overview. Searched: https://productresources.collibra.com/docs/collibra/latest/Content/Home.htm, read 13 Nov 2026. - **collibra-07** (Profile, Collibra's own claim): Collibra says AI Command Center aggregates documentation, data integrity, lifecycle and regulatory signals into one AI Trust Score per AI system (not per data asset). [Source](https://www.collibra.com/products/ai-governance), read 13 Nov 2026. - **collibra-08** (Profile, Collibra's own claim): Collibra docs say data quality scores are shown automatically on Column, Table, Schema, Database and Database View asset pages. [Source](https://productresources.collibra.com/docs/collibra/latest/Content/UnifiedDataQuality/co_about-data-quality.htm), read 13 Nov 2026. - **collibra-09** (Profile, Collibra's own claim): Collibra says its lineage traces root causes and downstream impacts at table, column and report level. [Source](https://www.collibra.com/products/data-lineage), read 13 Nov 2026. - **collibra-10** (Profile, Collibra's own claim): Collibra docs say Usage Analytics shows behavioral data about users and popular resources inside Collibra; the page does not mention BI reports. [Source](https://productresources.collibra.com/docs/collibra/latest/Content/UsageAnalytics/to_usage-analytics.htm), read 13 Nov 2026. - **collibra-11** (Profile, Collibra's own claim): Collibra says Data Quality & Observability defines ownership by data domain and routes custom alerts to the right owner. [Source](https://www.collibra.com/products/data-quality-and-observability), read 13 Nov 2026. - **collibra-12** (Profile, Collibra's own claim): Collibra says automated classification labels data, including PII and PHI, and that it can generate descriptions for assets. [Source](https://www.collibra.com/products/data-catalog), read 13 Nov 2026. - **collibra-13** (Profile, Collibra's own claim): Collibra says the semantic layer gives a business view of data and links data attributes to business and measure assets. [Source](https://productresources.collibra.com/docs/collibra/latest/Content/Catalog/GuidedStewardship/SemanticLayer/co_ui-semantic-layer.htm), read 13 Nov 2026. - **collibra-14** (Profile, none-found): None found on 2026-11-13: a data freshness or staleness signal (time since last update versus expected) usable by a rule, in the Data Quality & Observability product page, the MCP tool list and the DQ docs overview. Searched: https://www.collibra.com/products/data-quality-and-observability, read 13 Nov 2026. - **collibra-15** (Profile, Collibra's own claim): Collibra says its MCP server connects Claude, ChatGPT, Databricks, Snowflake Cortex or any MCP-compatible tool to Collibra. [Source](https://www.collibra.com/products/mcp-server), read 13 Nov 2026. - **collibra-16** (Profile, observed): The public chip repository lists MCP tools for upstream and downstream lineage, asset details, column semantics, data quality rule results and classification matches. [Source](https://github.com/collibra/chip), read 13 Nov 2026. - **collibra-17** (Profile, observed): The repository README states one limit of the catalog column search tool: filtering by classification tag is not supported. [Source](https://github.com/collibra/chip), read 13 Nov 2026. - **collibra-18** (Profile, Collibra's own claim): Collibra and Databricks say their expanded integrations (MCP server context and a Unity Catalog link) are available to preview customers through an account team. [Source](https://www.prnewswire.com/news-releases/collibra-named-databricks-governance-partner-of-the-year-collibra-and-databricks-deepening-a-partnership-to-ground-agentic-ai-in-governed-context-302800655.html), read 13 Nov 2026. - **collibra-19** (Controls what an agent is told, observed): The chip README says tools work with the default scopes of any authenticated Collibra user, and a permission error means the connecting user lacks a scope such as dgc.ai-copilot or dgc.classify. [Source](https://github.com/collibra/chip), read 13 Nov 2026. - **collibra-20** (Controls what an agent is told, Collibra's own claim): Collibra says writes through the MCP server use Collibra existing permissions. [Source](https://www.collibra.com/products/mcp-server), read 13 Nov 2026. - **collibra-21** (Controls what an agent is told, Collibra's own claim): Collibra docs say most MCP tools work with the default scopes granted to any authenticated Collibra user, and tools that need extra scopes are marked in the tool tables. [Source](https://web.archive.org/web/20260713001251/https://productresources.collibra.com/docs/collibra/latest/Content/ModelContextProtocol/ref_mcp-tools.htm), read 13 Nov 2026. - **collibra-22** (Controls what an agent is told, Collibra's own claim): Collibra says AI Command Center guardian agents supervise agent behavior and intervene at defined boundaries; this is a newly launched product that entered private preview first. [Source](https://www.collibra.com/products/ai-governance), read 13 Nov 2026. - **collibra-23** (Controls what an agent is told, Collibra's own claim): Collibra press release says more than 40 enterprises took part in the AI Command Center private preview and gives no general availability date in the text read. [Source](https://www.prnewswire.com/news-releases/collibra-launches-ai-command-center-to-scale-agentic-ai-with-real-time-oversight-and-continuous-control-302763105.html), read 13 Nov 2026. - **collibra-24** (Profile, Collibra's own claim): Collibra says it maps lineage automatically across sources, ETL and BI tools. [Source](https://www.collibra.com/products/data-lineage), read 13 Nov 2026. - **collibra-25** (Follows sensitive data into BI, Collibra's own claim): Collibra docs list supported lineage sources including warehouses (Snowflake, Databricks Unity Catalog, BigQuery), dbt and Looker, Power BI, Qlik, Sigma, Tableau and ThoughtSpot; the docs state column-level lineage is not generated for tables created by SQL statements. [Source](https://productresources.collibra.com/docs/collibra/latest/Content/CollibraDataLineage/ref_technical-lineage-supported-data-sources.htm), read 13 Nov 2026. - **collibra-26** (Coverage of the stack, Collibra's own claim): Collibra docs list the adapters that dbt lineage supports (including Snowflake, Databricks, Postgres, BigQuery, Redshift); the page does not mention snapshot nodes. [Source](https://web.archive.org/web/20260421071225/https://productresources.collibra.com/docs/collibra/latest/Content/CollibraDataLineage/DataSources/dbtCore/ref_dbt-core-supported-transformations.htm), read 13 Nov 2026. - **collibra-27** (Coverage of the stack, Collibra's own claim): Collibra says Data Access manages access requests and provisioning across Snowflake, Databricks and BigQuery and integrates with Okta and Microsoft Entra ID. [Source](https://www.collibra.com/products/data-access), read 13 Nov 2026. - **collibra-28** (Shows who actually saw it, Collibra's own claim): Collibra says lineage gives a visual audit trail that shows where data originated, how it was processed and who accessed it. [Source](https://www.collibra.com/products/data-lineage), read 13 Nov 2026. - **collibra-29** (Shows who actually saw it, none-found): None found on 2026-11-13: viewers per BI report or per AI agent drawn from BI usage or agent access logs, in the Usage Analytics docs page and the lineage and MCP product pages. Searched: https://productresources.collibra.com/docs/collibra/latest/Content/UsageAnalytics/to_usage-analytics.htm, read 13 Nov 2026. - **collibra-30** (Carries classification downstream, Collibra's own claim): Collibra docs say Data Access policies use metadata tags imported from connected systems for attribute-based access control. [Source](https://productresources.collibra.com/docs/collibra/latest/Content/DataAccess/co_data-access.htm), read 13 Nov 2026. - **collibra-31** (Carries classification downstream, none-found): None found on 2026-11-13: documented automatic propagation of a sensitivity classification along lineage to downstream tables, BI fields or reports, in the lineage, data access and catalog product pages and the docs home. Searched: https://productresources.collibra.com/docs/collibra/latest/Content/Home.htm, read 13 Nov 2026. - **collibra-32** (Carries classification downstream, observed): The MCP tool list includes tools to search data classes, search classification matches, and add or remove a match, which need the dgc.classify and dgc.catalog scopes. [Source](https://github.com/collibra/chip), read 13 Nov 2026. - **collibra-33** (Acts on it, Collibra's own claim): Collibra says Data Access masks sensitive fields by user role or access purpose. [Source](https://www.collibra.com/products/data-access), read 13 Nov 2026. - **collibra-34** (Acts on it, Collibra's own claim): Collibra says Data Access applies masking and row filtering automatically from data classifications such as PII and PHI. [Source](https://www.collibra.com/products/data-access), read 13 Nov 2026. - **collibra-35** (Acts on it, Collibra's own claim): Collibra says data quality issue workflows assign tasks, notify owners and can hand off to Jira and ServiceNow. [Source](https://www.collibra.com/products/data-quality-and-observability), read 13 Nov 2026. - **collibra-36** (Acts on it, Collibra's own claim): Collibra docs say access controls are enforced in target systems as roles, column masks or row filters. [Source](https://productresources.collibra.com/docs/collibra/latest/Content/DataAccess/co_data-access.htm), read 13 Nov 2026. - **collibra-37** (Profile, Collibra's own claim): Collibra docs say data quality jobs can run on automated schedules. [Source](https://productresources.collibra.com/docs/collibra/latest/Content/UnifiedDataQuality/co_about-data-quality.htm), read 13 Nov 2026. - **collibra-38** (Profile, Collibra's own claim): Collibra docs say lineage synchronization into Collibra is manual or runs on a schedule. [Source](https://productresources.collibra.com/docs/collibra/latest/Content/CollibraDataLineage/co_synchronization-process.htm), read 13 Nov 2026. - **collibra-39** (Evidence beyond the vendor, Collibra's own claim): Collibra says Gartner named it a Leader in the 2026 Magic Quadrant for Data and Analytics Governance Platforms (Collibra press release, not the Gartner page, which blocked access). [Source](https://www.prnewswire.com/news-releases/collibra-named-a-leader-for-the-second-consecutive-year-in-gartner-magic-quadrant-for-data-and-analytics-governance-platforms-302671796.html), read 13 Nov 2026. - **collibra-40** (Evidence beyond the vendor, Collibra's own claim): Collibra customer story says Nationwide Building Society chose Collibra, citing Edge integrations and compatibility with Databricks; BCBS 239 was the primary use case. [Source](https://www.collibra.com/customer-stories/nationwide-building-society), read 13 Nov 2026. - **collibra-41** (Evidence beyond the vendor, observed): The public collibra/chip repository is Apache-2.0 licensed with 37 stars, 17 forks and release v0.0.67 (27 Oct), a pre-1.0 version number. [Source](https://github.com/collibra/chip/releases), read 13 Nov 2026. - **collibra-42** (Evidence beyond the vendor, none-found): None found on 2026-11-13: a Gartner Peer Insights page, cloud marketplace listing or partner page (Snowflake, Databricks, dbt) readable today, in Gartner, AWS Marketplace, Databricks Marketplace, Snowflake and dbt partner URLs (blocked, 404 or empty). Searched: https://www.collibra.com/, read 13 Nov 2026. - **collibra-43** (Price transparency, none-found): None found on 2026-11-13: a published price list, plan tiers or pricing page for the Collibra platform, in collibra.com/pricing (HTTP 404) and the site navigation. Searched: https://www.collibra.com/pricing, read 13 Nov 2026. - **collibra-44** (Price transparency, Collibra's own claim): Collibra docs say the generic MCP server is open source and a community offering for all customers, the Databricks MCP server is a commercial offering, and the tools reference marks which tools use Collibra Units; no price is stated. [Source](https://web.archive.org/web/20260609030714/https://productresources.collibra.com/docs/collibra/latest/Content/ModelContextProtocol/co_mcp.htm), read 13 Nov 2026. - **collibra-45** (Profile, Collibra's own claim): Collibra docs say a person sets the Certified characteristic on a data set by hand, and a workflow can be designed to take care of certification; no automatic rule is described. [Source](https://web.archive.org/web/20260512135817/https://productresources.collibra.com/docs/collibra/latest/Content/Catalog/DataSets/ta_certify-data-set.htm), read 13 Nov 2026. - **collibra-46** (Profile, Collibra's own claim): Collibra docs say a popularity score (Very high to None) is calculated from 30 days of query statistics, currently only for Snowflake, in the latest UI for Commercial Cloud customers. [Source](https://web.archive.org/web/20260512125859/https://productresources.collibra.com/docs/collibra/latest/Content/Catalog/RegisterDataSource/Edge/SynchronizeSchemas/co_popularity.htm), read 13 Nov 2026. - **collibra-47** (Shows who actually saw it, Collibra's own claim): Collibra docs describe a Protect audit log (in preview) of queries run against a data source and the data accessed, which is data-source access, not viewers per BI report or agent. [Source](https://web.archive.org/web/2026/https://productresources.collibra.com/docs/collibra/latest/Content/Protect/co_protect-audit.htm), read 13 Nov 2026. - **collibra-48** (Profile, Collibra's own claim): Collibra docs say the AI trust score of AI assets updates automatically, typically within seconds, when relevant data on the asset changes; it applies to AI use case, agent and model assets. [Source](https://web.archive.org/web/20260713001815/https://productresources.collibra.com/docs/collibra/latest/Content/AICommandCenter/ref_aicc-trust-score-inputs.htm), read 13 Nov 2026. - **collibra-49** (Evidence beyond the vendor, observed): The public README of STRM PACE, an open source policy engine published by a company other than Collibra, lists Collibra as a supported catalog connecting to Snowflake, Databricks, BigQuery and PostgreSQL. [Source](https://github.com/getstrm/pace), read 13 Nov 2026. - **collibra-50** (Evidence beyond the vendor, observed): The PyPI package collibra-connector, published by an individual developer and not by Collibra, describes itself as an unofficial Python connector for the Collibra Data Governance Center API (version 1.5.0, May 2026). [Source](https://pypi.org/project/collibra-connector/), read 13 Nov 2026. ## Compare Collibra - [Collibra vs Microsoft Purview](/compare/collibra-vs-microsoft-purview/) - [The full index](/index/) ## Sources - https://www.collibra.com/: https://www.collibra.com/ (read 13 Nov 2026) - https://www.prnewswire.com/news-releases/collibra-announces-the-acquisition-of-raito-and-new-powerful-advancements-in-unified-governance-for-data-and-ai-across-every-data-citizen-302472460.html: https://www.prnewswire.com/news-releases/collibra-announces-the-acquisition-of-raito-and-new-powerful-advancements-in-unified-governance-for-data-and-ai-across-every-data-citizen-302472460.html (read 13 Nov 2026) - https://www.collibra.com/company/trust-center: https://www.collibra.com/company/trust-center (read 13 Nov 2026) - https://developer.collibra.com/workflows/workflow-documentation/Content/Workflows/ref_what-is-a-workflow.htm: https://developer.collibra.com/workflows/workflow-documentation/Content/Workflows/ref_what-is-a-workflow.htm (read 13 Nov 2026) - https://www.collibra.com/products/data-catalog: https://www.collibra.com/products/data-catalog (read 13 Nov 2026) - https://productresources.collibra.com/docs/collibra/latest/Content/Home.htm: https://productresources.collibra.com/docs/collibra/latest/Content/Home.htm (read 13 Nov 2026) - https://www.collibra.com/products/ai-governance: https://www.collibra.com/products/ai-governance (read 13 Nov 2026) - https://productresources.collibra.com/docs/collibra/latest/Content/UnifiedDataQuality/co_about-data-quality.htm: https://productresources.collibra.com/docs/collibra/latest/Content/UnifiedDataQuality/co_about-data-quality.htm (read 13 Nov 2026) - https://www.collibra.com/products/data-lineage: https://www.collibra.com/products/data-lineage (read 13 Nov 2026) - https://productresources.collibra.com/docs/collibra/latest/Content/UsageAnalytics/to_usage-analytics.htm: https://productresources.collibra.com/docs/collibra/latest/Content/UsageAnalytics/to_usage-analytics.htm (read 13 Nov 2026) - https://www.collibra.com/products/data-quality-and-observability: https://www.collibra.com/products/data-quality-and-observability (read 13 Nov 2026) - https://productresources.collibra.com/docs/collibra/latest/Content/Catalog/GuidedStewardship/SemanticLayer/co_ui-semantic-layer.htm: https://productresources.collibra.com/docs/collibra/latest/Content/Catalog/GuidedStewardship/SemanticLayer/co_ui-semantic-layer.htm (read 13 Nov 2026) - https://www.collibra.com/products/mcp-server: https://www.collibra.com/products/mcp-server (read 13 Nov 2026) - https://github.com/collibra/chip: https://github.com/collibra/chip (read 13 Nov 2026) - https://www.prnewswire.com/news-releases/collibra-named-databricks-governance-partner-of-the-year-collibra-and-databricks-deepening-a-partnership-to-ground-agentic-ai-in-governed-context-302800655.html: https://www.prnewswire.com/news-releases/collibra-named-databricks-governance-partner-of-the-year-collibra-and-databricks-deepening-a-partnership-to-ground-agentic-ai-in-governed-context-302800655.html (read 13 Nov 2026) - https://web.archive.org/web/20260713001251/https://productresources.collibra.com/docs/collibra/latest/Content/ModelContextProtocol/ref_mcp-tools.htm: https://web.archive.org/web/20260713001251/https://productresources.collibra.com/docs/collibra/latest/Content/ModelContextProtocol/ref_mcp-tools.htm (read 13 Nov 2026) - https://www.prnewswire.com/news-releases/collibra-launches-ai-command-center-to-scale-agentic-ai-with-real-time-oversight-and-continuous-control-302763105.html: https://www.prnewswire.com/news-releases/collibra-launches-ai-command-center-to-scale-agentic-ai-with-real-time-oversight-and-continuous-control-302763105.html (read 13 Nov 2026) - https://productresources.collibra.com/docs/collibra/latest/Content/CollibraDataLineage/ref_technical-lineage-supported-data-sources.htm: https://productresources.collibra.com/docs/collibra/latest/Content/CollibraDataLineage/ref_technical-lineage-supported-data-sources.htm (read 13 Nov 2026) - https://web.archive.org/web/20260421071225/https://productresources.collibra.com/docs/collibra/latest/Content/CollibraDataLineage/DataSources/dbtCore/ref_dbt-core-supported-transformations.htm: https://web.archive.org/web/20260421071225/https://productresources.collibra.com/docs/collibra/latest/Content/CollibraDataLineage/DataSources/dbtCore/ref_dbt-core-supported-transformations.htm (read 13 Nov 2026) - https://www.collibra.com/products/data-access: https://www.collibra.com/products/data-access (read 13 Nov 2026) - https://productresources.collibra.com/docs/collibra/latest/Content/DataAccess/co_data-access.htm: https://productresources.collibra.com/docs/collibra/latest/Content/DataAccess/co_data-access.htm (read 13 Nov 2026) - https://productresources.collibra.com/docs/collibra/latest/Content/CollibraDataLineage/co_synchronization-process.htm: https://productresources.collibra.com/docs/collibra/latest/Content/CollibraDataLineage/co_synchronization-process.htm (read 13 Nov 2026) - https://www.prnewswire.com/news-releases/collibra-named-a-leader-for-the-second-consecutive-year-in-gartner-magic-quadrant-for-data-and-analytics-governance-platforms-302671796.html: https://www.prnewswire.com/news-releases/collibra-named-a-leader-for-the-second-consecutive-year-in-gartner-magic-quadrant-for-data-and-analytics-governance-platforms-302671796.html (read 13 Nov 2026) - https://www.collibra.com/customer-stories/nationwide-building-society: https://www.collibra.com/customer-stories/nationwide-building-society (read 13 Nov 2026) - https://github.com/collibra/chip/releases: https://github.com/collibra/chip/releases (read 13 Nov 2026) - https://www.collibra.com/pricing: https://www.collibra.com/pricing (read 13 Nov 2026) - https://web.archive.org/web/20260609030714/https://productresources.collibra.com/docs/collibra/latest/Content/ModelContextProtocol/co_mcp.htm: https://web.archive.org/web/20260609030714/https://productresources.collibra.com/docs/collibra/latest/Content/ModelContextProtocol/co_mcp.htm (read 13 Nov 2026) - https://web.archive.org/web/20260512135817/https://productresources.collibra.com/docs/collibra/latest/Content/Catalog/DataSets/ta_certify-data-set.htm: https://web.archive.org/web/20260512135817/https://productresources.collibra.com/docs/collibra/latest/Content/Catalog/DataSets/ta_certify-data-set.htm (read 13 Nov 2026) - https://web.archive.org/web/20260512125859/https://productresources.collibra.com/docs/collibra/latest/Content/Catalog/RegisterDataSource/Edge/SynchronizeSchemas/co_popularity.htm: https://web.archive.org/web/20260512125859/https://productresources.collibra.com/docs/collibra/latest/Content/Catalog/RegisterDataSource/Edge/SynchronizeSchemas/co_popularity.htm (read 13 Nov 2026) - https://web.archive.org/web/2026/https://productresources.collibra.com/docs/collibra/latest/Content/Protect/co_protect-audit.htm: https://web.archive.org/web/2026/https://productresources.collibra.com/docs/collibra/latest/Content/Protect/co_protect-audit.htm (read 13 Nov 2026) - https://web.archive.org/web/20260713001815/https://productresources.collibra.com/docs/collibra/latest/Content/AICommandCenter/ref_aicc-trust-score-inputs.htm: https://web.archive.org/web/20260713001815/https://productresources.collibra.com/docs/collibra/latest/Content/AICommandCenter/ref_aicc-trust-score-inputs.htm (read 13 Nov 2026) - https://github.com/getstrm/pace: https://github.com/getstrm/pace (read 13 Nov 2026) - https://pypi.org/project/collibra-connector/: https://pypi.org/project/collibra-connector/ (read 13 Nov 2026) Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/platforms/collibra/ --- # Immuta for AI data governance: rank 11 of 16, at 45.0 of 100 PLATFORM PROFILE, read 13 Nov 2026 **The short answer.** Immuta ranks 11 of 16 on the Need to Know index at 45.0 of 100, read 13 Nov 2026. Its best criterion is Acts on it at 8 of 10, and its weakest is Price transparency at 0. The exposure map records 1 of six stages as documented and 3 as partial. - **Category:** Data access control and authorization platform (policy engine with sensitive data tagging) - **Status:** Exists under this name on 13 Nov 2026 (immuta.com home page and documentation.immuta.com both live; docs release notes dated 4 Nov 2026). - **Exposure trail:** Warehouse column: documented; Transformation: none found; BI field: none found; Report: partial; Viewer: partial; Agent: partial - **Warehouses named:** Snowflake, Databricks Unity Catalog, Databricks Spark, Google BigQuery, Amazon Redshift, Amazon Athena, AWS Lake Formation, Amazon S3, Starburst, Trino, Azure Synapse Analytics, Oracle, SQL Server, Teradata, MySQL, MariaDB, PostgreSQL - **BI tools named:** Tableau, Power BI - **Security tools named:** Alation, Atlan, Collibra, Microsoft Purview - **Rank and total:** 11 of 16, 45.0 of 100 1 of 6 stages documented, 3 partial ## Immuta on the eight criteria | Criterion | Weight | Score | Why | | --- | --- | --- | --- | | Follows sensitive data into BI | 25 | 2 | Policies are enforced in Tableau and Power BI live connections, but column lineage and dbt following were none found on 2026-11-13. | | Controls what an agent is told | 20 | 6 | On-behalf-of agents get ephemeral roles tied to the user entitlements, enforced at the data tier; public preview and no data MCP found. | | Shows who actually saw it | 15 | 5 | Audit of queries by user and agent activity with on-behalf-of user; classification dashboards cover three platforms and no per-report viewers. | | Carries classification downstream | 15 | 4 | Own identification plus ingestion of external catalog tags, but propagation along lineage was none found on 2026-11-13. | | Acts on it | 10 | 8 | Tag-based column and cell masking, review flows and dashboard subscription policies are documented, and Databricks' partner page confirms row security and column masking as native controls. | | Coverage of the stack | 5 | 5 | Many data platforms and four external catalogs are named, but only Tableau and Power BI for BI and no transformation integration. | | Evidence beyond the vendor | 5 | 8 | Databricks partner page, a quoted Booz Allen Hamilton technologist and a Wikipedia article citing TechTarget are independent. | | Price transparency | 5 | 0 | No published prices or pricing model were found on 2026-11-13; the pricing page returned 404. | Blind scores for Immuta, 0 to 10. A vendor claim scores at most 7 until a second source confirms it. ## Where Immuta is strongest Vendor-stated: Policies masked or limited by tag are enforced in the data platform per person, and agents get ephemeral roles scoped to the asking user. ## Where Immuta falls short No lineage-based tag propagation or field-level BI follow-through was found, and audit is by user query rather than per report viewer. ## Immuta along the exposure trail | Stage | Reading | Evidence | | --- | --- | --- | | [Warehouse column](/exposure-map/column/) | documented | Immuta says identification scans data sources and tags columns using column names, data patterns or dictionaries. [Source](https://documentation.immuta.com/saas/configuration/tags/data-discovery.md), read 13 Nov 2026. | | [Transformation](/exposure-map/transformation/) | none found | None found on 2026-11-13: dbt or other transformation tool integration that follows a sensitive column, in the SaaS documentation support matrix and index. Searched: https://documentation.immuta.com/saas/, read 13 Nov 2026. | | [BI field](/exposure-map/bi-field/) | none found | None found on 2026-11-13: column-level lineage or sensitivity labels carried into BI fields or reports (Tableau, Power BI, Looker), in the SaaS documentation index and full text; only Tableau and Power BI connection examples were found. Searched: https://documentation.immuta.com/saas/, read 13 Nov 2026. | | [Report](/exposure-map/report/) | partial | Immuta says Tableau dashboard viewers see data according to their personal policies when the published data source prompts the user for credentials. [Source](https://documentation.immuta.com/saas/configuration/application-configuration/how-to-guides/bi-tools/tableau.md), read 13 Nov 2026. | | [Viewer](/exposure-map/viewer/) | partial | Immuta says its universal audit model records query, authentication, policy, project and tag events with a consistent structure. [Source](https://documentation.immuta.com/saas/govern/detect-introduction/index.md), read 13 Nov 2026. | | [Agent](/exposure-map/agent/) | partial | Immuta says its agentic data access is a centralized authorization framework governing how AI agents and LLMs interact with sensitive data. [Source](https://documentation.immuta.com/saas/agentic-data-access/introduction.md), read 13 Nov 2026. | Documented, partial or none found on the read date. Vendor claims are the vendor's. ## Immuta in each situation | Situation | Rank | Total | Leader | | --- | --- | --- | --- | | [A regulated field](/best-for/regulated-field/) | 11 | 42.5 | Atlan 68.5 | | [Agents on analytics](/best-for/agents-on-analytics/) | 8 | 49.0 | Euno 66.0 | | [A Microsoft estate](/best-for/microsoft-estate/) | 11 | 44.5 | Atlan 68.5 | | [A mixed stack](/best-for/mixed-stack/) | 12 | 39.0 | Euno 68.5 | | [A lean team](/best-for/lean-team/) | 11 | 43.5 | Euno 62.5 | Each situation ranks the same scores under its own published weights. ## The evidence on Immuta, fact by fact - **immuta-01** (Controls what an agent is told, Immuta's own claim): Immuta says its agentic data access is a centralized authorization framework governing how AI agents and LLMs interact with sensitive data. [Source](https://documentation.immuta.com/saas/agentic-data-access/introduction.md), read 13 Nov 2026. - **immuta-02** (Controls what an agent is told, Immuta's own claim): Immuta says an on-behalf-of agent gets the union of the agent's permissions and the requesting user's entitlements, via a vended role. [Source](https://documentation.immuta.com/saas/agentic-data-access/introduction.md), read 13 Nov 2026. - **immuta-03** (Controls what an agent is told, Immuta's own claim): Immuta says access for an agent is ephemeral: a role is created in the data platform and deleted after the action, so access is revoked. [Source](https://documentation.immuta.com/saas/agentic-data-access/introduction.md), read 13 Nov 2026. - **immuta-04** (Controls what an agent is told, Immuta's own claim): The agentic data access feature is in public preview and must be enabled by request for a tenant. [Source](https://documentation.immuta.com/saas/agentic-data-access/introduction.md), read 13 Nov 2026. - **immuta-05** (Controls what an agent is told, Immuta's own claim): Immuta's agentic page says an agent acting for a person operates under that person's Immuta-defined access rights, enforced at the data tier. [Source](https://www.immuta.com/platform/agentic-data-access), read 13 Nov 2026. - **immuta-06** (Controls what an agent is told, Immuta's own claim): Immuta's agentic page says the rules are enforced at the data tier, so prompts cannot bypass them. [Source](https://www.immuta.com/platform/agentic-data-access), read 13 Nov 2026. - **immuta-07** (Controls what an agent is told, Immuta's own claim): Immuta's documentation MCP server serves documentation pages to agents; the page does not describe an MCP server for querying governed data. [Source](https://documentation.immuta.com/saas/configuration/work-with-llms.md), read 13 Nov 2026. - **immuta-08** (Controls what an agent is told, none-found): None found on 2026-11-13: an Immuta-hosted MCP server that serves governed data or policy context to agents, in the SaaS documentation (llms.txt, llms-full.txt, agentic data access pages). Searched: https://documentation.immuta.com/saas/, read 13 Nov 2026. - **immuta-09** (Acts on it, Immuta's own claim): Immuta says a dynamic review flow can auto-approve, deny or route access requests, including agent requests, to a human reviewer. [Source](https://documentation.immuta.com/saas/releases/index.md), read 13 Nov 2026. - **immuta-10** (Acts on it, Immuta's own claim): Immuta release notes describe masking exception requests that stewards review with classification tags as context. [Source](https://documentation.immuta.com/saas/releases/index/2025.md), read 13 Nov 2026. - **immuta-11** (Acts on it, Immuta's own claim): Immuta supports column masking and cell-level masking policies authored against tags. [Source](https://documentation.immuta.com/saas/govern/authoring-policies-in-secure/data-policies/reference-guides/masking-matrix-functions.md), read 13 Nov 2026. - **immuta-12** (Acts on it, Immuta's own claim): Immuta says users can author a policy that masks columns by tag, such as one tagged Person Name by automatic identification. [Source](https://documentation.immuta.com/saas/configuration/tags/data-discovery.md), read 13 Nov 2026. - **immuta-13** (Acts on it, Immuta's own claim): Immuta release notes say subscription policies can now govern assets outside native integrations, including dashboards. [Source](https://documentation.immuta.com/saas/releases/index.md), read 13 Nov 2026. - **immuta-14** (Acts on it, Immuta's own claim): Immuta documents a Request app where consumers browse data products and stewards' decisions become policies and automatic provisioning. [Source](https://documentation.immuta.com/saas/request/configure/reference-guides/walkthrough.md), read 13 Nov 2026. - **immuta-15** (Carries classification downstream, Immuta's own claim): Immuta says identification scans data sources and tags columns using column names, data patterns or dictionaries. [Source](https://documentation.immuta.com/saas/configuration/tags/data-discovery.md), read 13 Nov 2026. - **immuta-16** (Carries classification downstream, Immuta's own claim): Immuta says identification runs inside the data platform and no data leaves it. [Source](https://documentation.immuta.com/saas/configuration/tags/data-discovery.md), read 13 Nov 2026. - **immuta-17** (Carries classification downstream, Immuta's own claim): Immuta says identification runs when data sources are added and when new columns are detected. [Source](https://documentation.immuta.com/saas/configuration/tags/data-discovery.md), read 13 Nov 2026. - **immuta-18** (Carries classification downstream, Immuta's own claim): Immuta says classification frameworks tag data by risk level using the entity tags that identification applied earlier. [Source](https://documentation.immuta.com/saas/configuration/tags/data-classification.md), read 13 Nov 2026. - **immuta-19** (Carries classification downstream, Immuta's own claim): Immuta says it ingests tags from external catalogs (Alation, Atlan, Collibra, Microsoft Purview, custom REST) and from three data platforms. [Source](https://documentation.immuta.com/saas/configuration/tags/catalogs.md), read 13 Nov 2026. - **immuta-20** (Carries classification downstream, Immuta's own claim): Immuta says it polls the connected external catalog for metadata changes every 24 hours. [Source](https://documentation.immuta.com/saas/configuration/tags/catalogs.md), read 13 Nov 2026. - **immuta-21** (Carries classification downstream, Immuta's own claim): Immuta's support matrix lists Snowflake, Databricks Unity Catalog and AWS Lake Formation as platforms it ingests tags from. [Source](https://documentation.immuta.com/saas/releases/support-matrix.md), read 13 Nov 2026. - **immuta-22** (Carries classification downstream, Immuta's own claim): Immuta says Snowflake tag ingestion imports table and column tags into Immuta. [Source](https://documentation.immuta.com/saas/configuration/integrations/snowflake/how-to-guides/enable-snowflake-tag-ingestion-1.md), read 13 Nov 2026. - **immuta-23** (Carries classification downstream, none-found): None found on 2026-11-13: tag or classification propagation along lineage (table or column lineage graph), in the SaaS documentation index and full text (llms.txt, llms-full.txt). Searched: https://documentation.immuta.com/saas/, read 13 Nov 2026. - **immuta-24** (Follows sensitive data into BI, Immuta's own claim): Immuta documents Tableau setup: a live connection is required for Immuta to enforce policies. [Source](https://documentation.immuta.com/saas/configuration/application-configuration/how-to-guides/bi-tools/tableau.md), read 13 Nov 2026. - **immuta-25** (Follows sensitive data into BI, Immuta's own claim): Immuta says Tableau dashboard viewers see data according to their personal policies when the published data source prompts the user for credentials. [Source](https://documentation.immuta.com/saas/configuration/application-configuration/how-to-guides/bi-tools/tableau.md), read 13 Nov 2026. - **immuta-26** (Follows sensitive data into BI, Immuta's own claim): Immuta documents Power BI setup: users must connect with personal credentials after publishing. [Source](https://documentation.immuta.com/saas/configuration/application-configuration/how-to-guides/bi-tools/power-bi.md), read 13 Nov 2026. - **immuta-27** (Follows sensitive data into BI, none-found): None found on 2026-11-13: column-level lineage or sensitivity labels carried into BI fields or reports (Tableau, Power BI, Looker), in the SaaS documentation index and full text; only Tableau and Power BI connection examples were found. Searched: https://documentation.immuta.com/saas/, read 13 Nov 2026. - **immuta-28** (Follows sensitive data into BI, none-found): None found on 2026-11-13: dbt or other transformation tool integration that follows a sensitive column, in the SaaS documentation support matrix and index. Searched: https://documentation.immuta.com/saas/, read 13 Nov 2026. - **immuta-29** (Shows who actually saw it, Immuta's own claim): Immuta says its universal audit model records query, authentication, policy, project and tag events with a consistent structure. [Source](https://documentation.immuta.com/saas/govern/detect-introduction/index.md), read 13 Nov 2026. - **immuta-30** (Shows who actually saw it, Immuta's own claim): Immuta says audit logs expire after 90 days unless exported to S3 or ADLS Gen2. [Source](https://documentation.immuta.com/saas/govern/detect-introduction/index.md), read 13 Nov 2026. - **immuta-31** (Shows who actually saw it, Immuta's own claim): Immuta says audit dashboards visualize user queries, and sensitivity of queries when classification is enabled. [Source](https://documentation.immuta.com/saas/govern/detect-introduction/detection/detect-concept.md), read 13 Nov 2026. - **immuta-32** (Shows who actually saw it, Immuta's own claim): Immuta says the classification-aware audit dashboards are limited to Snowflake, Databricks Unity Catalog and Trino. [Source](https://documentation.immuta.com/saas/govern/detect-introduction/detection/detect-concept.md), read 13 Nov 2026. - **immuta-33** (Shows who actually saw it, Immuta's own claim): Immuta's agentic page says agent activity is logged with on-behalf-of user, vended role and request and termination times. [Source](https://www.immuta.com/platform/agentic-data-access), read 13 Nov 2026. - **immuta-34** (Shows who actually saw it, none-found): None found on 2026-11-13: per-report viewer lists or BI report view logs, in the SaaS documentation (audit, dashboards, Tableau and Power BI pages); audit is by user query on data sources. Searched: https://documentation.immuta.com/saas/, read 13 Nov 2026. - **immuta-35** (Coverage of the stack, Immuta's own claim): Immuta's support matrix lists data platforms it governs, including Snowflake, Databricks, BigQuery, Redshift, Starburst, Trino, Oracle, SQL Server and Teradata. [Source](https://documentation.immuta.com/saas/releases/support-matrix.md), read 13 Nov 2026. - **immuta-36** (Coverage of the stack, Immuta's own claim): Immuta's support matrix lists external catalogs it reads tags from. [Source](https://documentation.immuta.com/saas/releases/support-matrix.md), read 13 Nov 2026. - **immuta-37** (Coverage of the stack, third-party): Databricks' partner page says Immuta reflects ABAC policies as native Unity Catalog controls. [Source](https://www.databricks.com/partners/immuta), read 13 Nov 2026. - **immuta-38** (Evidence beyond the vendor, third-party): Databricks' partner page quotes a Booz Allen Hamilton technologist about Immuta. [Source](https://www.databricks.com/partners/immuta), read 13 Nov 2026. - **immuta-39** (Evidence beyond the vendor, third-party): Wikipedia, citing TechTarget, reports Immuta's October 2025 data provisioning capabilities for analytics, applications and AI agents. [Source](https://en.wikipedia.org/wiki/Immuta), read 13 Nov 2026. - **immuta-40** (Evidence beyond the vendor, observed): The public GitHub organization lists mostly infrastructure utilities and forks; no governance product source was seen. [Source](https://github.com/immuta), read 13 Nov 2026. - **immuta-41** (Price transparency, none-found): None found on 2026-11-13: published prices or a pricing model, in immuta.com/pricing (404 page), the documentation and the home page. Searched: https://www.immuta.com/, read 13 Nov 2026. - **immuta-42** (Profile, third-party): Wikipedia says Immuta is a private data security software company founded in 2015 by Matt Carroll, Steven Touw and Mike Schiller. [Source](https://en.wikipedia.org/wiki/Immuta), read 13 Nov 2026. - **immuta-43** (Profile, third-party): A Reuters headline cited by Wikipedia reports a June 2022 raise that valued Immuta at $1 billion. [Source](https://en.wikipedia.org/wiki/Immuta), read 13 Nov 2026. - **immuta-44** (Profile, Immuta's own claim): Immuta describes itself on its home page as the authorization layer for data access for humans and agents. [Source](https://www.immuta.com/), read 13 Nov 2026. - **immuta-45** (Profile, Immuta's own claim): Immuta's trust page says Immuta SaaS is hosted on AWS in the customer-selected region (US, Europe or APJ). [Source](https://www.immuta.com/trust/), read 13 Nov 2026. - **immuta-46** (Coverage of the stack, Immuta's own claim): Immuta says its policies attach by tag to tables created by dbt or other transform tools, but that it does not receive DDL events from the data platform, which causes a window it calls policy downtime that its steps are meant to shorten. [Source](https://documentation.immuta.com/saas/govern/authoring-policies-in-secure/dbt-transform-workflow.md), read 13 Nov 2026. ## Compare Immuta - [Euno vs Immuta](/compare/euno-vs-immuta/) - [Databricks Unity Catalog vs Immuta](/compare/databricks-vs-immuta/) - [Immuta vs Privacera](/compare/immuta-vs-privacera/) - [Alternatives to Immuta](/alternatives/immuta/) - [The full index](/index/) ## Sources - https://documentation.immuta.com/saas/agentic-data-access/introduction.md: https://documentation.immuta.com/saas/agentic-data-access/introduction.md (read 13 Nov 2026) - https://www.immuta.com/platform/agentic-data-access: https://www.immuta.com/platform/agentic-data-access (read 13 Nov 2026) - https://documentation.immuta.com/saas/configuration/work-with-llms.md: https://documentation.immuta.com/saas/configuration/work-with-llms.md (read 13 Nov 2026) - https://documentation.immuta.com/saas/: https://documentation.immuta.com/saas/ (read 13 Nov 2026) - https://documentation.immuta.com/saas/releases/index.md: https://documentation.immuta.com/saas/releases/index.md (read 13 Nov 2026) - https://documentation.immuta.com/saas/releases/index/2025.md: https://documentation.immuta.com/saas/releases/index/2025.md (read 13 Nov 2026) - https://documentation.immuta.com/saas/govern/authoring-policies-in-secure/data-policies/reference-guides/masking-matrix-functions.md: https://documentation.immuta.com/saas/govern/authoring-policies-in-secure/data-policies/reference-guides/masking-matrix-functions.md (read 13 Nov 2026) - https://documentation.immuta.com/saas/configuration/tags/data-discovery.md: https://documentation.immuta.com/saas/configuration/tags/data-discovery.md (read 13 Nov 2026) - https://documentation.immuta.com/saas/request/configure/reference-guides/walkthrough.md: https://documentation.immuta.com/saas/request/configure/reference-guides/walkthrough.md (read 13 Nov 2026) - https://documentation.immuta.com/saas/configuration/tags/data-classification.md: https://documentation.immuta.com/saas/configuration/tags/data-classification.md (read 13 Nov 2026) - https://documentation.immuta.com/saas/configuration/tags/catalogs.md: https://documentation.immuta.com/saas/configuration/tags/catalogs.md (read 13 Nov 2026) - https://documentation.immuta.com/saas/releases/support-matrix.md: https://documentation.immuta.com/saas/releases/support-matrix.md (read 13 Nov 2026) - https://documentation.immuta.com/saas/configuration/integrations/snowflake/how-to-guides/enable-snowflake-tag-ingestion-1.md: https://documentation.immuta.com/saas/configuration/integrations/snowflake/how-to-guides/enable-snowflake-tag-ingestion-1.md (read 13 Nov 2026) - https://documentation.immuta.com/saas/configuration/application-configuration/how-to-guides/bi-tools/tableau.md: https://documentation.immuta.com/saas/configuration/application-configuration/how-to-guides/bi-tools/tableau.md (read 13 Nov 2026) - https://documentation.immuta.com/saas/configuration/application-configuration/how-to-guides/bi-tools/power-bi.md: https://documentation.immuta.com/saas/configuration/application-configuration/how-to-guides/bi-tools/power-bi.md (read 13 Nov 2026) - https://documentation.immuta.com/saas/govern/detect-introduction/index.md: https://documentation.immuta.com/saas/govern/detect-introduction/index.md (read 13 Nov 2026) - https://documentation.immuta.com/saas/govern/detect-introduction/detection/detect-concept.md: https://documentation.immuta.com/saas/govern/detect-introduction/detection/detect-concept.md (read 13 Nov 2026) - https://www.databricks.com/partners/immuta: https://www.databricks.com/partners/immuta (read 13 Nov 2026) - https://en.wikipedia.org/wiki/Immuta: https://en.wikipedia.org/wiki/Immuta (read 13 Nov 2026) - https://github.com/immuta: https://github.com/immuta (read 13 Nov 2026) - https://www.immuta.com/: https://www.immuta.com/ (read 13 Nov 2026) - https://www.immuta.com/trust/: https://www.immuta.com/trust/ (read 13 Nov 2026) - https://documentation.immuta.com/saas/govern/authoring-policies-in-secure/dbt-transform-workflow.md: https://documentation.immuta.com/saas/govern/authoring-policies-in-secure/dbt-transform-workflow.md (read 13 Nov 2026) Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/platforms/immuta/ --- # Ataccama ONE for AI data governance: rank 12 of 16, at 41.5 of 100 PLATFORM PROFILE, read 13 Nov 2026 **The short answer.** Ataccama ONE ranks 12 of 16 on the Need to Know index at 41.5 of 100, read 13 Nov 2026. Its best criterion is Evidence beyond the vendor at 8 of 10, and its weakest is Shows who actually saw it at 1. The exposure map records 1 of six stages as documented and 4 as partial. - **Category:** Data quality, catalog and observability platform with master data management - **Status:** Exists under this name on 13 Nov 2026 (ataccama.com and docs.ataccama.com serve Ataccama ONE; 17.2.0 released October 23, 2026; the docs now brand the platform "Ataccama ONE Agentic" / "Agentic Data Trust Platform"). - **Exposure trail:** Warehouse column: documented; Transformation: partial; BI field: partial; Report: partial; Viewer: none found; Agent: partial - **Warehouses named:** Snowflake, Databricks, BigQuery, Amazon Redshift, Azure Synapse Analytics, Amazon Athena, Teradata, Oracle - **BI tools named:** Tableau, Power BI, Power BI Report Server - **Security tools named:** none found on 13 Nov 2026 - **Rank and total:** 12 of 16, 41.5 of 100 1 of 6 stages documented, 4 partial ## Ataccama ONE on the eight criteria | Criterion | Weight | Score | Why | | --- | --- | --- | --- | | Follows sensitive data into BI | 25 | 5 | Column-to-field lineage for Tableau and design-time Power BI lineage (cloud only, one-way) is documented; no Looker, and no sensitive-column path. | | Controls what an agent is told | 20 | 5 | MCP requests run as the user and follow permissions in SSO mode, but Bedrock uses a shared account and classification on tool results was none found. | | Shows who actually saw it | 15 | 1 | Only an optional audit module for the platform own actions; viewers per report or agent were none found on 2026-11-13. | | Carries classification downstream | 15 | 3 | Rule-based detection classifies attributes on its own, but propagation of labels along lineage was none found on 2026-11-13. | | Acts on it | 10 | 5 | Classification tags hide sensitive attributes from unauthorized users and alerts escalate to Jira or ServiceNow, though the admin role bypasses protection. | | Coverage of the stack | 5 | 4 | Snowflake, Databricks, Tableau, Power BI and dbt are named with limits; no security tool integration appears. | | Evidence beyond the vendor | 5 | 8 | OpenLineage ecosystem listing and a PeerSpot reviews page with reviewer pricing summary are independent; analyst claims are vendor-stated and the listing is a logo only. | | Price transparency | 5 | 4 | Tiers depend on named users, objects and DQ configurations, but no dollar figures; reviewers say price is reasonable without a list. | Blind scores for Ataccama ONE, 0 to 10. A vendor claim scores at most 7 until a second source confirms it. ## Where Ataccama ONE is strongest Vendor-stated: Rule-based term detection classifies attributes during profiling, and classification tags hide protected attributes from unauthorized users, including in Data Stories. ## Where Ataccama ONE falls short No propagation of classification along lineage and no BI viewer data was found, and Snowflake pushdown excludes term detection. ## Ataccama ONE along the exposure trail | Stage | Reading | Evidence | | --- | --- | --- | | [Warehouse column](/exposure-map/column/) | documented | Ataccama docs say detection rules run during profiling to classify attributes and catalog items by condition, and are not AI-powered. [Source](https://docs.ataccama.com/one/latest/data-quality/rules.html), read 13 Nov 2026. | | [Transformation](/exposure-map/transformation/) | partial | Ataccama lists dbt lineage as design-time through the underlying database scanner. [Source](https://docs.ataccama.com/one/latest/lineage/supported-lineage-technologies.html), read 13 Nov 2026. | | [BI field](/exposure-map/bi-field/) | partial | Ataccama docs say the Tableau scanner maps column fields to database columns, giving column-to-field lineage. [Source](https://docs.ataccama.com/one/latest/lineage/tableau-lineage-scanner.html), read 13 Nov 2026. | | [Report](/exposure-map/report/) | partial | Ataccama docs say protected attributes block rendering of visualizations for unauthorized users, but this is inside ONE Data Stories, Ataccama's own visualization component. [Source](https://docs.ataccama.com/one/latest/data-stories/data-protection-classification-in-data-stories.html), read 13 Nov 2026. | | [Viewer](/exposure-map/viewer/) | none found | None found on 2026-11-13: viewers per BI report or per AI agent from BI usage or access logs, in the docs index, report and audit pages. Searched: https://docs.ataccama.com/, read 13 Nov 2026. | | [Agent](/exposure-map/agent/) | partial | Ataccama docs say each MCP request runs under the user's own identity. [Source](https://docs.ataccama.com/one/latest/generative-ai/mcp-dqc.html), read 13 Nov 2026. | Documented, partial or none found on the read date. Vendor claims are the vendor's. ## Ataccama ONE in each situation | Situation | Rank | Total | Leader | | --- | --- | --- | --- | | [A regulated field](/best-for/regulated-field/) | 12 | 39.0 | Atlan 68.5 | | [Agents on analytics](/best-for/agents-on-analytics/) | 12 | 41.0 | Euno 66.0 | | [A Microsoft estate](/best-for/microsoft-estate/) | 12 | 39.0 | Atlan 68.5 | | [A mixed stack](/best-for/mixed-stack/) | 11 | 39.5 | Euno 68.5 | | [A lean team](/best-for/lean-team/) | 12 | 42.5 | Euno 62.5 | Each situation ranks the same scores under its own published weights. ## The evidence on Ataccama ONE, fact by fact - **ataccama-01** (Evidence beyond the vendor, Ataccama ONE's own claim): Ataccama says on its home page that it is a 5-time Leader in the Gartner Magic Quadrant for Augmented Data Quality Solutions and a Leader in the first Forrester Wave for Data Quality Solutions (vendor claim, analyst pages not readable). [Source](https://www.ataccama.com/), read 13 Nov 2026. - **ataccama-02** (Profile, Ataccama ONE's own claim): Ataccama says the Data Trust Index is a machine-readable signal telling agents whether a dataset is cleared for autonomous action. [Source](https://www.ataccama.com/), read 13 Nov 2026. - **ataccama-03** (Profile, Ataccama ONE's own claim): Ataccama says the Data Trust Index scores data and MCP connects it to the AI stack. [Source](https://www.ataccama.com/), read 13 Nov 2026. - **ataccama-04** (Profile, Ataccama ONE's own claim): Ataccama documents the Data Trust Index as a 0 to 100 score on every catalog item covering quality, ownership and data context. [Source](https://docs.ataccama.com/ataccama-one-agentic/latest/data-catalog/data-trust-index.html), read 13 Nov 2026. - **ataccama-05** (Profile, Ataccama ONE's own claim): Ataccama maps the score to trust tiers, with 70 to 100 labeled Trusted and described as safe to use for AI. [Source](https://docs.ataccama.com/ataccama-one-agentic/latest/data-catalog/data-trust-index.html), read 13 Nov 2026. - **ataccama-06** (Profile, Ataccama ONE's own claim): The Data Trust Index reads whether an owner is assigned, worth up to 20 points. [Source](https://docs.ataccama.com/ataccama-one-agentic/latest/data-catalog/data-trust-index.html), read 13 Nov 2026. - **ataccama-07** (Profile, Ataccama ONE's own claim): The quality input comes only from the primary DQ monitor assigned to the item, worth up to 40 points; an item never evaluated gets 0 for that part. [Source](https://docs.ataccama.com/ataccama-one-agentic/latest/data-catalog/data-trust-index.html), read 13 Nov 2026. - **ataccama-08** (Profile, Ataccama ONE's own claim): The context input counts terms on attributes, terms on the item and whether a description exists (up to 40 points); there is no lineage, usage or sensitivity input listed. [Source](https://docs.ataccama.com/ataccama-one-agentic/latest/data-catalog/data-trust-index.html), read 13 Nov 2026. - **ataccama-09** (Profile, Ataccama ONE's own claim): Ataccama docs say detection rules run during profiling to classify attributes and catalog items by condition, and are not AI-powered. [Source](https://docs.ataccama.com/one/latest/data-quality/rules.html), read 13 Nov 2026. - **ataccama-10** (Profile, Ataccama ONE's own claim): Ataccama docs say term detection applies rules across the catalog instead of manual tagging, with a percentage threshold for assignment. [Source](https://docs.ataccama.com/ataccama-one-agentic/latest/data-catalog/detect-terms.html), read 13 Nov 2026. - **ataccama-11** (Acts on it, Ataccama ONE's own claim): Ataccama docs say classification tags on terms hide data in sensitive attributes from unauthorized users. [Source](https://docs.ataccama.com/one/latest/user-access-management/data-protection-classification.html), read 13 Nov 2026. - **ataccama-12** (Acts on it, Ataccama ONE's own claim): Ataccama docs list a limit: the admin identity provider role bypasses data protection classifications. [Source](https://docs.ataccama.com/one/latest/user-access-management/data-protection-classification.html), read 13 Nov 2026. - **ataccama-13** (Follows sensitive data into BI, Ataccama ONE's own claim): Ataccama docs say protected attributes block rendering of visualizations for unauthorized users, but this is inside ONE Data Stories, Ataccama's own visualization component. [Source](https://docs.ataccama.com/one/latest/data-stories/data-protection-classification-in-data-stories.html), read 13 Nov 2026. - **ataccama-14** (Controls what an agent is told, Ataccama ONE's own claim): Ataccama docs say each MCP request runs under the user's own identity. [Source](https://docs.ataccama.com/one/latest/generative-ai/mcp-dqc.html), read 13 Nov 2026. - **ataccama-15** (Controls what an agent is told, Ataccama ONE's own claim): Ataccama docs say Amazon Bedrock is the exception and uses a shared service account. [Source](https://docs.ataccama.com/one/latest/generative-ai/mcp-dqc.html), read 13 Nov 2026. - **ataccama-16** (Profile, Ataccama ONE's own claim): Ataccama docs say the DQ&C MCP server lets an assistant filter catalog items by quality score, business term, source or stewardship group. [Source](https://docs.ataccama.com/one/latest/generative-ai/mcp-dqc.html), read 13 Nov 2026. - **ataccama-17** (Profile, Ataccama ONE's own claim): Ataccama docs say the MCP server is enabled on request and that heavy load is the customer's responsibility in Cloud. [Source](https://docs.ataccama.com/one/latest/generative-ai/mcp-dqc.html), read 13 Nov 2026. - **ataccama-18** (Profile, Ataccama ONE's own claim): Ataccama 17.2.0 release notes (October 23, 2026) say MCP clients connect with no platform-side setup and the server is no longer cloud-only. [Source](https://docs.ataccama.com/one/latest/release-notes/ataccama-17.2.0-release-notes.html), read 13 Nov 2026. - **ataccama-19** (Coverage of the stack, Ataccama ONE's own claim): Ataccama lists Tableau lineage scanning as design-time lineage for cloud and on-premise. [Source](https://docs.ataccama.com/one/latest/lineage/supported-lineage-technologies.html), read 13 Nov 2026. - **ataccama-20** (Coverage of the stack, Ataccama ONE's own claim): Ataccama lists Power BI lineage as design-time, cloud version only. [Source](https://docs.ataccama.com/one/latest/lineage/supported-lineage-technologies.html), read 13 Nov 2026. - **ataccama-21** (Coverage of the stack, Ataccama ONE's own claim): Ataccama lists Snowflake runtime lineage including views, dynamic tables and streams. [Source](https://docs.ataccama.com/one/latest/lineage/supported-lineage-technologies.html), read 13 Nov 2026. - **ataccama-22** (Coverage of the stack, Ataccama ONE's own claim): Ataccama lists dbt lineage as design-time through the underlying database scanner. [Source](https://docs.ataccama.com/one/latest/lineage/supported-lineage-technologies.html), read 13 Nov 2026. - **ataccama-23** (Follows sensitive data into BI, Ataccama ONE's own claim): Ataccama docs say the Tableau scanner maps column fields to database columns, giving column-to-field lineage. [Source](https://docs.ataccama.com/one/latest/lineage/tableau-lineage-scanner.html), read 13 Nov 2026. - **ataccama-24** (Follows sensitive data into BI, Ataccama ONE's own claim): Ataccama docs say lineage can be traced at catalog item and attribute (column) level. [Source](https://docs.ataccama.com/one/latest/lineage/get-started.html), read 13 Nov 2026. - **ataccama-25** (Profile, Ataccama ONE's own claim): Ataccama docs say the built-in lineage scanner runs on a schedule (from version 16.0.0). [Source](https://docs.ataccama.com/one/latest/lineage/get-started.html), read 13 Nov 2026. - **ataccama-26** (Coverage of the stack, Ataccama ONE's own claim): Ataccama docs say the Power BI connection is one-way and that profiling dataset tables needs Premium, Premium Per User or Fabric capacity. [Source](https://docs.ataccama.com/one/latest/reports/reports-from-power-bi.html), read 13 Nov 2026. - **ataccama-27** (Profile, Ataccama ONE's own claim): Ataccama docs say a freshness SLA is set per catalog item in hours or days. [Source](https://docs.ataccama.com/ataccama-one-agentic/latest/data-observability/freshness-monitoring.html), read 13 Nov 2026. - **ataccama-28** (Profile, Ataccama ONE's own claim): Ataccama docs say freshness findings and alerts close on their own when data is written again. [Source](https://docs.ataccama.com/ataccama-one-agentic/latest/data-observability/freshness-monitoring.html), read 13 Nov 2026. - **ataccama-29** (Acts on it, Ataccama ONE's own claim): Ataccama docs say alerts can be escalated to Jira or ServiceNow tickets. [Source](https://docs.ataccama.com/ataccama-one-agentic/latest/alerts/escalate-alerts.html), read 13 Nov 2026. - **ataccama-30** (Coverage of the stack, Ataccama ONE's own claim): Ataccama docs say DQ rules can run in the data source instead of on Ataccama processing engines. [Source](https://docs.ataccama.com/one/latest/sources/pushdown-dq-evaluation.html), read 13 Nov 2026. - **ataccama-31** (Coverage of the stack, Ataccama ONE's own claim): Ataccama docs say Snowflake pushdown covers profiling, DQ and monitoring, but excludes term detection and AI-powered anomaly detection. [Source](https://docs.ataccama.com/one/latest/sources/snowflake-connection.html), read 13 Nov 2026. - **ataccama-32** (Price transparency, Ataccama ONE's own claim): Ataccama says pricing tiers depend on named users, data objects and active DQ configurations, with unlimited read-only consumers. [Source](https://www.ataccama.com/pricing), read 13 Nov 2026. - **ataccama-33** (Price transparency, Ataccama ONE's own claim): Ataccama says every named user gets an annual AI query allocation for the ONE AI Agent, with more as an add-on. [Source](https://www.ataccama.com/pricing), read 13 Nov 2026. - **ataccama-34** (Evidence beyond the vendor, Ataccama ONE's own claim): Ataccama's Snowflake partner page lists a news item about verifying data quality for AI agents and says the partnership began in 2024. [Source](https://www.ataccama.com/partners/snowflake), read 13 Nov 2026. - **ataccama-35** (Profile, Ataccama ONE's own claim): Ataccama docs say a data product defines what the data represents and can mark one catalog item as recommended. [Source](https://docs.ataccama.com/ataccama-one-agentic/latest/data-catalog/data-products.html), read 13 Nov 2026. - **ataccama-36** (Shows who actually saw it, Ataccama ONE's own claim): Ataccama docs describe an optional Audit module that collects logs from the metadata, processing and ONE Data modules (ONE's own actions, not BI report viewing). [Source](https://docs.ataccama.com/one/latest/audit/audit.html), read 13 Nov 2026. - **ataccama-37** (Evidence beyond the vendor, Ataccama ONE's own claim): A Snowflake executive is quoted in a 2023 press release (issued by Ataccama through PR Newswire) welcoming Ataccama's pushdown and observability for joint customers. [Source](https://www.prnewswire.com/news-releases/ataccama-advances-data-observability-and-processing-with-snowflake-data-cloud-for-joint-customers-301740721.html), read 13 Nov 2026. - **ataccama-38** (Evidence beyond the vendor, third-party): The OpenLineage project's public ecosystem page lists Ataccama among consumers (shown as a logo; text read is the section heading). [Source](https://openlineage.io/ecosystem/), read 13 Nov 2026. - **ataccama-39** (Carries classification downstream, none-found): None found on 2026-11-13: sensitivity labels or classification tags propagated along lineage, in the docs index, lineage overview and data protection classification pages. Searched: https://docs.ataccama.com/, read 13 Nov 2026. - **ataccama-40** (Shows who actually saw it, none-found): None found on 2026-11-13: viewers per BI report or per AI agent from BI usage or access logs, in the docs index, report and audit pages. Searched: https://docs.ataccama.com/, read 13 Nov 2026. - **ataccama-41** (Controls what an agent is told, none-found): None found on 2026-11-13: documentation saying data protection classification or access levels are applied to MCP tool results beyond the user-identity statement, in the MCP server page and docs index. Searched: https://docs.ataccama.com/one/latest/generative-ai/mcp-dqc.html, read 13 Nov 2026. - **ataccama-42** (Price transparency, none-found): None found on 2026-11-13: a published dollar price or list price per tier, on the pricing page (it says to talk to an expert) and in marketplace pages that could be read. Searched: https://www.ataccama.com/pricing, read 13 Nov 2026. - **ataccama-43** (Evidence beyond the vendor, none-found): None found on 2026-11-13: a readable Gartner Peer Insights, G2 or marketplace listing page (they returned HTTP 403 or no content), and no public GitHub repositories on the Ataccama organization. Searched: https://docs.ataccama.com/, read 13 Nov 2026. - **ataccama-44** (Profile, none-found): None found on 2026-11-13: usage or popularity of an asset (who queries a table or views a report) as an input to trust scoring, in the Data Trust Index page and docs index. Searched: https://docs.ataccama.com/ataccama-one-agentic/latest/data-catalog/data-trust-index.html, read 13 Nov 2026. - **ataccama-45** (Profile, none-found): None found on 2026-11-13: a certified or endorsed status on assets, in the Data Trust Index and catalog pages read. Searched: https://docs.ataccama.com/, read 13 Nov 2026. - **ataccama-46** (Profile, Ataccama ONE's own claim): Ataccama documents a hosted, read-only MCP trust layer for external AI agents (Claude, Copilot, Snowflake Intelligence, Bedrock) whose search_catalog_item tool filters by quality score, and says access follows the user's permissions in SSO mode. [Source](https://docs.ataccama.com/ataccama-one-agentic/latest/gen-ai/mcp-trust-layer.html), read 13 Nov 2026. - **ataccama-47** (Evidence beyond the vendor, third-party): PeerSpot, a review site, hosts a reviews page for Ataccama ONE Platform that describes it as a license-free tool with drag-and-drop features. [Source](https://www.peerspot.com/products/ataccama-one-platform-reviews), read 13 Nov 2026. - **ataccama-48** (Price transparency, third-party): PeerSpot summarizes reviewer opinion on Ataccama ONE Platform pricing as reasonable to many users, with some reporting high licensing and setup costs (reviewer summary, no list price). [Source](https://www.peerspot.com/products/ataccama-one-platform-reviews), read 13 Nov 2026. ## Compare Ataccama ONE - [The full index](/index/) ## Sources - https://www.ataccama.com/: https://www.ataccama.com/ (read 13 Nov 2026) - https://docs.ataccama.com/ataccama-one-agentic/latest/data-catalog/data-trust-index.html: https://docs.ataccama.com/ataccama-one-agentic/latest/data-catalog/data-trust-index.html (read 13 Nov 2026) - https://docs.ataccama.com/one/latest/data-quality/rules.html: https://docs.ataccama.com/one/latest/data-quality/rules.html (read 13 Nov 2026) - https://docs.ataccama.com/ataccama-one-agentic/latest/data-catalog/detect-terms.html: https://docs.ataccama.com/ataccama-one-agentic/latest/data-catalog/detect-terms.html (read 13 Nov 2026) - https://docs.ataccama.com/one/latest/user-access-management/data-protection-classification.html: https://docs.ataccama.com/one/latest/user-access-management/data-protection-classification.html (read 13 Nov 2026) - https://docs.ataccama.com/one/latest/data-stories/data-protection-classification-in-data-stories.html: https://docs.ataccama.com/one/latest/data-stories/data-protection-classification-in-data-stories.html (read 13 Nov 2026) - https://docs.ataccama.com/one/latest/generative-ai/mcp-dqc.html: https://docs.ataccama.com/one/latest/generative-ai/mcp-dqc.html (read 13 Nov 2026) - https://docs.ataccama.com/one/latest/release-notes/ataccama-17.2.0-release-notes.html: https://docs.ataccama.com/one/latest/release-notes/ataccama-17.2.0-release-notes.html (read 13 Nov 2026) - https://docs.ataccama.com/one/latest/lineage/supported-lineage-technologies.html: https://docs.ataccama.com/one/latest/lineage/supported-lineage-technologies.html (read 13 Nov 2026) - https://docs.ataccama.com/one/latest/lineage/tableau-lineage-scanner.html: https://docs.ataccama.com/one/latest/lineage/tableau-lineage-scanner.html (read 13 Nov 2026) - https://docs.ataccama.com/one/latest/lineage/get-started.html: https://docs.ataccama.com/one/latest/lineage/get-started.html (read 13 Nov 2026) - https://docs.ataccama.com/one/latest/reports/reports-from-power-bi.html: https://docs.ataccama.com/one/latest/reports/reports-from-power-bi.html (read 13 Nov 2026) - https://docs.ataccama.com/ataccama-one-agentic/latest/data-observability/freshness-monitoring.html: https://docs.ataccama.com/ataccama-one-agentic/latest/data-observability/freshness-monitoring.html (read 13 Nov 2026) - https://docs.ataccama.com/ataccama-one-agentic/latest/alerts/escalate-alerts.html: https://docs.ataccama.com/ataccama-one-agentic/latest/alerts/escalate-alerts.html (read 13 Nov 2026) - https://docs.ataccama.com/one/latest/sources/pushdown-dq-evaluation.html: https://docs.ataccama.com/one/latest/sources/pushdown-dq-evaluation.html (read 13 Nov 2026) - https://docs.ataccama.com/one/latest/sources/snowflake-connection.html: https://docs.ataccama.com/one/latest/sources/snowflake-connection.html (read 13 Nov 2026) - https://www.ataccama.com/pricing: https://www.ataccama.com/pricing (read 13 Nov 2026) - https://www.ataccama.com/partners/snowflake: https://www.ataccama.com/partners/snowflake (read 13 Nov 2026) - https://docs.ataccama.com/ataccama-one-agentic/latest/data-catalog/data-products.html: https://docs.ataccama.com/ataccama-one-agentic/latest/data-catalog/data-products.html (read 13 Nov 2026) - https://docs.ataccama.com/one/latest/audit/audit.html: https://docs.ataccama.com/one/latest/audit/audit.html (read 13 Nov 2026) - https://www.prnewswire.com/news-releases/ataccama-advances-data-observability-and-processing-with-snowflake-data-cloud-for-joint-customers-301740721.html: https://www.prnewswire.com/news-releases/ataccama-advances-data-observability-and-processing-with-snowflake-data-cloud-for-joint-customers-301740721.html (read 13 Nov 2026) - https://openlineage.io/ecosystem/: https://openlineage.io/ecosystem/ (read 13 Nov 2026) - https://docs.ataccama.com/: https://docs.ataccama.com/ (read 13 Nov 2026) - https://docs.ataccama.com/ataccama-one-agentic/latest/gen-ai/mcp-trust-layer.html: https://docs.ataccama.com/ataccama-one-agentic/latest/gen-ai/mcp-trust-layer.html (read 13 Nov 2026) - https://www.peerspot.com/products/ataccama-one-platform-reviews: https://www.peerspot.com/products/ataccama-one-platform-reviews (read 13 Nov 2026) Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/platforms/ataccama/ --- # Informatica for AI data governance: rank 13 of 16, at 30.0 of 100 PLATFORM PROFILE, read 13 Nov 2026 **The short answer.** Informatica ranks 13 of 16 on the Need to Know index at 30.0 of 100, read 13 Nov 2026. Its best criterion is Evidence beyond the vendor at 9 of 10, and its weakest is Follows sensitive data into BI at 2. The exposure map records 2 of six stages as documented and 3 as partial. - **Category:** Enterprise data catalog, governance, quality and access management platform (IDMC), now part of Salesforce - **Status:** Exists on 13 Nov 2026 as Cloud Data Governance and Catalog (CDGC) in the Intelligent Data Management Cloud; the informatica.com pages are branded "Informatica from Salesforce" after Salesforce completed the acquisition on November 18, 2025 (informatica-03); docs.informatica.com returned HTTP 403 to automated fetch, so documentation pages were not read; second pass 13 Nov 2026: docs.informatica.com still blocked (403) and Wayback blocked. - **Exposure trail:** Warehouse column: documented; Transformation: documented; BI field: partial; Report: none found; Viewer: partial; Agent: partial - **Warehouses named:** Snowflake, Databricks (Unity Catalog), Amazon Redshift, Salesforce Data 360 - **BI tools named:** Tableau, Power BI - **Security tools named:** none found on 13 Nov 2026 - **Rank and total:** 13 of 16, 30.0 of 100 2 of 6 stages documented, 3 partial ## Informatica on the eight criteria | Criterion | Weight | Score | Why | | --- | --- | --- | --- | | Follows sensitive data into BI | 25 | 2 | Lineage from code is claimed, but column lineage from warehouse to Power BI or Tableau fields was none found on 2026-11-13. | | Controls what an agent is told | 20 | 2 | Governance is said to travel with the agent, but MCP examples use service identity and per-user application was none found. | | Shows who actually saw it | 15 | 3 | Operational logging of who, what, when and why of data access in platforms such as Snowflake is claimed; viewers per report or agent were none found on 2026-11-13. | | Carries classification downstream | 15 | 3 | Automated classification and Databricks tag extraction are described, but lineage propagation was none found on 2026-11-13. | | Acts on it | 10 | 4 | Policy pushdown to Snowflake and Tableau is stated, with masking and row filtering described as forthcoming. | | Coverage of the stack | 5 | 3 | Snowflake, Databricks, Redshift, Tableau and Power BI are named with no transformation or security tools. | | Evidence beyond the vendor | 5 | 9 | Databricks partner and customer pages, KPMG and Point72 quotes and Microsoft documentation confirm it independently. | | Price transparency | 5 | 4 | Processing-unit pricing model is published and billed via Azure Marketplace, with no dollar amounts or rates. | Blind scores for Informatica, 0 to 10. A vendor claim scores at most 7 until a second source confirms it. ## Where Informatica is strongest Vendor-stated: Policy-based data access management (CDAM) built on metadata and CLAIRE classification pushes controls into Snowflake, Databricks, Power BI and Tableau. ## Where Informatica falls short No documented column-level lineage into Power BI or Tableau reports, no per-report viewer list, and no classification propagation along lineage was found; masking was listed as forthcoming in a 2024 post. ## Informatica along the exposure trail | Stage | Reading | Evidence | | --- | --- | --- | | [Warehouse column](/exposure-map/column/) | documented | Informatica says CLAIRE automates sensitive data classification (PII, personal and financial records) as part of CDAM. [Source](https://www.informatica.com/about-us/news/news-releases/2024/02/20240229-informatica-launches-cloud-data-access-management-industrys-first-ai-powered-solution-for-automating-data-access-policy-enforcement-at-scale.html), read 13 Nov 2026. | | [Transformation](/exposure-map/transformation/) | documented | Informatica says lineage can be derived from code in SQL scripts, stored procedures and AI/ML code, and inferred where documentation is missing. [Source](https://www.informatica.com/products/data-catalog/data-lineage.html), read 13 Nov 2026. | | [BI field](/exposure-map/bi-field/) | partial | Informatica says CDAM pushes policies into Snowflake, Databricks, Power BI and more. [Source](https://www.informatica.com/products/data-governance/data-access-management.html), read 13 Nov 2026. | | [Report](/exposure-map/report/) | none found | None found on 13 Nov 2026. | | [Viewer](/exposure-map/viewer/) | partial | Informatica says CDAM operational logging records who, what, when and why of data access in platforms such as Snowflake (data access, not report viewers). [Source](https://www.informatica.com/blogs/how-idmc-supports-native-security-controls-in-snowflake.html), read 13 Nov 2026. | | [Agent](/exposure-map/agent/) | partial | Informatica says governance travels with the agent in its headless design, with security and privacy controls built into the infrastructure. [Source](https://www.informatica.com/headless.html), read 13 Nov 2026. | Documented, partial or none found on the read date. Vendor claims are the vendor's. ## Informatica in each situation | Situation | Rank | Total | Leader | | --- | --- | --- | --- | | [A regulated field](/best-for/regulated-field/) | 14 | 30.0 | Atlan 68.5 | | [Agents on analytics](/best-for/agents-on-analytics/) | 16 | 26.0 | Euno 66.0 | | [A Microsoft estate](/best-for/microsoft-estate/) | 15 | 27.5 | Atlan 68.5 | | [A mixed stack](/best-for/mixed-stack/) | 13 | 27.0 | Euno 68.5 | | [A lean team](/best-for/lean-team/) | 14 | 33.5 | Euno 62.5 | Each situation ranks the same scores under its own published weights. ## The evidence on Informatica, fact by fact - **informatica-01** (Profile, Informatica's own claim): Informatica says on its home page that its brand is now "Informatica from Salesforce" and that it governs data across 50,000+ sources. [Source](https://www.informatica.com/), read 13 Nov 2026. - **informatica-02** (Profile, Informatica's own claim): Informatica lists the product on its own site as Cloud Data Governance & Catalog, inside the Intelligent Data Management Cloud (IDMC), and describes it as a governance and catalog service for data and AI. [Source](https://www.informatica.com/products/data-governance/cloud-data-governance-and-catalog.html), read 13 Nov 2026. - **informatica-03** (Profile, Informatica's own claim): Salesforce announced on November 18, 2025 that it completed its acquisition of Informatica. [Source](https://www.salesforce.com/news/press-releases/2025/11/18/salesforce-completes-acquisition-of-informatica/), read 13 Nov 2026. - **informatica-04** (Profile, Informatica's own claim): Salesforce announced in May 2025 an agreement to acquire Informatica for about $8 billion in equity value. [Source](https://www.salesforce.com/news/press-releases/2025/05/27/salesforce-signs-definitive-agreement-to-acquire-informatica/), read 13 Nov 2026. - **informatica-05** (Profile, Informatica's own claim): Informatica says its platform encrypts customer data at rest and in transit and runs as a multi-tenant cloud. [Source](https://www.informatica.com/trust-center.html), read 13 Nov 2026. - **informatica-06** (Profile, Informatica's own claim): Informatica says the Metadata Enrichment Agent will generate business descriptions and sensitivity labels as data flows, which would set labels without a person marking each asset. [Source](https://www.informatica.com/about-us/news/news-releases/2026/05/20260520-informatica-from-salesforce-delivers-the-trusted-data-foundation-every-ai-agent-needs-now-across-every-surface-every-platform-everywhere.html), read 13 Nov 2026. - **informatica-07** (Profile, Informatica's own claim): Informatica lists the Metadata Enrichment Agent as scheduled for Q4 2026, not generally available at the May 2026 announcement. [Source](https://www.informatica.com/about-us/news/news-releases/2026/05/20260520-informatica-from-salesforce-delivers-the-trusted-data-foundation-every-ai-agent-needs-now-across-every-surface-every-platform-everywhere.html), read 13 Nov 2026. - **informatica-08** (Profile, Informatica's own claim): Informatica says CDGC can automatically enrich metadata by applying data classification and association with business glossaries. [Source](https://www.informatica.com/blogs/the-role-of-trusted-context-in-building-ai-agents-how-informatica-idmc-empowers-smarter-data-management.html), read 13 Nov 2026. - **informatica-09** (Profile, Informatica's own claim): Informatica says CDGC workflows gained rule-based triggers and bulk approvals in the Spring 2026 release. [Source](https://www.informatica.com/blogs/activate-enterprise-data-with-trusted-context-new-capabilities-in-idmcs-spring-2026-release.html), read 13 Nov 2026. - **informatica-10** (Profile, Informatica's own claim): Informatica says the CLAIRE Data Quality Agent, now generally available, turns natural-language descriptions into data quality rules. [Source](https://www.informatica.com/blogs/activate-enterprise-data-with-trusted-context-new-capabilities-in-idmcs-spring-2026-release.html), read 13 Nov 2026. - **informatica-11** (Profile, Informatica's own claim): Informatica says the catalog profiles data, applies rules and reports quality through metrics and scorecards. [Source](https://www.informatica.com/products/data-catalog.html), read 13 Nov 2026. - **informatica-12** (Profile, Informatica's own claim): Informatica says its metadata catalog captures lineage, schema and usage statistics. [Source](https://www.informatica.com/blogs/the-role-of-trusted-context-in-building-ai-agents-how-informatica-idmc-empowers-smarter-data-management.html), read 13 Nov 2026. - **informatica-13** (Profile, Informatica's own claim): Informatica says the Claude plugin skill reads ownership, certification and PII or sensitivity tags on catalog assets before an agent uses them. [Source](https://www.informatica.com/blogs/introducing-the-informatica-plugin-for-claude-platform.html), read 13 Nov 2026. - **informatica-14** (Profile, Informatica's own claim): Informatica describes data observability as monitoring freshness, volume, distribution, schema changes and lineage (a general definition on the product page). [Source](https://www.informatica.com/products/data-quality.html), read 13 Nov 2026. - **informatica-15** (Profile, Informatica's own claim): Informatica says Informatica Headless exposes data management through MCP servers, APIs and A2A services so agents can call it from any tool. [Source](https://www.informatica.com/headless.html), read 13 Nov 2026. - **informatica-16** (Profile, Informatica's own claim): Informatica says the Spring 2026 release lets customers expose governance, quality, MDM and integration functions as MCP servers with no-code configuration. [Source](https://www.informatica.com/blogs/activate-enterprise-data-with-trusted-context-new-capabilities-in-idmcs-spring-2026-release.html), read 13 Nov 2026. - **informatica-17** (Profile, Informatica's own claim): Informatica says its CDGC Metadata Search MCP returns column definitions from the glossary, volume metrics, certification status and domain context to an agent. [Source](https://www.informatica.com/blogs/powering-agentic-workflows-on-aws-with-informatica-mcps.html), read 13 Nov 2026. - **informatica-18** (Profile, Informatica's own claim): Informatica says its Catalog Discovery MCP is the gateway to CDGC for AI agents, in a plugin for Claude published September 2026. [Source](https://www.informatica.com/blogs/introducing-the-informatica-plugin-for-claude-platform.html), read 13 Nov 2026. - **informatica-19** (Profile, none-found): None found on 2026-11-13: documentation of a filter or query parameter that returns only assets carrying a given certified or ready label through the MCP servers, in the Informatica docs site (automated fetches returned HTTP 403, so docs pages were not readable). Searched: https://docs.informatica.com/, read 13 Nov 2026. - **informatica-20** (Profile, third-party): Databricks lists Informatica CDGC as integrated with Databricks Unity Catalog for governance, lineage and cataloging. [Source](https://www.databricks.com/partners/partner-directory/informatica), read 13 Nov 2026. - **informatica-21** (Profile, none-found): None found on 2026-11-13: documentation that a readiness or certified label set in CDGC is written to warehouse, transformation and BI assets, in the Informatica docs site (HTTP 403 to automated fetch) and in the vendor product pages read. Searched: https://docs.informatica.com/, read 13 Nov 2026. - **informatica-22** (Profile, Informatica's own claim): Informatica says its data quality service profiles data continuously to find anomalies and quality risks. [Source](https://www.informatica.com/products/data-quality.html), read 13 Nov 2026. - **informatica-23** (Profile, none-found): None found on 2026-11-13: documentation that a certified or AI-ready label is re-evaluated on a schedule or withdrawn when a quality rule fails, in the Informatica docs site (HTTP 403 to automated fetch) and vendor product pages. Searched: https://docs.informatica.com/, read 13 Nov 2026. - **informatica-24** (Evidence beyond the vendor, third-party): Databricks publishes a partner page quoting KPMG LLP U.S. Chief Data Officer Jodi Morton on using Informatica with Databricks and Microsoft. [Source](https://www.databricks.com/partners/partner-directory/informatica), read 13 Nov 2026. - **informatica-25** (Evidence beyond the vendor, third-party): Databricks publishes a customer story summary in which Point72 reports shorter data discovery time with Informatica and Databricks. [Source](https://www.databricks.com/partners/partner-directory/informatica), read 13 Nov 2026. - **informatica-26** (Evidence beyond the vendor, Informatica's own claim): Informatica says it is recognized in six Gartner Magic Quadrant reports (vendor claim; the Gartner pages themselves returned HTTP 403 to automated fetch). [Source](https://www.informatica.com/), read 13 Nov 2026. - **informatica-27** (Price transparency, Informatica's own claim): Informatica says its pricing is based on Informatica Processing Units (IPUs) that cover all eligible cloud services. [Source](https://www.informatica.com/pricing.html), read 13 Nov 2026. - **informatica-28** (Price transparency, Informatica's own claim): Informatica offers CLAIRE GPT, copilots and agents at no extra IPU cost through January 31, 2027 for eligible customers, limited to design-time work and not job runs. [Source](https://www.informatica.com/platform/claire-ai.html), read 13 Nov 2026. - **informatica-29** (Price transparency, none-found): None found on 2026-11-13: a published dollar price or IPU rate for Cloud Data Governance and Catalog, in the Informatica pricing page, which offers a quote request ("get quote") instead. Searched: https://www.informatica.com/pricing.html, read 13 Nov 2026. - **informatica-30** (Follows sensitive data into BI, Informatica's own claim): Informatica says lineage can be derived from code in SQL scripts, stored procedures and AI/ML code, and inferred where documentation is missing. [Source](https://www.informatica.com/products/data-catalog/data-lineage.html), read 13 Nov 2026. - **informatica-31** (Follows sensitive data into BI, none-found): None found on 2026-11-13: column-level lineage from warehouse columns to Power BI or Tableau fields and reports, in the Informatica docs site (HTTP 403 to automated fetch) and the lineage, catalog and governance product pages and blogs read. Searched: https://docs.informatica.com/, read 13 Nov 2026. - **informatica-32** (Controls what an agent is told, Informatica's own claim): Informatica says governance travels with the agent in its headless design, with security and privacy controls built into the infrastructure. [Source](https://www.informatica.com/headless.html), read 13 Nov 2026. - **informatica-33** (Controls what an agent is told, Informatica's own claim): Informatica documents an AWS AgentCore gateway pattern in which Informatica MCPs are called with service-to-service OAuth 2.0 (a service identity, not stated per end user). [Source](https://www.informatica.com/blogs/powering-agentic-workflows-on-aws-with-informatica-mcps.html), read 13 Nov 2026. - **informatica-34** (Controls what an agent is told, none-found): None found on 2026-11-13: documentation of how the asking user's own permissions are applied on each MCP or CLAIRE agent call, in the Informatica docs site (HTTP 403 to automated fetch) and the headless, MCP and plugin pages read. Searched: https://docs.informatica.com/, read 13 Nov 2026. - **informatica-35** (Shows who actually saw it, Informatica's own claim): Informatica says CDAM operational logging records who, what, when and why of data access in platforms such as Snowflake (data access, not report viewers). [Source](https://www.informatica.com/blogs/how-idmc-supports-native-security-controls-in-snowflake.html), read 13 Nov 2026. - **informatica-36** (Shows who actually saw it, none-found): None found on 2026-11-13: lists of who viewed a given report or dashboard, or which AI agent received a given column, in the Informatica docs site (HTTP 403 to automated fetch) and the product pages and blogs read. Searched: https://docs.informatica.com/, read 13 Nov 2026. - **informatica-37** (Carries classification downstream, Informatica's own claim): Informatica says CLAIRE automates sensitive data classification (PII, personal and financial records) as part of CDAM. [Source](https://www.informatica.com/about-us/news/news-releases/2024/02/20240229-informatica-launches-cloud-data-access-management-industrys-first-ai-powered-solution-for-automating-data-access-policy-enforcement-at-scale.html), read 13 Nov 2026. - **informatica-38** (Carries classification downstream, Informatica's own claim): Informatica says CDAM policies are built from metadata captured by discovery, classification and cataloging, so one policy covers many tables and views. [Source](https://www.informatica.com/blogs/how-idmc-supports-native-security-controls-in-snowflake.html), read 13 Nov 2026. - **informatica-39** (Carries classification downstream, none-found): None found on 2026-11-13: documentation that imported classification or sensitivity tags are propagated along lineage to downstream columns, in vendor pages read; docs.informatica.com was unreadable (HTTP 403 to automated fetch). Searched: https://docs.informatica.com/, read 13 Nov 2026. - **informatica-40** (Acts on it, Informatica's own claim): Informatica says CDAM policy pushdown controls access to Snowflake tables and views by data and user-group attributes, with row, attribute and cell-level controls listed as to come (September 2024 post). [Source](https://www.informatica.com/blogs/how-idmc-supports-native-security-controls-in-snowflake.html), read 13 Nov 2026. - **informatica-41** (Acts on it, Informatica's own claim): Informatica said in September 2024 that row-level filtering and data masking in Snowflake would arrive in forthcoming releases. [Source](https://www.informatica.com/blogs/how-idmc-supports-native-security-controls-in-snowflake.html), read 13 Nov 2026. - **informatica-42** (Acts on it, Informatica's own claim): Informatica says the Spring 2026 release adds Policy Pushdown for Tableau, enforcing access controls on Tableau tables. [Source](https://www.informatica.com/blogs/activate-enterprise-data-with-trusted-context-new-capabilities-in-idmcs-spring-2026-release.html), read 13 Nov 2026. - **informatica-43** (Coverage of the stack, Informatica's own claim): Informatica says CDAM pushes policies into Snowflake, Databricks, Power BI and more. [Source](https://www.informatica.com/products/data-governance/data-access-management.html), read 13 Nov 2026. - **informatica-44** (Evidence beyond the vendor, third-party): Microsoft documents Informatica Intelligent Data Management Cloud as an Azure Native ISV Service that Microsoft and Informatica developed and manage together. [Source](https://learn.microsoft.com/en-us/azure/partner-solutions/informatica/faq), read 13 Nov 2026. - **informatica-45** (Price transparency, third-party): Microsoft documents that Informatica IDMC is billed through Azure Marketplace with a billing term and plan chosen at setup; the page gives no dollar amounts. [Source](https://learn.microsoft.com/en-us/azure/partner-solutions/informatica/faq), read 13 Nov 2026. - **informatica-46** (Carries classification downstream, Informatica's own claim): Informatica says CDGC can extract governance tags from Databricks Unity Catalog and show them in its catalog (April 2026 release); this brings in existing tags but the page does not say they are propagated along lineage. [Source](https://www.informatica.com/about-us/news/news-releases/2026/05/20260520-informatica-brings-headless-data-management-lakebase-connectivity-golden-record-publishing-and-unity-catalog-tag-extraction-to-the-databricks-platform.html), read 13 Nov 2026. ## Compare Informatica - [Informatica vs Microsoft Purview](/compare/informatica-vs-microsoft-purview/) - [The full index](/index/) ## Sources - https://www.informatica.com/: https://www.informatica.com/ (read 13 Nov 2026) - https://www.informatica.com/products/data-governance/cloud-data-governance-and-catalog.html: https://www.informatica.com/products/data-governance/cloud-data-governance-and-catalog.html (read 13 Nov 2026) - https://www.salesforce.com/news/press-releases/2025/11/18/salesforce-completes-acquisition-of-informatica/: https://www.salesforce.com/news/press-releases/2025/11/18/salesforce-completes-acquisition-of-informatica/ (read 13 Nov 2026) - https://www.salesforce.com/news/press-releases/2025/05/27/salesforce-signs-definitive-agreement-to-acquire-informatica/: https://www.salesforce.com/news/press-releases/2025/05/27/salesforce-signs-definitive-agreement-to-acquire-informatica/ (read 13 Nov 2026) - https://www.informatica.com/trust-center.html: https://www.informatica.com/trust-center.html (read 13 Nov 2026) - https://www.informatica.com/about-us/news/news-releases/2026/05/20260520-informatica-from-salesforce-delivers-the-trusted-data-foundation-every-ai-agent-needs-now-across-every-surface-every-platform-everywhere.html: https://www.informatica.com/about-us/news/news-releases/2026/05/20260520-informatica-from-salesforce-delivers-the-trusted-data-foundation-every-ai-agent-needs-now-across-every-surface-every-platform-everywhere.html (read 13 Nov 2026) - https://www.informatica.com/blogs/the-role-of-trusted-context-in-building-ai-agents-how-informatica-idmc-empowers-smarter-data-management.html: https://www.informatica.com/blogs/the-role-of-trusted-context-in-building-ai-agents-how-informatica-idmc-empowers-smarter-data-management.html (read 13 Nov 2026) - https://www.informatica.com/blogs/activate-enterprise-data-with-trusted-context-new-capabilities-in-idmcs-spring-2026-release.html: https://www.informatica.com/blogs/activate-enterprise-data-with-trusted-context-new-capabilities-in-idmcs-spring-2026-release.html (read 13 Nov 2026) - https://www.informatica.com/products/data-catalog.html: https://www.informatica.com/products/data-catalog.html (read 13 Nov 2026) - https://www.informatica.com/blogs/introducing-the-informatica-plugin-for-claude-platform.html: https://www.informatica.com/blogs/introducing-the-informatica-plugin-for-claude-platform.html (read 13 Nov 2026) - https://www.informatica.com/products/data-quality.html: https://www.informatica.com/products/data-quality.html (read 13 Nov 2026) - https://www.informatica.com/headless.html: https://www.informatica.com/headless.html (read 13 Nov 2026) - https://www.informatica.com/blogs/powering-agentic-workflows-on-aws-with-informatica-mcps.html: https://www.informatica.com/blogs/powering-agentic-workflows-on-aws-with-informatica-mcps.html (read 13 Nov 2026) - https://docs.informatica.com/: https://docs.informatica.com/ (read 13 Nov 2026) - https://www.databricks.com/partners/partner-directory/informatica: https://www.databricks.com/partners/partner-directory/informatica (read 13 Nov 2026) - https://www.informatica.com/pricing.html: https://www.informatica.com/pricing.html (read 13 Nov 2026) - https://www.informatica.com/platform/claire-ai.html: https://www.informatica.com/platform/claire-ai.html (read 13 Nov 2026) - https://www.informatica.com/products/data-catalog/data-lineage.html: https://www.informatica.com/products/data-catalog/data-lineage.html (read 13 Nov 2026) - https://www.informatica.com/blogs/how-idmc-supports-native-security-controls-in-snowflake.html: https://www.informatica.com/blogs/how-idmc-supports-native-security-controls-in-snowflake.html (read 13 Nov 2026) - https://www.informatica.com/about-us/news/news-releases/2024/02/20240229-informatica-launches-cloud-data-access-management-industrys-first-ai-powered-solution-for-automating-data-access-policy-enforcement-at-scale.html: https://www.informatica.com/about-us/news/news-releases/2024/02/20240229-informatica-launches-cloud-data-access-management-industrys-first-ai-powered-solution-for-automating-data-access-policy-enforcement-at-scale.html (read 13 Nov 2026) - https://www.informatica.com/products/data-governance/data-access-management.html: https://www.informatica.com/products/data-governance/data-access-management.html (read 13 Nov 2026) - https://learn.microsoft.com/en-us/azure/partner-solutions/informatica/faq: https://learn.microsoft.com/en-us/azure/partner-solutions/informatica/faq (read 13 Nov 2026) - https://www.informatica.com/about-us/news/news-releases/2026/05/20260520-informatica-brings-headless-data-management-lakebase-connectivity-golden-record-publishing-and-unity-catalog-tag-extraction-to-the-databricks-platform.html: https://www.informatica.com/about-us/news/news-releases/2026/05/20260520-informatica-brings-headless-data-management-lakebase-connectivity-golden-record-publishing-and-unity-catalog-tag-extraction-to-the-databricks-platform.html (read 13 Nov 2026) Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/platforms/informatica/ --- # Privacera for AI data governance: rank 14 of 16, at 30.0 of 100 PLATFORM PROFILE, read 13 Nov 2026 **The short answer.** Privacera ranks 14 of 16 on the Need to Know index at 30.0 of 100, read 13 Nov 2026. Its best criterion is Acts on it at 8 of 10, and its weakest is Follows sensitive data into BI at 0. The exposure map records 1 of six stages as documented and 2 as partial. - **Category:** Data security platform: sensitive data discovery, tag-based access control and masking (Apache Ranger based), plus AI agent governance - **Status:** Exists but renamed: docs.privacera.com now serves Trust3 AI Data Security documentation, described as 'formerly Privacera' (docs.trust3.ai), and privacera.com says it is now Trust3 AI; release 9.2.48.1 on Nov 4, 2026. Ownership/acquirer not stated on pages read. - **Exposure trail:** Warehouse column: documented; Transformation: none found; BI field: none found; Report: none found; Viewer: partial; Agent: partial - **Warehouses named:** Snowflake, Databricks Unity Catalog, Databricks SQL, Google BigQuery, AWS Redshift, AWS Athena, Azure Synapse, Trino, Starburst, Dremio, Oracle, Microsoft SQL Server, PostgreSQL, MySQL, Vertica - **BI tools named:** none found on 13 Nov 2026 - **Security tools named:** Collibra, Okta, Azure AD, LDAP, Apache Ranger - **Rank and total:** 14 of 16, 30.0 of 100 1 of 6 stages documented, 2 partial ## Privacera on the eight criteria | Criterion | Weight | Score | Why | | --- | --- | --- | --- | | Follows sensitive data into BI | 25 | 0 | Power BI, Tableau or Looker connectors or column lineage into BI fields were none found on 2026-11-13. | | Controls what an agent is told | 20 | 2 | Agent inventory, approvals and a read-only MCP key exist, but per-person scoping of what an agent is told is not documented. | | Shows who actually saw it | 15 | 4 | Access audits record who accessed what at table, column and path level; limited for PolicySync platforms and not BI reports or agents. | | Carries classification downstream | 15 | 4 | Own classifier plus tags read from an external catalog, synced to Ranger; propagation covers folders, not lineage. | | Acts on it | 10 | 8 | Tag-driven masking and deny policies are documented on several platforms and Databricks' partner directory confirms row, column and tag policy control; the alerts page is placeholder text. | | Coverage of the stack | 5 | 4 | Many data platforms and identity providers are named, but no BI or dbt connectors. | | Evidence beyond the vendor | 5 | 8 | Databricks partner directory and Dremio documentation list it independently; public repository is observed. | | Price transparency | 5 | 0 | No published price or pricing model was found on 2026-11-13; the page offers trial and demo only. | Blind scores for Privacera, 0 to 10. A vendor claim scores at most 7 until a second source confirms it. ## Where Privacera is strongest Vendor-stated: Discovery tags sensitive columns and files and Ranger tag-based policies mask or deny across many warehouses, with audit of allow/deny access. ## Where Privacera falls short No BI connector, lineage-based propagation or per-report viewer data found in the docs; propagation documented is only file part to folder. ## Privacera along the exposure trail | Stage | Reading | Evidence | | --- | --- | --- | | [Warehouse column](/exposure-map/column/) | documented | Trust3 AI says Discovery scans connected sources and automatically applies tags (for example EMAIL, PII) to columns, tables and files. [Source](https://docs.privacera.com/data-security/user-guide/discovery/scanning/classification/tags.html), read 13 Nov 2026. | | [Transformation](/exposure-map/transformation/) | none found | None found on 2026-11-13: tag or classification propagation along table or column lineage (search for lineage in Data Security docs sitemap of 1,146 pages and fetched Discovery pages), in docs.privacera.com/data-security. Searched: https://docs.privacera.com/data-security/index.html, read 13 Nov 2026. | | [BI field](/exposure-map/bi-field/) | none found | None found on 2026-11-13: Power BI, Tableau or Looker connector or column-level lineage into BI fields and reports, in the Data Security docs connector list and sitemap (1,146 pages) and Discovery user guide. Searched: https://docs.privacera.com/data-security/connectors/overview/index.html, read 13 Nov 2026. | | [Report](/exposure-map/report/) | none found | None found on 2026-11-13: Power BI, Tableau or Looker connector or column-level lineage into BI fields and reports, in the Data Security docs connector list and sitemap (1,146 pages) and Discovery user guide. Searched: https://docs.privacera.com/data-security/connectors/overview/index.html, read 13 Nov 2026. | | [Viewer](/exposure-map/viewer/) | partial | Access audits record who accessed what, whether allowed or denied, at table/column/path level across integrated platforms, with tags used in the decision. [Source](https://docs.privacera.com/data-security/user-guide/access-management/audits/access_audits.html), read 13 Nov 2026. | | [Agent](/exposure-map/agent/) | partial | Trust3 AI Governance docs say it discovers agents on Databricks, Microsoft Copilot Studio and Azure Foundry, scores them and tracks policy violations. [Source](https://docs.trust3.ai/get-started/overview.html), read 13 Nov 2026. | Documented, partial or none found on the read date. Vendor claims are the vendor's. ## Privacera in each situation | Situation | Rank | Total | Leader | | --- | --- | --- | --- | | [A regulated field](/best-for/regulated-field/) | 13 | 31.0 | Atlan 68.5 | | [Agents on analytics](/best-for/agents-on-analytics/) | 15 | 28.0 | Euno 66.0 | | [A Microsoft estate](/best-for/microsoft-estate/) | 13 | 32.0 | Atlan 68.5 | | [A mixed stack](/best-for/mixed-stack/) | 14 | 26.0 | Euno 68.5 | | [A lean team](/best-for/lean-team/) | 13 | 34.0 | Euno 62.5 | Each situation ranks the same scores under its own published weights. ## The evidence on Privacera, fact by fact - **privacera-01** (Profile, Privacera's own claim): Trust3 AI docs say the Data Security product is formerly Privacera and the docs moved from docs.privacera.com to docs.trust3.ai/data-security/. [Source](https://docs.trust3.ai/), read 13 Nov 2026. - **privacera-02** (Profile, Privacera's own claim): The Privacera docs home states the doc site covers Trust3 AI Cloud and the Self Managed version, so the product is now named Trust3 AI. [Source](https://docs.privacera.com/), read 13 Nov 2026. - **privacera-03** (Profile, Privacera's own claim): Release 9.2.48.1 (Nov 4, 2026) release notes still refer to Privacera's Self-Managed version, so the Privacera name persists in docs alongside Trust3 AI. [Source](https://docs.privacera.com/data-security/resources/releases/release9.2.48.1.html), read 13 Nov 2026. - **privacera-04** (Profile, Privacera's own claim): Trust3 AI docs now split into AI Security (Trust3 AI Governance for agents) and Data Security (the former Privacera product). [Source](https://docs.trust3.ai/), read 13 Nov 2026. - **privacera-05** (Profile, Privacera's own claim): A PR Newswire release issued by Privacera describes the company as founded by the creators of Apache Ranger; the page lists Privacera press releases up to July 2025. [Source](https://www.prnewswire.com/news/privacera/), read 13 Nov 2026. - **privacera-06** (Profile, Privacera's own claim): Trust3 AI connector overview says the platform offers three connector types: access, discovery and encryption. [Source](https://docs.privacera.com/data-security/connectors/overview/index.html), read 13 Nov 2026. - **privacera-07** (Profile, Privacera's own claim): The release notes index shows weekly rolling releases, with 9.2.48.1 on Nov 4, 2026 as the latest. [Source](https://docs.privacera.com/data-security/resources/releases/index.html), read 13 Nov 2026. - **privacera-08** (Profile, Privacera's own claim): Release notes state PrivaceraCloud and Self-Managed follow separate release schedules. [Source](https://docs.privacera.com/data-security/resources/releases/index.html), read 13 Nov 2026. - **privacera-09** (Carries classification downstream, Privacera's own claim): Trust3 AI says Discovery scans connected sources and automatically applies tags (for example EMAIL, PII) to columns, tables and files. [Source](https://docs.privacera.com/data-security/user-guide/discovery/scanning/classification/tags.html), read 13 Nov 2026. - **privacera-10** (Carries classification downstream, Privacera's own claim): Classification uses dictionaries, regex patterns, heuristic models (SSN syntax, credit card Luhn check) and rules that assign tags. [Source](https://docs.privacera.com/data-security/user-guide/discovery/scanning/classification/index.html), read 13 Nov 2026. - **privacera-11** (Carries classification downstream, Privacera's own claim): Discovery tags are synced to Apache Ranger so that tag-based policies can use them. [Source](https://docs.privacera.com/data-security/get-started/discovery/config_sync_tags_to_ranger.html), read 13 Nov 2026. - **privacera-12** (Carries classification downstream, Privacera's own claim): The Collibra connector reads tags assigned in Collibra and applies them in Trust3 AI (Ranger), keeping them synchronized, so tags can come from an external catalog. [Source](https://docs.privacera.com/data-security/connectors/collibra/index.html), read 13 Nov 2026. - **privacera-13** (Carries classification downstream, Privacera's own claim): Propagation documented is from part files up to parent folders in S3, GCS and ADLS, not along column lineage. [Source](https://docs.privacera.com/data-security/user-guide/discovery/advanced/part-file-tag-propagation.html), read 13 Nov 2026. - **privacera-14** (Carries classification downstream, none-found): None found on 2026-11-13: tag or classification propagation along table or column lineage (search for lineage in Data Security docs sitemap of 1,146 pages and fetched Discovery pages), in docs.privacera.com/data-security. Searched: https://docs.privacera.com/data-security/index.html, read 13 Nov 2026. - **privacera-15** (Follows sensitive data into BI, none-found): None found on 2026-11-13: Power BI, Tableau or Looker connector or column-level lineage into BI fields and reports, in the Data Security docs connector list and sitemap (1,146 pages) and Discovery user guide. Searched: https://docs.privacera.com/data-security/connectors/overview/index.html, read 13 Nov 2026. - **privacera-16** (Acts on it, Privacera's own claim): Trust3 AI says masking and deny policies apply to any data carrying a specific tag, for example deny all PII access to external users. [Source](https://docs.privacera.com/data-security/user-guide/discovery/scanning/classification/tags.html), read 13 Nov 2026. - **privacera-17** (Acts on it, Privacera's own claim): For SQL Server, tag-driven masking uses native dynamic data masking functions with types such as Credit Card, Email, Nullify and Random Number. [Source](https://docs.privacera.com/data-security/connectors/mssql/access/tag_based_masking_unmasking.html), read 13 Nov 2026. - **privacera-18** (Acts on it, Privacera's own claim): For Snowflake, masking can depend on group membership evaluated at runtime, so users outside allowed groups see masked values. [Source](https://docs.privacera.com/data-security/connectors/snowflake/access/connector-guide/column-masking-based-on-group-membership.html), read 13 Nov 2026. - **privacera-19** (Acts on it, Privacera's own claim): Discovery compliance workflow policies include de-identification, encryption, expunge and right-to-privacy on a connector support matrix with gaps for several sources. [Source](https://docs.privacera.com/data-security/user-guide/discovery/policies/compliance/workflow.html), read 13 Nov 2026. - **privacera-20** (Acts on it, Privacera's own claim): The Alerts and Notifications page for Discovery compliance policies contains only placeholder text. [Source](https://docs.privacera.com/data-security/user-guide/discovery/policies/compliance/alerts.html), read 13 Nov 2026. - **privacera-21** (Shows who actually saw it, Privacera's own claim): Access audits record who accessed what, whether allowed or denied, at table/column/path level across integrated platforms, with tags used in the decision. [Source](https://docs.privacera.com/data-security/user-guide/access-management/audits/access_audits.html), read 13 Nov 2026. - **privacera-22** (Shows who actually saw it, Privacera's own claim): Audit granularity and policy IDs are limited for platforms integrated via PolicySync, where the platform generates the logs. [Source](https://docs.privacera.com/data-security/user-guide/access-management/audits/access_audits.html), read 13 Nov 2026. - **privacera-23** (Shows who actually saw it, none-found): None found on 2026-11-13: viewers per BI report or per AI agent, in Data Security docs audits section (audits cover data-platform access, not BI report views). Searched: https://docs.privacera.com/data-security/user-guide/access-management/audits/index.html, read 13 Nov 2026. - **privacera-24** (Controls what an agent is told, Privacera's own claim): Trust3 AI Governance docs say it discovers agents on Databricks, Microsoft Copilot Studio and Azure Foundry, scores them and tracks policy violations. [Source](https://docs.trust3.ai/get-started/overview.html), read 13 Nov 2026. - **privacera-25** (Controls what an agent is told, Privacera's own claim): Docs describe an agent inventory that records which agents can access sensitive data, plus an approval workflow before production; this is governance of agents, not per-call data scoping. [Source](https://docs.trust3.ai/get-started/overview.html), read 13 Nov 2026. - **privacera-26** (Controls what an agent is told, Privacera's own claim): Trust3 AI product page claims purpose-based access per request, run-as identity resolution and runtime guardrails (vendor marketing, not documented in docs read). [Source](https://trust3.ai/), read 13 Nov 2026. - **privacera-27** (Controls what an agent is told, observed): PAIG is an Apache-2.0 open-source project to protect GenAI applications; the README does not detail per-user data scoping. [Source](https://github.com/privacera/paig), read 13 Nov 2026. - **privacera-28** (Controls what an agent is told, Privacera's own claim): Trust3 AI documents an MCP server that serves governance context (inventory, policies, trust scores) to external AI clients through a scoped read-only API key; the docs say the key covers reads that the key creator's role can already see. The docs do not describe filtering by the person asking an agent. [Source](https://docs.trust3.ai/how-to-guides/mcp-configuration.html), read 13 Nov 2026. - **privacera-29** (Coverage of the stack, Privacera's own claim): Access connectors named in docs include Snowflake, Databricks Unity Catalog, BigQuery, Redshift, Athena, S3, ADLS, Trino/Starburst, Dremio, Synapse, Oracle, MSSQL, Postgres, MySQL and Vertica; no BI or dbt connectors appear. [Source](https://docs.privacera.com/data-security/connectors/overview/index.html), read 13 Nov 2026. - **privacera-30** (Coverage of the stack, Privacera's own claim): Identity connectors include Okta, Azure AD, LDAP and SCIM; Collibra is the catalog tag-sync connector. [Source](https://docs.privacera.com/data-security/connectors/collibra/index.html), read 13 Nov 2026. - **privacera-31** (Coverage of the stack, Privacera's own claim): Realtime discovery scanning is documented for AWS S3, Azure ADLS, and GCP GCS and BigQuery only. [Source](https://docs.privacera.com/data-security/user-guide/discovery/scanning/ways/realtime-scanning.html), read 13 Nov 2026. - **privacera-32** (Evidence beyond the vendor, observed): PAIG GitHub repository: 209 stars, Apache-2.0, latest releases paig-server-v0.0.11 on 2025-07-25, last push 2025-08-05. [Source](https://github.com/privacera/paig), read 13 Nov 2026. - **privacera-33** (Evidence beyond the vendor, Privacera's own claim): A PR Newswire release issued by Privacera (July 29, 2025) says it was named a Leader in the GigaOm Radar for Data Access Governance for the fourth consecutive time. [Source](https://www.prnewswire.com/news/privacera/), read 13 Nov 2026. - **privacera-34** (Evidence beyond the vendor, none-found): None found on 2026-11-13: a named customer case study by a non-vendor, Gartner Peer Insights page (403), or AWS/Azure marketplace listing with a price, in fetches of gartner.com, aws.amazon.com marketplace and marketplace.microsoft.com. Searched: https://privacera.com/, read 13 Nov 2026. - **privacera-35** (Price transparency, none-found): None found on 2026-11-13: a published price or pricing model; the pricing page offers a trial and demo request only. Searched: https://privacera.com/pricing/, read 13 Nov 2026. - **privacera-36** (Coverage of the stack, third-party): Databricks' partner directory lists Privacera and says it provides fine-grained policy management for data access by row, column, tags and roles. [Source](https://www.databricks.com/partners/privacera), read 13 Nov 2026. - **privacera-37** (Evidence beyond the vendor, third-party): Dremio's security documentation names Privacera, with Lake Formation and Apache Ranger, as a third-party integration for access control and data governance. [Source](https://docs.dremio.com/current/security/), read 13 Nov 2026. ## Compare Privacera - [Euno vs Privacera](/compare/euno-vs-privacera/) - [Immuta vs Privacera](/compare/immuta-vs-privacera/) - [Alternatives to Privacera](/alternatives/privacera/) - [The full index](/index/) ## Sources - https://docs.trust3.ai/: https://docs.trust3.ai/ (read 13 Nov 2026) - https://docs.privacera.com/: https://docs.privacera.com/ (read 13 Nov 2026) - https://docs.privacera.com/data-security/resources/releases/release9.2.48.1.html: https://docs.privacera.com/data-security/resources/releases/release9.2.48.1.html (read 13 Nov 2026) - https://www.prnewswire.com/news/privacera/: https://www.prnewswire.com/news/privacera/ (read 13 Nov 2026) - https://docs.privacera.com/data-security/connectors/overview/index.html: https://docs.privacera.com/data-security/connectors/overview/index.html (read 13 Nov 2026) - https://docs.privacera.com/data-security/resources/releases/index.html: https://docs.privacera.com/data-security/resources/releases/index.html (read 13 Nov 2026) - https://docs.privacera.com/data-security/user-guide/discovery/scanning/classification/tags.html: https://docs.privacera.com/data-security/user-guide/discovery/scanning/classification/tags.html (read 13 Nov 2026) - https://docs.privacera.com/data-security/user-guide/discovery/scanning/classification/index.html: https://docs.privacera.com/data-security/user-guide/discovery/scanning/classification/index.html (read 13 Nov 2026) - https://docs.privacera.com/data-security/get-started/discovery/config_sync_tags_to_ranger.html: https://docs.privacera.com/data-security/get-started/discovery/config_sync_tags_to_ranger.html (read 13 Nov 2026) - https://docs.privacera.com/data-security/connectors/collibra/index.html: https://docs.privacera.com/data-security/connectors/collibra/index.html (read 13 Nov 2026) - https://docs.privacera.com/data-security/user-guide/discovery/advanced/part-file-tag-propagation.html: https://docs.privacera.com/data-security/user-guide/discovery/advanced/part-file-tag-propagation.html (read 13 Nov 2026) - https://docs.privacera.com/data-security/index.html: https://docs.privacera.com/data-security/index.html (read 13 Nov 2026) - https://docs.privacera.com/data-security/connectors/mssql/access/tag_based_masking_unmasking.html: https://docs.privacera.com/data-security/connectors/mssql/access/tag_based_masking_unmasking.html (read 13 Nov 2026) - https://docs.privacera.com/data-security/connectors/snowflake/access/connector-guide/column-masking-based-on-group-membership.html: https://docs.privacera.com/data-security/connectors/snowflake/access/connector-guide/column-masking-based-on-group-membership.html (read 13 Nov 2026) - https://docs.privacera.com/data-security/user-guide/discovery/policies/compliance/workflow.html: https://docs.privacera.com/data-security/user-guide/discovery/policies/compliance/workflow.html (read 13 Nov 2026) - https://docs.privacera.com/data-security/user-guide/discovery/policies/compliance/alerts.html: https://docs.privacera.com/data-security/user-guide/discovery/policies/compliance/alerts.html (read 13 Nov 2026) - https://docs.privacera.com/data-security/user-guide/access-management/audits/access_audits.html: https://docs.privacera.com/data-security/user-guide/access-management/audits/access_audits.html (read 13 Nov 2026) - https://docs.privacera.com/data-security/user-guide/access-management/audits/index.html: https://docs.privacera.com/data-security/user-guide/access-management/audits/index.html (read 13 Nov 2026) - https://docs.trust3.ai/get-started/overview.html: https://docs.trust3.ai/get-started/overview.html (read 13 Nov 2026) - https://trust3.ai/: https://trust3.ai/ (read 13 Nov 2026) - https://github.com/privacera/paig: https://github.com/privacera/paig (read 13 Nov 2026) - https://docs.trust3.ai/how-to-guides/mcp-configuration.html: https://docs.trust3.ai/how-to-guides/mcp-configuration.html (read 13 Nov 2026) - https://docs.privacera.com/data-security/user-guide/discovery/scanning/ways/realtime-scanning.html: https://docs.privacera.com/data-security/user-guide/discovery/scanning/ways/realtime-scanning.html (read 13 Nov 2026) - https://privacera.com/: https://privacera.com/ (read 13 Nov 2026) - https://privacera.com/pricing/: https://privacera.com/pricing/ (read 13 Nov 2026) - https://www.databricks.com/partners/privacera: https://www.databricks.com/partners/privacera (read 13 Nov 2026) - https://docs.dremio.com/current/security/: https://docs.dremio.com/current/security/ (read 13 Nov 2026) Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/platforms/privacera/ --- # Securiti for AI data governance: rank 15 of 16, at 29.5 of 100 PLATFORM PROFILE, read 13 Nov 2026 **The short answer.** Securiti ranks 15 of 16 on the Need to Know index at 29.5 of 100, read 13 Nov 2026. Its best criterion is Acts on it at 6 of 10, and its weakest is Follows sensitive data into BI at 1. The exposure map records 2 of six stages as documented and 3 as partial. - **Category:** Data security posture management and AI data governance platform - **Status:** Exists under this name on 13 Nov 2026, now owned by Veeam: securiti.ai/about says "In December 2025, Veeam acquired Securiti", and a May 2026 release calls it "Veeam's Securiti AI"; the platform is branded DataAI Command Platform (formerly Data Command Center). - **Exposure trail:** Warehouse column: documented; Transformation: partial; BI field: partial; Report: none found; Viewer: partial; Agent: documented - **Warehouses named:** Snowflake, Google BigQuery, Databricks - **BI tools named:** Tableau - **Security tools named:** Microsoft security center (sensitivity labels) - **Rank and total:** 15 of 16, 29.5 of 100 2 of 6 stages documented, 3 partial ## Securiti on the eight criteria | Criterion | Weight | Score | Why | | --- | --- | --- | --- | | Follows sensitive data into BI | 25 | 1 | Lineage from BI and ETL tools is claimed generally, but column-level lineage into BI fields was none found on 2026-11-13. | | Controls what an agent is told | 20 | 4 | Copilot respects source entitlements and labels, with row filtering, but Agent Commander is future and documentation is login-gated. | | Shows who actually saw it | 15 | 3 | Who has access and data access activity are claimed at file and table level; agent activity tracking belongs to Agent Commander, a future release, and report viewers were none found. | | Carries classification downstream | 15 | 3 | Discovers and labels data and imports Microsoft sensitivity labels, but propagation along lineage was none found on 2026-11-13. | | Acts on it | 10 | 6 | Dynamic masking by policy, auto-remediation, assigned findings and agent rollbacks are stated by the vendor only. | | Coverage of the stack | 5 | 2 | Snowflake, BigQuery, Databricks and Tableau are named; dbt, Power BI and Looker connectors were none found. | | Evidence beyond the vendor | 5 | 5 | Vendor-hosted GigaOm claim and unnamed customer; Wikipedia, citing CyberScoop, reports an acquisition plan, not governance confirmation. | | Price transparency | 5 | 1 | Modules are procured by use case with personalized quotes and no list price. | Blind scores for Securiti, 0 to 10. A vendor claim scores at most 7 until a second source confirms it. ## Where Securiti is strongest Vendor-stated: Securiti pairs sensitive data discovery with entitlement-aware, label-based filtering for AI copilots and masking and remediation actions. ## Where Securiti falls short No public evidence of column-level lineage into named BI fields or reports or of viewers per report; its Tableau connector targets the PII object, and docs are login-gated. ## Securiti along the exposure trail | Stage | Reading | Evidence | | --- | --- | --- | | [Warehouse column](/exposure-map/column/) | documented | Securiti says discovery finds personal and sensitive data in structured and unstructured systems. [Source](https://securiti.ai/products/data-discovery/), read 13 Nov 2026. | | [Transformation](/exposure-map/transformation/) | partial | Securiti says lineage is extracted automatically from source systems, BI tools and ETL tools. [Source](https://securiti.ai/products/data-lineage/), read 13 Nov 2026. | | [BI field](/exposure-map/bi-field/) | partial | Securiti says lineage is extracted automatically from source systems, BI tools and ETL tools. [Source](https://securiti.ai/products/data-lineage/), read 13 Nov 2026. | | [Report](/exposure-map/report/) | none found | None found on 2026-11-13: column-level lineage into Tableau or Power BI fields and reports, in the lineage product page and lineage explainer (no column-level or named BI tool statement). Searched: https://securiti.ai/what-is-data-lineage/, read 13 Nov 2026. | | [Viewer](/exposure-map/viewer/) | partial | Securiti says it shows who has data access at file and table level using a graph. [Source](https://securiti.ai/products/access-intelligence/), read 13 Nov 2026. | | [Agent](/exposure-map/agent/) | documented | Securiti says its copilot respects source file entitlements at ingestion and at user consumption. [Source](https://securiti.ai/gencore/safe-enterprise-ai-copilot/), read 13 Nov 2026. | Documented, partial or none found on the read date. Vendor claims are the vendor's. ## Securiti in each situation | Situation | Rank | Total | Leader | | --- | --- | --- | --- | | [A regulated field](/best-for/regulated-field/) | 15 | 27.0 | Atlan 68.5 | | [Agents on analytics](/best-for/agents-on-analytics/) | 13 | 32.5 | Euno 66.0 | | [A Microsoft estate](/best-for/microsoft-estate/) | 14 | 28.5 | Atlan 68.5 | | [A mixed stack](/best-for/mixed-stack/) | 15 | 23.5 | Euno 68.5 | | [A lean team](/best-for/lean-team/) | 16 | 30.5 | Euno 62.5 | Each situation ranks the same scores under its own published weights. ## The evidence on Securiti, fact by fact - **securiti-01** (Profile, Securiti's own claim): Securiti says Veeam acquired it in December 2025. [Source](https://securiti.ai/about/), read 13 Nov 2026. - **securiti-02** (Profile, Securiti's own claim): Veeam, Securiti's acquirer, says in its own press release that it signed a definitive agreement to acquire Securiti AI. [Source](https://www.veeam.com/company/press-release/veeam-to-acquire-securiti-ai.html), read 13 Nov 2026. - **securiti-03** (Profile, Securiti's own claim): Veeam, Securiti's acquirer, says in its own press release that it will continue to offer Securiti AI's Data Command Center. [Source](https://www.veeam.com/company/press-release/veeam-to-acquire-securiti-ai.html), read 13 Nov 2026. - **securiti-04** (Profile, Securiti's own claim): Securiti says in a May 27, 2026 release that it is owned by Veeam ("Veeam's Securiti AI") and was named a Leader in the GigaOm 2026 DSPM Radar. [Source](https://securiti.ai/press-release/veeams-securiti-ai-named-a-leader-and-fast-mover-in-gigaoms-2026-dspm-radar-with-top-scores-among-evaluated-vendors/), read 13 Nov 2026. - **securiti-05** (Profile, Securiti's own claim): Securiti says its DSPM covers 1000+ integrations across data systems. [Source](https://securiti.ai/dspm/), read 13 Nov 2026. - **securiti-06** (Profile, Securiti's own claim): Securiti says discovery uses 200+ native connectors to on-premises, hybrid and multicloud assets. [Source](https://securiti.ai/products/data-discovery/), read 13 Nov 2026. - **securiti-07** (Profile, Securiti's own claim): Securiti says it offers thousands of pre-built connectors, though the connector page names few BI or warehouse products. [Source](https://securiti.ai/connectors/), read 13 Nov 2026. - **securiti-08** (Profile, none-found): None found on 2026-11-13: public documentation pages (release notes, MCP, trust page), in docs.securiti.ai (redirects to a login-gated app, no llms.txt or sitemap) and securiti.ai/trust (404). Searched: https://docs.securiti.ai/, read 13 Nov 2026. - **securiti-09** (Coverage of the stack, Securiti's own claim): Securiti says its Tableau connector discovers, classifies, tags and catalogs data in Tableau's PII object including User (a data-subject-request use, not report scanning). [Source](https://securiti.ai/connectors/tableau/), read 13 Nov 2026. - **securiti-10** (Coverage of the stack, Securiti's own claim): Securiti says Gencore AI connects to AI models, vector databases and data systems; the listed systems are LLMs, vector DBs, SaaS and file stores, with no warehouses or BI tools named. [Source](https://securiti.ai/gencore/integrations/), read 13 Nov 2026. - **securiti-11** (Coverage of the stack, Securiti's own claim): Securiti says it applies automatic object tagging to Snowflake data. [Source](https://securiti.ai/press-release/securiti-joins-snowflake-governance-program/), read 13 Nov 2026. - **securiti-12** (Coverage of the stack, Securiti's own claim): Securiti says Gencore AI pipes and syncs multi-source data to Databricks Delta Tables with contextual filtering. [Source](https://securiti.ai/gencore/partners/databricks/), read 13 Nov 2026. - **securiti-13** (Coverage of the stack, none-found): None found on 2026-11-13: dbt, Power BI, Looker, Purview or Sentinel connectors, in the securiti.ai connectors page (first 100,000 characters; only BigQuery and Tableau appear as named warehouse and BI connectors). Searched: https://securiti.ai/connectors/, read 13 Nov 2026. - **securiti-14** (Follows sensitive data into BI, Securiti's own claim): Securiti says lineage is extracted automatically from source systems, BI tools and ETL tools. [Source](https://securiti.ai/products/data-lineage/), read 13 Nov 2026. - **securiti-15** (Follows sensitive data into BI, Securiti's own claim): Securiti says understanding the lineage of sensitive data is essential for privacy, security and governance. [Source](https://securiti.ai/products/data-lineage/), read 13 Nov 2026. - **securiti-16** (Follows sensitive data into BI, Securiti's own claim): Securiti says its sensitive data catalog automatically tracks changes and transformations of data through its lifecycle. [Source](https://securiti.ai/products/sensitive-data-catalog/), read 13 Nov 2026. - **securiti-17** (Follows sensitive data into BI, none-found): None found on 2026-11-13: column-level lineage into Tableau or Power BI fields and reports, in the lineage product page and lineage explainer (no column-level or named BI tool statement). Searched: https://securiti.ai/what-is-data-lineage/, read 13 Nov 2026. - **securiti-18** (Carries classification downstream, Securiti's own claim): Securiti says discovery finds personal and sensitive data in structured and unstructured systems. [Source](https://securiti.ai/products/data-discovery/), read 13 Nov 2026. - **securiti-19** (Carries classification downstream, Securiti's own claim): Securiti says it classifies and labels data so security controls apply to the most sensitive data. [Source](https://securiti.ai/products/data-classification/), read 13 Nov 2026. - **securiti-20** (Carries classification downstream, Securiti's own claim): Securiti says it can import sensitivity labels from a Microsoft security center. [Source](https://securiti.ai/products/data-classification/), read 13 Nov 2026. - **securiti-21** (Carries classification downstream, Securiti's own claim): Securiti says it automatically applies sensitivity labels to files (the page frames this around files). [Source](https://securiti.ai/products/data-classification/), read 13 Nov 2026. - **securiti-22** (Carries classification downstream, none-found): None found on 2026-11-13: classification or sensitivity tags propagated automatically along lineage to downstream assets, in the lineage and sensitive data catalog product pages. Searched: https://securiti.ai/products/data-lineage/, read 13 Nov 2026. - **securiti-23** (Controls what an agent is told, Securiti's own claim): Securiti says its copilot respects source file entitlements at ingestion and at user consumption. [Source](https://securiti.ai/gencore/safe-enterprise-ai-copilot/), read 13 Nov 2026. - **securiti-24** (Controls what an agent is told, Securiti's own claim): Securiti says it syncs permissions with source system changes and tailors results to user roles. [Source](https://securiti.ai/gencore/safe-enterprise-ai-copilot/), read 13 Nov 2026. - **securiti-25** (Controls what an agent is told, Securiti's own claim): Securiti says it can exclude files with specific labels from Copilot's responses to employee queries. [Source](https://securiti.ai/products/security-for-ai-agents-and-copilots/), read 13 Nov 2026. - **securiti-26** (Controls what an agent is told, Securiti's own claim): Securiti says it labels or quarantines redundant and obsolete files so AI excludes them. [Source](https://securiti.ai/products/security-for-ai-agents-and-copilots/), read 13 Nov 2026. - **securiti-27** (Controls what an agent is told, Securiti's own claim): Securiti says users can be given row filtering policies so they see data by business context. [Source](https://securiti.ai/products/access-intelligence/), read 13 Nov 2026. - **securiti-28** (Controls what an agent is told, Securiti's own claim): Veeam says in Securiti's release that Agent Commander will arrive in a future release of the platform (not yet generally available at the time of the release). [Source](https://securiti.ai/press-release/veeam-introduces-agent-commander-to-confront-agentic-ai-risk-at-enterprise-scale/), read 13 Nov 2026. - **securiti-29** (Controls what an agent is told, none-found): None found on 2026-11-13: MCP server or agent API documentation describing per-call permission scoping, in the Agent Commander page, press release and Gencore pages (docs are login-gated). Searched: https://securiti.ai/agent-commander/, read 13 Nov 2026. - **securiti-30** (Shows who actually saw it, Securiti's own claim): Securiti says it shows who has data access at file and table level using a graph. [Source](https://securiti.ai/products/access-intelligence/), read 13 Nov 2026. - **securiti-31** (Shows who actually saw it, Securiti's own claim): Securiti says it monitors data access activity and identifies active users. [Source](https://securiti.ai/products/access-intelligence/), read 13 Nov 2026. - **securiti-32** (Shows who actually saw it, Securiti's own claim): Securiti says Agent Commander tracks agent activity at file level. [Source](https://securiti.ai/agent-commander/), read 13 Nov 2026. - **securiti-33** (Shows who actually saw it, none-found): None found on 2026-11-13: viewers per BI report or dashboard from usage logs, in the access intelligence page (access is described at file and table level). Searched: https://securiti.ai/products/access-intelligence/, read 13 Nov 2026. - **securiti-34** (Acts on it, Securiti's own claim): Securiti says it dynamically masks sensitive data by policy. [Source](https://securiti.ai/dspm/), read 13 Nov 2026. - **securiti-35** (Acts on it, Securiti's own claim): Securiti says it auto-remediates misconfigurations or notifies data stewards. [Source](https://securiti.ai/dspm/), read 13 Nov 2026. - **securiti-36** (Acts on it, Securiti's own claim): Securiti says policies automatically assign security findings to the right teams. [Source](https://securiti.ai/products/security-for-ai-agents-and-copilots/), read 13 Nov 2026. - **securiti-37** (Acts on it, Securiti's own claim): Securiti says it uses dynamic data masking on Snowflake data. [Source](https://securiti.ai/press-release/securiti-joins-snowflake-governance-program/), read 13 Nov 2026. - **securiti-38** (Acts on it, Securiti's own claim): Veeam says Agent Commander can undo AI agent mistakes with rollbacks. [Source](https://securiti.ai/press-release/veeam-introduces-agent-commander-to-confront-agentic-ai-risk-at-enterprise-scale/), read 13 Nov 2026. - **securiti-39** (Evidence beyond the vendor, Securiti's own claim): Securiti says GigaOm named it a Leader in the 2026 DSPM Radar (dated May 27, 2026); the page is Securiti-hosted. [Source](https://securiti.ai/press-release/veeams-securiti-ai-named-a-leader-and-fast-mover-in-gigaoms-2026-dspm-radar-with-top-scores-among-evaluated-vendors/), read 13 Nov 2026. - **securiti-40** (Evidence beyond the vendor, Securiti's own claim): Securiti publishes a case study on an unnamed global manufacturer that used file-level evidence after a breach. [Source](https://securiti.ai/case-studies/global-manufacturer-data-intelligence/), read 13 Nov 2026. - **securiti-41** (Evidence beyond the vendor, observed): The Securiti-ai GitHub organization shows zero public repositories, so no code is observable. [Source](https://api.github.com/users/securiti-ai), read 13 Nov 2026. - **securiti-42** (Evidence beyond the vendor, none-found): None found on 2026-11-13: a Gartner Peer Insights page (403), AWS or Azure marketplace listing with a plan (no Securiti entry in AWS search), or a customer-authored case study, in those sites. Searched: https://securiti.ai/, read 13 Nov 2026. - **securiti-43** (Price transparency, Securiti's own claim): Securiti says modules are procured by use case and a quote is personalized, with no list prices. [Source](https://securiti.ai/pricing/), read 13 Nov 2026. - **securiti-44** (Price transparency, none-found): None found on 2026-11-13: published prices or a price model beyond module-based quotes, in the securiti.ai pricing page. Searched: https://securiti.ai/pricing/, read 13 Nov 2026. - **securiti-45** (Profile, third-party): CyberScoop, an independent news site, reports Veeam agreed to acquire Securiti AI for $1.725 billion and describes Securiti AI as a San Jose company that helps organizations see what data they have, who can access it and how it is used. [Source](https://cyberscoop.com/veeam-securiti-ai-acquisition/), read 13 Nov 2026. - **securiti-46** (Evidence beyond the vendor, third-party): Wikipedia's Veeam article, citing CyberScoop, says Veeam disclosed in October 2025 plans to acquire Securiti AI for $1.725 billion in cash and stock. [Source](https://en.wikipedia.org/wiki/Veeam), read 13 Nov 2026. ## Compare Securiti - [Euno vs Securiti](/compare/euno-vs-securiti/) - [OneTrust vs Securiti](/compare/onetrust-vs-securiti/) - [Alternatives to Securiti](/alternatives/securiti/) - [The full index](/index/) ## Sources - https://securiti.ai/about/: https://securiti.ai/about/ (read 13 Nov 2026) - https://www.veeam.com/company/press-release/veeam-to-acquire-securiti-ai.html: https://www.veeam.com/company/press-release/veeam-to-acquire-securiti-ai.html (read 13 Nov 2026) - https://securiti.ai/press-release/veeams-securiti-ai-named-a-leader-and-fast-mover-in-gigaoms-2026-dspm-radar-with-top-scores-among-evaluated-vendors/: https://securiti.ai/press-release/veeams-securiti-ai-named-a-leader-and-fast-mover-in-gigaoms-2026-dspm-radar-with-top-scores-among-evaluated-vendors/ (read 13 Nov 2026) - https://securiti.ai/dspm/: https://securiti.ai/dspm/ (read 13 Nov 2026) - https://securiti.ai/products/data-discovery/: https://securiti.ai/products/data-discovery/ (read 13 Nov 2026) - https://securiti.ai/connectors/: https://securiti.ai/connectors/ (read 13 Nov 2026) - https://docs.securiti.ai/: https://docs.securiti.ai/ (read 13 Nov 2026) - https://securiti.ai/connectors/tableau/: https://securiti.ai/connectors/tableau/ (read 13 Nov 2026) - https://securiti.ai/gencore/integrations/: https://securiti.ai/gencore/integrations/ (read 13 Nov 2026) - https://securiti.ai/press-release/securiti-joins-snowflake-governance-program/: https://securiti.ai/press-release/securiti-joins-snowflake-governance-program/ (read 13 Nov 2026) - https://securiti.ai/gencore/partners/databricks/: https://securiti.ai/gencore/partners/databricks/ (read 13 Nov 2026) - https://securiti.ai/products/data-lineage/: https://securiti.ai/products/data-lineage/ (read 13 Nov 2026) - https://securiti.ai/products/sensitive-data-catalog/: https://securiti.ai/products/sensitive-data-catalog/ (read 13 Nov 2026) - https://securiti.ai/what-is-data-lineage/: https://securiti.ai/what-is-data-lineage/ (read 13 Nov 2026) - https://securiti.ai/products/data-classification/: https://securiti.ai/products/data-classification/ (read 13 Nov 2026) - https://securiti.ai/gencore/safe-enterprise-ai-copilot/: https://securiti.ai/gencore/safe-enterprise-ai-copilot/ (read 13 Nov 2026) - https://securiti.ai/products/security-for-ai-agents-and-copilots/: https://securiti.ai/products/security-for-ai-agents-and-copilots/ (read 13 Nov 2026) - https://securiti.ai/products/access-intelligence/: https://securiti.ai/products/access-intelligence/ (read 13 Nov 2026) - https://securiti.ai/press-release/veeam-introduces-agent-commander-to-confront-agentic-ai-risk-at-enterprise-scale/: https://securiti.ai/press-release/veeam-introduces-agent-commander-to-confront-agentic-ai-risk-at-enterprise-scale/ (read 13 Nov 2026) - https://securiti.ai/agent-commander/: https://securiti.ai/agent-commander/ (read 13 Nov 2026) - https://securiti.ai/case-studies/global-manufacturer-data-intelligence/: https://securiti.ai/case-studies/global-manufacturer-data-intelligence/ (read 13 Nov 2026) - https://api.github.com/users/securiti-ai: https://api.github.com/users/securiti-ai (read 13 Nov 2026) - https://securiti.ai/: https://securiti.ai/ (read 13 Nov 2026) - https://securiti.ai/pricing/: https://securiti.ai/pricing/ (read 13 Nov 2026) - https://cyberscoop.com/veeam-securiti-ai-acquisition/: https://cyberscoop.com/veeam-securiti-ai-acquisition/ (read 13 Nov 2026) - https://en.wikipedia.org/wiki/Veeam: https://en.wikipedia.org/wiki/Veeam (read 13 Nov 2026) Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/platforms/securiti/ --- # OneTrust for AI data governance: rank 16 of 16, at 26.5 of 100 PLATFORM PROFILE, read 13 Nov 2026 **The short answer.** OneTrust ranks 16 of 16 on the Need to Know index at 26.5 of 100, read 13 Nov 2026. Its best criterion is Acts on it at 6 of 10, and its weakest is Follows sensitive data into BI at 0. The exposure map records 1 of six stages as documented and 1 as partial. - **Category:** Privacy, AI governance and data use governance platform - **Status:** Exists under this name on 13 Nov 2026 (onetrust.com serves 'AI-Ready Governance Platform' with Data Use Governance, AI Governance and Data Discovery; developer portal at developer.onetrust.com shows releases through 2026). - **Exposure trail:** Warehouse column: documented; Transformation: none found; BI field: none found; Report: none found; Viewer: none found; Agent: partial - **Warehouses named:** Snowflake, Databricks Unity Catalog, Amazon Redshift, Amazon Athena, Amazon RDS for SQL Server, Google BigQuery, Azure Databricks, Teradata - **BI tools named:** none found on 13 Nov 2026 - **Security tools named:** Palo Alto Networks - **Rank and total:** 16 of 16, 26.5 of 100 1 of 6 stages documented, 1 partial ## OneTrust on the eight criteria | Criterion | Weight | Score | Why | | --- | --- | --- | --- | | Follows sensitive data into BI | 25 | 0 | Column lineage into Tableau, Power BI or Looker was none found on 2026-11-13; no BI tool appears in the data source list. | | Controls what an agent is told | 20 | 3 | Agent tool and data controls are documented, but authorization is per service token and not per end user. | | Shows who actually saw it | 15 | 3 | Runtime activity counts per agent exist, but they are aggregated, with no per-viewer record or report viewers found. | | Carries classification downstream | 15 | 3 | AI-driven classification and API-written labels exist, but propagation along lineage was none found on 2026-11-13. | | Acts on it | 10 | 6 | Masking and row filtering pushed into Snowflake and Databricks, plus AI Guard redact and block; AI Guard is not recommended for high volumes. | | Coverage of the stack | 5 | 3 | Forty-four data sources are enumerated, but no BI or transformation tool; AI governance platforms are covered. | | Evidence beyond the vendor | 5 | 5 | A vendor-quoted customer and open client code exist; the only third-party page is a 2021 Okta listing unrelated to governance. | | Price transparency | 5 | 3 | AI Governance pricing is based on admin users and AI inventory with no amounts; Data Use Governance had none found. | Blind scores for OneTrust, 0 to 10. A vendor claim scores at most 7 until a second source confirms it. ## Where OneTrust is strongest Vendor-stated: Turns data policies into native masking and row-filtering controls in Snowflake and Databricks Unity Catalog and governs agent tools and prompts with AI Guard, with enforcement audited in the platform's own logs. ## Where OneTrust falls short No documented column lineage into BI fields or reports and no viewer-per-report data, so a sensitive column is not followed past the warehouse. ## OneTrust along the exposure trail | Stage | Reading | Evidence | | --- | --- | --- | | [Warehouse column](/exposure-map/column/) | documented | OneTrust says Data Use Governance classifies structured and unstructured sources with AI-driven techniques, using four contexts: business, regulatory, consent and data. [Source](https://www.onetrust.com/solutions/data-use-governance/), read 13 Nov 2026. | | [Transformation](/exposure-map/transformation/) | none found | None found on 2026-11-13: column lineage from warehouse through dbt or SQL transformation into Tableau, Power BI or Looker fields and reports, in the OneTrust developer documentation index, Data Use Governance page and integrations page. Searched: https://developer.onetrust.com/onetrust/llms.txt, read 13 Nov 2026. | | [BI field](/exposure-map/bi-field/) | none found | None found on 2026-11-13: column lineage from warehouse through dbt or SQL transformation into Tableau, Power BI or Looker fields and reports, in the OneTrust developer documentation index, Data Use Governance page and integrations page. Searched: https://developer.onetrust.com/onetrust/llms.txt, read 13 Nov 2026. | | [Report](/exposure-map/report/) | none found | None found on 2026-11-13: column lineage from warehouse through dbt or SQL transformation into Tableau, Power BI or Looker fields and reports, in the OneTrust developer documentation index, Data Use Governance page and integrations page. Searched: https://developer.onetrust.com/onetrust/llms.txt, read 13 Nov 2026. | | [Viewer](/exposure-map/viewer/) | none found | None found on 2026-11-13: viewers per report or dashboard (BI usage or query logs), in the OneTrust developer documentation index and the Data Use Governance and AI Governance product pages. Searched: https://developer.onetrust.com/onetrust/llms.txt, read 13 Nov 2026. | | [Agent](/exposure-map/agent/) | partial | OneTrust says its AI Governance module governs agents with defined purpose, permissions and allowed actions across MCP-enabled environments. [Source](https://www.onetrust.com/products/ai-governance/), read 13 Nov 2026. | Documented, partial or none found on the read date. Vendor claims are the vendor's. ## OneTrust in each situation | Situation | Rank | Total | Leader | | --- | --- | --- | --- | | [A regulated field](/best-for/regulated-field/) | 16 | 23.5 | Atlan 68.5 | | [Agents on analytics](/best-for/agents-on-analytics/) | 14 | 28.5 | Euno 66.0 | | [A Microsoft estate](/best-for/microsoft-estate/) | 16 | 25.5 | Atlan 68.5 | | [A mixed stack](/best-for/mixed-stack/) | 16 | 22.5 | Euno 68.5 | | [A lean team](/best-for/lean-team/) | 15 | 31.0 | Euno 62.5 | Each situation ranks the same scores under its own published weights. ## The evidence on OneTrust, fact by fact - **onetrust-01** (Profile, third-party): Wikipedia describes OneTrust as an American software company headquartered in Atlanta, Georgia. [Source](https://en.wikipedia.org/wiki/OneTrust), read 13 Nov 2026. - **onetrust-02** (Profile, OneTrust's own claim): OneTrust says it developed its first technology platform for responsible data use in 2016. [Source](https://www.onetrust.com/about-us/), read 13 Nov 2026. - **onetrust-03** (Profile, OneTrust's own claim): OneTrust says its About page counts more than 500 pre-built plug-ins connecting through APIs, SDKs and data feeds. [Source](https://www.onetrust.com/about-us/), read 13 Nov 2026. - **onetrust-04** (Profile, third-party): Wikipedia says OneTrust grew by acquisitions into adjacent markets such as third-party risk and security assurance, including Integris Software and DataGuidance. [Source](https://en.wikipedia.org/wiki/OneTrust), read 13 Nov 2026. - **onetrust-05** (Profile, OneTrust's own claim): OneTrust's product pages show a CEO change: the Data Use Governance page footer links to a news item announcing John Heyman as CEO. [Source](https://www.onetrust.com/solutions/data-use-governance/), read 13 Nov 2026. - **onetrust-06** (Profile, OneTrust's own claim): OneTrust positions Data Use Governance as one module of its AI-Ready Governance Platform, next to AI Governance, Consent and Preferences, Privacy Automation, Tech Risk and Compliance, and Third-Party Management. [Source](https://www.onetrust.com/solutions/data-use-governance/), read 13 Nov 2026. - **onetrust-07** (Profile, OneTrust's own claim): OneTrust publishes a trust page listing SOC 2, ISO and other certifications and audit reports. [Source](https://www.onetrust.com/trust/), read 13 Nov 2026. - **onetrust-08** (Carries classification downstream, OneTrust's own claim): OneTrust says Data Use Governance classifies structured and unstructured sources with AI-driven techniques, using four contexts: business, regulatory, consent and data. [Source](https://www.onetrust.com/solutions/data-use-governance/), read 13 Nov 2026. - **onetrust-09** (Carries classification downstream, OneTrust's own claim): OneTrust's data discovery API reference lists scan profiles, scan jobs, data sources and custom classifiers, and the data catalog API lets tags and terms be associated to data assets. [Source](https://developer.onetrust.com/onetrust/reference/data-use-governance-data-catalog/llms.txt), read 13 Nov 2026. - **onetrust-10** (Carries classification downstream, none-found): None found on 2026-11-13: classification or sensitivity labels carried downstream along column lineage, in the OneTrust developer documentation index and the Data Use Governance product page. Searched: https://developer.onetrust.com/onetrust/llms.txt, read 13 Nov 2026. - **onetrust-11** (Follows sensitive data into BI, none-found): None found on 2026-11-13: column lineage from warehouse through dbt or SQL transformation into Tableau, Power BI or Looker fields and reports, in the OneTrust developer documentation index, Data Use Governance page and integrations page. Searched: https://developer.onetrust.com/onetrust/llms.txt, read 13 Nov 2026. - **onetrust-12** (Shows who actually saw it, none-found): None found on 2026-11-13: viewers per report or dashboard (BI usage or query logs), in the OneTrust developer documentation index and the Data Use Governance and AI Governance product pages. Searched: https://developer.onetrust.com/onetrust/llms.txt, read 13 Nov 2026. - **onetrust-13** (Shows who actually saw it, OneTrust's own claim): OneTrust says Data Use Governance pushes masking and row-filtering logic into Snowflake or Databricks and relies on the platform's own audit logs to track last-mile enforcement. [Source](https://www.onetrust.com/solutions/data-use-governance/), read 13 Nov 2026. - **onetrust-14** (Shows who actually saw it, OneTrust's own claim): OneTrust says its AI Governance runtime view can track blocked, redacted, routed and allowed activity per system, model, agent or application. [Source](https://www.onetrust.com/products/ai-governance/), read 13 Nov 2026. - **onetrust-15** (Acts on it, OneTrust's own claim): OneTrust says Data Use Governance gives visibility into where column masking and row-filtering policies are applied, pushing policy logic down through platforms like Snowflake or Databricks for native enforcement. [Source](https://www.onetrust.com/solutions/data-use-governance/), read 13 Nov 2026. - **onetrust-16** (Acts on it, OneTrust's own claim): OneTrust's Databricks announcement says rows are filtered by customer consent status and query purpose, and sensitive personal data is masked by role and declared purpose, through Unity Catalog. [Source](https://www.prnewswire.com/news-releases/onetrust-announces-partnership-with-databricks-to-power-real-time-policy-enforcement-in-the-databricks-data-intelligence-platform-302477871.html), read 13 Nov 2026. - **onetrust-17** (Acts on it, OneTrust's own claim): OneTrust says AI Guard can redact sensitive data or block whole messages in prompts and responses, with 300+ built-in classifiers. [Source](https://developer.onetrust.com/onetrust/docs/ai-guard.md), read 13 Nov 2026. - **onetrust-18** (Acts on it, OneTrust's own claim): OneTrust says runtime governance can block, route, redact or restrict agent behavior at the point of execution, with coverage varying by integration. [Source](https://www.onetrust.com/products/ai-governance/), read 13 Nov 2026. - **onetrust-19** (Controls what an agent is told, OneTrust's own claim): OneTrust says its AI Governance module governs agents with defined purpose, permissions and allowed actions across MCP-enabled environments. [Source](https://www.onetrust.com/products/ai-governance/), read 13 Nov 2026. - **onetrust-20** (Controls what an agent is told, OneTrust's own claim): OneTrust says its MCP governance controls define which tools an agent may invoke and what data it can access, documented for audit. [Source](https://www.onetrust.com/products/ai-governance/), read 13 Nov 2026. - **onetrust-21** (Controls what an agent is told, OneTrust's own claim): OneTrust documents the AI Guard control plane as defining classification behavior without collecting prompts or responses; only summary metrics are sent back. [Source](https://developer.onetrust.com/onetrust/docs/ai-guard.md), read 13 Nov 2026. - **onetrust-22** (Controls what an agent is told, observed): The public AI Guard SDK README shows the client authenticated with a service API key and an agent_id, with no per-end-user identity parameter in its quick start. [Source](https://github.com/onetrust-oss/ai-guard-sdk), read 13 Nov 2026. - **onetrust-23** (Controls what an agent is told, OneTrust's own claim): OneTrust's developer MCP server serves documentation and API help to code editors such as Cursor and Windsurf; the docs say no authentication headers are currently required. [Source](https://developer.onetrust.com/onetrust/reference/mcp.md), read 13 Nov 2026. - **onetrust-24** (Controls what an agent is told, OneTrust's own claim): OneTrust states that platform coverage varies: Amazon Bedrock gives usage, token, log analysis and PII findings, while Microsoft Foundry gives evaluation visibility and guardrail enforcement. [Source](https://www.onetrust.com/products/ai-governance/), read 13 Nov 2026. - **onetrust-25** (Coverage of the stack, OneTrust's own claim): OneTrust says its Databricks Unity Catalog integration combines AI asset oversight with automated data controls. [Source](https://www.onetrust.com/integrations/databricks/), read 13 Nov 2026. - **onetrust-26** (Coverage of the stack, OneTrust's own claim): OneTrust says it integrates natively with Snowflake and offers a Consent Management Native App in the Snowflake Marketplace and Trust Center scanners. [Source](https://www.onetrust.com/integrations/snowflake/), read 13 Nov 2026. - **onetrust-27** (Coverage of the stack, OneTrust's own claim): OneTrust says Amazon Redshift and Amazon RDS for SQL Server can be connected to OneTrust Data Discovery to discover and classify PII. [Source](https://www.onetrust.com/integrations/), read 13 Nov 2026. - **onetrust-28** (Coverage of the stack, OneTrust's own claim): OneTrust says AI Governance supports Amazon Bedrock, Microsoft AI Foundry, Google Vertex and Databricks Unity Catalog out of the box and integrates with Jira and Palo Alto Networks. [Source](https://www.onetrust.com/products/ai-governance/), read 13 Nov 2026. - **onetrust-29** (Coverage of the stack, OneTrust's own claim): OneTrust's press release says it achieved validated Databricks Technology Partner status and integrates with Unity Catalog to sync AI projects. [Source](https://www.prnewswire.com/news-releases/onetrust-is-officially-a-validated-databricks-technology-partner-302596908.html), read 13 Nov 2026. - **onetrust-30** (Coverage of the stack, OneTrust's own claim): The OneTrust changelog for release 202609.1.0 lists new generally available AI Governance attribute APIs and an ai-governance task source, showing active AI Governance releases. [Source](https://developer.onetrust.com/onetrust/changelog/september-4-2026-20260910.md), read 13 Nov 2026. - **onetrust-31** (Evidence beyond the vendor, OneTrust's own claim): OneTrust's Data Use Governance page quotes BT Group's Group Data Privacy and Ethics Officer on simplified compliance and trusting the data. [Source](https://www.onetrust.com/solutions/data-use-governance/), read 13 Nov 2026. - **onetrust-32** (Evidence beyond the vendor, observed): The public GitHub repository onetrust-oss/ai-guard-sdk (Apache-2.0, Python, last pushed 2026-10-28) is the open client for AI Guard; observed on the GitHub API and README. [Source](https://github.com/onetrust-oss/ai-guard-sdk), read 13 Nov 2026. - **onetrust-33** (Evidence beyond the vendor, none-found): None found on 2026-11-13: a Gartner Peer Insights, Forrester or IDC page naming OneTrust Data Use Governance or Data Discovery that could be read (Gartner and G2 returned 403), and no third-party customer case study naming Data Use Governance enforcement in Snowflake or Databricks. Searched: https://www.onetrust.com/solutions/data-use-governance/, read 13 Nov 2026. - **onetrust-34** (Price transparency, OneTrust's own claim): OneTrust's pricing page lists AI Governance with a Get Pricing button and says pricing is based on admin users and AI inventory; no amounts are shown. [Source](https://www.onetrust.com/pricing/), read 13 Nov 2026. - **onetrust-35** (Price transparency, none-found): None found on 2026-11-13: a published package or price for Data Use Governance or Data Discovery, in the OneTrust pricing page (its package tabs do not list them). Searched: https://www.onetrust.com/pricing/, read 13 Nov 2026. - **onetrust-46** (Evidence beyond the vendor, observed): A community GitHub repository, Knuckles-Team/onetrust-api (MIT, not published by OneTrust), describes a Python client, MCP server and A2A agent for the OneTrust platform; it shows third parties build on the public API, and says nothing about customers or governance outcomes. [Source](https://raw.githubusercontent.com/Knuckles-Team/onetrust-api/main/README.md), read 13 Nov 2026. - **onetrust-47** (Evidence beyond the vendor, observed): The PyPI registry lists a community package onetrust-api (version 1.4.0, MIT, uploaded 2026-11-13) summarized as an API plus MCP server plus A2A agent for OneTrust; the maintainers are not OneTrust. [Source](https://pypi.org/pypi/onetrust-api/json), read 13 Nov 2026. - **onetrust-48** (Evidence beyond the vendor, third-party): Okta's Integration Network page names OneTrust as an integration and describes it as consent and preference syncing with Okta Universal Directory; the page was last updated in February 2021 and does not cover data governance. [Source](https://www.okta.com/integrations/onetrust/), read 13 Nov 2026. - **onetrust-49** (Carries classification downstream, OneTrust's own claim): OneTrust's Data Catalog API says terms, tags and attributes written to an existing data asset are merged with the existing values, so labels from an outside system can be pushed onto catalog assets through the API. [Source](https://developer.onetrust.com/onetrust/reference/createorupsertdataassetv1-1.md), read 13 Nov 2026. - **onetrust-50** (Coverage of the stack, OneTrust's own claim): OneTrust's Data Discovery Worker Node API lets a custom connector submit content to be classified and metadata to be cataloged, which extends discovery to sources without a built-in connector. [Source](https://developer.onetrust.com/onetrust/reference/classifydatausingpost.md), read 13 Nov 2026. - **onetrust-51** (Coverage of the stack, OneTrust's own claim): OneTrust's Data Discovery API reference enumerates 44 data source system types, including Snowflake, Redshift, Amazon Athena, Google BigQuery, Azure Databricks, Iceberg and Kafka plus file and SaaS systems; no BI tool or transformation tool such as dbt appears in the list. [Source](https://developer.onetrust.com/onetrust/reference/getallusingget_1.md), read 13 Nov 2026. - **onetrust-52** (Controls what an agent is told, OneTrust's own claim): OneTrust's AI Guard documentation says its production authorization mode forwards the client's bearer token to a OneTrust endpoint and authorizes the request on a 200 response, so authorization is per service token, not per end user. [Source](https://developer.onetrust.com/onetrust/docs/ai-guard-authentication.md), read 13 Nov 2026. - **onetrust-53** (Shows who actually saw it, OneTrust's own claim): OneTrust's AI Guard documentation says a unique AI agent in AI Governance is the combination of agent_id and platform, so usage metrics attach to an agent, not to a report. [Source](https://developer.onetrust.com/onetrust/docs/ai-guard-metrics-overview.md), read 13 Nov 2026. - **onetrust-54** (Shows who actually saw it, OneTrust's own claim): OneTrust's AI Guard documentation says metrics are aggregated and flushed on an interval, and only aggregated counts leave the customer environment, so there is no per-viewer record of who received sensitive content. [Source](https://developer.onetrust.com/onetrust/docs/ai-guard-metrics-overview.md), read 13 Nov 2026. - **onetrust-55** (Acts on it, OneTrust's own claim): OneTrust's AI Guard FAQ says the tool is optimized for development and testing workloads and is not recommended for the large classification volumes of externally facing AI applications or agents as of that release. [Source](https://developer.onetrust.com/onetrust/docs/ai-guard-faq.md), read 13 Nov 2026. ## Compare OneTrust - [Euno vs OneTrust](/compare/euno-vs-onetrust/) - [OneTrust vs Securiti](/compare/onetrust-vs-securiti/) - [Alternatives to OneTrust](/alternatives/onetrust/) - [The full index](/index/) ## Sources - https://en.wikipedia.org/wiki/OneTrust: https://en.wikipedia.org/wiki/OneTrust (read 13 Nov 2026) - https://www.onetrust.com/about-us/: https://www.onetrust.com/about-us/ (read 13 Nov 2026) - https://www.onetrust.com/solutions/data-use-governance/: https://www.onetrust.com/solutions/data-use-governance/ (read 13 Nov 2026) - https://www.onetrust.com/trust/: https://www.onetrust.com/trust/ (read 13 Nov 2026) - https://developer.onetrust.com/onetrust/reference/data-use-governance-data-catalog/llms.txt: https://developer.onetrust.com/onetrust/reference/data-use-governance-data-catalog/llms.txt (read 13 Nov 2026) - https://developer.onetrust.com/onetrust/llms.txt: https://developer.onetrust.com/onetrust/llms.txt (read 13 Nov 2026) - https://www.onetrust.com/products/ai-governance/: https://www.onetrust.com/products/ai-governance/ (read 13 Nov 2026) - https://www.prnewswire.com/news-releases/onetrust-announces-partnership-with-databricks-to-power-real-time-policy-enforcement-in-the-databricks-data-intelligence-platform-302477871.html: https://www.prnewswire.com/news-releases/onetrust-announces-partnership-with-databricks-to-power-real-time-policy-enforcement-in-the-databricks-data-intelligence-platform-302477871.html (read 13 Nov 2026) - https://developer.onetrust.com/onetrust/docs/ai-guard.md: https://developer.onetrust.com/onetrust/docs/ai-guard.md (read 13 Nov 2026) - https://github.com/onetrust-oss/ai-guard-sdk: https://github.com/onetrust-oss/ai-guard-sdk (read 13 Nov 2026) - https://developer.onetrust.com/onetrust/reference/mcp.md: https://developer.onetrust.com/onetrust/reference/mcp.md (read 13 Nov 2026) - https://www.onetrust.com/integrations/databricks/: https://www.onetrust.com/integrations/databricks/ (read 13 Nov 2026) - https://www.onetrust.com/integrations/snowflake/: https://www.onetrust.com/integrations/snowflake/ (read 13 Nov 2026) - https://www.onetrust.com/integrations/: https://www.onetrust.com/integrations/ (read 13 Nov 2026) - https://www.prnewswire.com/news-releases/onetrust-is-officially-a-validated-databricks-technology-partner-302596908.html: https://www.prnewswire.com/news-releases/onetrust-is-officially-a-validated-databricks-technology-partner-302596908.html (read 13 Nov 2026) - https://developer.onetrust.com/onetrust/changelog/september-4-2026-20260910.md: https://developer.onetrust.com/onetrust/changelog/september-4-2026-20260910.md (read 13 Nov 2026) - https://www.onetrust.com/pricing/: https://www.onetrust.com/pricing/ (read 13 Nov 2026) - https://raw.githubusercontent.com/Knuckles-Team/onetrust-api/main/README.md: https://raw.githubusercontent.com/Knuckles-Team/onetrust-api/main/README.md (read 13 Nov 2026) - https://pypi.org/pypi/onetrust-api/json: https://pypi.org/pypi/onetrust-api/json (read 13 Nov 2026) - https://www.okta.com/integrations/onetrust/: https://www.okta.com/integrations/onetrust/ (read 13 Nov 2026) - https://developer.onetrust.com/onetrust/reference/createorupsertdataassetv1-1.md: https://developer.onetrust.com/onetrust/reference/createorupsertdataassetv1-1.md (read 13 Nov 2026) - https://developer.onetrust.com/onetrust/reference/classifydatausingpost.md: https://developer.onetrust.com/onetrust/reference/classifydatausingpost.md (read 13 Nov 2026) - https://developer.onetrust.com/onetrust/reference/getallusingget_1.md: https://developer.onetrust.com/onetrust/reference/getallusingget_1.md (read 13 Nov 2026) - https://developer.onetrust.com/onetrust/docs/ai-guard-authentication.md: https://developer.onetrust.com/onetrust/docs/ai-guard-authentication.md (read 13 Nov 2026) - https://developer.onetrust.com/onetrust/docs/ai-guard-metrics-overview.md: https://developer.onetrust.com/onetrust/docs/ai-guard-metrics-overview.md (read 13 Nov 2026) - https://developer.onetrust.com/onetrust/docs/ai-guard-faq.md: https://developer.onetrust.com/onetrust/docs/ai-guard-faq.md (read 13 Nov 2026) Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/platforms/onetrust/ --- # 16 platform profiles, each with its score, its trail and its gap PLATFORMS, read 13 Nov 2026 **The short answer.** Each platform page gives one tool's rank and total, its score on the eight criteria with the reason for each, its exposure trail from column to agent, one sentence on where it is strongest, one on where it falls short, and every sourced fact behind the score, read 13 Nov 2026. | Rank | Platform | Category | Exposure trail | Total | | --- | --- | --- | --- | --- | | 1 | [Euno](/platforms/euno/) | AI context platform for enterprise data (metadata graph with rule-based labels and an MCP server) | Warehouse column: documented; Transformation: partial; BI field: documented; Report: documented; Viewer: partial; Agent: partial | 67.0 | | 2 | [Atlan](/platforms/atlan/) | Data catalog, metadata and governance platform, now marketed as a context layer for AI | Warehouse column: documented; Transformation: partial; BI field: partial; Report: partial; Viewer: partial; Agent: documented | 65.5 | | 3 | [DataHub](/platforms/datahub/) | Open source data catalog and metadata platform with a managed Cloud edition | Warehouse column: partial; Transformation: partial; BI field: partial; Report: partial; Viewer: partial; Agent: documented | 61.0 | | 4 | [Snowflake Horizon](/platforms/snowflake/) | Data platform's built-in catalog, governance and context layer | Warehouse column: documented; Transformation: partial; BI field: partial; Report: partial; Viewer: partial; Agent: documented | 55.5 | | 5 | [Databricks Unity Catalog](/platforms/databricks/) | Lakehouse data catalog and governance layer (built into the Databricks platform, with an open source core) | Warehouse column: documented; Transformation: partial; BI field: partial; Report: partial; Viewer: partial; Agent: documented | 55.0 | | 6 | [Microsoft Purview](/platforms/microsoft-purview/) | Microsoft data security and compliance suite (sensitivity labels, DLP, DSPM for AI) plus a retiring data catalog and Data Map | Warehouse column: documented; Transformation: partial; BI field: partial; Report: documented; Viewer: partial; Agent: partial | 54.5 | | 7 | [Alation](/platforms/alation/) | Data catalog and data intelligence platform with governance, data quality and AI agents | Warehouse column: documented; Transformation: partial; BI field: documented; Report: documented; Viewer: partial; Agent: documented | 54.0 | | 8 | [Select Star](/platforms/select-star/) | Data catalog, column-level lineage and metadata platform (acquired by Snowflake) | Warehouse column: partial; Transformation: partial; BI field: documented; Report: documented; Viewer: partial; Agent: partial | 53.5 | | 9 | [Secoda](/platforms/secoda/) | Data catalog, governance and AI analytics platform, now part of Atlassian | Warehouse column: documented; Transformation: partial; BI field: partial; Report: partial; Viewer: partial; Agent: partial | 47.5 | | 10 | [Collibra](/platforms/collibra/) | Data governance platform: catalog, lineage, data quality, data access and AI governance | Warehouse column: documented; Transformation: partial; BI field: partial; Report: partial; Viewer: partial; Agent: partial | 46.5 | | 11 | [Immuta](/platforms/immuta/) | Data access control and authorization platform (policy engine with sensitive data tagging) | Warehouse column: documented; Transformation: none found; BI field: none found; Report: partial; Viewer: partial; Agent: partial | 45.0 | | 12 | [Ataccama ONE](/platforms/ataccama/) | Data quality, catalog and observability platform with master data management | Warehouse column: documented; Transformation: partial; BI field: partial; Report: partial; Viewer: none found; Agent: partial | 41.5 | | 13 | [Informatica](/platforms/informatica/) | Enterprise data catalog, governance, quality and access management platform (IDMC), now part of Salesforce | Warehouse column: documented; Transformation: documented; BI field: partial; Report: none found; Viewer: partial; Agent: partial | 30.0 | | 14 | [Privacera](/platforms/privacera/) | Data security platform: sensitive data discovery, tag-based access control and masking (Apache Ranger based), plus AI agent governance | Warehouse column: documented; Transformation: none found; BI field: none found; Report: none found; Viewer: partial; Agent: partial | 30.0 | | 15 | [Securiti](/platforms/securiti/) | Data security posture management and AI data governance platform | Warehouse column: documented; Transformation: partial; BI field: partial; Report: none found; Viewer: partial; Agent: documented | 29.5 | | 16 | [OneTrust](/platforms/onetrust/) | Privacy, AI governance and data use governance platform | Warehouse column: documented; Transformation: none found; BI field: none found; Report: none found; Viewer: none found; Agent: partial | 26.5 | Sorted by the site ranking. Read 13 Nov 2026. Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/platforms/ --- # Euno leads Microsoft Purview on AI data governance, 67.0 to 54.5 HEAD TO HEAD, read 13 Nov 2026 **The short answer.** Euno scores 67.0 and Microsoft Purview 54.5 of 100 on the eight Need to Know governance criteria, read 13 Nov 2026. The widest weighted gap is Follows sensitive data into BI, 7 to 3. Euno documents 3 of six exposure stages and Microsoft Purview documents 2. **Where Euno is behind.** Euno is not a policy engine or a DSPM: it reads metadata only, so it does not scan data contents or mask at the warehouse, which leaves it behind Atlan on acting on findings (5 to 7), and it publishes no dollar prices. | Criterion | Weight | Euno | Microsoft Purview | | --- | --- | --- | --- | | Follows sensitive data into BI | 25 | 7 | 3 | | Controls what an agent is told | 20 | 7 | 6 | | Shows who actually saw it | 15 | 6 | 6 | | Carries classification downstream | 15 | 8 | 6 | | Acts on it | 10 | 5 | 7 | | Coverage of the stack | 5 | 7 | 5 | | Evidence beyond the vendor | 5 | 8 | 8 | | Price transparency | 5 | 4 | 7 | | Total | 100 | 67.0 | 54.5 | Blind scores 0 to 10, read 13 Nov 2026. The higher score on each row is marked. ## Why the leader leads Euno leads on Follows sensitive data into BI (7 to 3) and Carries classification downstream (8 to 6), while Microsoft Purview is ahead on Acts on it (7 to 5). The gap is 12.5 points on the site weights. ## How far each one follows the field | Stage | Euno | Microsoft Purview | | --- | --- | --- | | [Warehouse column](/exposure-map/column/) | documented | documented | | [Transformation](/exposure-map/transformation/) | partial | partial | | [BI field](/exposure-map/bi-field/) | documented | partial | | [Report](/exposure-map/report/) | documented | documented | | [Viewer](/exposure-map/viewer/) | partial | partial | | [Agent](/exposure-map/agent/) | partial | partial | From the PII Exposure Map. None found means none found in the documentation read. Euno documents 3 of six stages and Microsoft Purview documents 2. Euno names 9 BI tools and Microsoft Purview names 2. Shared BI tools: Looker, Power BI. ## Verdict by situation - **A regulated field:** Euno leads 68.5 to 51.0. Euno leads on Follows sensitive data into BI (7 to 3) and Carries classification downstream (8 to 6), while Microsoft Purview is ahead on Acts on it (7 to 5). - **Agents on analytics:** Euno leads 66.0 to 56.5. Euno leads on Follows sensitive data into BI (7 to 3) and Controls what an agent is told (7 to 6), while Microsoft Purview is ahead on Acts on it (7 to 5). - **A Microsoft estate:** Euno leads 67.5 to 51.5. Euno leads on Follows sensitive data into BI (7 to 3) and Carries classification downstream (8 to 6), while Microsoft Purview is ahead on Acts on it (7 to 5). - **A mixed stack:** Euno leads 68.5 to 50.0. Euno leads on Follows sensitive data into BI (7 to 3) and Carries classification downstream (8 to 6), while Microsoft Purview is ahead on Price transparency (7 to 4). - **A lean team:** Euno leads 62.5 to 58.0. Euno leads on Follows sensitive data into BI (7 to 3) and Carries classification downstream (8 to 6), while Microsoft Purview is ahead on Price transparency (7 to 4). ## What Microsoft Purview does better Vendor-stated: Sensitivity labels carry from Azure SQL and Synapse into Power BI semantic models, then downstream to reports and dashboards, with the Power BI activity log and AI interaction events recording who and which AI app touched labeled data. ## What Euno does better Vendor-stated: Euno takes classifications from Cyera and BigID, carries them along column-level lineage into BI fields and reports, and scopes MCP context by persona. ## Read next - [Euno profile](/platforms/euno/) - [Microsoft Purview profile](/platforms/microsoft-purview/) - [Alternatives to Microsoft Purview](/alternatives/microsoft-purview/) - [Every head-to-head](/compare/) ## Sources - https://docs.euno.ai/ai/mcp-setup.md: https://docs.euno.ai/ai/mcp-setup.md (read 13 Nov 2026) - https://docs.euno.ai/using-euno/metadata-activation/metadata-tags.md: https://docs.euno.ai/using-euno/metadata-activation/metadata-tags.md (read 13 Nov 2026) - https://euno.ai/: https://euno.ai/ (read 13 Nov 2026) - https://www.getdbt.com/blog/alphasense-dbt-ai-context-data-rebuild.md: https://www.getdbt.com/blog/alphasense-dbt-ai-context-data-rebuild.md (read 13 Nov 2026) - https://www.cyera.com/integrations: https://www.cyera.com/integrations (read 13 Nov 2026) - https://www.prnewswire.com/news-releases/euno-raises-23-million-series-a-to-build-the-ai-context-brain-for-the-enterprise-302872947.html: https://www.prnewswire.com/news-releases/euno-raises-23-million-series-a-to-build-the-ai-context-brain-for-the-enterprise-302872947.html (read 13 Nov 2026) - https://euno.ai/pricing: https://euno.ai/pricing (read 13 Nov 2026) - https://docs.euno.ai/using-euno/usage-optimization/tableau-usage-data.md: https://docs.euno.ai/using-euno/usage-optimization/tableau-usage-data.md (read 13 Nov 2026) - https://docs.euno.ai/using-euno/usage-optimization/power-bi-usage-data.md: https://docs.euno.ai/using-euno/usage-optimization/power-bi-usage-data.md (read 13 Nov 2026) - https://docs.euno.ai/sources/data-security/cyera-integration/cyera-integration-use-cases.md: https://docs.euno.ai/sources/data-security/cyera-integration/cyera-integration-use-cases.md (read 13 Nov 2026) - https://docs.euno.ai/setup-configuration/personas.md: https://docs.euno.ai/setup-configuration/personas.md (read 13 Nov 2026) - https://docs.euno.ai/sources/data-security/bigid-integration/bigid-integration-use-cases.md: https://docs.euno.ai/sources/data-security/bigid-integration/bigid-integration-use-cases.md (read 13 Nov 2026) - https://euno.ai/blog/euno-is-officially-live-on-cyeras-integrations: https://euno.ai/blog/euno-is-officially-live-on-cyeras-integrations (read 13 Nov 2026) - https://docs.euno.ai/support-resources/faq.md: https://docs.euno.ai/support-resources/faq.md (read 13 Nov 2026) - https://docs.euno.ai/sources/data-security/microsoft-purview-integration.md: https://docs.euno.ai/sources/data-security/microsoft-purview-integration.md (read 13 Nov 2026) - https://docs.euno.ai/sources.md: https://docs.euno.ai/sources.md (read 13 Nov 2026) - https://learn.microsoft.com/power-bi/enterprise/service-security-sensitivity-label-inheritance-from-data-sources: https://learn.microsoft.com/power-bi/enterprise/service-security-sensitivity-label-inheritance-from-data-sources (read 13 Nov 2026) - https://learn.microsoft.com/power-bi/enterprise/service-security-sensitivity-label-downstream-inheritance: https://learn.microsoft.com/power-bi/enterprise/service-security-sensitivity-label-downstream-inheritance (read 13 Nov 2026) - https://learn.microsoft.com/power-bi/enterprise/service-security-sensitivity-label-overview: https://learn.microsoft.com/power-bi/enterprise/service-security-sensitivity-label-overview (read 13 Nov 2026) - https://learn.microsoft.com/purview/how-to-lineage-powerbi: https://learn.microsoft.com/purview/how-to-lineage-powerbi (read 13 Nov 2026) - https://learn.microsoft.com/purview/register-scan-power-bi-tenant: https://learn.microsoft.com/purview/register-scan-power-bi-tenant (read 13 Nov 2026) - https://learn.microsoft.com/purview/: https://learn.microsoft.com/purview/ (read 13 Nov 2026) - https://learn.microsoft.com/purview/register-scan-snowflake: https://learn.microsoft.com/purview/register-scan-snowflake (read 13 Nov 2026) - https://learn.microsoft.com/purview/register-scan-azure-databricks-unity-catalog: https://learn.microsoft.com/purview/register-scan-azure-databricks-unity-catalog (read 13 Nov 2026) - https://learn.microsoft.com/purview/microsoft-purview-connector-overview: https://learn.microsoft.com/purview/microsoft-purview-connector-overview (read 13 Nov 2026) - https://learn.microsoft.com/power-bi/enterprise/service-admin-auditing: https://learn.microsoft.com/power-bi/enterprise/service-admin-auditing (read 13 Nov 2026) - https://learn.microsoft.com/purview/ai-microsoft-purview: https://learn.microsoft.com/purview/ai-microsoft-purview (read 13 Nov 2026) - https://learn.microsoft.com/purview/ai-agents: https://learn.microsoft.com/purview/ai-agents (read 13 Nov 2026) - https://learn.microsoft.com/power-bi/developer/mcp/mcp-servers-overview: https://learn.microsoft.com/power-bi/developer/mcp/mcp-servers-overview (read 13 Nov 2026) - https://learn.microsoft.com/fabric/governance/protection-policies-overview: https://learn.microsoft.com/fabric/governance/protection-policies-overview (read 13 Nov 2026) - https://learn.microsoft.com/purview/dlp-powerbi-get-started: https://learn.microsoft.com/purview/dlp-powerbi-get-started (read 13 Nov 2026) - https://www.peerspot.com/products/microsoft-purview-reviews: https://www.peerspot.com/products/microsoft-purview-reviews (read 13 Nov 2026) - https://azure.microsoft.com/en-us/pricing/details/purview/: https://azure.microsoft.com/en-us/pricing/details/purview/ (read 13 Nov 2026) - https://github.com/microsoft/Purview-ADB-Lineage-Solution-Accelerator: https://github.com/microsoft/Purview-ADB-Lineage-Solution-Accelerator (read 13 Nov 2026) - https://pypi.org/pypi/pyapacheatlas/json: https://pypi.org/pypi/pyapacheatlas/json (read 13 Nov 2026) - https://prices.azure.com/api/retail/prices?$filter=serviceName eq 'Microsoft Purview' and armRegionName eq 'eastus' and contains(meterName,'Governance'): https://prices.azure.com/api/retail/prices?$filter=serviceName eq 'Microsoft Purview' and armRegionName eq 'eastus' and contains(meterName,'Governance') (read 13 Nov 2026) Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/compare/euno-vs-microsoft-purview/ --- # Euno leads Immuta on AI data governance, 67.0 to 45.0 HEAD TO HEAD, read 13 Nov 2026 **The short answer.** Euno scores 67.0 and Immuta 45.0 of 100 on the eight Need to Know governance criteria, read 13 Nov 2026. The widest weighted gap is Follows sensitive data into BI, 7 to 2. Euno documents 3 of six exposure stages and Immuta documents 1. **Where Euno is behind.** Euno is not a policy engine or a DSPM: it reads metadata only, so it does not scan data contents or mask at the warehouse, which leaves it behind Atlan on acting on findings (5 to 7), and it publishes no dollar prices. | Criterion | Weight | Euno | Immuta | | --- | --- | --- | --- | | Follows sensitive data into BI | 25 | 7 | 2 | | Controls what an agent is told | 20 | 7 | 6 | | Shows who actually saw it | 15 | 6 | 5 | | Carries classification downstream | 15 | 8 | 4 | | Acts on it | 10 | 5 | 8 | | Coverage of the stack | 5 | 7 | 5 | | Evidence beyond the vendor | 5 | 8 | 8 | | Price transparency | 5 | 4 | 0 | | Total | 100 | 67.0 | 45.0 | Blind scores 0 to 10, read 13 Nov 2026. The higher score on each row is marked. ## Why the leader leads Euno leads on Follows sensitive data into BI (7 to 2) and Carries classification downstream (8 to 4), while Immuta is ahead on Acts on it (8 to 5). The gap is 22.0 points on the site weights. ## How far each one follows the field | Stage | Euno | Immuta | | --- | --- | --- | | [Warehouse column](/exposure-map/column/) | documented | documented | | [Transformation](/exposure-map/transformation/) | partial | none found | | [BI field](/exposure-map/bi-field/) | documented | none found | | [Report](/exposure-map/report/) | documented | partial | | [Viewer](/exposure-map/viewer/) | partial | partial | | [Agent](/exposure-map/agent/) | partial | partial | From the PII Exposure Map. None found means none found in the documentation read. Euno documents 3 of six stages and Immuta documents 1. Euno names 9 BI tools and Immuta names 2. Shared BI tools: Tableau, Power BI. ## Verdict by situation - **A regulated field:** Euno leads 68.5 to 42.5. Euno leads on Follows sensitive data into BI (7 to 2) and Carries classification downstream (8 to 4), while Immuta is ahead on Acts on it (8 to 5). - **Agents on analytics:** Euno leads 66.0 to 49.0. Euno leads on Follows sensitive data into BI (7 to 2) and Controls what an agent is told (7 to 6), while Immuta is ahead on Acts on it (8 to 5). - **A Microsoft estate:** Euno leads 67.5 to 44.5. Euno leads on Follows sensitive data into BI (7 to 2) and Carries classification downstream (8 to 4), while Immuta is ahead on Acts on it (8 to 5). - **A mixed stack:** Euno leads 68.5 to 39.0. Euno leads on Follows sensitive data into BI (7 to 2) and Carries classification downstream (8 to 4), while Immuta is ahead on Acts on it (8 to 5). - **A lean team:** Euno leads 62.5 to 43.5. Euno leads on Follows sensitive data into BI (7 to 2) and Carries classification downstream (8 to 4), while Immuta is ahead on Acts on it (8 to 5). ## What Immuta does better Vendor-stated: Policies masked or limited by tag are enforced in the data platform per person, and agents get ephemeral roles scoped to the asking user. ## What Euno does better Vendor-stated: Euno takes classifications from Cyera and BigID, carries them along column-level lineage into BI fields and reports, and scopes MCP context by persona. ## Read next - [Euno profile](/platforms/euno/) - [Immuta profile](/platforms/immuta/) - [Alternatives to Immuta](/alternatives/immuta/) - [Every head-to-head](/compare/) ## Sources - https://docs.euno.ai/ai/mcp-setup.md: https://docs.euno.ai/ai/mcp-setup.md (read 13 Nov 2026) - https://docs.euno.ai/using-euno/metadata-activation/metadata-tags.md: https://docs.euno.ai/using-euno/metadata-activation/metadata-tags.md (read 13 Nov 2026) - https://euno.ai/: https://euno.ai/ (read 13 Nov 2026) - https://www.getdbt.com/blog/alphasense-dbt-ai-context-data-rebuild.md: https://www.getdbt.com/blog/alphasense-dbt-ai-context-data-rebuild.md (read 13 Nov 2026) - https://www.cyera.com/integrations: https://www.cyera.com/integrations (read 13 Nov 2026) - https://www.prnewswire.com/news-releases/euno-raises-23-million-series-a-to-build-the-ai-context-brain-for-the-enterprise-302872947.html: https://www.prnewswire.com/news-releases/euno-raises-23-million-series-a-to-build-the-ai-context-brain-for-the-enterprise-302872947.html (read 13 Nov 2026) - https://euno.ai/pricing: https://euno.ai/pricing (read 13 Nov 2026) - https://docs.euno.ai/using-euno/usage-optimization/tableau-usage-data.md: https://docs.euno.ai/using-euno/usage-optimization/tableau-usage-data.md (read 13 Nov 2026) - https://docs.euno.ai/using-euno/usage-optimization/power-bi-usage-data.md: https://docs.euno.ai/using-euno/usage-optimization/power-bi-usage-data.md (read 13 Nov 2026) - https://docs.euno.ai/sources/data-security/cyera-integration/cyera-integration-use-cases.md: https://docs.euno.ai/sources/data-security/cyera-integration/cyera-integration-use-cases.md (read 13 Nov 2026) - https://docs.euno.ai/setup-configuration/personas.md: https://docs.euno.ai/setup-configuration/personas.md (read 13 Nov 2026) - https://docs.euno.ai/sources/data-security/bigid-integration/bigid-integration-use-cases.md: https://docs.euno.ai/sources/data-security/bigid-integration/bigid-integration-use-cases.md (read 13 Nov 2026) - https://euno.ai/blog/euno-is-officially-live-on-cyeras-integrations: https://euno.ai/blog/euno-is-officially-live-on-cyeras-integrations (read 13 Nov 2026) - https://docs.euno.ai/support-resources/faq.md: https://docs.euno.ai/support-resources/faq.md (read 13 Nov 2026) - https://docs.euno.ai/sources/data-security/microsoft-purview-integration.md: https://docs.euno.ai/sources/data-security/microsoft-purview-integration.md (read 13 Nov 2026) - https://docs.euno.ai/sources.md: https://docs.euno.ai/sources.md (read 13 Nov 2026) - https://documentation.immuta.com/saas/agentic-data-access/introduction.md: https://documentation.immuta.com/saas/agentic-data-access/introduction.md (read 13 Nov 2026) - https://www.immuta.com/platform/agentic-data-access: https://www.immuta.com/platform/agentic-data-access (read 13 Nov 2026) - https://documentation.immuta.com/saas/: https://documentation.immuta.com/saas/ (read 13 Nov 2026) - https://documentation.immuta.com/saas/releases/index.md: https://documentation.immuta.com/saas/releases/index.md (read 13 Nov 2026) - https://documentation.immuta.com/saas/releases/index/2025.md: https://documentation.immuta.com/saas/releases/index/2025.md (read 13 Nov 2026) - https://documentation.immuta.com/saas/govern/authoring-policies-in-secure/data-policies/reference-guides/masking-matrix-functions.md: https://documentation.immuta.com/saas/govern/authoring-policies-in-secure/data-policies/reference-guides/masking-matrix-functions.md (read 13 Nov 2026) - https://documentation.immuta.com/saas/configuration/tags/data-discovery.md: https://documentation.immuta.com/saas/configuration/tags/data-discovery.md (read 13 Nov 2026) - https://documentation.immuta.com/saas/configuration/tags/data-classification.md: https://documentation.immuta.com/saas/configuration/tags/data-classification.md (read 13 Nov 2026) - https://documentation.immuta.com/saas/configuration/tags/catalogs.md: https://documentation.immuta.com/saas/configuration/tags/catalogs.md (read 13 Nov 2026) - https://documentation.immuta.com/saas/releases/support-matrix.md: https://documentation.immuta.com/saas/releases/support-matrix.md (read 13 Nov 2026) - https://documentation.immuta.com/saas/configuration/application-configuration/how-to-guides/bi-tools/tableau.md: https://documentation.immuta.com/saas/configuration/application-configuration/how-to-guides/bi-tools/tableau.md (read 13 Nov 2026) - https://documentation.immuta.com/saas/configuration/application-configuration/how-to-guides/bi-tools/power-bi.md: https://documentation.immuta.com/saas/configuration/application-configuration/how-to-guides/bi-tools/power-bi.md (read 13 Nov 2026) - https://documentation.immuta.com/saas/govern/detect-introduction/index.md: https://documentation.immuta.com/saas/govern/detect-introduction/index.md (read 13 Nov 2026) - https://documentation.immuta.com/saas/govern/detect-introduction/detection/detect-concept.md: https://documentation.immuta.com/saas/govern/detect-introduction/detection/detect-concept.md (read 13 Nov 2026) - https://www.databricks.com/partners/immuta: https://www.databricks.com/partners/immuta (read 13 Nov 2026) - https://en.wikipedia.org/wiki/Immuta: https://en.wikipedia.org/wiki/Immuta (read 13 Nov 2026) - https://www.immuta.com/: https://www.immuta.com/ (read 13 Nov 2026) - https://documentation.immuta.com/saas/govern/authoring-policies-in-secure/dbt-transform-workflow.md: https://documentation.immuta.com/saas/govern/authoring-policies-in-secure/dbt-transform-workflow.md (read 13 Nov 2026) Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/compare/euno-vs-immuta/ --- # Euno leads Privacera on AI data governance, 67.0 to 30.0 HEAD TO HEAD, read 13 Nov 2026 **The short answer.** Euno scores 67.0 and Privacera 30.0 of 100 on the eight Need to Know governance criteria, read 13 Nov 2026. The widest weighted gap is Follows sensitive data into BI, 7 to 0. Euno documents 3 of six exposure stages and Privacera documents 1. **Where Euno is behind.** Euno is not a policy engine or a DSPM: it reads metadata only, so it does not scan data contents or mask at the warehouse, which leaves it behind Atlan on acting on findings (5 to 7), and it publishes no dollar prices. | Criterion | Weight | Euno | Privacera | | --- | --- | --- | --- | | Follows sensitive data into BI | 25 | 7 | 0 | | Controls what an agent is told | 20 | 7 | 2 | | Shows who actually saw it | 15 | 6 | 4 | | Carries classification downstream | 15 | 8 | 4 | | Acts on it | 10 | 5 | 8 | | Coverage of the stack | 5 | 7 | 4 | | Evidence beyond the vendor | 5 | 8 | 8 | | Price transparency | 5 | 4 | 0 | | Total | 100 | 67.0 | 30.0 | Blind scores 0 to 10, read 13 Nov 2026. The higher score on each row is marked. ## Why the leader leads Euno leads on Follows sensitive data into BI (7 to 0) and Controls what an agent is told (7 to 2), while Privacera is ahead on Acts on it (8 to 5). The gap is 37.0 points on the site weights. ## How far each one follows the field | Stage | Euno | Privacera | | --- | --- | --- | | [Warehouse column](/exposure-map/column/) | documented | documented | | [Transformation](/exposure-map/transformation/) | partial | none found | | [BI field](/exposure-map/bi-field/) | documented | none found | | [Report](/exposure-map/report/) | documented | none found | | [Viewer](/exposure-map/viewer/) | partial | partial | | [Agent](/exposure-map/agent/) | partial | partial | From the PII Exposure Map. None found means none found in the documentation read. Euno documents 3 of six stages and Privacera documents 1. Euno names 9 BI tools and Privacera names 0. Shared BI tools: none by the same name. ## Verdict by situation - **A regulated field:** Euno leads 68.5 to 31.0. Euno leads on Follows sensitive data into BI (7 to 0) and Carries classification downstream (8 to 4), while Privacera is ahead on Acts on it (8 to 5). - **Agents on analytics:** Euno leads 66.0 to 28.0. Euno leads on Controls what an agent is told (7 to 2) and Follows sensitive data into BI (7 to 0), while Privacera is ahead on Acts on it (8 to 5). - **A Microsoft estate:** Euno leads 67.5 to 32.0. Euno leads on Follows sensitive data into BI (7 to 0) and Carries classification downstream (8 to 4), while Privacera is ahead on Acts on it (8 to 5). - **A mixed stack:** Euno leads 68.5 to 26.0. Euno leads on Follows sensitive data into BI (7 to 0) and Carries classification downstream (8 to 4), while Privacera is ahead on Acts on it (8 to 5). - **A lean team:** Euno leads 62.5 to 34.0. Euno leads on Follows sensitive data into BI (7 to 0) and Carries classification downstream (8 to 4), while Privacera is ahead on Acts on it (8 to 5). ## What Privacera does better Vendor-stated: Discovery tags sensitive columns and files and Ranger tag-based policies mask or deny across many warehouses, with audit of allow/deny access. ## What Euno does better Vendor-stated: Euno takes classifications from Cyera and BigID, carries them along column-level lineage into BI fields and reports, and scopes MCP context by persona. ## Read next - [Euno profile](/platforms/euno/) - [Privacera profile](/platforms/privacera/) - [Alternatives to Privacera](/alternatives/privacera/) - [Every head-to-head](/compare/) ## Sources - https://docs.euno.ai/ai/mcp-setup.md: https://docs.euno.ai/ai/mcp-setup.md (read 13 Nov 2026) - https://docs.euno.ai/using-euno/metadata-activation/metadata-tags.md: https://docs.euno.ai/using-euno/metadata-activation/metadata-tags.md (read 13 Nov 2026) - https://euno.ai/: https://euno.ai/ (read 13 Nov 2026) - https://www.getdbt.com/blog/alphasense-dbt-ai-context-data-rebuild.md: https://www.getdbt.com/blog/alphasense-dbt-ai-context-data-rebuild.md (read 13 Nov 2026) - https://www.cyera.com/integrations: https://www.cyera.com/integrations (read 13 Nov 2026) - https://www.prnewswire.com/news-releases/euno-raises-23-million-series-a-to-build-the-ai-context-brain-for-the-enterprise-302872947.html: https://www.prnewswire.com/news-releases/euno-raises-23-million-series-a-to-build-the-ai-context-brain-for-the-enterprise-302872947.html (read 13 Nov 2026) - https://euno.ai/pricing: https://euno.ai/pricing (read 13 Nov 2026) - https://docs.euno.ai/using-euno/usage-optimization/tableau-usage-data.md: https://docs.euno.ai/using-euno/usage-optimization/tableau-usage-data.md (read 13 Nov 2026) - https://docs.euno.ai/using-euno/usage-optimization/power-bi-usage-data.md: https://docs.euno.ai/using-euno/usage-optimization/power-bi-usage-data.md (read 13 Nov 2026) - https://docs.euno.ai/sources/data-security/cyera-integration/cyera-integration-use-cases.md: https://docs.euno.ai/sources/data-security/cyera-integration/cyera-integration-use-cases.md (read 13 Nov 2026) - https://docs.euno.ai/setup-configuration/personas.md: https://docs.euno.ai/setup-configuration/personas.md (read 13 Nov 2026) - https://docs.euno.ai/sources/data-security/bigid-integration/bigid-integration-use-cases.md: https://docs.euno.ai/sources/data-security/bigid-integration/bigid-integration-use-cases.md (read 13 Nov 2026) - https://euno.ai/blog/euno-is-officially-live-on-cyeras-integrations: https://euno.ai/blog/euno-is-officially-live-on-cyeras-integrations (read 13 Nov 2026) - https://docs.euno.ai/support-resources/faq.md: https://docs.euno.ai/support-resources/faq.md (read 13 Nov 2026) - https://docs.euno.ai/sources/data-security/microsoft-purview-integration.md: https://docs.euno.ai/sources/data-security/microsoft-purview-integration.md (read 13 Nov 2026) - https://docs.euno.ai/sources.md: https://docs.euno.ai/sources.md (read 13 Nov 2026) - https://docs.privacera.com/data-security/user-guide/discovery/scanning/classification/tags.html: https://docs.privacera.com/data-security/user-guide/discovery/scanning/classification/tags.html (read 13 Nov 2026) - https://docs.privacera.com/data-security/user-guide/discovery/scanning/classification/index.html: https://docs.privacera.com/data-security/user-guide/discovery/scanning/classification/index.html (read 13 Nov 2026) - https://docs.privacera.com/data-security/get-started/discovery/config_sync_tags_to_ranger.html: https://docs.privacera.com/data-security/get-started/discovery/config_sync_tags_to_ranger.html (read 13 Nov 2026) - https://docs.privacera.com/data-security/connectors/collibra/index.html: https://docs.privacera.com/data-security/connectors/collibra/index.html (read 13 Nov 2026) - https://docs.privacera.com/data-security/user-guide/discovery/advanced/part-file-tag-propagation.html: https://docs.privacera.com/data-security/user-guide/discovery/advanced/part-file-tag-propagation.html (read 13 Nov 2026) - https://docs.privacera.com/data-security/index.html: https://docs.privacera.com/data-security/index.html (read 13 Nov 2026) - https://docs.privacera.com/data-security/connectors/overview/index.html: https://docs.privacera.com/data-security/connectors/overview/index.html (read 13 Nov 2026) - https://docs.privacera.com/data-security/connectors/mssql/access/tag_based_masking_unmasking.html: https://docs.privacera.com/data-security/connectors/mssql/access/tag_based_masking_unmasking.html (read 13 Nov 2026) - https://docs.privacera.com/data-security/connectors/snowflake/access/connector-guide/column-masking-based-on-group-membership.html: https://docs.privacera.com/data-security/connectors/snowflake/access/connector-guide/column-masking-based-on-group-membership.html (read 13 Nov 2026) - https://docs.privacera.com/data-security/user-guide/discovery/policies/compliance/workflow.html: https://docs.privacera.com/data-security/user-guide/discovery/policies/compliance/workflow.html (read 13 Nov 2026) - https://docs.privacera.com/data-security/user-guide/discovery/policies/compliance/alerts.html: https://docs.privacera.com/data-security/user-guide/discovery/policies/compliance/alerts.html (read 13 Nov 2026) - https://docs.privacera.com/data-security/user-guide/access-management/audits/access_audits.html: https://docs.privacera.com/data-security/user-guide/access-management/audits/access_audits.html (read 13 Nov 2026) - https://docs.privacera.com/data-security/user-guide/access-management/audits/index.html: https://docs.privacera.com/data-security/user-guide/access-management/audits/index.html (read 13 Nov 2026) - https://docs.trust3.ai/get-started/overview.html: https://docs.trust3.ai/get-started/overview.html (read 13 Nov 2026) - https://trust3.ai/: https://trust3.ai/ (read 13 Nov 2026) - https://docs.trust3.ai/how-to-guides/mcp-configuration.html: https://docs.trust3.ai/how-to-guides/mcp-configuration.html (read 13 Nov 2026) - https://docs.privacera.com/data-security/user-guide/discovery/scanning/ways/realtime-scanning.html: https://docs.privacera.com/data-security/user-guide/discovery/scanning/ways/realtime-scanning.html (read 13 Nov 2026) - https://github.com/privacera/paig: https://github.com/privacera/paig (read 13 Nov 2026) - https://www.prnewswire.com/news/privacera/: https://www.prnewswire.com/news/privacera/ (read 13 Nov 2026) - https://privacera.com/pricing/: https://privacera.com/pricing/ (read 13 Nov 2026) - https://www.databricks.com/partners/privacera: https://www.databricks.com/partners/privacera (read 13 Nov 2026) - https://docs.dremio.com/current/security/: https://docs.dremio.com/current/security/ (read 13 Nov 2026) Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/compare/euno-vs-privacera/ --- # Euno leads Securiti on AI data governance, 67.0 to 29.5 HEAD TO HEAD, read 13 Nov 2026 **The short answer.** Euno scores 67.0 and Securiti 29.5 of 100 on the eight Need to Know governance criteria, read 13 Nov 2026. The widest weighted gap is Follows sensitive data into BI, 7 to 1. Euno documents 3 of six exposure stages and Securiti documents 2. **Where Euno is behind.** Euno is not a policy engine or a DSPM: it reads metadata only, so it does not scan data contents or mask at the warehouse, which leaves it behind Atlan on acting on findings (5 to 7), and it publishes no dollar prices. | Criterion | Weight | Euno | Securiti | | --- | --- | --- | --- | | Follows sensitive data into BI | 25 | 7 | 1 | | Controls what an agent is told | 20 | 7 | 4 | | Shows who actually saw it | 15 | 6 | 3 | | Carries classification downstream | 15 | 8 | 3 | | Acts on it | 10 | 5 | 6 | | Coverage of the stack | 5 | 7 | 2 | | Evidence beyond the vendor | 5 | 8 | 5 | | Price transparency | 5 | 4 | 1 | | Total | 100 | 67.0 | 29.5 | Blind scores 0 to 10, read 13 Nov 2026. The higher score on each row is marked. ## Why the leader leads Euno leads on Follows sensitive data into BI (7 to 1) and Carries classification downstream (8 to 3), while Securiti is ahead on Acts on it (6 to 5). The gap is 37.5 points on the site weights. ## How far each one follows the field | Stage | Euno | Securiti | | --- | --- | --- | | [Warehouse column](/exposure-map/column/) | documented | documented | | [Transformation](/exposure-map/transformation/) | partial | partial | | [BI field](/exposure-map/bi-field/) | documented | partial | | [Report](/exposure-map/report/) | documented | none found | | [Viewer](/exposure-map/viewer/) | partial | partial | | [Agent](/exposure-map/agent/) | partial | documented | From the PII Exposure Map. None found means none found in the documentation read. Euno documents 3 of six stages and Securiti documents 2. Euno names 9 BI tools and Securiti names 1. Shared BI tools: Tableau. ## Verdict by situation - **A regulated field:** Euno leads 68.5 to 27.0. Euno leads on Follows sensitive data into BI (7 to 1) and Carries classification downstream (8 to 3), while Securiti is ahead on Acts on it (6 to 5). - **Agents on analytics:** Euno leads 66.0 to 32.5. Euno leads on Controls what an agent is told (7 to 4) and Follows sensitive data into BI (7 to 1), while Securiti is ahead on Acts on it (6 to 5). - **A Microsoft estate:** Euno leads 67.5 to 28.5. Euno leads on Follows sensitive data into BI (7 to 1) and Carries classification downstream (8 to 3), while Securiti is ahead on Acts on it (6 to 5). - **A mixed stack:** Euno leads 68.5 to 23.5. Euno leads on Follows sensitive data into BI (7 to 1) and Carries classification downstream (8 to 3), while Securiti is ahead on Acts on it (6 to 5). - **A lean team:** Euno leads 62.5 to 30.5. Euno leads on Follows sensitive data into BI (7 to 1) and Carries classification downstream (8 to 3), while Securiti is ahead on Acts on it (6 to 5). ## What Securiti does better Vendor-stated: Securiti pairs sensitive data discovery with entitlement-aware, label-based filtering for AI copilots and masking and remediation actions. ## What Euno does better Vendor-stated: Euno takes classifications from Cyera and BigID, carries them along column-level lineage into BI fields and reports, and scopes MCP context by persona. ## Read next - [Euno profile](/platforms/euno/) - [Securiti profile](/platforms/securiti/) - [Alternatives to Securiti](/alternatives/securiti/) - [Every head-to-head](/compare/) ## Sources - https://docs.euno.ai/ai/mcp-setup.md: https://docs.euno.ai/ai/mcp-setup.md (read 13 Nov 2026) - https://docs.euno.ai/using-euno/metadata-activation/metadata-tags.md: https://docs.euno.ai/using-euno/metadata-activation/metadata-tags.md (read 13 Nov 2026) - https://euno.ai/: https://euno.ai/ (read 13 Nov 2026) - https://www.getdbt.com/blog/alphasense-dbt-ai-context-data-rebuild.md: https://www.getdbt.com/blog/alphasense-dbt-ai-context-data-rebuild.md (read 13 Nov 2026) - https://www.cyera.com/integrations: https://www.cyera.com/integrations (read 13 Nov 2026) - https://www.prnewswire.com/news-releases/euno-raises-23-million-series-a-to-build-the-ai-context-brain-for-the-enterprise-302872947.html: https://www.prnewswire.com/news-releases/euno-raises-23-million-series-a-to-build-the-ai-context-brain-for-the-enterprise-302872947.html (read 13 Nov 2026) - https://euno.ai/pricing: https://euno.ai/pricing (read 13 Nov 2026) - https://docs.euno.ai/using-euno/usage-optimization/tableau-usage-data.md: https://docs.euno.ai/using-euno/usage-optimization/tableau-usage-data.md (read 13 Nov 2026) - https://docs.euno.ai/using-euno/usage-optimization/power-bi-usage-data.md: https://docs.euno.ai/using-euno/usage-optimization/power-bi-usage-data.md (read 13 Nov 2026) - https://docs.euno.ai/sources/data-security/cyera-integration/cyera-integration-use-cases.md: https://docs.euno.ai/sources/data-security/cyera-integration/cyera-integration-use-cases.md (read 13 Nov 2026) - https://docs.euno.ai/setup-configuration/personas.md: https://docs.euno.ai/setup-configuration/personas.md (read 13 Nov 2026) - https://docs.euno.ai/sources/data-security/bigid-integration/bigid-integration-use-cases.md: https://docs.euno.ai/sources/data-security/bigid-integration/bigid-integration-use-cases.md (read 13 Nov 2026) - https://euno.ai/blog/euno-is-officially-live-on-cyeras-integrations: https://euno.ai/blog/euno-is-officially-live-on-cyeras-integrations (read 13 Nov 2026) - https://docs.euno.ai/support-resources/faq.md: https://docs.euno.ai/support-resources/faq.md (read 13 Nov 2026) - https://docs.euno.ai/sources/data-security/microsoft-purview-integration.md: https://docs.euno.ai/sources/data-security/microsoft-purview-integration.md (read 13 Nov 2026) - https://docs.euno.ai/sources.md: https://docs.euno.ai/sources.md (read 13 Nov 2026) - https://securiti.ai/connectors/tableau/: https://securiti.ai/connectors/tableau/ (read 13 Nov 2026) - https://securiti.ai/gencore/integrations/: https://securiti.ai/gencore/integrations/ (read 13 Nov 2026) - https://securiti.ai/press-release/securiti-joins-snowflake-governance-program/: https://securiti.ai/press-release/securiti-joins-snowflake-governance-program/ (read 13 Nov 2026) - https://securiti.ai/gencore/partners/databricks/: https://securiti.ai/gencore/partners/databricks/ (read 13 Nov 2026) - https://securiti.ai/connectors/: https://securiti.ai/connectors/ (read 13 Nov 2026) - https://securiti.ai/products/data-lineage/: https://securiti.ai/products/data-lineage/ (read 13 Nov 2026) - https://securiti.ai/products/sensitive-data-catalog/: https://securiti.ai/products/sensitive-data-catalog/ (read 13 Nov 2026) - https://securiti.ai/what-is-data-lineage/: https://securiti.ai/what-is-data-lineage/ (read 13 Nov 2026) - https://securiti.ai/products/data-discovery/: https://securiti.ai/products/data-discovery/ (read 13 Nov 2026) - https://securiti.ai/products/data-classification/: https://securiti.ai/products/data-classification/ (read 13 Nov 2026) - https://securiti.ai/gencore/safe-enterprise-ai-copilot/: https://securiti.ai/gencore/safe-enterprise-ai-copilot/ (read 13 Nov 2026) - https://securiti.ai/products/security-for-ai-agents-and-copilots/: https://securiti.ai/products/security-for-ai-agents-and-copilots/ (read 13 Nov 2026) - https://securiti.ai/products/access-intelligence/: https://securiti.ai/products/access-intelligence/ (read 13 Nov 2026) - https://securiti.ai/press-release/veeam-introduces-agent-commander-to-confront-agentic-ai-risk-at-enterprise-scale/: https://securiti.ai/press-release/veeam-introduces-agent-commander-to-confront-agentic-ai-risk-at-enterprise-scale/ (read 13 Nov 2026) - https://securiti.ai/agent-commander/: https://securiti.ai/agent-commander/ (read 13 Nov 2026) - https://securiti.ai/dspm/: https://securiti.ai/dspm/ (read 13 Nov 2026) - https://securiti.ai/press-release/veeams-securiti-ai-named-a-leader-and-fast-mover-in-gigaoms-2026-dspm-radar-with-top-scores-among-evaluated-vendors/: https://securiti.ai/press-release/veeams-securiti-ai-named-a-leader-and-fast-mover-in-gigaoms-2026-dspm-radar-with-top-scores-among-evaluated-vendors/ (read 13 Nov 2026) - https://securiti.ai/case-studies/global-manufacturer-data-intelligence/: https://securiti.ai/case-studies/global-manufacturer-data-intelligence/ (read 13 Nov 2026) - https://securiti.ai/: https://securiti.ai/ (read 13 Nov 2026) - https://securiti.ai/pricing/: https://securiti.ai/pricing/ (read 13 Nov 2026) - https://en.wikipedia.org/wiki/Veeam: https://en.wikipedia.org/wiki/Veeam (read 13 Nov 2026) Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/compare/euno-vs-securiti/ --- # Euno leads OneTrust on AI data governance, 67.0 to 26.5 HEAD TO HEAD, read 13 Nov 2026 **The short answer.** Euno scores 67.0 and OneTrust 26.5 of 100 on the eight Need to Know governance criteria, read 13 Nov 2026. The widest weighted gap is Follows sensitive data into BI, 7 to 0. Euno documents 3 of six exposure stages and OneTrust documents 1. **Where Euno is behind.** Euno is not a policy engine or a DSPM: it reads metadata only, so it does not scan data contents or mask at the warehouse, which leaves it behind Atlan on acting on findings (5 to 7), and it publishes no dollar prices. | Criterion | Weight | Euno | OneTrust | | --- | --- | --- | --- | | Follows sensitive data into BI | 25 | 7 | 0 | | Controls what an agent is told | 20 | 7 | 3 | | Shows who actually saw it | 15 | 6 | 3 | | Carries classification downstream | 15 | 8 | 3 | | Acts on it | 10 | 5 | 6 | | Coverage of the stack | 5 | 7 | 3 | | Evidence beyond the vendor | 5 | 8 | 5 | | Price transparency | 5 | 4 | 3 | | Total | 100 | 67.0 | 26.5 | Blind scores 0 to 10, read 13 Nov 2026. The higher score on each row is marked. ## Why the leader leads Euno leads on Follows sensitive data into BI (7 to 0) and Controls what an agent is told (7 to 3), while OneTrust is ahead on Acts on it (6 to 5). The gap is 40.5 points on the site weights. ## How far each one follows the field | Stage | Euno | OneTrust | | --- | --- | --- | | [Warehouse column](/exposure-map/column/) | documented | documented | | [Transformation](/exposure-map/transformation/) | partial | none found | | [BI field](/exposure-map/bi-field/) | documented | none found | | [Report](/exposure-map/report/) | documented | none found | | [Viewer](/exposure-map/viewer/) | partial | none found | | [Agent](/exposure-map/agent/) | partial | partial | From the PII Exposure Map. None found means none found in the documentation read. Euno documents 3 of six stages and OneTrust documents 1. Euno names 9 BI tools and OneTrust names 0. Shared BI tools: none by the same name. ## Verdict by situation - **A regulated field:** Euno leads 68.5 to 23.5. Euno leads on Follows sensitive data into BI (7 to 0) and Carries classification downstream (8 to 3), while OneTrust is ahead on Acts on it (6 to 5). - **Agents on analytics:** Euno leads 66.0 to 28.5. Euno leads on Controls what an agent is told (7 to 3) and Follows sensitive data into BI (7 to 0), while OneTrust is ahead on Acts on it (6 to 5). - **A Microsoft estate:** Euno leads 67.5 to 25.5. Euno leads on Follows sensitive data into BI (7 to 0) and Carries classification downstream (8 to 3), while OneTrust is ahead on Acts on it (6 to 5). - **A mixed stack:** Euno leads 68.5 to 22.5. Euno leads on Follows sensitive data into BI (7 to 0) and Carries classification downstream (8 to 3), while OneTrust is ahead on Acts on it (6 to 5). - **A lean team:** Euno leads 62.5 to 31.0. Euno leads on Follows sensitive data into BI (7 to 0) and Carries classification downstream (8 to 3), while OneTrust is ahead on Acts on it (6 to 5). ## What OneTrust does better Vendor-stated: Turns data policies into native masking and row-filtering controls in Snowflake and Databricks Unity Catalog and governs agent tools and prompts with AI Guard, with enforcement audited in the platform's own logs. ## What Euno does better Vendor-stated: Euno takes classifications from Cyera and BigID, carries them along column-level lineage into BI fields and reports, and scopes MCP context by persona. ## Read next - [Euno profile](/platforms/euno/) - [OneTrust profile](/platforms/onetrust/) - [Alternatives to OneTrust](/alternatives/onetrust/) - [Every head-to-head](/compare/) ## Sources - https://docs.euno.ai/ai/mcp-setup.md: https://docs.euno.ai/ai/mcp-setup.md (read 13 Nov 2026) - https://docs.euno.ai/using-euno/metadata-activation/metadata-tags.md: https://docs.euno.ai/using-euno/metadata-activation/metadata-tags.md (read 13 Nov 2026) - https://euno.ai/: https://euno.ai/ (read 13 Nov 2026) - https://www.getdbt.com/blog/alphasense-dbt-ai-context-data-rebuild.md: https://www.getdbt.com/blog/alphasense-dbt-ai-context-data-rebuild.md (read 13 Nov 2026) - https://www.cyera.com/integrations: https://www.cyera.com/integrations (read 13 Nov 2026) - https://www.prnewswire.com/news-releases/euno-raises-23-million-series-a-to-build-the-ai-context-brain-for-the-enterprise-302872947.html: https://www.prnewswire.com/news-releases/euno-raises-23-million-series-a-to-build-the-ai-context-brain-for-the-enterprise-302872947.html (read 13 Nov 2026) - https://euno.ai/pricing: https://euno.ai/pricing (read 13 Nov 2026) - https://docs.euno.ai/using-euno/usage-optimization/tableau-usage-data.md: https://docs.euno.ai/using-euno/usage-optimization/tableau-usage-data.md (read 13 Nov 2026) - https://docs.euno.ai/using-euno/usage-optimization/power-bi-usage-data.md: https://docs.euno.ai/using-euno/usage-optimization/power-bi-usage-data.md (read 13 Nov 2026) - https://docs.euno.ai/sources/data-security/cyera-integration/cyera-integration-use-cases.md: https://docs.euno.ai/sources/data-security/cyera-integration/cyera-integration-use-cases.md (read 13 Nov 2026) - https://docs.euno.ai/setup-configuration/personas.md: https://docs.euno.ai/setup-configuration/personas.md (read 13 Nov 2026) - https://docs.euno.ai/sources/data-security/bigid-integration/bigid-integration-use-cases.md: https://docs.euno.ai/sources/data-security/bigid-integration/bigid-integration-use-cases.md (read 13 Nov 2026) - https://euno.ai/blog/euno-is-officially-live-on-cyeras-integrations: https://euno.ai/blog/euno-is-officially-live-on-cyeras-integrations (read 13 Nov 2026) - https://docs.euno.ai/support-resources/faq.md: https://docs.euno.ai/support-resources/faq.md (read 13 Nov 2026) - https://docs.euno.ai/sources/data-security/microsoft-purview-integration.md: https://docs.euno.ai/sources/data-security/microsoft-purview-integration.md (read 13 Nov 2026) - https://docs.euno.ai/sources.md: https://docs.euno.ai/sources.md (read 13 Nov 2026) - https://www.onetrust.com/solutions/data-use-governance/: https://www.onetrust.com/solutions/data-use-governance/ (read 13 Nov 2026) - https://developer.onetrust.com/onetrust/reference/data-use-governance-data-catalog/llms.txt: https://developer.onetrust.com/onetrust/reference/data-use-governance-data-catalog/llms.txt (read 13 Nov 2026) - https://developer.onetrust.com/onetrust/llms.txt: https://developer.onetrust.com/onetrust/llms.txt (read 13 Nov 2026) - https://www.onetrust.com/products/ai-governance/: https://www.onetrust.com/products/ai-governance/ (read 13 Nov 2026) - https://www.prnewswire.com/news-releases/onetrust-announces-partnership-with-databricks-to-power-real-time-policy-enforcement-in-the-databricks-data-intelligence-platform-302477871.html: https://www.prnewswire.com/news-releases/onetrust-announces-partnership-with-databricks-to-power-real-time-policy-enforcement-in-the-databricks-data-intelligence-platform-302477871.html (read 13 Nov 2026) - https://developer.onetrust.com/onetrust/docs/ai-guard.md: https://developer.onetrust.com/onetrust/docs/ai-guard.md (read 13 Nov 2026) - https://github.com/onetrust-oss/ai-guard-sdk: https://github.com/onetrust-oss/ai-guard-sdk (read 13 Nov 2026) - https://developer.onetrust.com/onetrust/reference/mcp.md: https://developer.onetrust.com/onetrust/reference/mcp.md (read 13 Nov 2026) - https://www.onetrust.com/integrations/snowflake/: https://www.onetrust.com/integrations/snowflake/ (read 13 Nov 2026) - https://www.onetrust.com/integrations/: https://www.onetrust.com/integrations/ (read 13 Nov 2026) - https://www.onetrust.com/pricing/: https://www.onetrust.com/pricing/ (read 13 Nov 2026) - https://raw.githubusercontent.com/Knuckles-Team/onetrust-api/main/README.md: https://raw.githubusercontent.com/Knuckles-Team/onetrust-api/main/README.md (read 13 Nov 2026) - https://pypi.org/pypi/onetrust-api/json: https://pypi.org/pypi/onetrust-api/json (read 13 Nov 2026) - https://www.okta.com/integrations/onetrust/: https://www.okta.com/integrations/onetrust/ (read 13 Nov 2026) - https://developer.onetrust.com/onetrust/reference/createorupsertdataassetv1-1.md: https://developer.onetrust.com/onetrust/reference/createorupsertdataassetv1-1.md (read 13 Nov 2026) - https://developer.onetrust.com/onetrust/reference/getallusingget_1.md: https://developer.onetrust.com/onetrust/reference/getallusingget_1.md (read 13 Nov 2026) - https://developer.onetrust.com/onetrust/docs/ai-guard-authentication.md: https://developer.onetrust.com/onetrust/docs/ai-guard-authentication.md (read 13 Nov 2026) - https://developer.onetrust.com/onetrust/docs/ai-guard-metrics-overview.md: https://developer.onetrust.com/onetrust/docs/ai-guard-metrics-overview.md (read 13 Nov 2026) - https://developer.onetrust.com/onetrust/docs/ai-guard-faq.md: https://developer.onetrust.com/onetrust/docs/ai-guard-faq.md (read 13 Nov 2026) Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/compare/euno-vs-onetrust/ --- # Microsoft Purview leads Collibra on AI data governance, 54.5 to 46.5 HEAD TO HEAD, read 13 Nov 2026 **The short answer.** Microsoft Purview scores 54.5 and Collibra 46.5 of 100 on the eight Need to Know governance criteria, read 13 Nov 2026. The widest weighted gap is Shows who actually saw it, 6 to 3. Collibra documents 1 of six exposure stages and Microsoft Purview documents 2. | Criterion | Weight | Collibra | Microsoft Purview | | --- | --- | --- | --- | | Follows sensitive data into BI | 25 | 5 | 3 | | Controls what an agent is told | 20 | 5 | 6 | | Shows who actually saw it | 15 | 3 | 6 | | Carries classification downstream | 15 | 3 | 6 | | Acts on it | 10 | 7 | 7 | | Coverage of the stack | 5 | 6 | 5 | | Evidence beyond the vendor | 5 | 8 | 8 | | Price transparency | 5 | 2 | 7 | | Total | 100 | 46.5 | 54.5 | Blind scores 0 to 10, read 13 Nov 2026. The higher score on each row is marked. ## Why the leader leads Microsoft Purview leads on Shows who actually saw it (6 to 3) and Carries classification downstream (6 to 3), while Collibra is ahead on Follows sensitive data into BI (5 to 3). The gap is 8.0 points on the site weights. ## How far each one follows the field | Stage | Collibra | Microsoft Purview | | --- | --- | --- | | [Warehouse column](/exposure-map/column/) | documented | documented | | [Transformation](/exposure-map/transformation/) | partial | partial | | [BI field](/exposure-map/bi-field/) | partial | partial | | [Report](/exposure-map/report/) | partial | documented | | [Viewer](/exposure-map/viewer/) | partial | partial | | [Agent](/exposure-map/agent/) | partial | partial | From the PII Exposure Map. None found means none found in the documentation read. Collibra documents 1 of six stages and Microsoft Purview documents 2. Collibra names 8 BI tools and Microsoft Purview names 2. Shared BI tools: Power BI, Looker. ## Verdict by situation - **A regulated field:** Microsoft Purview leads 51.0 to 46.0. Microsoft Purview leads on Shows who actually saw it (6 to 3) and Carries classification downstream (6 to 3), while Collibra is ahead on Follows sensitive data into BI (5 to 3). - **Agents on analytics:** Microsoft Purview leads 56.5 to 46.0. Microsoft Purview leads on Shows who actually saw it (6 to 3) and Controls what an agent is told (6 to 5), while Collibra is ahead on Follows sensitive data into BI (5 to 3). - **A Microsoft estate:** Microsoft Purview leads 51.5 to 47.0. Microsoft Purview leads on Carries classification downstream (6 to 3) and Shows who actually saw it (6 to 3), while Collibra is ahead on Follows sensitive data into BI (5 to 3). - **A mixed stack:** Microsoft Purview leads 50.0 to 45.5. Microsoft Purview leads on Carries classification downstream (6 to 3) and Shows who actually saw it (6 to 3), while Collibra is ahead on Follows sensitive data into BI (5 to 3). - **A lean team:** Microsoft Purview leads 58.0 to 46.5. Microsoft Purview leads on Price transparency (7 to 2) and Carries classification downstream (6 to 3), while Collibra is ahead on Follows sensitive data into BI (5 to 3). ## What Collibra does better Data Access applies masking and row filters on Snowflake, Databricks and BigQuery from data classifications, backed by lineage to reports and an MCP server that runs under user scopes. ## What Microsoft Purview does better Vendor-stated: Sensitivity labels carry from Azure SQL and Synapse into Power BI semantic models, then downstream to reports and dashboards, with the Power BI activity log and AI interaction events recording who and which AI app touched labeled data. ## Read next - [Collibra profile](/platforms/collibra/) - [Microsoft Purview profile](/platforms/microsoft-purview/) - [Alternatives to Microsoft Purview](/alternatives/microsoft-purview/) - [Every head-to-head](/compare/) ## Sources - https://www.collibra.com/products/data-lineage: https://www.collibra.com/products/data-lineage (read 13 Nov 2026) - https://productresources.collibra.com/docs/collibra/latest/Content/UsageAnalytics/to_usage-analytics.htm: https://productresources.collibra.com/docs/collibra/latest/Content/UsageAnalytics/to_usage-analytics.htm (read 13 Nov 2026) - https://www.collibra.com/products/data-catalog: https://www.collibra.com/products/data-catalog (read 13 Nov 2026) - https://github.com/collibra/chip: https://github.com/collibra/chip (read 13 Nov 2026) - https://www.collibra.com/products/mcp-server: https://www.collibra.com/products/mcp-server (read 13 Nov 2026) - https://web.archive.org/web/20260713001251/https://productresources.collibra.com/docs/collibra/latest/Content/ModelContextProtocol/ref_mcp-tools.htm: https://web.archive.org/web/20260713001251/https://productresources.collibra.com/docs/collibra/latest/Content/ModelContextProtocol/ref_mcp-tools.htm (read 13 Nov 2026) - https://www.collibra.com/products/ai-governance: https://www.collibra.com/products/ai-governance (read 13 Nov 2026) - https://productresources.collibra.com/docs/collibra/latest/Content/CollibraDataLineage/ref_technical-lineage-supported-data-sources.htm: https://productresources.collibra.com/docs/collibra/latest/Content/CollibraDataLineage/ref_technical-lineage-supported-data-sources.htm (read 13 Nov 2026) - https://web.archive.org/web/20260421071225/https://productresources.collibra.com/docs/collibra/latest/Content/CollibraDataLineage/DataSources/dbtCore/ref_dbt-core-supported-transformations.htm: https://web.archive.org/web/20260421071225/https://productresources.collibra.com/docs/collibra/latest/Content/CollibraDataLineage/DataSources/dbtCore/ref_dbt-core-supported-transformations.htm (read 13 Nov 2026) - https://www.collibra.com/products/data-access: https://www.collibra.com/products/data-access (read 13 Nov 2026) - https://productresources.collibra.com/docs/collibra/latest/Content/DataAccess/co_data-access.htm: https://productresources.collibra.com/docs/collibra/latest/Content/DataAccess/co_data-access.htm (read 13 Nov 2026) - https://productresources.collibra.com/docs/collibra/latest/Content/Home.htm: https://productresources.collibra.com/docs/collibra/latest/Content/Home.htm (read 13 Nov 2026) - https://www.collibra.com/products/data-quality-and-observability: https://www.collibra.com/products/data-quality-and-observability (read 13 Nov 2026) - https://www.prnewswire.com/news-releases/collibra-named-a-leader-for-the-second-consecutive-year-in-gartner-magic-quadrant-for-data-and-analytics-governance-platforms-302671796.html: https://www.prnewswire.com/news-releases/collibra-named-a-leader-for-the-second-consecutive-year-in-gartner-magic-quadrant-for-data-and-analytics-governance-platforms-302671796.html (read 13 Nov 2026) - https://www.collibra.com/customer-stories/nationwide-building-society: https://www.collibra.com/customer-stories/nationwide-building-society (read 13 Nov 2026) - https://www.collibra.com/: https://www.collibra.com/ (read 13 Nov 2026) - https://www.collibra.com/pricing: https://www.collibra.com/pricing (read 13 Nov 2026) - https://web.archive.org/web/20260609030714/https://productresources.collibra.com/docs/collibra/latest/Content/ModelContextProtocol/co_mcp.htm: https://web.archive.org/web/20260609030714/https://productresources.collibra.com/docs/collibra/latest/Content/ModelContextProtocol/co_mcp.htm (read 13 Nov 2026) - https://web.archive.org/web/2026/https://productresources.collibra.com/docs/collibra/latest/Content/Protect/co_protect-audit.htm: https://web.archive.org/web/2026/https://productresources.collibra.com/docs/collibra/latest/Content/Protect/co_protect-audit.htm (read 13 Nov 2026) - https://github.com/getstrm/pace: https://github.com/getstrm/pace (read 13 Nov 2026) - https://pypi.org/project/collibra-connector/: https://pypi.org/project/collibra-connector/ (read 13 Nov 2026) - https://learn.microsoft.com/power-bi/enterprise/service-security-sensitivity-label-inheritance-from-data-sources: https://learn.microsoft.com/power-bi/enterprise/service-security-sensitivity-label-inheritance-from-data-sources (read 13 Nov 2026) - https://learn.microsoft.com/power-bi/enterprise/service-security-sensitivity-label-downstream-inheritance: https://learn.microsoft.com/power-bi/enterprise/service-security-sensitivity-label-downstream-inheritance (read 13 Nov 2026) - https://learn.microsoft.com/power-bi/enterprise/service-security-sensitivity-label-overview: https://learn.microsoft.com/power-bi/enterprise/service-security-sensitivity-label-overview (read 13 Nov 2026) - https://learn.microsoft.com/purview/how-to-lineage-powerbi: https://learn.microsoft.com/purview/how-to-lineage-powerbi (read 13 Nov 2026) - https://learn.microsoft.com/purview/register-scan-power-bi-tenant: https://learn.microsoft.com/purview/register-scan-power-bi-tenant (read 13 Nov 2026) - https://learn.microsoft.com/purview/: https://learn.microsoft.com/purview/ (read 13 Nov 2026) - https://learn.microsoft.com/purview/register-scan-snowflake: https://learn.microsoft.com/purview/register-scan-snowflake (read 13 Nov 2026) - https://learn.microsoft.com/purview/register-scan-azure-databricks-unity-catalog: https://learn.microsoft.com/purview/register-scan-azure-databricks-unity-catalog (read 13 Nov 2026) - https://learn.microsoft.com/purview/microsoft-purview-connector-overview: https://learn.microsoft.com/purview/microsoft-purview-connector-overview (read 13 Nov 2026) - https://learn.microsoft.com/power-bi/enterprise/service-admin-auditing: https://learn.microsoft.com/power-bi/enterprise/service-admin-auditing (read 13 Nov 2026) - https://learn.microsoft.com/purview/ai-microsoft-purview: https://learn.microsoft.com/purview/ai-microsoft-purview (read 13 Nov 2026) - https://learn.microsoft.com/purview/ai-agents: https://learn.microsoft.com/purview/ai-agents (read 13 Nov 2026) - https://learn.microsoft.com/power-bi/developer/mcp/mcp-servers-overview: https://learn.microsoft.com/power-bi/developer/mcp/mcp-servers-overview (read 13 Nov 2026) - https://learn.microsoft.com/fabric/governance/protection-policies-overview: https://learn.microsoft.com/fabric/governance/protection-policies-overview (read 13 Nov 2026) - https://learn.microsoft.com/purview/dlp-powerbi-get-started: https://learn.microsoft.com/purview/dlp-powerbi-get-started (read 13 Nov 2026) - https://www.peerspot.com/products/microsoft-purview-reviews: https://www.peerspot.com/products/microsoft-purview-reviews (read 13 Nov 2026) - https://azure.microsoft.com/en-us/pricing/details/purview/: https://azure.microsoft.com/en-us/pricing/details/purview/ (read 13 Nov 2026) - https://github.com/microsoft/Purview-ADB-Lineage-Solution-Accelerator: https://github.com/microsoft/Purview-ADB-Lineage-Solution-Accelerator (read 13 Nov 2026) - https://pypi.org/pypi/pyapacheatlas/json: https://pypi.org/pypi/pyapacheatlas/json (read 13 Nov 2026) - https://prices.azure.com/api/retail/prices?$filter=serviceName eq 'Microsoft Purview' and armRegionName eq 'eastus' and contains(meterName,'Governance'): https://prices.azure.com/api/retail/prices?$filter=serviceName eq 'Microsoft Purview' and armRegionName eq 'eastus' and contains(meterName,'Governance') (read 13 Nov 2026) Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/compare/collibra-vs-microsoft-purview/ --- # Databricks Unity Catalog leads Immuta on AI data governance, 55.0 to 45.0 HEAD TO HEAD, read 13 Nov 2026 **The short answer.** Databricks Unity Catalog scores 55.0 and Immuta 45.0 of 100 on the eight Need to Know governance criteria, read 13 Nov 2026. The widest weighted gap is Follows sensitive data into BI, 4 to 2. Databricks Unity Catalog documents 2 of six exposure stages and Immuta documents 1. | Criterion | Weight | Databricks Unity Catalog | Immuta | | --- | --- | --- | --- | | Follows sensitive data into BI | 25 | 4 | 2 | | Controls what an agent is told | 20 | 7 | 6 | | Shows who actually saw it | 15 | 6 | 5 | | Carries classification downstream | 15 | 5 | 4 | | Acts on it | 10 | 6 | 8 | | Coverage of the stack | 5 | 4 | 5 | | Evidence beyond the vendor | 5 | 9 | 8 | | Price transparency | 5 | 4 | 0 | | Total | 100 | 55.0 | 45.0 | Blind scores 0 to 10, read 13 Nov 2026. The higher score on each row is marked. ## Why the leader leads Databricks Unity Catalog leads on Follows sensitive data into BI (4 to 2) and Controls what an agent is told (7 to 6), while Immuta is ahead on Acts on it (8 to 6). The gap is 10.0 points on the site weights. ## How far each one follows the field | Stage | Databricks Unity Catalog | Immuta | | --- | --- | --- | | [Warehouse column](/exposure-map/column/) | documented | documented | | [Transformation](/exposure-map/transformation/) | partial | none found | | [BI field](/exposure-map/bi-field/) | partial | none found | | [Report](/exposure-map/report/) | partial | partial | | [Viewer](/exposure-map/viewer/) | partial | partial | | [Agent](/exposure-map/agent/) | documented | partial | From the PII Exposure Map. None found means none found in the documentation read. Databricks Unity Catalog documents 2 of six stages and Immuta documents 1. Databricks Unity Catalog names 4 BI tools and Immuta names 2. Shared BI tools: Tableau, Power BI. ## Verdict by situation - **A regulated field:** Databricks Unity Catalog leads 52.0 to 42.5. Databricks Unity Catalog leads on Follows sensitive data into BI (4 to 2) and Shows who actually saw it (6 to 5), while Immuta is ahead on Acts on it (8 to 6). - **Agents on analytics:** Databricks Unity Catalog leads 58.0 to 49.0. Databricks Unity Catalog leads on Controls what an agent is told (7 to 6) and Follows sensitive data into BI (4 to 2), while Immuta is ahead on Acts on it (8 to 6). - **A Microsoft estate:** Databricks Unity Catalog leads 51.0 to 44.5. Databricks Unity Catalog leads on Follows sensitive data into BI (4 to 2) and Carries classification downstream (5 to 4), while Immuta is ahead on Acts on it (8 to 6). - **A mixed stack:** Databricks Unity Catalog leads 48.0 to 39.0. Databricks Unity Catalog leads on Follows sensitive data into BI (4 to 2) and Carries classification downstream (5 to 4), while Immuta is ahead on Coverage of the stack (5 to 4). - **A lean team:** Databricks Unity Catalog leads 53.0 to 43.5. Databricks Unity Catalog leads on Price transparency (4 to 0) and Follows sensitive data into BI (4 to 2), while Immuta is ahead on Acts on it (8 to 6). ## What Immuta does better Vendor-stated: Policies masked or limited by tag are enforced in the data platform per person, and agents get ephemeral roles scoped to the asking user. ## What Databricks Unity Catalog does better Vendor-stated: Automatic PII classification feeds governed tags, tag propagation (Beta) along lineage applies matching ABAC policies to derived columns, and Genie enforces row filters and column masks per user. ## Read next - [Databricks Unity Catalog profile](/platforms/databricks/) - [Immuta profile](/platforms/immuta/) - [Alternatives to Immuta](/alternatives/immuta/) - [Every head-to-head](/compare/) ## Sources - https://docs.databricks.com/aws/en/data-governance/unity-catalog/data-classification: https://docs.databricks.com/aws/en/data-governance/unity-catalog/data-classification (read 13 Nov 2026) - https://docs.databricks.com/aws/en/data-governance/unity-catalog/data-lineage: https://docs.databricks.com/aws/en/data-governance/unity-catalog/data-lineage (read 13 Nov 2026) - https://docs.databricks.com/aws/en/agents/mcp-tools/built-in-mcp-services: https://docs.databricks.com/aws/en/agents/mcp-tools/built-in-mcp-services (read 13 Nov 2026) - https://docs.getdbt.com/reference/resource-configs/databricks-configs: https://docs.getdbt.com/reference/resource-configs/databricks-configs (read 13 Nov 2026) - https://aws.amazon.com/marketplace/pp/prodview-wtyi5lgtce6n6: https://aws.amazon.com/marketplace/pp/prodview-wtyi5lgtce6n6 (read 13 Nov 2026) - https://www.databricks.com/product/pricing: https://www.databricks.com/product/pricing (read 13 Nov 2026) - https://docs.databricks.com/aws/en/data-governance/unity-catalog/external-lineage: https://docs.databricks.com/aws/en/data-governance/unity-catalog/external-lineage (read 13 Nov 2026) - https://docs.databricks.com/aws/en/genie/set-up: https://docs.databricks.com/aws/en/genie/set-up (read 13 Nov 2026) - https://docs.databricks.com/aws/en/agents/mcp-tools/authentication-networking: https://docs.databricks.com/aws/en/agents/mcp-tools/authentication-networking (read 13 Nov 2026) - https://docs.databricks.com/aws/en/ai-gateway/govern-mcp-service: https://docs.databricks.com/aws/en/ai-gateway/govern-mcp-service (read 13 Nov 2026) - https://docs.databricks.com/aws/en/admin/account-settings/audit-logs: https://docs.databricks.com/aws/en/admin/account-settings/audit-logs (read 13 Nov 2026) - https://docs.databricks.com/aws/en/admin/system-tables/query-history: https://docs.databricks.com/aws/en/admin/system-tables/query-history (read 13 Nov 2026) - https://docs.databricks.com/aws/en/admin/system-tables/: https://docs.databricks.com/aws/en/admin/system-tables/ (read 13 Nov 2026) - https://docs.databricks.com/aws/en/admin/governed-tags/tag-propagation: https://docs.databricks.com/aws/en/admin/governed-tags/tag-propagation (read 13 Nov 2026) - https://docs.databricks.com/aws/en/data-governance/unity-catalog/abac/: https://docs.databricks.com/aws/en/data-governance/unity-catalog/abac/ (read 13 Nov 2026) - https://www.databricks.com/product/unity-catalog: https://www.databricks.com/product/unity-catalog (read 13 Nov 2026) - https://learn.microsoft.com/en-us/purview/register-scan-azure-databricks-unity-catalog: https://learn.microsoft.com/en-us/purview/register-scan-azure-databricks-unity-catalog (read 13 Nov 2026) - https://help.tableau.com/current/pro/desktop/en-us/examples_databricks.htm: https://help.tableau.com/current/pro/desktop/en-us/examples_databricks.htm (read 13 Nov 2026) - https://documentation.immuta.com/saas/agentic-data-access/introduction.md: https://documentation.immuta.com/saas/agentic-data-access/introduction.md (read 13 Nov 2026) - https://www.immuta.com/platform/agentic-data-access: https://www.immuta.com/platform/agentic-data-access (read 13 Nov 2026) - https://documentation.immuta.com/saas/: https://documentation.immuta.com/saas/ (read 13 Nov 2026) - https://documentation.immuta.com/saas/releases/index.md: https://documentation.immuta.com/saas/releases/index.md (read 13 Nov 2026) - https://documentation.immuta.com/saas/releases/index/2025.md: https://documentation.immuta.com/saas/releases/index/2025.md (read 13 Nov 2026) - https://documentation.immuta.com/saas/govern/authoring-policies-in-secure/data-policies/reference-guides/masking-matrix-functions.md: https://documentation.immuta.com/saas/govern/authoring-policies-in-secure/data-policies/reference-guides/masking-matrix-functions.md (read 13 Nov 2026) - https://documentation.immuta.com/saas/configuration/tags/data-discovery.md: https://documentation.immuta.com/saas/configuration/tags/data-discovery.md (read 13 Nov 2026) - https://documentation.immuta.com/saas/configuration/tags/data-classification.md: https://documentation.immuta.com/saas/configuration/tags/data-classification.md (read 13 Nov 2026) - https://documentation.immuta.com/saas/configuration/tags/catalogs.md: https://documentation.immuta.com/saas/configuration/tags/catalogs.md (read 13 Nov 2026) - https://documentation.immuta.com/saas/releases/support-matrix.md: https://documentation.immuta.com/saas/releases/support-matrix.md (read 13 Nov 2026) - https://documentation.immuta.com/saas/configuration/application-configuration/how-to-guides/bi-tools/tableau.md: https://documentation.immuta.com/saas/configuration/application-configuration/how-to-guides/bi-tools/tableau.md (read 13 Nov 2026) - https://documentation.immuta.com/saas/configuration/application-configuration/how-to-guides/bi-tools/power-bi.md: https://documentation.immuta.com/saas/configuration/application-configuration/how-to-guides/bi-tools/power-bi.md (read 13 Nov 2026) - https://documentation.immuta.com/saas/govern/detect-introduction/index.md: https://documentation.immuta.com/saas/govern/detect-introduction/index.md (read 13 Nov 2026) - https://documentation.immuta.com/saas/govern/detect-introduction/detection/detect-concept.md: https://documentation.immuta.com/saas/govern/detect-introduction/detection/detect-concept.md (read 13 Nov 2026) - https://www.databricks.com/partners/immuta: https://www.databricks.com/partners/immuta (read 13 Nov 2026) - https://en.wikipedia.org/wiki/Immuta: https://en.wikipedia.org/wiki/Immuta (read 13 Nov 2026) - https://www.immuta.com/: https://www.immuta.com/ (read 13 Nov 2026) - https://documentation.immuta.com/saas/govern/authoring-policies-in-secure/dbt-transform-workflow.md: https://documentation.immuta.com/saas/govern/authoring-policies-in-secure/dbt-transform-workflow.md (read 13 Nov 2026) Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/compare/databricks-vs-immuta/ --- # Immuta leads Privacera on AI data governance, 45.0 to 30.0 HEAD TO HEAD, read 13 Nov 2026 **The short answer.** Immuta scores 45.0 and Privacera 30.0 of 100 on the eight Need to Know governance criteria, read 13 Nov 2026. The widest weighted gap is Controls what an agent is told, 6 to 2. Immuta documents 1 of six exposure stages and Privacera documents 1. | Criterion | Weight | Immuta | Privacera | | --- | --- | --- | --- | | Follows sensitive data into BI | 25 | 2 | 0 | | Controls what an agent is told | 20 | 6 | 2 | | Shows who actually saw it | 15 | 5 | 4 | | Carries classification downstream | 15 | 4 | 4 | | Acts on it | 10 | 8 | 8 | | Coverage of the stack | 5 | 5 | 4 | | Evidence beyond the vendor | 5 | 8 | 8 | | Price transparency | 5 | 0 | 0 | | Total | 100 | 45.0 | 30.0 | Blind scores 0 to 10, read 13 Nov 2026. The higher score on each row is marked. ## Why the leader leads Immuta leads on Controls what an agent is told (6 to 2) and Follows sensitive data into BI (2 to 0). The gap is 15.0 points on the site weights. ## How far each one follows the field | Stage | Immuta | Privacera | | --- | --- | --- | | [Warehouse column](/exposure-map/column/) | documented | documented | | [Transformation](/exposure-map/transformation/) | none found | none found | | [BI field](/exposure-map/bi-field/) | none found | none found | | [Report](/exposure-map/report/) | partial | none found | | [Viewer](/exposure-map/viewer/) | partial | partial | | [Agent](/exposure-map/agent/) | partial | partial | From the PII Exposure Map. None found means none found in the documentation read. Immuta documents 1 of six stages and Privacera documents 1. Immuta names 2 BI tools and Privacera names 0. Shared BI tools: none by the same name. ## Verdict by situation - **A regulated field:** Immuta leads 42.5 to 31.0. Immuta leads on Follows sensitive data into BI (2 to 0) and Controls what an agent is told (6 to 2). - **Agents on analytics:** Immuta leads 49.0 to 28.0. Immuta leads on Controls what an agent is told (6 to 2) and Follows sensitive data into BI (2 to 0). - **A Microsoft estate:** Immuta leads 44.5 to 32.0. Immuta leads on Follows sensitive data into BI (2 to 0) and Controls what an agent is told (6 to 2). - **A mixed stack:** Immuta leads 39.0 to 26.0. Immuta leads on Follows sensitive data into BI (2 to 0) and Controls what an agent is told (6 to 2). - **A lean team:** Immuta leads 43.5 to 34.0. Immuta leads on Follows sensitive data into BI (2 to 0) and Controls what an agent is told (6 to 2). ## What Privacera does better Vendor-stated: Discovery tags sensitive columns and files and Ranger tag-based policies mask or deny across many warehouses, with audit of allow/deny access. ## What Immuta does better Vendor-stated: Policies masked or limited by tag are enforced in the data platform per person, and agents get ephemeral roles scoped to the asking user. ## Read next - [Immuta profile](/platforms/immuta/) - [Privacera profile](/platforms/privacera/) - [Alternatives to Immuta](/alternatives/immuta/) - [Alternatives to Privacera](/alternatives/privacera/) - [Every head-to-head](/compare/) ## Sources - https://documentation.immuta.com/saas/agentic-data-access/introduction.md: https://documentation.immuta.com/saas/agentic-data-access/introduction.md (read 13 Nov 2026) - https://www.immuta.com/platform/agentic-data-access: https://www.immuta.com/platform/agentic-data-access (read 13 Nov 2026) - https://documentation.immuta.com/saas/: https://documentation.immuta.com/saas/ (read 13 Nov 2026) - https://documentation.immuta.com/saas/releases/index.md: https://documentation.immuta.com/saas/releases/index.md (read 13 Nov 2026) - https://documentation.immuta.com/saas/releases/index/2025.md: https://documentation.immuta.com/saas/releases/index/2025.md (read 13 Nov 2026) - https://documentation.immuta.com/saas/govern/authoring-policies-in-secure/data-policies/reference-guides/masking-matrix-functions.md: https://documentation.immuta.com/saas/govern/authoring-policies-in-secure/data-policies/reference-guides/masking-matrix-functions.md (read 13 Nov 2026) - https://documentation.immuta.com/saas/configuration/tags/data-discovery.md: https://documentation.immuta.com/saas/configuration/tags/data-discovery.md (read 13 Nov 2026) - https://documentation.immuta.com/saas/configuration/tags/data-classification.md: https://documentation.immuta.com/saas/configuration/tags/data-classification.md (read 13 Nov 2026) - https://documentation.immuta.com/saas/configuration/tags/catalogs.md: https://documentation.immuta.com/saas/configuration/tags/catalogs.md (read 13 Nov 2026) - https://documentation.immuta.com/saas/releases/support-matrix.md: https://documentation.immuta.com/saas/releases/support-matrix.md (read 13 Nov 2026) - https://documentation.immuta.com/saas/configuration/application-configuration/how-to-guides/bi-tools/tableau.md: https://documentation.immuta.com/saas/configuration/application-configuration/how-to-guides/bi-tools/tableau.md (read 13 Nov 2026) - https://documentation.immuta.com/saas/configuration/application-configuration/how-to-guides/bi-tools/power-bi.md: https://documentation.immuta.com/saas/configuration/application-configuration/how-to-guides/bi-tools/power-bi.md (read 13 Nov 2026) - https://documentation.immuta.com/saas/govern/detect-introduction/index.md: https://documentation.immuta.com/saas/govern/detect-introduction/index.md (read 13 Nov 2026) - https://documentation.immuta.com/saas/govern/detect-introduction/detection/detect-concept.md: https://documentation.immuta.com/saas/govern/detect-introduction/detection/detect-concept.md (read 13 Nov 2026) - https://www.databricks.com/partners/immuta: https://www.databricks.com/partners/immuta (read 13 Nov 2026) - https://en.wikipedia.org/wiki/Immuta: https://en.wikipedia.org/wiki/Immuta (read 13 Nov 2026) - https://www.immuta.com/: https://www.immuta.com/ (read 13 Nov 2026) - https://documentation.immuta.com/saas/govern/authoring-policies-in-secure/dbt-transform-workflow.md: https://documentation.immuta.com/saas/govern/authoring-policies-in-secure/dbt-transform-workflow.md (read 13 Nov 2026) - https://docs.privacera.com/data-security/user-guide/discovery/scanning/classification/tags.html: https://docs.privacera.com/data-security/user-guide/discovery/scanning/classification/tags.html (read 13 Nov 2026) - https://docs.privacera.com/data-security/user-guide/discovery/scanning/classification/index.html: https://docs.privacera.com/data-security/user-guide/discovery/scanning/classification/index.html (read 13 Nov 2026) - https://docs.privacera.com/data-security/get-started/discovery/config_sync_tags_to_ranger.html: https://docs.privacera.com/data-security/get-started/discovery/config_sync_tags_to_ranger.html (read 13 Nov 2026) - https://docs.privacera.com/data-security/connectors/collibra/index.html: https://docs.privacera.com/data-security/connectors/collibra/index.html (read 13 Nov 2026) - https://docs.privacera.com/data-security/user-guide/discovery/advanced/part-file-tag-propagation.html: https://docs.privacera.com/data-security/user-guide/discovery/advanced/part-file-tag-propagation.html (read 13 Nov 2026) - https://docs.privacera.com/data-security/index.html: https://docs.privacera.com/data-security/index.html (read 13 Nov 2026) - https://docs.privacera.com/data-security/connectors/overview/index.html: https://docs.privacera.com/data-security/connectors/overview/index.html (read 13 Nov 2026) - https://docs.privacera.com/data-security/connectors/mssql/access/tag_based_masking_unmasking.html: https://docs.privacera.com/data-security/connectors/mssql/access/tag_based_masking_unmasking.html (read 13 Nov 2026) - https://docs.privacera.com/data-security/connectors/snowflake/access/connector-guide/column-masking-based-on-group-membership.html: https://docs.privacera.com/data-security/connectors/snowflake/access/connector-guide/column-masking-based-on-group-membership.html (read 13 Nov 2026) - https://docs.privacera.com/data-security/user-guide/discovery/policies/compliance/workflow.html: https://docs.privacera.com/data-security/user-guide/discovery/policies/compliance/workflow.html (read 13 Nov 2026) - https://docs.privacera.com/data-security/user-guide/discovery/policies/compliance/alerts.html: https://docs.privacera.com/data-security/user-guide/discovery/policies/compliance/alerts.html (read 13 Nov 2026) - https://docs.privacera.com/data-security/user-guide/access-management/audits/access_audits.html: https://docs.privacera.com/data-security/user-guide/access-management/audits/access_audits.html (read 13 Nov 2026) - https://docs.privacera.com/data-security/user-guide/access-management/audits/index.html: https://docs.privacera.com/data-security/user-guide/access-management/audits/index.html (read 13 Nov 2026) - https://docs.trust3.ai/get-started/overview.html: https://docs.trust3.ai/get-started/overview.html (read 13 Nov 2026) - https://trust3.ai/: https://trust3.ai/ (read 13 Nov 2026) - https://docs.trust3.ai/how-to-guides/mcp-configuration.html: https://docs.trust3.ai/how-to-guides/mcp-configuration.html (read 13 Nov 2026) - https://docs.privacera.com/data-security/user-guide/discovery/scanning/ways/realtime-scanning.html: https://docs.privacera.com/data-security/user-guide/discovery/scanning/ways/realtime-scanning.html (read 13 Nov 2026) - https://github.com/privacera/paig: https://github.com/privacera/paig (read 13 Nov 2026) - https://www.prnewswire.com/news/privacera/: https://www.prnewswire.com/news/privacera/ (read 13 Nov 2026) - https://privacera.com/pricing/: https://privacera.com/pricing/ (read 13 Nov 2026) - https://www.databricks.com/partners/privacera: https://www.databricks.com/partners/privacera (read 13 Nov 2026) - https://docs.dremio.com/current/security/: https://docs.dremio.com/current/security/ (read 13 Nov 2026) Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/compare/immuta-vs-privacera/ --- # Microsoft Purview leads Informatica on AI data governance, 54.5 to 30.0 HEAD TO HEAD, read 13 Nov 2026 **The short answer.** Microsoft Purview scores 54.5 and Informatica 30.0 of 100 on the eight Need to Know governance criteria, read 13 Nov 2026. The widest weighted gap is Controls what an agent is told, 6 to 2. Informatica documents 2 of six exposure stages and Microsoft Purview documents 2. | Criterion | Weight | Informatica | Microsoft Purview | | --- | --- | --- | --- | | Follows sensitive data into BI | 25 | 2 | 3 | | Controls what an agent is told | 20 | 2 | 6 | | Shows who actually saw it | 15 | 3 | 6 | | Carries classification downstream | 15 | 3 | 6 | | Acts on it | 10 | 4 | 7 | | Coverage of the stack | 5 | 3 | 5 | | Evidence beyond the vendor | 5 | 9 | 8 | | Price transparency | 5 | 4 | 7 | | Total | 100 | 30.0 | 54.5 | Blind scores 0 to 10, read 13 Nov 2026. The higher score on each row is marked. ## Why the leader leads Microsoft Purview leads on Controls what an agent is told (6 to 2) and Shows who actually saw it (6 to 3), while Informatica is ahead on Evidence beyond the vendor (9 to 8). The gap is 24.5 points on the site weights. ## How far each one follows the field | Stage | Informatica | Microsoft Purview | | --- | --- | --- | | [Warehouse column](/exposure-map/column/) | documented | documented | | [Transformation](/exposure-map/transformation/) | documented | partial | | [BI field](/exposure-map/bi-field/) | partial | partial | | [Report](/exposure-map/report/) | none found | documented | | [Viewer](/exposure-map/viewer/) | partial | partial | | [Agent](/exposure-map/agent/) | partial | partial | From the PII Exposure Map. None found means none found in the documentation read. Informatica documents 2 of six stages and Microsoft Purview documents 2. Informatica names 2 BI tools and Microsoft Purview names 2. Shared BI tools: Power BI. ## Verdict by situation - **A regulated field:** Microsoft Purview leads 51.0 to 30.0. Microsoft Purview leads on Shows who actually saw it (6 to 3) and Carries classification downstream (6 to 3), while Informatica is ahead on Evidence beyond the vendor (9 to 8). - **Agents on analytics:** Microsoft Purview leads 56.5 to 26.0. Microsoft Purview leads on Controls what an agent is told (6 to 2) and Shows who actually saw it (6 to 3). - **A Microsoft estate:** Microsoft Purview leads 51.5 to 27.5. Microsoft Purview leads on Carries classification downstream (6 to 3) and Shows who actually saw it (6 to 3). - **A mixed stack:** Microsoft Purview leads 50.0 to 27.0. Microsoft Purview leads on Carries classification downstream (6 to 3) and Controls what an agent is told (6 to 2). - **A lean team:** Microsoft Purview leads 58.0 to 33.5. Microsoft Purview leads on Acts on it (7 to 4) and Carries classification downstream (6 to 3), while Informatica is ahead on Evidence beyond the vendor (9 to 8). ## What Informatica does better Vendor-stated: Policy-based data access management (CDAM) built on metadata and CLAIRE classification pushes controls into Snowflake, Databricks, Power BI and Tableau. ## What Microsoft Purview does better Vendor-stated: Sensitivity labels carry from Azure SQL and Synapse into Power BI semantic models, then downstream to reports and dashboards, with the Power BI activity log and AI interaction events recording who and which AI app touched labeled data. ## Read next - [Informatica profile](/platforms/informatica/) - [Microsoft Purview profile](/platforms/microsoft-purview/) - [Alternatives to Microsoft Purview](/alternatives/microsoft-purview/) - [Every head-to-head](/compare/) ## Sources - https://www.databricks.com/partners/partner-directory/informatica: https://www.databricks.com/partners/partner-directory/informatica (read 13 Nov 2026) - https://www.informatica.com/pricing.html: https://www.informatica.com/pricing.html (read 13 Nov 2026) - https://www.informatica.com/products/data-catalog/data-lineage.html: https://www.informatica.com/products/data-catalog/data-lineage.html (read 13 Nov 2026) - https://docs.informatica.com/: https://docs.informatica.com/ (read 13 Nov 2026) - https://www.informatica.com/headless.html: https://www.informatica.com/headless.html (read 13 Nov 2026) - https://www.informatica.com/blogs/powering-agentic-workflows-on-aws-with-informatica-mcps.html: https://www.informatica.com/blogs/powering-agentic-workflows-on-aws-with-informatica-mcps.html (read 13 Nov 2026) - https://www.informatica.com/blogs/how-idmc-supports-native-security-controls-in-snowflake.html: https://www.informatica.com/blogs/how-idmc-supports-native-security-controls-in-snowflake.html (read 13 Nov 2026) - https://www.informatica.com/about-us/news/news-releases/2024/02/20240229-informatica-launches-cloud-data-access-management-industrys-first-ai-powered-solution-for-automating-data-access-policy-enforcement-at-scale.html: https://www.informatica.com/about-us/news/news-releases/2024/02/20240229-informatica-launches-cloud-data-access-management-industrys-first-ai-powered-solution-for-automating-data-access-policy-enforcement-at-scale.html (read 13 Nov 2026) - https://www.informatica.com/blogs/activate-enterprise-data-with-trusted-context-new-capabilities-in-idmcs-spring-2026-release.html: https://www.informatica.com/blogs/activate-enterprise-data-with-trusted-context-new-capabilities-in-idmcs-spring-2026-release.html (read 13 Nov 2026) - https://www.informatica.com/products/data-governance/data-access-management.html: https://www.informatica.com/products/data-governance/data-access-management.html (read 13 Nov 2026) - https://learn.microsoft.com/en-us/azure/partner-solutions/informatica/faq: https://learn.microsoft.com/en-us/azure/partner-solutions/informatica/faq (read 13 Nov 2026) - https://www.informatica.com/about-us/news/news-releases/2026/05/20260520-informatica-brings-headless-data-management-lakebase-connectivity-golden-record-publishing-and-unity-catalog-tag-extraction-to-the-databricks-platform.html: https://www.informatica.com/about-us/news/news-releases/2026/05/20260520-informatica-brings-headless-data-management-lakebase-connectivity-golden-record-publishing-and-unity-catalog-tag-extraction-to-the-databricks-platform.html (read 13 Nov 2026) - https://learn.microsoft.com/power-bi/enterprise/service-security-sensitivity-label-inheritance-from-data-sources: https://learn.microsoft.com/power-bi/enterprise/service-security-sensitivity-label-inheritance-from-data-sources (read 13 Nov 2026) - https://learn.microsoft.com/power-bi/enterprise/service-security-sensitivity-label-downstream-inheritance: https://learn.microsoft.com/power-bi/enterprise/service-security-sensitivity-label-downstream-inheritance (read 13 Nov 2026) - https://learn.microsoft.com/power-bi/enterprise/service-security-sensitivity-label-overview: https://learn.microsoft.com/power-bi/enterprise/service-security-sensitivity-label-overview (read 13 Nov 2026) - https://learn.microsoft.com/purview/how-to-lineage-powerbi: https://learn.microsoft.com/purview/how-to-lineage-powerbi (read 13 Nov 2026) - https://learn.microsoft.com/purview/register-scan-power-bi-tenant: https://learn.microsoft.com/purview/register-scan-power-bi-tenant (read 13 Nov 2026) - https://learn.microsoft.com/purview/: https://learn.microsoft.com/purview/ (read 13 Nov 2026) - https://learn.microsoft.com/purview/register-scan-snowflake: https://learn.microsoft.com/purview/register-scan-snowflake (read 13 Nov 2026) - https://learn.microsoft.com/purview/register-scan-azure-databricks-unity-catalog: https://learn.microsoft.com/purview/register-scan-azure-databricks-unity-catalog (read 13 Nov 2026) - https://learn.microsoft.com/purview/microsoft-purview-connector-overview: https://learn.microsoft.com/purview/microsoft-purview-connector-overview (read 13 Nov 2026) - https://learn.microsoft.com/power-bi/enterprise/service-admin-auditing: https://learn.microsoft.com/power-bi/enterprise/service-admin-auditing (read 13 Nov 2026) - https://learn.microsoft.com/purview/ai-microsoft-purview: https://learn.microsoft.com/purview/ai-microsoft-purview (read 13 Nov 2026) - https://learn.microsoft.com/purview/ai-agents: https://learn.microsoft.com/purview/ai-agents (read 13 Nov 2026) - https://learn.microsoft.com/power-bi/developer/mcp/mcp-servers-overview: https://learn.microsoft.com/power-bi/developer/mcp/mcp-servers-overview (read 13 Nov 2026) - https://learn.microsoft.com/fabric/governance/protection-policies-overview: https://learn.microsoft.com/fabric/governance/protection-policies-overview (read 13 Nov 2026) - https://learn.microsoft.com/purview/dlp-powerbi-get-started: https://learn.microsoft.com/purview/dlp-powerbi-get-started (read 13 Nov 2026) - https://www.peerspot.com/products/microsoft-purview-reviews: https://www.peerspot.com/products/microsoft-purview-reviews (read 13 Nov 2026) - https://azure.microsoft.com/en-us/pricing/details/purview/: https://azure.microsoft.com/en-us/pricing/details/purview/ (read 13 Nov 2026) - https://github.com/microsoft/Purview-ADB-Lineage-Solution-Accelerator: https://github.com/microsoft/Purview-ADB-Lineage-Solution-Accelerator (read 13 Nov 2026) - https://pypi.org/pypi/pyapacheatlas/json: https://pypi.org/pypi/pyapacheatlas/json (read 13 Nov 2026) - https://prices.azure.com/api/retail/prices?$filter=serviceName eq 'Microsoft Purview' and armRegionName eq 'eastus' and contains(meterName,'Governance'): https://prices.azure.com/api/retail/prices?$filter=serviceName eq 'Microsoft Purview' and armRegionName eq 'eastus' and contains(meterName,'Governance') (read 13 Nov 2026) Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/compare/informatica-vs-microsoft-purview/ --- # Securiti leads OneTrust on AI data governance, 29.5 to 26.5 HEAD TO HEAD, read 13 Nov 2026 **The short answer.** Securiti scores 29.5 and OneTrust 26.5 of 100 on the eight Need to Know governance criteria, read 13 Nov 2026. The widest weighted gap is Follows sensitive data into BI, 1 to 0. OneTrust documents 1 of six exposure stages and Securiti documents 2. | Criterion | Weight | OneTrust | Securiti | | --- | --- | --- | --- | | Follows sensitive data into BI | 25 | 0 | 1 | | Controls what an agent is told | 20 | 3 | 4 | | Shows who actually saw it | 15 | 3 | 3 | | Carries classification downstream | 15 | 3 | 3 | | Acts on it | 10 | 6 | 6 | | Coverage of the stack | 5 | 3 | 2 | | Evidence beyond the vendor | 5 | 5 | 5 | | Price transparency | 5 | 3 | 1 | | Total | 100 | 26.5 | 29.5 | Blind scores 0 to 10, read 13 Nov 2026. The higher score on each row is marked. ## Why the leader leads Securiti leads on Follows sensitive data into BI (1 to 0) and Controls what an agent is told (4 to 3), while OneTrust is ahead on Price transparency (3 to 1). The gap is 3.0 points on the site weights. ## How far each one follows the field | Stage | OneTrust | Securiti | | --- | --- | --- | | [Warehouse column](/exposure-map/column/) | documented | documented | | [Transformation](/exposure-map/transformation/) | none found | partial | | [BI field](/exposure-map/bi-field/) | none found | partial | | [Report](/exposure-map/report/) | none found | none found | | [Viewer](/exposure-map/viewer/) | none found | partial | | [Agent](/exposure-map/agent/) | partial | documented | From the PII Exposure Map. None found means none found in the documentation read. OneTrust documents 1 of six stages and Securiti documents 2. OneTrust names 0 BI tools and Securiti names 1. Shared BI tools: none by the same name. ## Verdict by situation - **A regulated field:** Securiti leads 27.0 to 23.5. Securiti leads on Follows sensitive data into BI (1 to 0) and Controls what an agent is told (4 to 3), while OneTrust is ahead on Coverage of the stack (3 to 2). - **Agents on analytics:** Securiti leads 32.5 to 28.5. Securiti leads on Controls what an agent is told (4 to 3) and Follows sensitive data into BI (1 to 0), while OneTrust is ahead on Price transparency (3 to 1). - **A Microsoft estate:** Securiti leads 28.5 to 25.5. Securiti leads on Follows sensitive data into BI (1 to 0) and Controls what an agent is told (4 to 3), while OneTrust is ahead on Coverage of the stack (3 to 2). - **A mixed stack:** Securiti leads 23.5 to 22.5. Securiti leads on Follows sensitive data into BI (1 to 0) and Controls what an agent is told (4 to 3), while OneTrust is ahead on Coverage of the stack (3 to 2). - **A lean team:** OneTrust leads 31.0 to 30.5. OneTrust leads on Price transparency (3 to 1) and Coverage of the stack (3 to 2), while Securiti is ahead on Follows sensitive data into BI (1 to 0). ## What OneTrust does better Vendor-stated: Turns data policies into native masking and row-filtering controls in Snowflake and Databricks Unity Catalog and governs agent tools and prompts with AI Guard, with enforcement audited in the platform's own logs. ## What Securiti does better Vendor-stated: Securiti pairs sensitive data discovery with entitlement-aware, label-based filtering for AI copilots and masking and remediation actions. ## Read next - [OneTrust profile](/platforms/onetrust/) - [Securiti profile](/platforms/securiti/) - [Alternatives to OneTrust](/alternatives/onetrust/) - [Alternatives to Securiti](/alternatives/securiti/) - [Every head-to-head](/compare/) ## Sources - https://www.onetrust.com/solutions/data-use-governance/: https://www.onetrust.com/solutions/data-use-governance/ (read 13 Nov 2026) - https://developer.onetrust.com/onetrust/reference/data-use-governance-data-catalog/llms.txt: https://developer.onetrust.com/onetrust/reference/data-use-governance-data-catalog/llms.txt (read 13 Nov 2026) - https://developer.onetrust.com/onetrust/llms.txt: https://developer.onetrust.com/onetrust/llms.txt (read 13 Nov 2026) - https://www.onetrust.com/products/ai-governance/: https://www.onetrust.com/products/ai-governance/ (read 13 Nov 2026) - https://www.prnewswire.com/news-releases/onetrust-announces-partnership-with-databricks-to-power-real-time-policy-enforcement-in-the-databricks-data-intelligence-platform-302477871.html: https://www.prnewswire.com/news-releases/onetrust-announces-partnership-with-databricks-to-power-real-time-policy-enforcement-in-the-databricks-data-intelligence-platform-302477871.html (read 13 Nov 2026) - https://developer.onetrust.com/onetrust/docs/ai-guard.md: https://developer.onetrust.com/onetrust/docs/ai-guard.md (read 13 Nov 2026) - https://github.com/onetrust-oss/ai-guard-sdk: https://github.com/onetrust-oss/ai-guard-sdk (read 13 Nov 2026) - https://developer.onetrust.com/onetrust/reference/mcp.md: https://developer.onetrust.com/onetrust/reference/mcp.md (read 13 Nov 2026) - https://www.onetrust.com/integrations/snowflake/: https://www.onetrust.com/integrations/snowflake/ (read 13 Nov 2026) - https://www.onetrust.com/integrations/: https://www.onetrust.com/integrations/ (read 13 Nov 2026) - https://www.onetrust.com/pricing/: https://www.onetrust.com/pricing/ (read 13 Nov 2026) - https://raw.githubusercontent.com/Knuckles-Team/onetrust-api/main/README.md: https://raw.githubusercontent.com/Knuckles-Team/onetrust-api/main/README.md (read 13 Nov 2026) - https://pypi.org/pypi/onetrust-api/json: https://pypi.org/pypi/onetrust-api/json (read 13 Nov 2026) - https://www.okta.com/integrations/onetrust/: https://www.okta.com/integrations/onetrust/ (read 13 Nov 2026) - https://developer.onetrust.com/onetrust/reference/createorupsertdataassetv1-1.md: https://developer.onetrust.com/onetrust/reference/createorupsertdataassetv1-1.md (read 13 Nov 2026) - https://developer.onetrust.com/onetrust/reference/getallusingget_1.md: https://developer.onetrust.com/onetrust/reference/getallusingget_1.md (read 13 Nov 2026) - https://developer.onetrust.com/onetrust/docs/ai-guard-authentication.md: https://developer.onetrust.com/onetrust/docs/ai-guard-authentication.md (read 13 Nov 2026) - https://developer.onetrust.com/onetrust/docs/ai-guard-metrics-overview.md: https://developer.onetrust.com/onetrust/docs/ai-guard-metrics-overview.md (read 13 Nov 2026) - https://developer.onetrust.com/onetrust/docs/ai-guard-faq.md: https://developer.onetrust.com/onetrust/docs/ai-guard-faq.md (read 13 Nov 2026) - https://securiti.ai/connectors/tableau/: https://securiti.ai/connectors/tableau/ (read 13 Nov 2026) - https://securiti.ai/gencore/integrations/: https://securiti.ai/gencore/integrations/ (read 13 Nov 2026) - https://securiti.ai/press-release/securiti-joins-snowflake-governance-program/: https://securiti.ai/press-release/securiti-joins-snowflake-governance-program/ (read 13 Nov 2026) - https://securiti.ai/gencore/partners/databricks/: https://securiti.ai/gencore/partners/databricks/ (read 13 Nov 2026) - https://securiti.ai/connectors/: https://securiti.ai/connectors/ (read 13 Nov 2026) - https://securiti.ai/products/data-lineage/: https://securiti.ai/products/data-lineage/ (read 13 Nov 2026) - https://securiti.ai/products/sensitive-data-catalog/: https://securiti.ai/products/sensitive-data-catalog/ (read 13 Nov 2026) - https://securiti.ai/what-is-data-lineage/: https://securiti.ai/what-is-data-lineage/ (read 13 Nov 2026) - https://securiti.ai/products/data-discovery/: https://securiti.ai/products/data-discovery/ (read 13 Nov 2026) - https://securiti.ai/products/data-classification/: https://securiti.ai/products/data-classification/ (read 13 Nov 2026) - https://securiti.ai/gencore/safe-enterprise-ai-copilot/: https://securiti.ai/gencore/safe-enterprise-ai-copilot/ (read 13 Nov 2026) - https://securiti.ai/products/security-for-ai-agents-and-copilots/: https://securiti.ai/products/security-for-ai-agents-and-copilots/ (read 13 Nov 2026) - https://securiti.ai/products/access-intelligence/: https://securiti.ai/products/access-intelligence/ (read 13 Nov 2026) - https://securiti.ai/press-release/veeam-introduces-agent-commander-to-confront-agentic-ai-risk-at-enterprise-scale/: https://securiti.ai/press-release/veeam-introduces-agent-commander-to-confront-agentic-ai-risk-at-enterprise-scale/ (read 13 Nov 2026) - https://securiti.ai/agent-commander/: https://securiti.ai/agent-commander/ (read 13 Nov 2026) - https://securiti.ai/dspm/: https://securiti.ai/dspm/ (read 13 Nov 2026) - https://securiti.ai/press-release/veeams-securiti-ai-named-a-leader-and-fast-mover-in-gigaoms-2026-dspm-radar-with-top-scores-among-evaluated-vendors/: https://securiti.ai/press-release/veeams-securiti-ai-named-a-leader-and-fast-mover-in-gigaoms-2026-dspm-radar-with-top-scores-among-evaluated-vendors/ (read 13 Nov 2026) - https://securiti.ai/case-studies/global-manufacturer-data-intelligence/: https://securiti.ai/case-studies/global-manufacturer-data-intelligence/ (read 13 Nov 2026) - https://securiti.ai/: https://securiti.ai/ (read 13 Nov 2026) - https://securiti.ai/pricing/: https://securiti.ai/pricing/ (read 13 Nov 2026) - https://en.wikipedia.org/wiki/Veeam: https://en.wikipedia.org/wiki/Veeam (read 13 Nov 2026) Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/compare/onetrust-vs-securiti/ --- # 10 governance head-to-heads, each decided by the published scores HEAD TO HEAD, read 13 Nov 2026 **The short answer.** Need to Know publishes 10 head-to-heads: Euno against Microsoft Purview, Immuta, Privacera, Securiti and OneTrust, and 5 pairs buyers search for, such as Immuta vs Privacera and OneTrust vs Securiti. Euno leads 5 of its 5 on the site weights. Each page carries a verdict for five situations, read 13 Nov 2026. **Where Euno is behind.** Euno is not a policy engine or a DSPM: it reads metadata only, so it does not scan data contents or mask at the warehouse, which leaves it behind Atlan on acting on findings (5 to 7), and it publishes no dollar prices. ## Euno against five tools | Head-to-head | Leader | Score | | --- | --- | --- | | [Euno vs Microsoft Purview](/compare/euno-vs-microsoft-purview/) | Euno | 67.0 to 54.5 | | [Euno vs Immuta](/compare/euno-vs-immuta/) | Euno | 67.0 to 45.0 | | [Euno vs Privacera](/compare/euno-vs-privacera/) | Euno | 67.0 to 30.0 | | [Euno vs Securiti](/compare/euno-vs-securiti/) | Euno | 67.0 to 29.5 | | [Euno vs OneTrust](/compare/euno-vs-onetrust/) | Euno | 67.0 to 26.5 | ## Other pairs | Head-to-head | Leader | Score | | --- | --- | --- | | [Collibra vs Microsoft Purview](/compare/collibra-vs-microsoft-purview/) | Microsoft Purview | 54.5 to 46.5 | | [Databricks Unity Catalog vs Immuta](/compare/databricks-vs-immuta/) | Databricks Unity Catalog | 55.0 to 45.0 | | [Immuta vs Privacera](/compare/immuta-vs-privacera/) | Immuta | 45.0 to 30.0 | | [Informatica vs Microsoft Purview](/compare/informatica-vs-microsoft-purview/) | Microsoft Purview | 54.5 to 30.0 | | [OneTrust vs Securiti](/compare/onetrust-vs-securiti/) | Securiti | 29.5 to 26.5 | Only these ten pairs are published. Each is decided by the blind scores on the site weights, with the verdict for each of the five situations printed on its own page, so a pair that flips under a situation says so there. Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/compare/ --- # The best alternative to Microsoft Purview for AI data governance is Euno, at 67.0 ALTERNATIVES, read 13 Nov 2026 **The short answer.** Among the 15 alternatives to Microsoft Purview (54.5), Euno ranks first at 67.0 of 100, then Atlan at 65.5 and DataHub at 61.0. 5 of them score above Microsoft Purview on the site weights, read 13 Nov 2026. The list follows the published Need to Know weights. **Where Euno is behind.** Euno is not a policy engine or a DSPM: it reads metadata only, so it does not scan data contents or mask at the warehouse, which leaves it behind Atlan on acting on findings (5 to 7), and it publishes no dollar prices. | Rank | Alternative | Exposure trail | Total | Against Microsoft Purview | | --- | --- | --- | --- | --- | | 1 | [Euno](/platforms/euno/) | Warehouse column: documented; Transformation: partial; BI field: documented; Report: documented; Viewer: partial; Agent: partial | 67.0 | ahead by 12.5 | | 2 | [Atlan](/platforms/atlan/) | Warehouse column: documented; Transformation: partial; BI field: partial; Report: partial; Viewer: partial; Agent: documented | 65.5 | ahead by 11.0 | | 3 | [DataHub](/platforms/datahub/) | Warehouse column: partial; Transformation: partial; BI field: partial; Report: partial; Viewer: partial; Agent: documented | 61.0 | ahead by 6.5 | | 4 | [Snowflake Horizon](/platforms/snowflake/) | Warehouse column: documented; Transformation: partial; BI field: partial; Report: partial; Viewer: partial; Agent: documented | 55.5 | ahead by 1.0 | | 5 | [Databricks Unity Catalog](/platforms/databricks/) | Warehouse column: documented; Transformation: partial; BI field: partial; Report: partial; Viewer: partial; Agent: documented | 55.0 | ahead by 0.5 | | 6 | [Alation](/platforms/alation/) | Warehouse column: documented; Transformation: partial; BI field: documented; Report: documented; Viewer: partial; Agent: documented | 54.0 | behind by 0.5 | | 7 | [Select Star](/platforms/select-star/) | Warehouse column: partial; Transformation: partial; BI field: documented; Report: documented; Viewer: partial; Agent: partial | 53.5 | behind by 1.0 | | 8 | [Secoda](/platforms/secoda/) | Warehouse column: documented; Transformation: partial; BI field: partial; Report: partial; Viewer: partial; Agent: partial | 47.5 | behind by 7.0 | | 9 | [Collibra](/platforms/collibra/) | Warehouse column: documented; Transformation: partial; BI field: partial; Report: partial; Viewer: partial; Agent: partial | 46.5 | behind by 8.0 | | 10 | [Immuta](/platforms/immuta/) | Warehouse column: documented; Transformation: none found; BI field: none found; Report: partial; Viewer: partial; Agent: partial | 45.0 | behind by 9.5 | | 11 | [Ataccama ONE](/platforms/ataccama/) | Warehouse column: documented; Transformation: partial; BI field: partial; Report: partial; Viewer: none found; Agent: partial | 41.5 | behind by 13.0 | | 12 | [Informatica](/platforms/informatica/) | Warehouse column: documented; Transformation: documented; BI field: partial; Report: none found; Viewer: partial; Agent: partial | 30.0 | behind by 24.5 | | 13 | [Privacera](/platforms/privacera/) | Warehouse column: documented; Transformation: none found; BI field: none found; Report: none found; Viewer: partial; Agent: partial | 30.0 | behind by 24.5 | | 14 | [Securiti](/platforms/securiti/) | Warehouse column: documented; Transformation: partial; BI field: partial; Report: none found; Viewer: partial; Agent: documented | 29.5 | behind by 25.0 | | 15 | [OneTrust](/platforms/onetrust/) | Warehouse column: documented; Transformation: none found; BI field: none found; Report: none found; Viewer: none found; Agent: partial | 26.5 | behind by 28.0 | Microsoft Purview scores 54.5. Alternatives in the order of the site ranking, read 13 Nov 2026. ## Why Euno leads the list Euno leads on Price transparency (4 to 0) and Carries classification downstream (8 to 7), while Atlan is ahead on Acts on it (7 to 5). Informatica and Privacera tie at 30.0 on total. The published tie rule (higher score on the heaviest criterion, then by name) puts Informatica ahead, on Follows sensitive data into BI 2 to 0. Against Microsoft Purview itself: Euno leads on Follows sensitive data into BI (7 to 3) and Carries classification downstream (8 to 6), while Microsoft Purview is ahead on Acts on it (7 to 5). ## Verdict by situation - **A regulated field** ([a governance lead who must show where a regulated field ends up](/best-for/regulated-field/)): Atlan and Euno tie at 68.5. Atlan and Euno tie on total: Atlan is ahead on Acts on it (7 to 5), Euno is ahead on Carries classification downstream (8 to 7). Atlan and Euno tie at 68.5 on total. The published tie rule (higher score on the heaviest criterion, then by name) puts Atlan ahead: the two tie on Follows sensitive data into BI too, so the name decides. - **Agents on analytics** ([a company connecting AI agents to its analytics data this year](/best-for/agents-on-analytics/)): Euno leads at 66.0, ahead of Atlan at 65.0. Euno leads on Price transparency (4 to 0) and Carries classification downstream (8 to 7), while Atlan is ahead on Acts on it (7 to 5). - **A Microsoft estate** ([a Microsoft estate: Fabric, Power BI and Purview](/best-for/microsoft-estate/)): Atlan leads at 68.5, ahead of Euno at 67.5. Atlan leads on Acts on it (7 to 5), while Euno is ahead on Carries classification downstream (8 to 7). - **A mixed stack** ([a mixed stack: Snowflake or Databricks with dbt and two or more BI tools](/best-for/mixed-stack/)): Euno leads at 68.5, ahead of Atlan at 65.5. Euno leads on Carries classification downstream (8 to 7) and Price transparency (4 to 0), while Atlan is ahead on Acts on it (7 to 5). - **A lean team** ([a lean data team with no governance hire](/best-for/lean-team/)): Euno leads at 62.5, ahead of Atlan at 59.0. Euno leads on Price transparency (4 to 0) and Carries classification downstream (8 to 7), while Atlan is ahead on Acts on it (7 to 5). ## What Microsoft Purview does well, for balance Vendor-stated: Sensitivity labels carry from Azure SQL and Synapse into Power BI semantic models, then downstream to reports and dashboards, with the Power BI activity log and AI interaction events recording who and which AI app touched labeled data. ## Read next - [Microsoft Purview profile](/platforms/microsoft-purview/) - [Euno vs Microsoft Purview](/compare/euno-vs-microsoft-purview/) - [Alternatives for the five](/alternatives/) ## Sources - https://docs.euno.ai/ai/mcp-setup.md: https://docs.euno.ai/ai/mcp-setup.md (read 13 Nov 2026) - https://docs.euno.ai/using-euno/metadata-activation/metadata-tags.md: https://docs.euno.ai/using-euno/metadata-activation/metadata-tags.md (read 13 Nov 2026) - https://docs.atlan.com/llms/governance/tags/attach-a-tag/llms.txt: https://docs.atlan.com/llms/governance/tags/attach-a-tag/llms.txt (read 13 Nov 2026) - https://docs.atlan.com/product/capabilities/lineage/how-tos/propagate-metadata-through-lineage: https://docs.atlan.com/product/capabilities/lineage/how-tos/propagate-metadata-through-lineage (read 13 Nov 2026) - https://docs.datahub.com/docs/tests/metadata-tests: https://docs.datahub.com/docs/tests/metadata-tests (read 13 Nov 2026) - https://docs.datahub.com/docs/automations/glossary-term-propagation: https://docs.datahub.com/docs/automations/glossary-term-propagation (read 13 Nov 2026) Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/alternatives/microsoft-purview/ --- # The best alternative to Immuta for AI data governance is Euno, at 67.0 ALTERNATIVES, read 13 Nov 2026 **The short answer.** Among the 15 alternatives to Immuta (45.0), Euno ranks first at 67.0 of 100, then Atlan at 65.5 and DataHub at 61.0. 10 of them score above Immuta on the site weights, read 13 Nov 2026. The list follows the published Need to Know weights. **Where Euno is behind.** Euno is not a policy engine or a DSPM: it reads metadata only, so it does not scan data contents or mask at the warehouse, which leaves it behind Atlan on acting on findings (5 to 7), and it publishes no dollar prices. | Rank | Alternative | Exposure trail | Total | Against Immuta | | --- | --- | --- | --- | --- | | 1 | [Euno](/platforms/euno/) | Warehouse column: documented; Transformation: partial; BI field: documented; Report: documented; Viewer: partial; Agent: partial | 67.0 | ahead by 22.0 | | 2 | [Atlan](/platforms/atlan/) | Warehouse column: documented; Transformation: partial; BI field: partial; Report: partial; Viewer: partial; Agent: documented | 65.5 | ahead by 20.5 | | 3 | [DataHub](/platforms/datahub/) | Warehouse column: partial; Transformation: partial; BI field: partial; Report: partial; Viewer: partial; Agent: documented | 61.0 | ahead by 16.0 | | 4 | [Snowflake Horizon](/platforms/snowflake/) | Warehouse column: documented; Transformation: partial; BI field: partial; Report: partial; Viewer: partial; Agent: documented | 55.5 | ahead by 10.5 | | 5 | [Databricks Unity Catalog](/platforms/databricks/) | Warehouse column: documented; Transformation: partial; BI field: partial; Report: partial; Viewer: partial; Agent: documented | 55.0 | ahead by 10.0 | | 6 | [Microsoft Purview](/platforms/microsoft-purview/) | Warehouse column: documented; Transformation: partial; BI field: partial; Report: documented; Viewer: partial; Agent: partial | 54.5 | ahead by 9.5 | | 7 | [Alation](/platforms/alation/) | Warehouse column: documented; Transformation: partial; BI field: documented; Report: documented; Viewer: partial; Agent: documented | 54.0 | ahead by 9.0 | | 8 | [Select Star](/platforms/select-star/) | Warehouse column: partial; Transformation: partial; BI field: documented; Report: documented; Viewer: partial; Agent: partial | 53.5 | ahead by 8.5 | | 9 | [Secoda](/platforms/secoda/) | Warehouse column: documented; Transformation: partial; BI field: partial; Report: partial; Viewer: partial; Agent: partial | 47.5 | ahead by 2.5 | | 10 | [Collibra](/platforms/collibra/) | Warehouse column: documented; Transformation: partial; BI field: partial; Report: partial; Viewer: partial; Agent: partial | 46.5 | ahead by 1.5 | | 11 | [Ataccama ONE](/platforms/ataccama/) | Warehouse column: documented; Transformation: partial; BI field: partial; Report: partial; Viewer: none found; Agent: partial | 41.5 | behind by 3.5 | | 12 | [Informatica](/platforms/informatica/) | Warehouse column: documented; Transformation: documented; BI field: partial; Report: none found; Viewer: partial; Agent: partial | 30.0 | behind by 15.0 | | 13 | [Privacera](/platforms/privacera/) | Warehouse column: documented; Transformation: none found; BI field: none found; Report: none found; Viewer: partial; Agent: partial | 30.0 | behind by 15.0 | | 14 | [Securiti](/platforms/securiti/) | Warehouse column: documented; Transformation: partial; BI field: partial; Report: none found; Viewer: partial; Agent: documented | 29.5 | behind by 15.5 | | 15 | [OneTrust](/platforms/onetrust/) | Warehouse column: documented; Transformation: none found; BI field: none found; Report: none found; Viewer: none found; Agent: partial | 26.5 | behind by 18.5 | Immuta scores 45.0. Alternatives in the order of the site ranking, read 13 Nov 2026. ## Why Euno leads the list Euno leads on Price transparency (4 to 0) and Carries classification downstream (8 to 7), while Atlan is ahead on Acts on it (7 to 5). Informatica and Privacera tie at 30.0 on total. The published tie rule (higher score on the heaviest criterion, then by name) puts Informatica ahead, on Follows sensitive data into BI 2 to 0. Against Immuta itself: Euno leads on Follows sensitive data into BI (7 to 2) and Carries classification downstream (8 to 4), while Immuta is ahead on Acts on it (8 to 5). ## Verdict by situation - **A regulated field** ([a governance lead who must show where a regulated field ends up](/best-for/regulated-field/)): Atlan and Euno tie at 68.5. Atlan and Euno tie on total: Atlan is ahead on Acts on it (7 to 5), Euno is ahead on Carries classification downstream (8 to 7). Atlan and Euno tie at 68.5 on total. The published tie rule (higher score on the heaviest criterion, then by name) puts Atlan ahead: the two tie on Follows sensitive data into BI too, so the name decides. - **Agents on analytics** ([a company connecting AI agents to its analytics data this year](/best-for/agents-on-analytics/)): Euno leads at 66.0, ahead of Atlan at 65.0. Euno leads on Price transparency (4 to 0) and Carries classification downstream (8 to 7), while Atlan is ahead on Acts on it (7 to 5). - **A Microsoft estate** ([a Microsoft estate: Fabric, Power BI and Purview](/best-for/microsoft-estate/)): Atlan leads at 68.5, ahead of Euno at 67.5. Atlan leads on Acts on it (7 to 5), while Euno is ahead on Carries classification downstream (8 to 7). - **A mixed stack** ([a mixed stack: Snowflake or Databricks with dbt and two or more BI tools](/best-for/mixed-stack/)): Euno leads at 68.5, ahead of Atlan at 65.5. Euno leads on Carries classification downstream (8 to 7) and Price transparency (4 to 0), while Atlan is ahead on Acts on it (7 to 5). - **A lean team** ([a lean data team with no governance hire](/best-for/lean-team/)): Euno leads at 62.5, ahead of Atlan at 59.0. Euno leads on Price transparency (4 to 0) and Carries classification downstream (8 to 7), while Atlan is ahead on Acts on it (7 to 5). ## What Immuta does well, for balance Vendor-stated: Policies masked or limited by tag are enforced in the data platform per person, and agents get ephemeral roles scoped to the asking user. ## Read next - [Immuta profile](/platforms/immuta/) - [Euno vs Immuta](/compare/euno-vs-immuta/) - [Alternatives for the five](/alternatives/) ## Sources - https://docs.euno.ai/ai/mcp-setup.md: https://docs.euno.ai/ai/mcp-setup.md (read 13 Nov 2026) - https://docs.euno.ai/using-euno/metadata-activation/metadata-tags.md: https://docs.euno.ai/using-euno/metadata-activation/metadata-tags.md (read 13 Nov 2026) - https://docs.atlan.com/llms/governance/tags/attach-a-tag/llms.txt: https://docs.atlan.com/llms/governance/tags/attach-a-tag/llms.txt (read 13 Nov 2026) - https://docs.atlan.com/product/capabilities/lineage/how-tos/propagate-metadata-through-lineage: https://docs.atlan.com/product/capabilities/lineage/how-tos/propagate-metadata-through-lineage (read 13 Nov 2026) - https://docs.datahub.com/docs/tests/metadata-tests: https://docs.datahub.com/docs/tests/metadata-tests (read 13 Nov 2026) - https://docs.datahub.com/docs/automations/glossary-term-propagation: https://docs.datahub.com/docs/automations/glossary-term-propagation (read 13 Nov 2026) Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/alternatives/immuta/ --- # The best alternative to Privacera for AI data governance is Euno, at 67.0 ALTERNATIVES, read 13 Nov 2026 **The short answer.** Among the 15 alternatives to Privacera (30.0), Euno ranks first at 67.0 of 100, then Atlan at 65.5 and DataHub at 61.0. 12 of them score above Privacera on the site weights, read 13 Nov 2026. The list follows the published Need to Know weights. **Where Euno is behind.** Euno is not a policy engine or a DSPM: it reads metadata only, so it does not scan data contents or mask at the warehouse, which leaves it behind Atlan on acting on findings (5 to 7), and it publishes no dollar prices. | Rank | Alternative | Exposure trail | Total | Against Privacera | | --- | --- | --- | --- | --- | | 1 | [Euno](/platforms/euno/) | Warehouse column: documented; Transformation: partial; BI field: documented; Report: documented; Viewer: partial; Agent: partial | 67.0 | ahead by 37.0 | | 2 | [Atlan](/platforms/atlan/) | Warehouse column: documented; Transformation: partial; BI field: partial; Report: partial; Viewer: partial; Agent: documented | 65.5 | ahead by 35.5 | | 3 | [DataHub](/platforms/datahub/) | Warehouse column: partial; Transformation: partial; BI field: partial; Report: partial; Viewer: partial; Agent: documented | 61.0 | ahead by 31.0 | | 4 | [Snowflake Horizon](/platforms/snowflake/) | Warehouse column: documented; Transformation: partial; BI field: partial; Report: partial; Viewer: partial; Agent: documented | 55.5 | ahead by 25.5 | | 5 | [Databricks Unity Catalog](/platforms/databricks/) | Warehouse column: documented; Transformation: partial; BI field: partial; Report: partial; Viewer: partial; Agent: documented | 55.0 | ahead by 25.0 | | 6 | [Microsoft Purview](/platforms/microsoft-purview/) | Warehouse column: documented; Transformation: partial; BI field: partial; Report: documented; Viewer: partial; Agent: partial | 54.5 | ahead by 24.5 | | 7 | [Alation](/platforms/alation/) | Warehouse column: documented; Transformation: partial; BI field: documented; Report: documented; Viewer: partial; Agent: documented | 54.0 | ahead by 24.0 | | 8 | [Select Star](/platforms/select-star/) | Warehouse column: partial; Transformation: partial; BI field: documented; Report: documented; Viewer: partial; Agent: partial | 53.5 | ahead by 23.5 | | 9 | [Secoda](/platforms/secoda/) | Warehouse column: documented; Transformation: partial; BI field: partial; Report: partial; Viewer: partial; Agent: partial | 47.5 | ahead by 17.5 | | 10 | [Collibra](/platforms/collibra/) | Warehouse column: documented; Transformation: partial; BI field: partial; Report: partial; Viewer: partial; Agent: partial | 46.5 | ahead by 16.5 | | 11 | [Immuta](/platforms/immuta/) | Warehouse column: documented; Transformation: none found; BI field: none found; Report: partial; Viewer: partial; Agent: partial | 45.0 | ahead by 15.0 | | 12 | [Ataccama ONE](/platforms/ataccama/) | Warehouse column: documented; Transformation: partial; BI field: partial; Report: partial; Viewer: none found; Agent: partial | 41.5 | ahead by 11.5 | | 13 | [Informatica](/platforms/informatica/) | Warehouse column: documented; Transformation: documented; BI field: partial; Report: none found; Viewer: partial; Agent: partial | 30.0 | level | | 14 | [Securiti](/platforms/securiti/) | Warehouse column: documented; Transformation: partial; BI field: partial; Report: none found; Viewer: partial; Agent: documented | 29.5 | behind by 0.5 | | 15 | [OneTrust](/platforms/onetrust/) | Warehouse column: documented; Transformation: none found; BI field: none found; Report: none found; Viewer: none found; Agent: partial | 26.5 | behind by 3.5 | Privacera scores 30.0. Alternatives in the order of the site ranking, read 13 Nov 2026. ## Why Euno leads the list Euno leads on Price transparency (4 to 0) and Carries classification downstream (8 to 7), while Atlan is ahead on Acts on it (7 to 5). Against Privacera itself: Euno leads on Follows sensitive data into BI (7 to 0) and Controls what an agent is told (7 to 2), while Privacera is ahead on Acts on it (8 to 5). ## Verdict by situation - **A regulated field** ([a governance lead who must show where a regulated field ends up](/best-for/regulated-field/)): Atlan and Euno tie at 68.5. Atlan and Euno tie on total: Atlan is ahead on Acts on it (7 to 5), Euno is ahead on Carries classification downstream (8 to 7). Atlan and Euno tie at 68.5 on total. The published tie rule (higher score on the heaviest criterion, then by name) puts Atlan ahead: the two tie on Follows sensitive data into BI too, so the name decides. - **Agents on analytics** ([a company connecting AI agents to its analytics data this year](/best-for/agents-on-analytics/)): Euno leads at 66.0, ahead of Atlan at 65.0. Euno leads on Price transparency (4 to 0) and Carries classification downstream (8 to 7), while Atlan is ahead on Acts on it (7 to 5). - **A Microsoft estate** ([a Microsoft estate: Fabric, Power BI and Purview](/best-for/microsoft-estate/)): Atlan leads at 68.5, ahead of Euno at 67.5. Atlan leads on Acts on it (7 to 5), while Euno is ahead on Carries classification downstream (8 to 7). - **A mixed stack** ([a mixed stack: Snowflake or Databricks with dbt and two or more BI tools](/best-for/mixed-stack/)): Euno leads at 68.5, ahead of Atlan at 65.5. Euno leads on Carries classification downstream (8 to 7) and Price transparency (4 to 0), while Atlan is ahead on Acts on it (7 to 5). - **A lean team** ([a lean data team with no governance hire](/best-for/lean-team/)): Euno leads at 62.5, ahead of Atlan at 59.0. Euno leads on Price transparency (4 to 0) and Carries classification downstream (8 to 7), while Atlan is ahead on Acts on it (7 to 5). ## What Privacera does well, for balance Vendor-stated: Discovery tags sensitive columns and files and Ranger tag-based policies mask or deny across many warehouses, with audit of allow/deny access. ## Read next - [Privacera profile](/platforms/privacera/) - [Euno vs Privacera](/compare/euno-vs-privacera/) - [Alternatives for the five](/alternatives/) ## Sources - https://docs.euno.ai/ai/mcp-setup.md: https://docs.euno.ai/ai/mcp-setup.md (read 13 Nov 2026) - https://docs.euno.ai/using-euno/metadata-activation/metadata-tags.md: https://docs.euno.ai/using-euno/metadata-activation/metadata-tags.md (read 13 Nov 2026) - https://docs.atlan.com/llms/governance/tags/attach-a-tag/llms.txt: https://docs.atlan.com/llms/governance/tags/attach-a-tag/llms.txt (read 13 Nov 2026) - https://docs.atlan.com/product/capabilities/lineage/how-tos/propagate-metadata-through-lineage: https://docs.atlan.com/product/capabilities/lineage/how-tos/propagate-metadata-through-lineage (read 13 Nov 2026) - https://docs.datahub.com/docs/tests/metadata-tests: https://docs.datahub.com/docs/tests/metadata-tests (read 13 Nov 2026) - https://docs.datahub.com/docs/automations/glossary-term-propagation: https://docs.datahub.com/docs/automations/glossary-term-propagation (read 13 Nov 2026) Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/alternatives/privacera/ --- # The best alternative to Securiti for AI data governance is Euno, at 67.0 ALTERNATIVES, read 13 Nov 2026 **The short answer.** Among the 15 alternatives to Securiti (29.5), Euno ranks first at 67.0 of 100, then Atlan at 65.5 and DataHub at 61.0. 14 of them score above Securiti on the site weights, read 13 Nov 2026. The list follows the published Need to Know weights. **Where Euno is behind.** Euno is not a policy engine or a DSPM: it reads metadata only, so it does not scan data contents or mask at the warehouse, which leaves it behind Atlan on acting on findings (5 to 7), and it publishes no dollar prices. | Rank | Alternative | Exposure trail | Total | Against Securiti | | --- | --- | --- | --- | --- | | 1 | [Euno](/platforms/euno/) | Warehouse column: documented; Transformation: partial; BI field: documented; Report: documented; Viewer: partial; Agent: partial | 67.0 | ahead by 37.5 | | 2 | [Atlan](/platforms/atlan/) | Warehouse column: documented; Transformation: partial; BI field: partial; Report: partial; Viewer: partial; Agent: documented | 65.5 | ahead by 36.0 | | 3 | [DataHub](/platforms/datahub/) | Warehouse column: partial; Transformation: partial; BI field: partial; Report: partial; Viewer: partial; Agent: documented | 61.0 | ahead by 31.5 | | 4 | [Snowflake Horizon](/platforms/snowflake/) | Warehouse column: documented; Transformation: partial; BI field: partial; Report: partial; Viewer: partial; Agent: documented | 55.5 | ahead by 26.0 | | 5 | [Databricks Unity Catalog](/platforms/databricks/) | Warehouse column: documented; Transformation: partial; BI field: partial; Report: partial; Viewer: partial; Agent: documented | 55.0 | ahead by 25.5 | | 6 | [Microsoft Purview](/platforms/microsoft-purview/) | Warehouse column: documented; Transformation: partial; BI field: partial; Report: documented; Viewer: partial; Agent: partial | 54.5 | ahead by 25.0 | | 7 | [Alation](/platforms/alation/) | Warehouse column: documented; Transformation: partial; BI field: documented; Report: documented; Viewer: partial; Agent: documented | 54.0 | ahead by 24.5 | | 8 | [Select Star](/platforms/select-star/) | Warehouse column: partial; Transformation: partial; BI field: documented; Report: documented; Viewer: partial; Agent: partial | 53.5 | ahead by 24.0 | | 9 | [Secoda](/platforms/secoda/) | Warehouse column: documented; Transformation: partial; BI field: partial; Report: partial; Viewer: partial; Agent: partial | 47.5 | ahead by 18.0 | | 10 | [Collibra](/platforms/collibra/) | Warehouse column: documented; Transformation: partial; BI field: partial; Report: partial; Viewer: partial; Agent: partial | 46.5 | ahead by 17.0 | | 11 | [Immuta](/platforms/immuta/) | Warehouse column: documented; Transformation: none found; BI field: none found; Report: partial; Viewer: partial; Agent: partial | 45.0 | ahead by 15.5 | | 12 | [Ataccama ONE](/platforms/ataccama/) | Warehouse column: documented; Transformation: partial; BI field: partial; Report: partial; Viewer: none found; Agent: partial | 41.5 | ahead by 12.0 | | 13 | [Informatica](/platforms/informatica/) | Warehouse column: documented; Transformation: documented; BI field: partial; Report: none found; Viewer: partial; Agent: partial | 30.0 | ahead by 0.5 | | 14 | [Privacera](/platforms/privacera/) | Warehouse column: documented; Transformation: none found; BI field: none found; Report: none found; Viewer: partial; Agent: partial | 30.0 | ahead by 0.5 | | 15 | [OneTrust](/platforms/onetrust/) | Warehouse column: documented; Transformation: none found; BI field: none found; Report: none found; Viewer: none found; Agent: partial | 26.5 | behind by 3.0 | Securiti scores 29.5. Alternatives in the order of the site ranking, read 13 Nov 2026. ## Why Euno leads the list Euno leads on Price transparency (4 to 0) and Carries classification downstream (8 to 7), while Atlan is ahead on Acts on it (7 to 5). Informatica and Privacera tie at 30.0 on total. The published tie rule (higher score on the heaviest criterion, then by name) puts Informatica ahead, on Follows sensitive data into BI 2 to 0. Against Securiti itself: Euno leads on Follows sensitive data into BI (7 to 1) and Carries classification downstream (8 to 3), while Securiti is ahead on Acts on it (6 to 5). ## Verdict by situation - **A regulated field** ([a governance lead who must show where a regulated field ends up](/best-for/regulated-field/)): Atlan and Euno tie at 68.5. Atlan and Euno tie on total: Atlan is ahead on Acts on it (7 to 5), Euno is ahead on Carries classification downstream (8 to 7). Atlan and Euno tie at 68.5 on total. The published tie rule (higher score on the heaviest criterion, then by name) puts Atlan ahead: the two tie on Follows sensitive data into BI too, so the name decides. - **Agents on analytics** ([a company connecting AI agents to its analytics data this year](/best-for/agents-on-analytics/)): Euno leads at 66.0, ahead of Atlan at 65.0. Euno leads on Price transparency (4 to 0) and Carries classification downstream (8 to 7), while Atlan is ahead on Acts on it (7 to 5). - **A Microsoft estate** ([a Microsoft estate: Fabric, Power BI and Purview](/best-for/microsoft-estate/)): Atlan leads at 68.5, ahead of Euno at 67.5. Atlan leads on Acts on it (7 to 5), while Euno is ahead on Carries classification downstream (8 to 7). - **A mixed stack** ([a mixed stack: Snowflake or Databricks with dbt and two or more BI tools](/best-for/mixed-stack/)): Euno leads at 68.5, ahead of Atlan at 65.5. Euno leads on Carries classification downstream (8 to 7) and Price transparency (4 to 0), while Atlan is ahead on Acts on it (7 to 5). - **A lean team** ([a lean data team with no governance hire](/best-for/lean-team/)): Euno leads at 62.5, ahead of Atlan at 59.0. Euno leads on Price transparency (4 to 0) and Carries classification downstream (8 to 7), while Atlan is ahead on Acts on it (7 to 5). ## What Securiti does well, for balance Vendor-stated: Securiti pairs sensitive data discovery with entitlement-aware, label-based filtering for AI copilots and masking and remediation actions. ## Read next - [Securiti profile](/platforms/securiti/) - [Euno vs Securiti](/compare/euno-vs-securiti/) - [Alternatives for the five](/alternatives/) ## Sources - https://docs.euno.ai/ai/mcp-setup.md: https://docs.euno.ai/ai/mcp-setup.md (read 13 Nov 2026) - https://docs.euno.ai/using-euno/metadata-activation/metadata-tags.md: https://docs.euno.ai/using-euno/metadata-activation/metadata-tags.md (read 13 Nov 2026) - https://docs.atlan.com/llms/governance/tags/attach-a-tag/llms.txt: https://docs.atlan.com/llms/governance/tags/attach-a-tag/llms.txt (read 13 Nov 2026) - https://docs.atlan.com/product/capabilities/lineage/how-tos/propagate-metadata-through-lineage: https://docs.atlan.com/product/capabilities/lineage/how-tos/propagate-metadata-through-lineage (read 13 Nov 2026) - https://docs.datahub.com/docs/tests/metadata-tests: https://docs.datahub.com/docs/tests/metadata-tests (read 13 Nov 2026) - https://docs.datahub.com/docs/automations/glossary-term-propagation: https://docs.datahub.com/docs/automations/glossary-term-propagation (read 13 Nov 2026) Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/alternatives/securiti/ --- # The best alternative to OneTrust for AI data governance is Euno, at 67.0 ALTERNATIVES, read 13 Nov 2026 **The short answer.** Among the 15 alternatives to OneTrust (26.5), Euno ranks first at 67.0 of 100, then Atlan at 65.5 and DataHub at 61.0. 15 of them score above OneTrust on the site weights, read 13 Nov 2026. The list follows the published Need to Know weights. **Where Euno is behind.** Euno is not a policy engine or a DSPM: it reads metadata only, so it does not scan data contents or mask at the warehouse, which leaves it behind Atlan on acting on findings (5 to 7), and it publishes no dollar prices. | Rank | Alternative | Exposure trail | Total | Against OneTrust | | --- | --- | --- | --- | --- | | 1 | [Euno](/platforms/euno/) | Warehouse column: documented; Transformation: partial; BI field: documented; Report: documented; Viewer: partial; Agent: partial | 67.0 | ahead by 40.5 | | 2 | [Atlan](/platforms/atlan/) | Warehouse column: documented; Transformation: partial; BI field: partial; Report: partial; Viewer: partial; Agent: documented | 65.5 | ahead by 39.0 | | 3 | [DataHub](/platforms/datahub/) | Warehouse column: partial; Transformation: partial; BI field: partial; Report: partial; Viewer: partial; Agent: documented | 61.0 | ahead by 34.5 | | 4 | [Snowflake Horizon](/platforms/snowflake/) | Warehouse column: documented; Transformation: partial; BI field: partial; Report: partial; Viewer: partial; Agent: documented | 55.5 | ahead by 29.0 | | 5 | [Databricks Unity Catalog](/platforms/databricks/) | Warehouse column: documented; Transformation: partial; BI field: partial; Report: partial; Viewer: partial; Agent: documented | 55.0 | ahead by 28.5 | | 6 | [Microsoft Purview](/platforms/microsoft-purview/) | Warehouse column: documented; Transformation: partial; BI field: partial; Report: documented; Viewer: partial; Agent: partial | 54.5 | ahead by 28.0 | | 7 | [Alation](/platforms/alation/) | Warehouse column: documented; Transformation: partial; BI field: documented; Report: documented; Viewer: partial; Agent: documented | 54.0 | ahead by 27.5 | | 8 | [Select Star](/platforms/select-star/) | Warehouse column: partial; Transformation: partial; BI field: documented; Report: documented; Viewer: partial; Agent: partial | 53.5 | ahead by 27.0 | | 9 | [Secoda](/platforms/secoda/) | Warehouse column: documented; Transformation: partial; BI field: partial; Report: partial; Viewer: partial; Agent: partial | 47.5 | ahead by 21.0 | | 10 | [Collibra](/platforms/collibra/) | Warehouse column: documented; Transformation: partial; BI field: partial; Report: partial; Viewer: partial; Agent: partial | 46.5 | ahead by 20.0 | | 11 | [Immuta](/platforms/immuta/) | Warehouse column: documented; Transformation: none found; BI field: none found; Report: partial; Viewer: partial; Agent: partial | 45.0 | ahead by 18.5 | | 12 | [Ataccama ONE](/platforms/ataccama/) | Warehouse column: documented; Transformation: partial; BI field: partial; Report: partial; Viewer: none found; Agent: partial | 41.5 | ahead by 15.0 | | 13 | [Informatica](/platforms/informatica/) | Warehouse column: documented; Transformation: documented; BI field: partial; Report: none found; Viewer: partial; Agent: partial | 30.0 | ahead by 3.5 | | 14 | [Privacera](/platforms/privacera/) | Warehouse column: documented; Transformation: none found; BI field: none found; Report: none found; Viewer: partial; Agent: partial | 30.0 | ahead by 3.5 | | 15 | [Securiti](/platforms/securiti/) | Warehouse column: documented; Transformation: partial; BI field: partial; Report: none found; Viewer: partial; Agent: documented | 29.5 | ahead by 3.0 | OneTrust scores 26.5. Alternatives in the order of the site ranking, read 13 Nov 2026. ## Why Euno leads the list Euno leads on Price transparency (4 to 0) and Carries classification downstream (8 to 7), while Atlan is ahead on Acts on it (7 to 5). Informatica and Privacera tie at 30.0 on total. The published tie rule (higher score on the heaviest criterion, then by name) puts Informatica ahead, on Follows sensitive data into BI 2 to 0. Against OneTrust itself: Euno leads on Follows sensitive data into BI (7 to 0) and Controls what an agent is told (7 to 3), while OneTrust is ahead on Acts on it (6 to 5). ## Verdict by situation - **A regulated field** ([a governance lead who must show where a regulated field ends up](/best-for/regulated-field/)): Atlan and Euno tie at 68.5. Atlan and Euno tie on total: Atlan is ahead on Acts on it (7 to 5), Euno is ahead on Carries classification downstream (8 to 7). Atlan and Euno tie at 68.5 on total. The published tie rule (higher score on the heaviest criterion, then by name) puts Atlan ahead: the two tie on Follows sensitive data into BI too, so the name decides. - **Agents on analytics** ([a company connecting AI agents to its analytics data this year](/best-for/agents-on-analytics/)): Euno leads at 66.0, ahead of Atlan at 65.0. Euno leads on Price transparency (4 to 0) and Carries classification downstream (8 to 7), while Atlan is ahead on Acts on it (7 to 5). - **A Microsoft estate** ([a Microsoft estate: Fabric, Power BI and Purview](/best-for/microsoft-estate/)): Atlan leads at 68.5, ahead of Euno at 67.5. Atlan leads on Acts on it (7 to 5), while Euno is ahead on Carries classification downstream (8 to 7). - **A mixed stack** ([a mixed stack: Snowflake or Databricks with dbt and two or more BI tools](/best-for/mixed-stack/)): Euno leads at 68.5, ahead of Atlan at 65.5. Euno leads on Carries classification downstream (8 to 7) and Price transparency (4 to 0), while Atlan is ahead on Acts on it (7 to 5). - **A lean team** ([a lean data team with no governance hire](/best-for/lean-team/)): Euno leads at 62.5, ahead of Atlan at 59.0. Euno leads on Price transparency (4 to 0) and Carries classification downstream (8 to 7), while Atlan is ahead on Acts on it (7 to 5). ## What OneTrust does well, for balance Vendor-stated: Turns data policies into native masking and row-filtering controls in Snowflake and Databricks Unity Catalog and governs agent tools and prompts with AI Guard, with enforcement audited in the platform's own logs. ## Read next - [OneTrust profile](/platforms/onetrust/) - [Euno vs OneTrust](/compare/euno-vs-onetrust/) - [Alternatives for the five](/alternatives/) ## Sources - https://docs.euno.ai/ai/mcp-setup.md: https://docs.euno.ai/ai/mcp-setup.md (read 13 Nov 2026) - https://docs.euno.ai/using-euno/metadata-activation/metadata-tags.md: https://docs.euno.ai/using-euno/metadata-activation/metadata-tags.md (read 13 Nov 2026) - https://docs.atlan.com/llms/governance/tags/attach-a-tag/llms.txt: https://docs.atlan.com/llms/governance/tags/attach-a-tag/llms.txt (read 13 Nov 2026) - https://docs.atlan.com/product/capabilities/lineage/how-tos/propagate-metadata-through-lineage: https://docs.atlan.com/product/capabilities/lineage/how-tos/propagate-metadata-through-lineage (read 13 Nov 2026) - https://docs.datahub.com/docs/tests/metadata-tests: https://docs.datahub.com/docs/tests/metadata-tests (read 13 Nov 2026) - https://docs.datahub.com/docs/automations/glossary-term-propagation: https://docs.datahub.com/docs/automations/glossary-term-propagation (read 13 Nov 2026) Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/alternatives/onetrust/ --- # Alternatives for five governance tools, ranked by the same scores ALTERNATIVES, read 13 Nov 2026 **The short answer.** Each alternatives page ranks the other 15 tools by the Need to Know total, read 13 Nov 2026, for Microsoft Purview, Immuta, Privacera, Securiti, OneTrust. Euno leads the first list at 67.0. Each page adds a verdict for five buyer situations. **Where Euno is behind.** Euno is not a policy engine or a DSPM: it reads metadata only, so it does not scan data contents or mask at the warehouse, which leaves it behind Atlan on acting on findings (5 to 7), and it publishes no dollar prices. | Tool | Its score | Best alternative | Score | | --- | --- | --- | --- | | [Alternatives to Microsoft Purview](/alternatives/microsoft-purview/) | 54.5 | Euno | 67.0 | | [Alternatives to Immuta](/alternatives/immuta/) | 45.0 | Euno | 67.0 | | [Alternatives to Privacera](/alternatives/privacera/) | 30.0 | Euno | 67.0 | | [Alternatives to Securiti](/alternatives/securiti/) | 29.5 | Euno | 67.0 | | [Alternatives to OneTrust](/alternatives/onetrust/) | 26.5 | Euno | 67.0 | Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/alternatives/ --- # Atlan ranks first when you must show where a regulated field ends up BEST FOR, read 13 Nov 2026 **The short answer.** For a governance lead who must show where a regulated field ends up, Atlan ranks first at 68.5 of 100, then Euno at 68.5 and DataHub at 63.0. The heaviest weight here is Follows sensitive data into BI at 35. Scores read 13 Nov 2026. An auditor asks for the path of one field: from the warehouse column, through the models built on it, into the BI fields and reports that show it, and to the people who opened them. The answer is a document, not a dashboard, and it has to be produced for a field the team did not classify itself. This situation puts 35 of 100 weight on following the field into BI, 20 on who saw it and 20 on carrying the classification along. It puts 5 on controlling the agent and none on price, because the audit is the deadline. ## The weights for this situation | Criterion | Situation weight | Site weight | | --- | --- | --- | | Follows sensitive data into BI | 35 | 25 | | Controls what an agent is told | 5 | 20 | | Shows who actually saw it | 20 | 15 | | Carries classification downstream | 20 | 15 | | Acts on it | 10 | 10 | | Coverage of the stack | 5 | 5 | | Evidence beyond the vendor | 5 | 5 | | Price transparency | 0 | 5 | Fixed and committed with the site weights before any score. ## The ranking for this situation | Rank | Tool | Total | Into BI (35) | Agent told (5) | Who saw it (20) | Label carried (20) | Acts (10) | Stack (5) | Evidence (5) | Exposure trail | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | 1 | [Atlan](/platforms/atlan/) | 68.5 | 7 | 7 | 6 | 7 | 7 | 7 | 8 | Warehouse column: documented; Transformation: partial; BI field: partial; Report: partial; Viewer: partial; Agent: documented | | 2 | [Euno](/platforms/euno/) | 68.5 | 7 | 7 | 6 | 8 | 5 | 7 | 8 | Warehouse column: documented; Transformation: partial; BI field: documented; Report: documented; Viewer: partial; Agent: partial | | 3 | [DataHub](/platforms/datahub/) | 63.0 | 8 | 7 | 4 | 6 | 4 | 6 | 9 | Warehouse column: partial; Transformation: partial; BI field: partial; Report: partial; Viewer: partial; Agent: documented | | 4 | [Select Star](/platforms/select-star/) | 62.0 | 7 | 2 | 6 | 6 | 5 | 6 | 9 | Warehouse column: partial; Transformation: partial; BI field: documented; Report: documented; Viewer: partial; Agent: partial | | 5 | [Alation](/platforms/alation/) | 54.0 | 7 | 6 | 4 | 4 | 4 | 5 | 8 | Warehouse column: documented; Transformation: partial; BI field: documented; Report: documented; Viewer: partial; Agent: documented | | 6 | [Snowflake Horizon](/platforms/snowflake/) | 52.5 | 5 | 6 | 4 | 5 | 7 | 5 | 9 | Warehouse column: documented; Transformation: partial; BI field: partial; Report: partial; Viewer: partial; Agent: documented | | 7 | [Databricks Unity Catalog](/platforms/databricks/) | 52.0 | 4 | 7 | 6 | 5 | 6 | 4 | 9 | Warehouse column: documented; Transformation: partial; BI field: partial; Report: partial; Viewer: partial; Agent: documented | | 8 | [Microsoft Purview](/platforms/microsoft-purview/) | 51.0 | 3 | 6 | 6 | 6 | 7 | 5 | 8 | Warehouse column: documented; Transformation: partial; BI field: partial; Report: documented; Viewer: partial; Agent: partial | | 9 | [Secoda](/platforms/secoda/) | 49.5 | 6 | 4 | 3 | 4 | 5 | 6 | 9 | Warehouse column: documented; Transformation: partial; BI field: partial; Report: partial; Viewer: partial; Agent: partial | | 10 | [Collibra](/platforms/collibra/) | 46.0 | 5 | 5 | 3 | 3 | 7 | 6 | 8 | Warehouse column: documented; Transformation: partial; BI field: partial; Report: partial; Viewer: partial; Agent: partial | | 11 | [Immuta](/platforms/immuta/) | 42.5 | 2 | 6 | 5 | 4 | 8 | 5 | 8 | Warehouse column: documented; Transformation: none found; BI field: none found; Report: partial; Viewer: partial; Agent: partial | | 12 | [Ataccama ONE](/platforms/ataccama/) | 39.0 | 5 | 5 | 1 | 3 | 5 | 4 | 8 | Warehouse column: documented; Transformation: partial; BI field: partial; Report: partial; Viewer: none found; Agent: partial | | 13 | [Privacera](/platforms/privacera/) | 31.0 | 0 | 2 | 4 | 4 | 8 | 4 | 8 | Warehouse column: documented; Transformation: none found; BI field: none found; Report: none found; Viewer: partial; Agent: partial | | 14 | [Informatica](/platforms/informatica/) | 30.0 | 2 | 2 | 3 | 3 | 4 | 3 | 9 | Warehouse column: documented; Transformation: documented; BI field: partial; Report: none found; Viewer: partial; Agent: partial | | 15 | [Securiti](/platforms/securiti/) | 27.0 | 1 | 4 | 3 | 3 | 6 | 2 | 5 | Warehouse column: documented; Transformation: partial; BI field: partial; Report: none found; Viewer: partial; Agent: documented | | 16 | [OneTrust](/platforms/onetrust/) | 23.5 | 0 | 3 | 3 | 3 | 6 | 3 | 5 | Warehouse column: documented; Transformation: none found; BI field: none found; Report: none found; Viewer: none found; Agent: partial | Ranked under the weights for this situation (a regulated field). Ties go to the higher score on the heaviest criterion, then to the name. Read 13 Nov 2026. ## Why the leader leads here Atlan and Euno tie on total: Atlan is ahead on Acts on it (7 to 5), Euno is ahead on Carries classification downstream (8 to 7). Atlan and Euno tie at 68.5 on total. The published tie rule (higher score on the heaviest criterion, then by name) puts Atlan ahead: the two tie on Follows sensitive data into BI too, so the name decides. DataHub is third at 63.0. ## The top three, in one line each - [Atlan](/platforms/atlan/), 68.5: Vendor-stated: Tag-driven purposes mask or deny sensitive columns, tags can propagate through lineage, and MCP runs under the asking user's persona with every call logged. - [Euno](/platforms/euno/), 68.5: Vendor-stated: Euno takes classifications from Cyera and BigID, carries them along column-level lineage into BI fields and reports, and scopes MCP context by persona. - [DataHub](/platforms/datahub/), 63.0: Vendor-stated: Column-level lineage tracking, glossary term propagation to downstream lineage columns, and per-user OAuth logins for MCP. ## Other situations - [A company connecting AI agents to its analytics data this year](/best-for/agents-on-analytics/) - [A Microsoft estate: Fabric, Power BI and Purview](/best-for/microsoft-estate/) - [A mixed stack: Snowflake or Databricks with dbt and two or more BI tools](/best-for/mixed-stack/) - [A lean data team with no governance hire](/best-for/lean-team/) ## Sources - https://docs.atlan.com/llms/governance/tags/attach-a-tag/llms.txt: https://docs.atlan.com/llms/governance/tags/attach-a-tag/llms.txt (read 13 Nov 2026) - https://docs.atlan.com/product/capabilities/lineage/how-tos/propagate-metadata-through-lineage: https://docs.atlan.com/product/capabilities/lineage/how-tos/propagate-metadata-through-lineage (read 13 Nov 2026) - https://docs.atlan.com/llms/governance/tags/what-are-tags/llms.txt: https://docs.atlan.com/llms/governance/tags/what-are-tags/llms.txt (read 13 Nov 2026) - https://docs.euno.ai/ai/mcp-setup.md: https://docs.euno.ai/ai/mcp-setup.md (read 13 Nov 2026) - https://docs.euno.ai/using-euno/metadata-activation/metadata-tags.md: https://docs.euno.ai/using-euno/metadata-activation/metadata-tags.md (read 13 Nov 2026) - https://euno.ai/: https://euno.ai/ (read 13 Nov 2026) - https://docs.datahub.com/docs/tests/metadata-tests: https://docs.datahub.com/docs/tests/metadata-tests (read 13 Nov 2026) - https://docs.datahub.com/docs/automations/glossary-term-propagation: https://docs.datahub.com/docs/automations/glossary-term-propagation (read 13 Nov 2026) Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/best-for/regulated-field/ --- # Euno ranks first when AI agents are about to connect to analytics data BEST FOR, read 13 Nov 2026 **The short answer.** For a company connecting AI agents to its analytics data this year, Euno ranks first at 66.0 of 100, then Atlan at 65.0 and DataHub at 59.5. The heaviest weight here is Controls what an agent is told at 40. Scores read 13 Nov 2026. **Where Euno is behind.** Euno is not a policy engine or a DSPM: it reads metadata only, so it does not scan data contents or mask at the warehouse, which leaves it behind Atlan on acting on findings (5 to 7), and it publishes no dollar prices. Before an agent connects, someone signs off on what it can be told for each person it acts for, and on what is logged when it answers. A tool that controls access only in the warehouse leaves the agent's answer, built from a semantic model or a BI field, outside the control. This situation puts 40 of 100 weight on controlling what an agent is told, 15 on following the field into BI and 15 on who saw it. It gives nothing to evidence beyond the vendor, since the question is whether the control works on each call. ## The weights for this situation | Criterion | Situation weight | Site weight | | --- | --- | --- | | Follows sensitive data into BI | 15 | 25 | | Controls what an agent is told | 40 | 20 | | Shows who actually saw it | 15 | 15 | | Carries classification downstream | 10 | 15 | | Acts on it | 10 | 10 | | Coverage of the stack | 5 | 5 | | Evidence beyond the vendor | 0 | 5 | | Price transparency | 5 | 5 | Fixed and committed with the site weights before any score. ## The ranking for this situation | Rank | Tool | Total | Into BI (15) | Agent told (40) | Who saw it (15) | Label carried (10) | Acts (10) | Stack (5) | Price (5) | Exposure trail | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | 1 | [Euno](/platforms/euno/) | 66.0 | 7 | 7 | 6 | 8 | 5 | 7 | 4 | Warehouse column: documented; Transformation: partial; BI field: documented; Report: documented; Viewer: partial; Agent: partial | | 2 | [Atlan](/platforms/atlan/) | 65.0 | 7 | 7 | 6 | 7 | 7 | 7 | 0 | Warehouse column: documented; Transformation: partial; BI field: partial; Report: partial; Viewer: partial; Agent: documented | | 3 | [DataHub](/platforms/datahub/) | 59.5 | 8 | 7 | 4 | 6 | 4 | 6 | 1 | Warehouse column: partial; Transformation: partial; BI field: partial; Report: partial; Viewer: partial; Agent: documented | | 4 | [Databricks Unity Catalog](/platforms/databricks/) | 58.0 | 4 | 7 | 6 | 5 | 6 | 4 | 4 | Warehouse column: documented; Transformation: partial; BI field: partial; Report: partial; Viewer: partial; Agent: documented | | 5 | [Microsoft Purview](/platforms/microsoft-purview/) | 56.5 | 3 | 6 | 6 | 6 | 7 | 5 | 7 | Warehouse column: documented; Transformation: partial; BI field: partial; Report: documented; Viewer: partial; Agent: partial | | 6 | [Snowflake Horizon](/platforms/snowflake/) | 55.5 | 5 | 6 | 4 | 5 | 7 | 5 | 7 | Warehouse column: documented; Transformation: partial; BI field: partial; Report: partial; Viewer: partial; Agent: documented | | 7 | [Alation](/platforms/alation/) | 53.0 | 7 | 6 | 4 | 4 | 4 | 5 | 4 | Warehouse column: documented; Transformation: partial; BI field: documented; Report: documented; Viewer: partial; Agent: documented | | 8 | [Immuta](/platforms/immuta/) | 49.0 | 2 | 6 | 5 | 4 | 8 | 5 | 0 | Warehouse column: documented; Transformation: none found; BI field: none found; Report: partial; Viewer: partial; Agent: partial | | 9 | [Collibra](/platforms/collibra/) | 46.0 | 5 | 5 | 3 | 3 | 7 | 6 | 2 | Warehouse column: documented; Transformation: partial; BI field: partial; Report: partial; Viewer: partial; Agent: partial | | 10 | [Secoda](/platforms/secoda/) | 43.0 | 6 | 4 | 3 | 4 | 5 | 6 | 3 | Warehouse column: documented; Transformation: partial; BI field: partial; Report: partial; Viewer: partial; Agent: partial | | 11 | [Select Star](/platforms/select-star/) | 43.0 | 7 | 2 | 6 | 6 | 5 | 6 | 3 | Warehouse column: partial; Transformation: partial; BI field: documented; Report: documented; Viewer: partial; Agent: partial | | 12 | [Ataccama ONE](/platforms/ataccama/) | 41.0 | 5 | 5 | 1 | 3 | 5 | 4 | 4 | Warehouse column: documented; Transformation: partial; BI field: partial; Report: partial; Viewer: none found; Agent: partial | | 13 | [Securiti](/platforms/securiti/) | 32.5 | 1 | 4 | 3 | 3 | 6 | 2 | 1 | Warehouse column: documented; Transformation: partial; BI field: partial; Report: none found; Viewer: partial; Agent: documented | | 14 | [OneTrust](/platforms/onetrust/) | 28.5 | 0 | 3 | 3 | 3 | 6 | 3 | 3 | Warehouse column: documented; Transformation: none found; BI field: none found; Report: none found; Viewer: none found; Agent: partial | | 15 | [Privacera](/platforms/privacera/) | 28.0 | 0 | 2 | 4 | 4 | 8 | 4 | 0 | Warehouse column: documented; Transformation: none found; BI field: none found; Report: none found; Viewer: partial; Agent: partial | | 16 | [Informatica](/platforms/informatica/) | 26.0 | 2 | 2 | 3 | 3 | 4 | 3 | 4 | Warehouse column: documented; Transformation: documented; BI field: partial; Report: none found; Viewer: partial; Agent: partial | Ranked under the weights for this situation (agents on analytics). Ties go to the higher score on the heaviest criterion, then to the name. Read 13 Nov 2026. ## Why the leader leads here Euno leads on Price transparency (4 to 0) and Carries classification downstream (8 to 7), while Atlan is ahead on Acts on it (7 to 5). Secoda and Select Star tie at 43.0 on total. The published tie rule (higher score on the heaviest criterion, then by name) puts Secoda ahead, on Controls what an agent is told 4 to 2. DataHub is third at 59.5. ## The top three, in one line each - [Euno](/platforms/euno/), 66.0: Vendor-stated: Euno takes classifications from Cyera and BigID, carries them along column-level lineage into BI fields and reports, and scopes MCP context by persona. - [Atlan](/platforms/atlan/), 65.0: Vendor-stated: Tag-driven purposes mask or deny sensitive columns, tags can propagate through lineage, and MCP runs under the asking user's persona with every call logged. - [DataHub](/platforms/datahub/), 59.5: Vendor-stated: Column-level lineage tracking, glossary term propagation to downstream lineage columns, and per-user OAuth logins for MCP. ## Other situations - [A governance lead who must show where a regulated field ends up](/best-for/regulated-field/) - [A Microsoft estate: Fabric, Power BI and Purview](/best-for/microsoft-estate/) - [A mixed stack: Snowflake or Databricks with dbt and two or more BI tools](/best-for/mixed-stack/) - [A lean data team with no governance hire](/best-for/lean-team/) ## Sources - https://docs.euno.ai/ai/mcp-setup.md: https://docs.euno.ai/ai/mcp-setup.md (read 13 Nov 2026) - https://docs.euno.ai/using-euno/metadata-activation/metadata-tags.md: https://docs.euno.ai/using-euno/metadata-activation/metadata-tags.md (read 13 Nov 2026) - https://euno.ai/: https://euno.ai/ (read 13 Nov 2026) - https://docs.atlan.com/llms/governance/tags/attach-a-tag/llms.txt: https://docs.atlan.com/llms/governance/tags/attach-a-tag/llms.txt (read 13 Nov 2026) - https://docs.atlan.com/product/capabilities/lineage/how-tos/propagate-metadata-through-lineage: https://docs.atlan.com/product/capabilities/lineage/how-tos/propagate-metadata-through-lineage (read 13 Nov 2026) - https://docs.atlan.com/llms/governance/tags/what-are-tags/llms.txt: https://docs.atlan.com/llms/governance/tags/what-are-tags/llms.txt (read 13 Nov 2026) - https://docs.datahub.com/docs/tests/metadata-tests: https://docs.datahub.com/docs/tests/metadata-tests (read 13 Nov 2026) - https://docs.datahub.com/docs/automations/glossary-term-propagation: https://docs.datahub.com/docs/automations/glossary-term-propagation (read 13 Nov 2026) Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/best-for/agents-on-analytics/ --- # Atlan ranks first in a Microsoft estate of Fabric, Power BI and Purview BEST FOR, read 13 Nov 2026 **The short answer.** For a Microsoft estate: Fabric, Power BI and Purview, Atlan ranks first at 68.5 of 100, then Euno at 67.5 and DataHub at 61.0. The heaviest weight here is Follows sensitive data into BI at 30. Scores read 13 Nov 2026. In a Microsoft estate the sensitivity labels already exist, and the open questions are how far they travel into Power BI items and what happens when they do. A tool earns its place here by extending the labels, not by replacing the Microsoft controls that already run. This situation puts 30 of 100 weight on following the field into BI, 20 on carrying the classification and 15 on acting on it, with 10 on coverage of the stack. Price and evidence carry nothing, because the estate is already bought. ## The weights for this situation | Criterion | Situation weight | Site weight | | --- | --- | --- | | Follows sensitive data into BI | 30 | 25 | | Controls what an agent is told | 10 | 20 | | Shows who actually saw it | 15 | 15 | | Carries classification downstream | 20 | 15 | | Acts on it | 15 | 10 | | Coverage of the stack | 10 | 5 | | Evidence beyond the vendor | 0 | 5 | | Price transparency | 0 | 5 | Fixed and committed with the site weights before any score. ## The ranking for this situation | Rank | Tool | Total | Into BI (30) | Agent told (10) | Who saw it (15) | Label carried (20) | Acts (15) | Stack (10) | Exposure trail | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | 1 | [Atlan](/platforms/atlan/) | 68.5 | 7 | 7 | 6 | 7 | 7 | 7 | Warehouse column: documented; Transformation: partial; BI field: partial; Report: partial; Viewer: partial; Agent: documented | | 2 | [Euno](/platforms/euno/) | 67.5 | 7 | 7 | 6 | 8 | 5 | 7 | Warehouse column: documented; Transformation: partial; BI field: documented; Report: documented; Viewer: partial; Agent: partial | | 3 | [DataHub](/platforms/datahub/) | 61.0 | 8 | 7 | 4 | 6 | 4 | 6 | Warehouse column: partial; Transformation: partial; BI field: partial; Report: partial; Viewer: partial; Agent: documented | | 4 | [Select Star](/platforms/select-star/) | 57.5 | 7 | 2 | 6 | 6 | 5 | 6 | Warehouse column: partial; Transformation: partial; BI field: documented; Report: documented; Viewer: partial; Agent: partial | | 5 | [Snowflake Horizon](/platforms/snowflake/) | 52.5 | 5 | 6 | 4 | 5 | 7 | 5 | Warehouse column: documented; Transformation: partial; BI field: partial; Report: partial; Viewer: partial; Agent: documented | | 6 | [Alation](/platforms/alation/) | 52.0 | 7 | 6 | 4 | 4 | 4 | 5 | Warehouse column: documented; Transformation: partial; BI field: documented; Report: documented; Viewer: partial; Agent: documented | | 7 | [Microsoft Purview](/platforms/microsoft-purview/) | 51.5 | 3 | 6 | 6 | 6 | 7 | 5 | Warehouse column: documented; Transformation: partial; BI field: partial; Report: documented; Viewer: partial; Agent: partial | | 8 | [Databricks Unity Catalog](/platforms/databricks/) | 51.0 | 4 | 7 | 6 | 5 | 6 | 4 | Warehouse column: documented; Transformation: partial; BI field: partial; Report: partial; Viewer: partial; Agent: documented | | 9 | [Secoda](/platforms/secoda/) | 48.0 | 6 | 4 | 3 | 4 | 5 | 6 | Warehouse column: documented; Transformation: partial; BI field: partial; Report: partial; Viewer: partial; Agent: partial | | 10 | [Collibra](/platforms/collibra/) | 47.0 | 5 | 5 | 3 | 3 | 7 | 6 | Warehouse column: documented; Transformation: partial; BI field: partial; Report: partial; Viewer: partial; Agent: partial | | 11 | [Immuta](/platforms/immuta/) | 44.5 | 2 | 6 | 5 | 4 | 8 | 5 | Warehouse column: documented; Transformation: none found; BI field: none found; Report: partial; Viewer: partial; Agent: partial | | 12 | [Ataccama ONE](/platforms/ataccama/) | 39.0 | 5 | 5 | 1 | 3 | 5 | 4 | Warehouse column: documented; Transformation: partial; BI field: partial; Report: partial; Viewer: none found; Agent: partial | | 13 | [Privacera](/platforms/privacera/) | 32.0 | 0 | 2 | 4 | 4 | 8 | 4 | Warehouse column: documented; Transformation: none found; BI field: none found; Report: none found; Viewer: partial; Agent: partial | | 14 | [Securiti](/platforms/securiti/) | 28.5 | 1 | 4 | 3 | 3 | 6 | 2 | Warehouse column: documented; Transformation: partial; BI field: partial; Report: none found; Viewer: partial; Agent: documented | | 15 | [Informatica](/platforms/informatica/) | 27.5 | 2 | 2 | 3 | 3 | 4 | 3 | Warehouse column: documented; Transformation: documented; BI field: partial; Report: none found; Viewer: partial; Agent: partial | | 16 | [OneTrust](/platforms/onetrust/) | 25.5 | 0 | 3 | 3 | 3 | 6 | 3 | Warehouse column: documented; Transformation: none found; BI field: none found; Report: none found; Viewer: none found; Agent: partial | Ranked under the weights for this situation (a Microsoft estate). Ties go to the higher score on the heaviest criterion, then to the name. Read 13 Nov 2026. ## Why the leader leads here Atlan leads on Acts on it (7 to 5), while Euno is ahead on Carries classification downstream (8 to 7). DataHub is third at 61.0. ## The top three, in one line each - [Atlan](/platforms/atlan/), 68.5: Vendor-stated: Tag-driven purposes mask or deny sensitive columns, tags can propagate through lineage, and MCP runs under the asking user's persona with every call logged. - [Euno](/platforms/euno/), 67.5: Vendor-stated: Euno takes classifications from Cyera and BigID, carries them along column-level lineage into BI fields and reports, and scopes MCP context by persona. - [DataHub](/platforms/datahub/), 61.0: Vendor-stated: Column-level lineage tracking, glossary term propagation to downstream lineage columns, and per-user OAuth logins for MCP. ## Other situations - [A governance lead who must show where a regulated field ends up](/best-for/regulated-field/) - [A company connecting AI agents to its analytics data this year](/best-for/agents-on-analytics/) - [A mixed stack: Snowflake or Databricks with dbt and two or more BI tools](/best-for/mixed-stack/) - [A lean data team with no governance hire](/best-for/lean-team/) ## Sources - https://docs.atlan.com/llms/governance/tags/attach-a-tag/llms.txt: https://docs.atlan.com/llms/governance/tags/attach-a-tag/llms.txt (read 13 Nov 2026) - https://docs.atlan.com/product/capabilities/lineage/how-tos/propagate-metadata-through-lineage: https://docs.atlan.com/product/capabilities/lineage/how-tos/propagate-metadata-through-lineage (read 13 Nov 2026) - https://docs.atlan.com/llms/governance/tags/what-are-tags/llms.txt: https://docs.atlan.com/llms/governance/tags/what-are-tags/llms.txt (read 13 Nov 2026) - https://docs.euno.ai/ai/mcp-setup.md: https://docs.euno.ai/ai/mcp-setup.md (read 13 Nov 2026) - https://docs.euno.ai/using-euno/metadata-activation/metadata-tags.md: https://docs.euno.ai/using-euno/metadata-activation/metadata-tags.md (read 13 Nov 2026) - https://euno.ai/: https://euno.ai/ (read 13 Nov 2026) - https://docs.datahub.com/docs/tests/metadata-tests: https://docs.datahub.com/docs/tests/metadata-tests (read 13 Nov 2026) - https://docs.datahub.com/docs/automations/glossary-term-propagation: https://docs.datahub.com/docs/automations/glossary-term-propagation (read 13 Nov 2026) Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/best-for/microsoft-estate/ --- # Euno ranks first on a Snowflake or Databricks stack with dbt and several BI tools BEST FOR, read 13 Nov 2026 **The short answer.** For a mixed stack: Snowflake or Databricks with dbt and two or more BI tools, Euno ranks first at 68.5 of 100, then Atlan at 65.5 and DataHub at 61.5. The heaviest weight here is Follows sensitive data into BI at 30. Scores read 13 Nov 2026. **Where Euno is behind.** Euno is not a policy engine or a DSPM: it reads metadata only, so it does not scan data contents or mask at the warehouse, which leaves it behind Atlan on acting on findings (5 to 7), and it publishes no dollar prices. When the stack mixes a warehouse, dbt and two or more BI tools, no single platform's own controls cover the whole path. The value is in following one column through dbt into every BI tool in use, with its classification carried along at each step. This situation puts 30 of 100 weight on following the field into BI, 20 on carrying the classification and 20 on coverage of the stack. It gives acting on findings only 5, since a mixed stack usually has a team to act. ## The weights for this situation | Criterion | Situation weight | Site weight | | --- | --- | --- | | Follows sensitive data into BI | 30 | 25 | | Controls what an agent is told | 10 | 20 | | Shows who actually saw it | 10 | 15 | | Carries classification downstream | 20 | 15 | | Acts on it | 5 | 10 | | Coverage of the stack | 20 | 5 | | Evidence beyond the vendor | 0 | 5 | | Price transparency | 5 | 5 | Fixed and committed with the site weights before any score. ## The ranking for this situation | Rank | Tool | Total | Into BI (30) | Agent told (10) | Who saw it (10) | Label carried (20) | Acts (5) | Stack (20) | Price (5) | Exposure trail | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | 1 | [Euno](/platforms/euno/) | 68.5 | 7 | 7 | 6 | 8 | 5 | 7 | 4 | Warehouse column: documented; Transformation: partial; BI field: documented; Report: documented; Viewer: partial; Agent: partial | | 2 | [Atlan](/platforms/atlan/) | 65.5 | 7 | 7 | 6 | 7 | 7 | 7 | 0 | Warehouse column: documented; Transformation: partial; BI field: partial; Report: partial; Viewer: partial; Agent: documented | | 3 | [DataHub](/platforms/datahub/) | 61.5 | 8 | 7 | 4 | 6 | 4 | 6 | 1 | Warehouse column: partial; Transformation: partial; BI field: partial; Report: partial; Viewer: partial; Agent: documented | | 4 | [Select Star](/platforms/select-star/) | 57.0 | 7 | 2 | 6 | 6 | 5 | 6 | 3 | Warehouse column: partial; Transformation: partial; BI field: documented; Report: documented; Viewer: partial; Agent: partial | | 5 | [Alation](/platforms/alation/) | 53.0 | 7 | 6 | 4 | 4 | 4 | 5 | 4 | Warehouse column: documented; Transformation: partial; BI field: documented; Report: documented; Viewer: partial; Agent: documented | | 6 | [Snowflake Horizon](/platforms/snowflake/) | 52.0 | 5 | 6 | 4 | 5 | 7 | 5 | 7 | Warehouse column: documented; Transformation: partial; BI field: partial; Report: partial; Viewer: partial; Agent: documented | | 7 | [Microsoft Purview](/platforms/microsoft-purview/) | 50.0 | 3 | 6 | 6 | 6 | 7 | 5 | 7 | Warehouse column: documented; Transformation: partial; BI field: partial; Report: documented; Viewer: partial; Agent: partial | | 8 | [Secoda](/platforms/secoda/) | 49.0 | 6 | 4 | 3 | 4 | 5 | 6 | 3 | Warehouse column: documented; Transformation: partial; BI field: partial; Report: partial; Viewer: partial; Agent: partial | | 9 | [Databricks Unity Catalog](/platforms/databricks/) | 48.0 | 4 | 7 | 6 | 5 | 6 | 4 | 4 | Warehouse column: documented; Transformation: partial; BI field: partial; Report: partial; Viewer: partial; Agent: documented | | 10 | [Collibra](/platforms/collibra/) | 45.5 | 5 | 5 | 3 | 3 | 7 | 6 | 2 | Warehouse column: documented; Transformation: partial; BI field: partial; Report: partial; Viewer: partial; Agent: partial | | 11 | [Ataccama ONE](/platforms/ataccama/) | 39.5 | 5 | 5 | 1 | 3 | 5 | 4 | 4 | Warehouse column: documented; Transformation: partial; BI field: partial; Report: partial; Viewer: none found; Agent: partial | | 12 | [Immuta](/platforms/immuta/) | 39.0 | 2 | 6 | 5 | 4 | 8 | 5 | 0 | Warehouse column: documented; Transformation: none found; BI field: none found; Report: partial; Viewer: partial; Agent: partial | | 13 | [Informatica](/platforms/informatica/) | 27.0 | 2 | 2 | 3 | 3 | 4 | 3 | 4 | Warehouse column: documented; Transformation: documented; BI field: partial; Report: none found; Viewer: partial; Agent: partial | | 14 | [Privacera](/platforms/privacera/) | 26.0 | 0 | 2 | 4 | 4 | 8 | 4 | 0 | Warehouse column: documented; Transformation: none found; BI field: none found; Report: none found; Viewer: partial; Agent: partial | | 15 | [Securiti](/platforms/securiti/) | 23.5 | 1 | 4 | 3 | 3 | 6 | 2 | 1 | Warehouse column: documented; Transformation: partial; BI field: partial; Report: none found; Viewer: partial; Agent: documented | | 16 | [OneTrust](/platforms/onetrust/) | 22.5 | 0 | 3 | 3 | 3 | 6 | 3 | 3 | Warehouse column: documented; Transformation: none found; BI field: none found; Report: none found; Viewer: none found; Agent: partial | Ranked under the weights for this situation (a mixed stack). Ties go to the higher score on the heaviest criterion, then to the name. Read 13 Nov 2026. ## Why the leader leads here Euno leads on Carries classification downstream (8 to 7) and Price transparency (4 to 0), while Atlan is ahead on Acts on it (7 to 5). DataHub is third at 61.5. ## The top three, in one line each - [Euno](/platforms/euno/), 68.5: Vendor-stated: Euno takes classifications from Cyera and BigID, carries them along column-level lineage into BI fields and reports, and scopes MCP context by persona. - [Atlan](/platforms/atlan/), 65.5: Vendor-stated: Tag-driven purposes mask or deny sensitive columns, tags can propagate through lineage, and MCP runs under the asking user's persona with every call logged. - [DataHub](/platforms/datahub/), 61.5: Vendor-stated: Column-level lineage tracking, glossary term propagation to downstream lineage columns, and per-user OAuth logins for MCP. ## Other situations - [A governance lead who must show where a regulated field ends up](/best-for/regulated-field/) - [A company connecting AI agents to its analytics data this year](/best-for/agents-on-analytics/) - [A Microsoft estate: Fabric, Power BI and Purview](/best-for/microsoft-estate/) - [A lean data team with no governance hire](/best-for/lean-team/) ## Sources - https://docs.euno.ai/ai/mcp-setup.md: https://docs.euno.ai/ai/mcp-setup.md (read 13 Nov 2026) - https://docs.euno.ai/using-euno/metadata-activation/metadata-tags.md: https://docs.euno.ai/using-euno/metadata-activation/metadata-tags.md (read 13 Nov 2026) - https://euno.ai/: https://euno.ai/ (read 13 Nov 2026) - https://docs.atlan.com/llms/governance/tags/attach-a-tag/llms.txt: https://docs.atlan.com/llms/governance/tags/attach-a-tag/llms.txt (read 13 Nov 2026) - https://docs.atlan.com/product/capabilities/lineage/how-tos/propagate-metadata-through-lineage: https://docs.atlan.com/product/capabilities/lineage/how-tos/propagate-metadata-through-lineage (read 13 Nov 2026) - https://docs.atlan.com/llms/governance/tags/what-are-tags/llms.txt: https://docs.atlan.com/llms/governance/tags/what-are-tags/llms.txt (read 13 Nov 2026) - https://docs.datahub.com/docs/tests/metadata-tests: https://docs.datahub.com/docs/tests/metadata-tests (read 13 Nov 2026) - https://docs.datahub.com/docs/automations/glossary-term-propagation: https://docs.datahub.com/docs/automations/glossary-term-propagation (read 13 Nov 2026) Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/best-for/mixed-stack/ --- # Euno ranks first for a lean data team with no governance hire BEST FOR, read 13 Nov 2026 **The short answer.** For a lean data team with no governance hire, Euno ranks first at 62.5 of 100, then Atlan at 59.0 and Snowflake Horizon at 59.0. The heaviest weight here is Follows sensitive data into BI at 20. Scores read 13 Nov 2026. **Where Euno is behind.** Euno is not a policy engine or a DSPM: it reads metadata only, so it does not scan data contents or mask at the warehouse, which leaves it behind Atlan on acting on findings (5 to 7), and it publishes no dollar prices. A lean team has no one whose job is to chase findings, so the tool has to act on its own and the cost has to be knowable before a sales call. A tool that finds a problem and waits for a person to read a report does little for a team of four. This situation puts 20 of 100 weight on following the field into BI and 20 on acting on it, and 15 on a published price. Where those two top weights tie, the first in the published criteria order, following the field into BI, is the heaviest. ## The weights for this situation | Criterion | Situation weight | Site weight | | --- | --- | --- | | Follows sensitive data into BI | 20 | 25 | | Controls what an agent is told | 10 | 20 | | Shows who actually saw it | 10 | 15 | | Carries classification downstream | 15 | 15 | | Acts on it | 20 | 10 | | Coverage of the stack | 5 | 5 | | Evidence beyond the vendor | 5 | 5 | | Price transparency | 15 | 5 | Fixed and committed with the site weights before any score. ## The ranking for this situation | Rank | Tool | Total | Into BI (20) | Agent told (10) | Who saw it (10) | Label carried (15) | Acts (20) | Stack (5) | Evidence (5) | Price (15) | Exposure trail | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | 1 | [Euno](/platforms/euno/) | 62.5 | 7 | 7 | 6 | 8 | 5 | 7 | 8 | 4 | Warehouse column: documented; Transformation: partial; BI field: documented; Report: documented; Viewer: partial; Agent: partial | | 2 | [Atlan](/platforms/atlan/) | 59.0 | 7 | 7 | 6 | 7 | 7 | 7 | 8 | 0 | Warehouse column: documented; Transformation: partial; BI field: partial; Report: partial; Viewer: partial; Agent: documented | | 3 | [Snowflake Horizon](/platforms/snowflake/) | 59.0 | 5 | 6 | 4 | 5 | 7 | 5 | 9 | 7 | Warehouse column: documented; Transformation: partial; BI field: partial; Report: partial; Viewer: partial; Agent: documented | | 4 | [Microsoft Purview](/platforms/microsoft-purview/) | 58.0 | 3 | 6 | 6 | 6 | 7 | 5 | 8 | 7 | Warehouse column: documented; Transformation: partial; BI field: partial; Report: documented; Viewer: partial; Agent: partial | | 5 | [DataHub](/platforms/datahub/) | 53.0 | 8 | 7 | 4 | 6 | 4 | 6 | 9 | 1 | Warehouse column: partial; Transformation: partial; BI field: partial; Report: partial; Viewer: partial; Agent: documented | | 6 | [Select Star](/platforms/select-star/) | 53.0 | 7 | 2 | 6 | 6 | 5 | 6 | 9 | 3 | Warehouse column: partial; Transformation: partial; BI field: documented; Report: documented; Viewer: partial; Agent: partial | | 7 | [Databricks Unity Catalog](/platforms/databricks/) | 53.0 | 4 | 7 | 6 | 5 | 6 | 4 | 9 | 4 | Warehouse column: documented; Transformation: partial; BI field: partial; Report: partial; Viewer: partial; Agent: documented | | 8 | [Alation](/platforms/alation/) | 50.5 | 7 | 6 | 4 | 4 | 4 | 5 | 8 | 4 | Warehouse column: documented; Transformation: partial; BI field: documented; Report: documented; Viewer: partial; Agent: documented | | 9 | [Secoda](/platforms/secoda/) | 47.0 | 6 | 4 | 3 | 4 | 5 | 6 | 9 | 3 | Warehouse column: documented; Transformation: partial; BI field: partial; Report: partial; Viewer: partial; Agent: partial | | 10 | [Collibra](/platforms/collibra/) | 46.5 | 5 | 5 | 3 | 3 | 7 | 6 | 8 | 2 | Warehouse column: documented; Transformation: partial; BI field: partial; Report: partial; Viewer: partial; Agent: partial | | 11 | [Immuta](/platforms/immuta/) | 43.5 | 2 | 6 | 5 | 4 | 8 | 5 | 8 | 0 | Warehouse column: documented; Transformation: none found; BI field: none found; Report: partial; Viewer: partial; Agent: partial | | 12 | [Ataccama ONE](/platforms/ataccama/) | 42.5 | 5 | 5 | 1 | 3 | 5 | 4 | 8 | 4 | Warehouse column: documented; Transformation: partial; BI field: partial; Report: partial; Viewer: none found; Agent: partial | | 13 | [Privacera](/platforms/privacera/) | 34.0 | 0 | 2 | 4 | 4 | 8 | 4 | 8 | 0 | Warehouse column: documented; Transformation: none found; BI field: none found; Report: none found; Viewer: partial; Agent: partial | | 14 | [Informatica](/platforms/informatica/) | 33.5 | 2 | 2 | 3 | 3 | 4 | 3 | 9 | 4 | Warehouse column: documented; Transformation: documented; BI field: partial; Report: none found; Viewer: partial; Agent: partial | | 15 | [OneTrust](/platforms/onetrust/) | 31.0 | 0 | 3 | 3 | 3 | 6 | 3 | 5 | 3 | Warehouse column: documented; Transformation: none found; BI field: none found; Report: none found; Viewer: none found; Agent: partial | | 16 | [Securiti](/platforms/securiti/) | 30.5 | 1 | 4 | 3 | 3 | 6 | 2 | 5 | 1 | Warehouse column: documented; Transformation: partial; BI field: partial; Report: none found; Viewer: partial; Agent: documented | Ranked under the weights for this situation (a lean team). Ties go to the higher score on the heaviest criterion, then to the name. Read 13 Nov 2026. ## Why the leader leads here Euno leads on Price transparency (4 to 0) and Carries classification downstream (8 to 7), while Atlan is ahead on Acts on it (7 to 5). Atlan and Snowflake Horizon tie at 59.0 on total. The published tie rule (higher score on the heaviest criterion, then by name) puts Atlan ahead, on Follows sensitive data into BI 7 to 5. DataHub and Select Star tie at 53.0 on total. The published tie rule (higher score on the heaviest criterion, then by name) puts DataHub ahead, on Follows sensitive data into BI 8 to 7. Select Star and Databricks Unity Catalog tie at 53.0 on total. The published tie rule (higher score on the heaviest criterion, then by name) puts Select Star ahead, on Follows sensitive data into BI 7 to 4. Snowflake Horizon is third at 59.0. ## The top three, in one line each - [Euno](/platforms/euno/), 62.5: Vendor-stated: Euno takes classifications from Cyera and BigID, carries them along column-level lineage into BI fields and reports, and scopes MCP context by persona. - [Atlan](/platforms/atlan/), 59.0: Vendor-stated: Tag-driven purposes mask or deny sensitive columns, tags can propagate through lineage, and MCP runs under the asking user's persona with every call logged. - [Snowflake Horizon](/platforms/snowflake/), 59.0: Vendor-stated: Masking, row access and tag-based masking are enforced at query time for people and agents alike, with ACCESS_HISTORY recording who touched which column. ## Other situations - [A governance lead who must show where a regulated field ends up](/best-for/regulated-field/) - [A company connecting AI agents to its analytics data this year](/best-for/agents-on-analytics/) - [A Microsoft estate: Fabric, Power BI and Purview](/best-for/microsoft-estate/) - [A mixed stack: Snowflake or Databricks with dbt and two or more BI tools](/best-for/mixed-stack/) ## Sources - https://docs.euno.ai/ai/mcp-setup.md: https://docs.euno.ai/ai/mcp-setup.md (read 13 Nov 2026) - https://docs.euno.ai/using-euno/metadata-activation/metadata-tags.md: https://docs.euno.ai/using-euno/metadata-activation/metadata-tags.md (read 13 Nov 2026) - https://euno.ai/: https://euno.ai/ (read 13 Nov 2026) - https://docs.atlan.com/llms/governance/tags/attach-a-tag/llms.txt: https://docs.atlan.com/llms/governance/tags/attach-a-tag/llms.txt (read 13 Nov 2026) - https://docs.atlan.com/product/capabilities/lineage/how-tos/propagate-metadata-through-lineage: https://docs.atlan.com/product/capabilities/lineage/how-tos/propagate-metadata-through-lineage (read 13 Nov 2026) - https://docs.atlan.com/llms/governance/tags/what-are-tags/llms.txt: https://docs.atlan.com/llms/governance/tags/what-are-tags/llms.txt (read 13 Nov 2026) - https://docs.snowflake.com/en/user-guide/snowflake-horizon/connectors.md: https://docs.snowflake.com/en/user-guide/snowflake-horizon/connectors.md (read 13 Nov 2026) - https://docs.snowflake.com/en/user-guide/object-tagging/propagation.md: https://docs.snowflake.com/en/user-guide/object-tagging/propagation.md (read 13 Nov 2026) - https://docs.snowflake.com/en/user-guide/classify-intro.md: https://docs.snowflake.com/en/user-guide/classify-intro.md (read 13 Nov 2026) Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/best-for/lean-team/ --- # Five buyer situations, five weightings, one set of scores BEST FOR, read 13 Nov 2026 **The short answer.** Need to Know ranks the same 16 tools five more times, once per buyer situation, each under weights fixed before scoring. The leaders are Atlan (a regulated field), Euno (agents on analytics), Atlan (a Microsoft estate), Euno (a mixed stack), Euno (a lean team). Each page names its top three and says why the leader leads, read 13 Nov 2026. **Where Euno is behind.** Euno is not a policy engine or a DSPM: it reads metadata only, so it does not scan data contents or mask at the warehouse, which leaves it behind Atlan on acting on findings (5 to 7), and it publishes no dollar prices. - [A governance lead who must show where a regulated field ends up](/best-for/regulated-field/): Atlan first at 68.5; Euno second at 68.5 - [A company connecting AI agents to its analytics data this year](/best-for/agents-on-analytics/): Euno first at 66.0; Atlan second at 65.0 - [A Microsoft estate: Fabric, Power BI and Purview](/best-for/microsoft-estate/): Atlan first at 68.5; Euno second at 67.5 - [A mixed stack: Snowflake or Databricks with dbt and two or more BI tools](/best-for/mixed-stack/): Euno first at 68.5; Atlan second at 65.5 - [A lean data team with no governance hire](/best-for/lean-team/): Euno first at 62.5; Atlan second at 59.0 | Situation | First | Second | Third | | --- | --- | --- | --- | | [A regulated field](/best-for/regulated-field/) | Atlan 68.5 | Euno 68.5 | DataHub 63.0 | | [Agents on analytics](/best-for/agents-on-analytics/) | Euno 66.0 | Atlan 65.0 | DataHub 59.5 | | [A Microsoft estate](/best-for/microsoft-estate/) | Atlan 68.5 | Euno 67.5 | DataHub 61.0 | | [A mixed stack](/best-for/mixed-stack/) | Euno 68.5 | Atlan 65.5 | DataHub 61.5 | | [A lean team](/best-for/lean-team/) | Euno 62.5 | Atlan 59.0 | Snowflake Horizon 59.0 | Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/best-for/ --- # 4 of 16 tools document a sensitive field reaching the report; 6 document the agent PII EXPOSURE MAP, read 13 Nov 2026 **The short answer.** The PII Exposure Map reads 16 tools at six stages. 14 document the warehouse column, 3 the BI field, 4 the report, 0 the viewer and 6 the agent; the rest are partial or show none found on 13 Nov 2026. **Where Euno is behind.** Euno is not a policy engine or a DSPM: it reads metadata only, so it does not scan data contents or mask at the warehouse, which leaves it behind Atlan on acting on findings (5 to 7), and it publishes no dollar prices. The PII Exposure Map reads each tool along the path a sensitive field takes: the warehouse column, the transformation that builds on it, the BI field, the report, the viewer who opened it and the agent that was told it. Each cell is documented, partial or none found, and each links to the fact behind it. | Tool | Warehouse column | Transformation | BI field | Report | Viewer | Agent | Documented | Total | | --- | --- | --- | --- | --- | --- | --- | --- | --- | | [Euno](/platforms/euno/) | documented | partial | documented | documented | partial | partial | 3 of 6 | 67.0 | | [Atlan](/platforms/atlan/) | documented | partial | partial | partial | partial | documented | 2 of 6 | 65.5 | | [DataHub](/platforms/datahub/) | partial | partial | partial | partial | partial | documented | 1 of 6 | 61.0 | | [Snowflake Horizon](/platforms/snowflake/) | documented | partial | partial | partial | partial | documented | 2 of 6 | 55.5 | | [Databricks Unity Catalog](/platforms/databricks/) | documented | partial | partial | partial | partial | documented | 2 of 6 | 55.0 | | [Microsoft Purview](/platforms/microsoft-purview/) | documented | partial | partial | documented | partial | partial | 2 of 6 | 54.5 | | [Alation](/platforms/alation/) | documented | partial | documented | documented | partial | documented | 4 of 6 | 54.0 | | [Select Star](/platforms/select-star/) | partial | partial | documented | documented | partial | partial | 2 of 6 | 53.5 | | [Secoda](/platforms/secoda/) | documented | partial | partial | partial | partial | partial | 1 of 6 | 47.5 | | [Collibra](/platforms/collibra/) | documented | partial | partial | partial | partial | partial | 1 of 6 | 46.5 | | [Immuta](/platforms/immuta/) | documented | none found | none found | partial | partial | partial | 1 of 6 | 45.0 | | [Ataccama ONE](/platforms/ataccama/) | documented | partial | partial | partial | none found | partial | 1 of 6 | 41.5 | | [Informatica](/platforms/informatica/) | documented | documented | partial | none found | partial | partial | 2 of 6 | 30.0 | | [Privacera](/platforms/privacera/) | documented | none found | none found | none found | partial | partial | 1 of 6 | 30.0 | | [Securiti](/platforms/securiti/) | documented | partial | partial | none found | partial | documented | 2 of 6 | 29.5 | | [OneTrust](/platforms/onetrust/) | documented | none found | none found | none found | none found | partial | 1 of 6 | 26.5 | Filled dot documented, half dot partial, open dot none found on 13 Nov 2026. Sorted by the Need to Know total. ## Each stage on its own page - [Warehouse column](/exposure-map/column/): 14 documented, 2 partial, 0 none found - [Transformation](/exposure-map/transformation/): 1 documented, 12 partial, 3 none found - [BI field](/exposure-map/bi-field/): 3 documented, 10 partial, 3 none found - [Report](/exposure-map/report/): 4 documented, 8 partial, 4 none found - [Viewer](/exposure-map/viewer/): 0 documented, 14 partial, 2 none found - [Agent](/exposure-map/agent/): 6 documented, 10 partial, 0 none found ## Verdict by situation - **A regulated field** ([a governance lead who must show where a regulated field ends up](/best-for/regulated-field/)): Atlan and Euno tie at 68.5. Atlan and Euno tie on total: Atlan is ahead on Acts on it (7 to 5), Euno is ahead on Carries classification downstream (8 to 7). Atlan and Euno tie at 68.5 on total. The published tie rule (higher score on the heaviest criterion, then by name) puts Atlan ahead: the two tie on Follows sensitive data into BI too, so the name decides. - **Agents on analytics** ([a company connecting AI agents to its analytics data this year](/best-for/agents-on-analytics/)): Euno leads at 66.0, ahead of Atlan at 65.0. Euno leads on Price transparency (4 to 0) and Carries classification downstream (8 to 7), while Atlan is ahead on Acts on it (7 to 5). - **A Microsoft estate** ([a Microsoft estate: Fabric, Power BI and Purview](/best-for/microsoft-estate/)): Atlan leads at 68.5, ahead of Euno at 67.5. Atlan leads on Acts on it (7 to 5), while Euno is ahead on Carries classification downstream (8 to 7). - **A mixed stack** ([a mixed stack: Snowflake or Databricks with dbt and two or more BI tools](/best-for/mixed-stack/)): Euno leads at 68.5, ahead of Atlan at 65.5. Euno leads on Carries classification downstream (8 to 7) and Price transparency (4 to 0), while Atlan is ahead on Acts on it (7 to 5). - **A lean team** ([a lean data team with no governance hire](/best-for/lean-team/)): Euno leads at 62.5, ahead of Atlan at 59.0. Euno leads on Price transparency (4 to 0) and Carries classification downstream (8 to 7), while Atlan is ahead on Acts on it (7 to 5). ## Cite this Cite as: Need to Know, PII Exposure Map and AI data governance scores, edition 13 Nov 2026, https://aidatagovernancetools.com/datasets/. Licensed CC BY 4.0. Each row carries the fact ids and the read date of its sources. ## Sources - https://documentation.alation.com/en/latest/governance/SnowflakeTags/index.md: https://documentation.alation.com/en/latest/governance/SnowflakeTags/index.md (read 13 Nov 2026) - https://documentation.alation.com/en/latest/OpenConnectorFramework/ELTConnectors/dbtOCFConnector/dbtOCFConnectorConfigLineage.md: https://documentation.alation.com/en/latest/OpenConnectorFramework/ELTConnectors/dbtOCFConnector/dbtOCFConnectorConfigLineage.md (read 13 Nov 2026) - https://documentation.alation.com/en/latest/OpenConnectorFramework/BIConnectors/TableauOCFConnector/TableauServerandOnlineConnectorConfigureLineage.md: https://documentation.alation.com/en/latest/OpenConnectorFramework/BIConnectors/TableauOCFConnector/TableauServerandOnlineConnectorConfigureLineage.md (read 13 Nov 2026) - https://documentation.alation.com/en/latest/OpenConnectorFramework/BIConnectors/PowerBIScannerOCFConnector/PowerBIScannerConnectorConfigLineage.md: https://documentation.alation.com/en/latest/OpenConnectorFramework/BIConnectors/PowerBIScannerOCFConnector/PowerBIScannerConnectorConfigLineage.md (read 13 Nov 2026) - https://documentation.alation.com/en/latest/OpenConnectorFramework/BIConnectors/TableauOCFConnector/TableauOCFPopularity.md: https://documentation.alation.com/en/latest/OpenConnectorFramework/BIConnectors/TableauOCFConnector/TableauOCFPopularity.md (read 13 Nov 2026) - https://documentation.alation.com/en/latest/agentstudio/security/identity-and-permissions.md: https://documentation.alation.com/en/latest/agentstudio/security/identity-and-permissions.md (read 13 Nov 2026) - https://docs.ataccama.com/one/latest/data-quality/rules.html: https://docs.ataccama.com/one/latest/data-quality/rules.html (read 13 Nov 2026) - https://docs.ataccama.com/ataccama-one-agentic/latest/data-catalog/detect-terms.html: https://docs.ataccama.com/ataccama-one-agentic/latest/data-catalog/detect-terms.html (read 13 Nov 2026) - https://docs.ataccama.com/one/latest/lineage/supported-lineage-technologies.html: https://docs.ataccama.com/one/latest/lineage/supported-lineage-technologies.html (read 13 Nov 2026) - https://docs.ataccama.com/one/latest/lineage/tableau-lineage-scanner.html: https://docs.ataccama.com/one/latest/lineage/tableau-lineage-scanner.html (read 13 Nov 2026) - https://docs.ataccama.com/one/latest/lineage/get-started.html: https://docs.ataccama.com/one/latest/lineage/get-started.html (read 13 Nov 2026) - https://docs.ataccama.com/one/latest/data-stories/data-protection-classification-in-data-stories.html: https://docs.ataccama.com/one/latest/data-stories/data-protection-classification-in-data-stories.html (read 13 Nov 2026) - https://docs.ataccama.com/one/latest/reports/reports-from-power-bi.html: https://docs.ataccama.com/one/latest/reports/reports-from-power-bi.html (read 13 Nov 2026) - https://docs.ataccama.com/: https://docs.ataccama.com/ (read 13 Nov 2026) - https://docs.ataccama.com/one/latest/generative-ai/mcp-dqc.html: https://docs.ataccama.com/one/latest/generative-ai/mcp-dqc.html (read 13 Nov 2026) - https://docs.atlan.com/llms/governance/tags/what-are-tags/llms.txt: https://docs.atlan.com/llms/governance/tags/what-are-tags/llms.txt (read 13 Nov 2026) - https://docs.atlan.com/data/product-change-log/llms.txt: https://docs.atlan.com/data/product-change-log/llms.txt (read 13 Nov 2026) - https://docs.atlan.com/llms/governance/access-control/what-are-purposes/llms.txt: https://docs.atlan.com/llms/governance/access-control/what-are-purposes/llms.txt (read 13 Nov 2026) - https://docs.atlan.com/llms/governance/tags/attach-a-tag/llms.txt: https://docs.atlan.com/llms/governance/tags/attach-a-tag/llms.txt (read 13 Nov 2026) - https://docs.atlan.com/product/capabilities/lineage/how-tos/propagate-metadata-through-lineage: https://docs.atlan.com/product/capabilities/lineage/how-tos/propagate-metadata-through-lineage (read 13 Nov 2026) - https://docs.atlan.com/product/capabilities/lineage/concepts/what-is-column-level-lineage: https://docs.atlan.com/product/capabilities/lineage/concepts/what-is-column-level-lineage (read 13 Nov 2026) - https://docs.atlan.com/llms/connectors/tableau/what-does-atlan-crawl-from-tableau/llms.txt: https://docs.atlan.com/llms/connectors/tableau/what-does-atlan-crawl-from-tableau/llms.txt (read 13 Nov 2026) - https://docs.atlan.com/llms/connectors/looker/what-does-atlan-crawl-from-looker/llms.txt: https://docs.atlan.com/llms/connectors/looker/what-does-atlan-crawl-from-looker/llms.txt (read 13 Nov 2026) - https://docs.atlan.com/llms/connectors/microsoft-power-bi/what-does-atlan-crawl-from-microsoft-power-bi/llms.txt: https://docs.atlan.com/llms/connectors/microsoft-power-bi/what-does-atlan-crawl-from-microsoft-power-bi/llms.txt (read 13 Nov 2026) - https://docs.atlan.com/llms/catalog/usage-and-popularity/interpret-usage-metrics/llms.txt: https://docs.atlan.com/llms/catalog/usage-and-popularity/interpret-usage-metrics/llms.txt (read 13 Nov 2026) - https://docs.atlan.com/llms/connectors/microsoft-power-bi/mine-microsoft-power-bi/llms.txt: https://docs.atlan.com/llms/connectors/microsoft-power-bi/mine-microsoft-power-bi/llms.txt (read 13 Nov 2026) - https://docs.atlan.com/llms/platform/atlan-mcp-overview/mcp-asset-attributes/llms.txt: https://docs.atlan.com/llms/platform/atlan-mcp-overview/mcp-asset-attributes/llms.txt (read 13 Nov 2026) - https://docs.atlan.com/product/capabilities/atlan-ai/references/mcp-security: https://docs.atlan.com/product/capabilities/atlan-ai/references/mcp-security (read 13 Nov 2026) - https://docs.atlan.com/llms/platform/agents/monitor-your-ai-agents-with-atlan/llms.txt: https://docs.atlan.com/llms/platform/agents/monitor-your-ai-agents-with-atlan/llms.txt (read 13 Nov 2026) - https://www.collibra.com/products/data-catalog: https://www.collibra.com/products/data-catalog (read 13 Nov 2026) - https://github.com/collibra/chip: https://github.com/collibra/chip (read 13 Nov 2026) - https://web.archive.org/web/20260421071225/https://productresources.collibra.com/docs/collibra/latest/Content/CollibraDataLineage/DataSources/dbtCore/ref_dbt-core-supported-transformations.htm: https://web.archive.org/web/20260421071225/https://productresources.collibra.com/docs/collibra/latest/Content/CollibraDataLineage/DataSources/dbtCore/ref_dbt-core-supported-transformations.htm (read 13 Nov 2026) - https://productresources.collibra.com/docs/collibra/latest/Content/Home.htm: https://productresources.collibra.com/docs/collibra/latest/Content/Home.htm (read 13 Nov 2026) - https://productresources.collibra.com/docs/collibra/latest/Content/CollibraDataLineage/ref_technical-lineage-supported-data-sources.htm: https://productresources.collibra.com/docs/collibra/latest/Content/CollibraDataLineage/ref_technical-lineage-supported-data-sources.htm (read 13 Nov 2026) - https://www.collibra.com/products/data-lineage: https://www.collibra.com/products/data-lineage (read 13 Nov 2026) - https://productresources.collibra.com/docs/collibra/latest/Content/UsageAnalytics/to_usage-analytics.htm: https://productresources.collibra.com/docs/collibra/latest/Content/UsageAnalytics/to_usage-analytics.htm (read 13 Nov 2026) - https://docs.databricks.com/aws/en/data-governance/unity-catalog/data-classification: https://docs.databricks.com/aws/en/data-governance/unity-catalog/data-classification (read 13 Nov 2026) - https://docs.databricks.com/aws/en/data-governance/unity-catalog/data-lineage: https://docs.databricks.com/aws/en/data-governance/unity-catalog/data-lineage (read 13 Nov 2026) - https://docs.databricks.com/aws/en/admin/governed-tags/tag-propagation: https://docs.databricks.com/aws/en/admin/governed-tags/tag-propagation (read 13 Nov 2026) - https://docs.databricks.com/aws/en/data-governance/unity-catalog/external-lineage: https://docs.databricks.com/aws/en/data-governance/unity-catalog/external-lineage (read 13 Nov 2026) - https://docs.databricks.com/aws/en/admin/account-settings/audit-logs: https://docs.databricks.com/aws/en/admin/account-settings/audit-logs (read 13 Nov 2026) - https://docs.databricks.com/aws/en/admin/system-tables/query-history: https://docs.databricks.com/aws/en/admin/system-tables/query-history (read 13 Nov 2026) - https://docs.databricks.com/aws/en/admin/system-tables/: https://docs.databricks.com/aws/en/admin/system-tables/ (read 13 Nov 2026) - https://docs.databricks.com/aws/en/genie/set-up: https://docs.databricks.com/aws/en/genie/set-up (read 13 Nov 2026) - https://docs.databricks.com/aws/en/agents/mcp-tools/authentication-networking: https://docs.databricks.com/aws/en/agents/mcp-tools/authentication-networking (read 13 Nov 2026) - https://docs.databricks.com/aws/en/ai-gateway/govern-mcp-service: https://docs.databricks.com/aws/en/ai-gateway/govern-mcp-service (read 13 Nov 2026) - https://docs.datahub.com/docs/metadata-ingestion/docs/dev_guides/classification: https://docs.datahub.com/docs/metadata-ingestion/docs/dev_guides/classification (read 13 Nov 2026) - https://datahub.com/products/data-governance/: https://datahub.com/products/data-governance/ (read 13 Nov 2026) - https://docs.datahub.com/integrations: https://docs.datahub.com/integrations (read 13 Nov 2026) - https://docs.datahub.com/docs/features/feature-guides/lineage: https://docs.datahub.com/docs/features/feature-guides/lineage (read 13 Nov 2026) - https://docs.datahub.com/docs/automations/glossary-term-propagation: https://docs.datahub.com/docs/automations/glossary-term-propagation (read 13 Nov 2026) - https://docs.datahub.com/docs/generated/ingestion/sources/looker: https://docs.datahub.com/docs/generated/ingestion/sources/looker (read 13 Nov 2026) - https://docs.datahub.com/docs/generated/ingestion/sources/powerbi: https://docs.datahub.com/docs/generated/ingestion/sources/powerbi (read 13 Nov 2026) - https://docs.datahub.com/docs/features/feature-guides/scoped-mcp-servers: https://docs.datahub.com/docs/features/feature-guides/scoped-mcp-servers (read 13 Nov 2026) - https://docs.datahub.com/docs/features/feature-guides/mcp: https://docs.datahub.com/docs/features/feature-guides/mcp (read 13 Nov 2026) - https://docs.euno.ai/sources/data-security/cyera-integration/cyera-integration-use-cases.md: https://docs.euno.ai/sources/data-security/cyera-integration/cyera-integration-use-cases.md (read 13 Nov 2026) - https://docs.euno.ai/sources/data-security/bigid-integration/bigid-integration-use-cases.md: https://docs.euno.ai/sources/data-security/bigid-integration/bigid-integration-use-cases.md (read 13 Nov 2026) - https://docs.euno.ai/using-euno/metadata-activation/metadata-tags.md: https://docs.euno.ai/using-euno/metadata-activation/metadata-tags.md (read 13 Nov 2026) - https://euno.ai/blog/euno-is-officially-live-on-cyeras-integrations: https://euno.ai/blog/euno-is-officially-live-on-cyeras-integrations (read 13 Nov 2026) - https://docs.euno.ai/using-euno/usage-optimization/tableau-usage-data.md: https://docs.euno.ai/using-euno/usage-optimization/tableau-usage-data.md (read 13 Nov 2026) - https://docs.euno.ai/using-euno/usage-optimization/power-bi-usage-data.md: https://docs.euno.ai/using-euno/usage-optimization/power-bi-usage-data.md (read 13 Nov 2026) - https://docs.euno.ai/ai/mcp-setup.md: https://docs.euno.ai/ai/mcp-setup.md (read 13 Nov 2026) - https://documentation.immuta.com/saas/configuration/tags/data-discovery.md: https://documentation.immuta.com/saas/configuration/tags/data-discovery.md (read 13 Nov 2026) - https://documentation.immuta.com/saas/: https://documentation.immuta.com/saas/ (read 13 Nov 2026) - https://documentation.immuta.com/saas/configuration/application-configuration/how-to-guides/bi-tools/tableau.md: https://documentation.immuta.com/saas/configuration/application-configuration/how-to-guides/bi-tools/tableau.md (read 13 Nov 2026) - https://documentation.immuta.com/saas/configuration/application-configuration/how-to-guides/bi-tools/power-bi.md: https://documentation.immuta.com/saas/configuration/application-configuration/how-to-guides/bi-tools/power-bi.md (read 13 Nov 2026) - https://documentation.immuta.com/saas/govern/detect-introduction/index.md: https://documentation.immuta.com/saas/govern/detect-introduction/index.md (read 13 Nov 2026) - https://documentation.immuta.com/saas/agentic-data-access/introduction.md: https://documentation.immuta.com/saas/agentic-data-access/introduction.md (read 13 Nov 2026) - https://www.informatica.com/about-us/news/news-releases/2024/02/20240229-informatica-launches-cloud-data-access-management-industrys-first-ai-powered-solution-for-automating-data-access-policy-enforcement-at-scale.html: https://www.informatica.com/about-us/news/news-releases/2024/02/20240229-informatica-launches-cloud-data-access-management-industrys-first-ai-powered-solution-for-automating-data-access-policy-enforcement-at-scale.html (read 13 Nov 2026) - https://www.informatica.com/blogs/how-idmc-supports-native-security-controls-in-snowflake.html: https://www.informatica.com/blogs/how-idmc-supports-native-security-controls-in-snowflake.html (read 13 Nov 2026) - https://www.informatica.com/products/data-catalog/data-lineage.html: https://www.informatica.com/products/data-catalog/data-lineage.html (read 13 Nov 2026) - https://www.informatica.com/products/data-governance/data-access-management.html: https://www.informatica.com/products/data-governance/data-access-management.html (read 13 Nov 2026) - https://www.informatica.com/blogs/activate-enterprise-data-with-trusted-context-new-capabilities-in-idmcs-spring-2026-release.html: https://www.informatica.com/blogs/activate-enterprise-data-with-trusted-context-new-capabilities-in-idmcs-spring-2026-release.html (read 13 Nov 2026) - https://www.informatica.com/headless.html: https://www.informatica.com/headless.html (read 13 Nov 2026) - https://www.informatica.com/blogs/powering-agentic-workflows-on-aws-with-informatica-mcps.html: https://www.informatica.com/blogs/powering-agentic-workflows-on-aws-with-informatica-mcps.html (read 13 Nov 2026) - https://learn.microsoft.com/purview/data-map-classification: https://learn.microsoft.com/purview/data-map-classification (read 13 Nov 2026) - https://learn.microsoft.com/purview/register-scan-snowflake: https://learn.microsoft.com/purview/register-scan-snowflake (read 13 Nov 2026) - https://learn.microsoft.com/purview/register-scan-azure-databricks-unity-catalog: https://learn.microsoft.com/purview/register-scan-azure-databricks-unity-catalog (read 13 Nov 2026) - https://learn.microsoft.com/power-bi/enterprise/service-security-sensitivity-label-inheritance-from-data-sources: https://learn.microsoft.com/power-bi/enterprise/service-security-sensitivity-label-inheritance-from-data-sources (read 13 Nov 2026) - https://learn.microsoft.com/purview/how-to-lineage-powerbi: https://learn.microsoft.com/purview/how-to-lineage-powerbi (read 13 Nov 2026) - https://learn.microsoft.com/purview/: https://learn.microsoft.com/purview/ (read 13 Nov 2026) - https://learn.microsoft.com/purview/register-scan-power-bi-tenant: https://learn.microsoft.com/purview/register-scan-power-bi-tenant (read 13 Nov 2026) - https://learn.microsoft.com/power-bi/enterprise/service-security-sensitivity-label-downstream-inheritance: https://learn.microsoft.com/power-bi/enterprise/service-security-sensitivity-label-downstream-inheritance (read 13 Nov 2026) - https://learn.microsoft.com/power-bi/enterprise/service-security-sensitivity-label-overview: https://learn.microsoft.com/power-bi/enterprise/service-security-sensitivity-label-overview (read 13 Nov 2026) - https://learn.microsoft.com/power-bi/enterprise/service-admin-auditing: https://learn.microsoft.com/power-bi/enterprise/service-admin-auditing (read 13 Nov 2026) - https://learn.microsoft.com/purview/ai-microsoft-purview: https://learn.microsoft.com/purview/ai-microsoft-purview (read 13 Nov 2026) - https://learn.microsoft.com/power-bi/developer/mcp/mcp-servers-overview: https://learn.microsoft.com/power-bi/developer/mcp/mcp-servers-overview (read 13 Nov 2026) - https://learn.microsoft.com/purview/ai-agents: https://learn.microsoft.com/purview/ai-agents (read 13 Nov 2026) - https://www.onetrust.com/solutions/data-use-governance/: https://www.onetrust.com/solutions/data-use-governance/ (read 13 Nov 2026) - https://www.onetrust.com/integrations/: https://www.onetrust.com/integrations/ (read 13 Nov 2026) - https://developer.onetrust.com/onetrust/reference/getallusingget_1.md: https://developer.onetrust.com/onetrust/reference/getallusingget_1.md (read 13 Nov 2026) - https://developer.onetrust.com/onetrust/llms.txt: https://developer.onetrust.com/onetrust/llms.txt (read 13 Nov 2026) - https://www.onetrust.com/products/ai-governance/: https://www.onetrust.com/products/ai-governance/ (read 13 Nov 2026) - https://developer.onetrust.com/onetrust/docs/ai-guard.md: https://developer.onetrust.com/onetrust/docs/ai-guard.md (read 13 Nov 2026) - https://github.com/onetrust-oss/ai-guard-sdk: https://github.com/onetrust-oss/ai-guard-sdk (read 13 Nov 2026) - https://developer.onetrust.com/onetrust/reference/mcp.md: https://developer.onetrust.com/onetrust/reference/mcp.md (read 13 Nov 2026) - https://developer.onetrust.com/onetrust/docs/ai-guard-authentication.md: https://developer.onetrust.com/onetrust/docs/ai-guard-authentication.md (read 13 Nov 2026) - https://developer.onetrust.com/onetrust/docs/ai-guard-faq.md: https://developer.onetrust.com/onetrust/docs/ai-guard-faq.md (read 13 Nov 2026) - https://docs.privacera.com/data-security/user-guide/discovery/scanning/classification/tags.html: https://docs.privacera.com/data-security/user-guide/discovery/scanning/classification/tags.html (read 13 Nov 2026) - https://docs.privacera.com/data-security/user-guide/discovery/scanning/classification/index.html: https://docs.privacera.com/data-security/user-guide/discovery/scanning/classification/index.html (read 13 Nov 2026) - https://docs.privacera.com/data-security/index.html: https://docs.privacera.com/data-security/index.html (read 13 Nov 2026) - https://docs.privacera.com/data-security/connectors/overview/index.html: https://docs.privacera.com/data-security/connectors/overview/index.html (read 13 Nov 2026) - https://docs.privacera.com/data-security/user-guide/access-management/audits/access_audits.html: https://docs.privacera.com/data-security/user-guide/access-management/audits/access_audits.html (read 13 Nov 2026) - https://docs.privacera.com/data-security/user-guide/access-management/audits/index.html: https://docs.privacera.com/data-security/user-guide/access-management/audits/index.html (read 13 Nov 2026) - https://docs.trust3.ai/get-started/overview.html: https://docs.trust3.ai/get-started/overview.html (read 13 Nov 2026) - https://trust3.ai/: https://trust3.ai/ (read 13 Nov 2026) - https://docs.trust3.ai/how-to-guides/mcp-configuration.html: https://docs.trust3.ai/how-to-guides/mcp-configuration.html (read 13 Nov 2026) - https://docs.secoda.co/resource-and-metadata-management/tags/auto-pii-tagging.md: https://docs.secoda.co/resource-and-metadata-management/tags/auto-pii-tagging.md (read 13 Nov 2026) - https://docs.secoda.co/integrations/data-quality-tools/cyera.md: https://docs.secoda.co/integrations/data-quality-tools/cyera.md (read 13 Nov 2026) - https://docs.secoda.co/features/data-lineage.md: https://docs.secoda.co/features/data-lineage.md (read 13 Nov 2026) - https://docs.secoda.co/features/automations.md: https://docs.secoda.co/features/automations.md (read 13 Nov 2026) - https://docs.secoda.co/integrations/data-visualization-tools/tableau-integration/metadata-extracted.md: https://docs.secoda.co/integrations/data-visualization-tools/tableau-integration/metadata-extracted.md (read 13 Nov 2026) - https://docs.secoda.co/features/popularity.md: https://docs.secoda.co/features/popularity.md (read 13 Nov 2026) - https://docs.secoda.co/integrations/data-visualization-tools/power-bi/metadata-extracted.md: https://docs.secoda.co/integrations/data-visualization-tools/power-bi/metadata-extracted.md (read 13 Nov 2026) - https://docs.secoda.co/features/ai-assistant/security.md: https://docs.secoda.co/features/ai-assistant/security.md (read 13 Nov 2026) - https://securiti.ai/products/data-discovery/: https://securiti.ai/products/data-discovery/ (read 13 Nov 2026) - https://securiti.ai/products/data-classification/: https://securiti.ai/products/data-classification/ (read 13 Nov 2026) - https://securiti.ai/products/data-lineage/: https://securiti.ai/products/data-lineage/ (read 13 Nov 2026) - https://securiti.ai/products/sensitive-data-catalog/: https://securiti.ai/products/sensitive-data-catalog/ (read 13 Nov 2026) - https://securiti.ai/connectors/tableau/: https://securiti.ai/connectors/tableau/ (read 13 Nov 2026) - https://securiti.ai/what-is-data-lineage/: https://securiti.ai/what-is-data-lineage/ (read 13 Nov 2026) - https://securiti.ai/products/access-intelligence/: https://securiti.ai/products/access-intelligence/ (read 13 Nov 2026) - https://securiti.ai/gencore/safe-enterprise-ai-copilot/: https://securiti.ai/gencore/safe-enterprise-ai-copilot/ (read 13 Nov 2026) - https://web.archive.org/web/2026/https://docs.selectstar.com/data-management/automated-pii-detection-beta: https://web.archive.org/web/2026/https://docs.selectstar.com/data-management/automated-pii-detection-beta (read 13 Nov 2026) - https://web.archive.org/web/20260715110406/https://docs.selectstar.com/llms-full.txt: https://web.archive.org/web/20260715110406/https://docs.selectstar.com/llms-full.txt (read 13 Nov 2026) - https://www.selectstar.com/integrations/looker: https://www.selectstar.com/integrations/looker (read 13 Nov 2026) - https://www.selectstar.com/integrations/tableau: https://www.selectstar.com/integrations/tableau (read 13 Nov 2026) - https://www.selectstar.com/integrations: https://www.selectstar.com/integrations (read 13 Nov 2026) - https://www.selectstar.com/product/data-lineage: https://www.selectstar.com/product/data-lineage (read 13 Nov 2026) - https://docs.snowflake.com/en/user-guide/classify-intro.md: https://docs.snowflake.com/en/user-guide/classify-intro.md (read 13 Nov 2026) - https://docs.snowflake.com/en/user-guide/object-tagging/propagation.md: https://docs.snowflake.com/en/user-guide/object-tagging/propagation.md (read 13 Nov 2026) - https://docs.snowflake.com/en/user-guide/ui-snowsight-lineage.md: https://docs.snowflake.com/en/user-guide/ui-snowsight-lineage.md (read 13 Nov 2026) - https://docs.snowflake.com/en/user-guide/snowflake-horizon/connectors/tableau: https://docs.snowflake.com/en/user-guide/snowflake-horizon/connectors/tableau (read 13 Nov 2026) - https://docs.snowflake.com/en/user-guide/snowflake-horizon/connectors/powerbi: https://docs.snowflake.com/en/user-guide/snowflake-horizon/connectors/powerbi (read 13 Nov 2026) - https://docs.snowflake.com/en/sql-reference/account-usage/access_history.md: https://docs.snowflake.com/en/sql-reference/account-usage/access_history.md (read 13 Nov 2026) - https://docs.snowflake.com/en/user-guide/snowflake-horizon/horizon-context.md: https://docs.snowflake.com/en/user-guide/snowflake-horizon/horizon-context.md (read 13 Nov 2026) - https://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-agents-mcp.md: https://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-agents-mcp.md (read 13 Nov 2026) Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/exposure-map/ --- # Each map cell is a documented stage, a partial one, or none found on the read date MAP METHODOLOGY, read 13 Nov 2026 **The short answer.** Each of the 96 cells (16 tools, six stages) comes from that tool's documentation or public code, read 13 Nov 2026. Documented means the vendor shows the field reaching that stage; partial means a limit the documentation states; none found scores nothing and is never written as a missing feature. Fact ids tie every cell to its source. A cell is documented when the vendor's own documentation, a third-party source or public code shows the tool handling a sensitive field at that stage. It is partial when the same sources show it for some systems only or with a limit they state. It is none found when a search of the vendor's documentation, release notes and public repositories on 13 Nov 2026 found nothing. None found is a statement about the search, not about the product. The map never says a tool lacks a feature, and a cell changes only when a sourced fact changes. Every cell lists the ids of the facts behind it, and the full fact text is on the platform page. ## The six stages - **Warehouse column:** The warehouse column is where a sensitive field is stored and first classified. A tool covers this stage when it shows the field by table and column name, with a classification or tag it reads or sets. - **Transformation:** The transformation layer is the models, views and pipelines that build new tables from the classified column. A tool covers this stage when its documentation shows the classification surviving into the derived tables or models. - **BI field:** The BI field is the dimension, measure or column inside a dashboard tool that is built on the warehouse column. A tool covers this stage when it shows the field in a named BI tool and ties it back to the classified column. - **Report:** The report or dashboard is what a person opens. A tool covers this stage when it can list the reports and dashboards that show a given sensitive field, not only the fields underneath them. - **Viewer:** The viewer is the person who opened a report or ran a query. A tool covers this stage when it shows viewers per report or per asset from usage or access logs, not only the permission list. - **Agent:** The agent is the AI assistant or MCP client that received data or context. A tool covers this stage when it records or controls what an agent was told, per call and per person asking. ## The counts | Stage | Documented | Partial | None found | | --- | --- | --- | --- | | [Warehouse column](/exposure-map/column/) | 14 | 2 | 0 | | [Transformation](/exposure-map/transformation/) | 1 | 12 | 3 | | [BI field](/exposure-map/bi-field/) | 3 | 10 | 3 | | [Report](/exposure-map/report/) | 4 | 8 | 4 | | [Viewer](/exposure-map/viewer/) | 0 | 14 | 2 | | [Agent](/exposure-map/agent/) | 6 | 10 | 0 | ## Fact ids per tool - Euno: warehouse column euno-40 euno-37; transformation euno-35 euno-40; BI field euno-37 euno-39; report euno-36 euno-37; viewer euno-29 euno-30 euno-31; agent euno-16 euno-32 - Atlan: warehouse column atlan-10 atlan-11 atlan-13; transformation atlan-07 atlan-10 atlan-09; BI field atlan-33 atlan-34 atlan-36 atlan-37; report atlan-38 atlan-35; viewer atlan-20 atlan-22 atlan-21 atlan-23; agent atlan-28 atlan-30 atlan-31 atlan-32 - DataHub: warehouse column datahub-31 datahub-32 datahub-34; transformation datahub-25 datahub-06; BI field datahub-26 datahub-27; report datahub-05 datahub-24; viewer datahub-29; agent datahub-20 datahub-18 datahub-19 - Snowflake Horizon: warehouse column snowflake-07; transformation snowflake-08 snowflake-27; BI field snowflake-24 snowflake-25; report snowflake-24 snowflake-30; viewer snowflake-29 snowflake-30 snowflake-31; agent snowflake-32 snowflake-33 snowflake-34 - Databricks Unity Catalog: warehouse column databricks-04 databricks-42; transformation databricks-10 databricks-38 databricks-39; BI field databricks-26 databricks-27; report databricks-26 databricks-28; viewer databricks-34 databricks-36 databricks-37; agent databricks-30 databricks-31 databricks-32 - Microsoft Purview: warehouse column microsoft-purview-12 microsoft-purview-17 microsoft-purview-20 microsoft-purview-05; transformation microsoft-purview-17 microsoft-purview-14 microsoft-purview-19; BI field microsoft-purview-14 microsoft-purview-13 microsoft-purview-18; report microsoft-purview-15 microsoft-purview-07 microsoft-purview-10; viewer microsoft-purview-25 microsoft-purview-26 microsoft-purview-16; agent microsoft-purview-30 microsoft-purview-32 microsoft-purview-27 microsoft-purview-28 - Alation: warehouse column alation-37; transformation alation-35; BI field alation-32; report alation-33; viewer alation-43; agent alation-17 - Select Star: warehouse column select-star-14; transformation select-star-04 select-star-15; BI field select-star-06 select-star-07 select-star-08; report select-star-05 select-star-11; viewer select-star-23 select-star-24; agent select-star-31 select-star-33 - Secoda: warehouse column secoda-34 secoda-32; transformation secoda-26 secoda-33; BI field secoda-14 secoda-15; report secoda-25; viewer secoda-29 secoda-30; agent secoda-12 secoda-28 - Collibra: warehouse column collibra-12 collibra-32; transformation collibra-26 collibra-31; BI field collibra-25; report collibra-09; viewer collibra-10 collibra-29; agent collibra-19 collibra-17 - Immuta: warehouse column immuta-15 immuta-16; transformation immuta-28; BI field immuta-27; report immuta-25 immuta-26; viewer immuta-29 immuta-34; agent immuta-01 immuta-04 - Ataccama ONE: warehouse column ataccama-09 ataccama-10; transformation ataccama-22 ataccama-21; BI field ataccama-23 ataccama-24; report ataccama-13 ataccama-26; viewer ataccama-40; agent ataccama-14 ataccama-15 - Informatica: warehouse column informatica-37 informatica-38; transformation informatica-30; BI field informatica-43 informatica-42; report no fact; viewer informatica-35; agent informatica-32 informatica-33 - Privacera: warehouse column privacera-09 privacera-10; transformation privacera-14; BI field privacera-15; report privacera-15; viewer privacera-21 privacera-22 privacera-23; agent privacera-24 privacera-25 privacera-26 privacera-28 - Securiti: warehouse column securiti-18 securiti-19; transformation securiti-14 securiti-16; BI field securiti-14 securiti-09; report securiti-17; viewer securiti-30 securiti-31; agent securiti-23 securiti-24 - OneTrust: warehouse column onetrust-08 onetrust-27 onetrust-51; transformation onetrust-11; BI field onetrust-11; report onetrust-11 onetrust-12; viewer onetrust-12 onetrust-13; agent onetrust-19 onetrust-20 onetrust-21 onetrust-22 onetrust-23 onetrust-52 onetrust-55 ## Cite this Cite as: Need to Know, PII Exposure Map and AI data governance scores, edition 13 Nov 2026, https://aidatagovernancetools.com/datasets/. Licensed CC BY 4.0. Each row carries the fact ids and the read date of its sources. ## Sources - PII Exposure Map, CSV: https://aidatagovernancetools.com/datasets/pii-exposure-map.csv (read 13 Nov 2026) - PII Exposure Map, JSON: https://aidatagovernancetools.com/datasets/pii-exposure-map.json (read 13 Nov 2026) Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/exposure-map/methodology/ --- # 14 of 16 tools document a sensitive field at the warehouse column EXPOSURE MAP, BY STAGE, read 13 Nov 2026 **The short answer.** At the warehouse column stage, 14 of 16 tools document it (Euno, Atlan, Snowflake Horizon, Databricks Unity Catalog and others), 2 are partial and 0 show none found on 13 Nov 2026. This is the stage warehouse scanners and catalogs both claim. None found means nothing was found in the documentation read, not that the feature is missing. The warehouse column is where a sensitive field is stored and first classified. A tool covers this stage when it shows the field by table and column name, with a classification or tag it reads or sets. Documented here means the documentation shows the tool reading or setting a sensitivity classification or tag on a warehouse column. Partial means it does so for some warehouses or data types only, or with a limit the documentation states. ## Documented - [Euno](/platforms/euno/), 67.0: Euno docs say Euno maps Cyera classifications onto Snowflake and BigQuery resources and traces them forward through column-level lineage. [Source](https://docs.euno.ai/sources/data-security/cyera-integration/cyera-integration-use-cases.md?utm_source=aidatagovernancetools.com&utm_medium=referral&utm_campaign=map), read 13 Nov 2026. - [Atlan](/platforms/atlan/), 65.5: Atlan says it crawls and syncs tags from source systems (AWS Glue, Confluent Kafka, Databricks, dbt, BigQuery, Snowflake) so they show up in Atlan. [Source](https://docs.atlan.com/llms/governance/tags/what-are-tags/llms.txt), read 13 Nov 2026. - [Snowflake Horizon](/platforms/snowflake/), 55.5: Snowflake says its classification feature automatically discovers sensitive data and makes it easy to apply tags and masking policies. [Source](https://docs.snowflake.com/en/user-guide/classify-intro.md), read 13 Nov 2026. - [Databricks Unity Catalog](/platforms/databricks/), 55.0: Databricks says Data Classification automatically tags columns with class.* governed tags when automatic tagging is enabled, and tags all existing and future detections. [Source](https://docs.databricks.com/aws/en/data-governance/unity-catalog/data-classification), read 13 Nov 2026. - [Microsoft Purview](/platforms/microsoft-purview/), 54.5: Microsoft says Data Map classifies assets automatically during scans with more than 200 built-in classifications plus custom ones. [Source](https://learn.microsoft.com/purview/data-map-classification), read 13 Nov 2026. - [Alation](/platforms/alation/), 54.0: Alation docs say Snowflake tags can be brought into Alation to track sensitive data and used as search filters; tags must be created in Snowflake first. [Source](https://documentation.alation.com/en/latest/governance/SnowflakeTags/index.md), read 13 Nov 2026. - [Secoda](/platforms/secoda/), 47.5: Secoda docs say PII is found by matching column-name keywords, which an admin can customize. [Source](https://docs.secoda.co/resource-and-metadata-management/tags/auto-pii-tagging.md), read 13 Nov 2026. - [Collibra](/platforms/collibra/), 46.5: Collibra says automated classification labels data, including PII and PHI, and that it can generate descriptions for assets. [Source](https://www.collibra.com/products/data-catalog), read 13 Nov 2026. - [Immuta](/platforms/immuta/), 45.0: Immuta says identification scans data sources and tags columns using column names, data patterns or dictionaries. [Source](https://documentation.immuta.com/saas/configuration/tags/data-discovery.md), read 13 Nov 2026. - [Ataccama ONE](/platforms/ataccama/), 41.5: Ataccama docs say detection rules run during profiling to classify attributes and catalog items by condition, and are not AI-powered. [Source](https://docs.ataccama.com/one/latest/data-quality/rules.html), read 13 Nov 2026. - [Informatica](/platforms/informatica/), 30.0: Informatica says CLAIRE automates sensitive data classification (PII, personal and financial records) as part of CDAM. [Source](https://www.informatica.com/about-us/news/news-releases/2024/02/20240229-informatica-launches-cloud-data-access-management-industrys-first-ai-powered-solution-for-automating-data-access-policy-enforcement-at-scale.html), read 13 Nov 2026. - [Privacera](/platforms/privacera/), 30.0: Trust3 AI says Discovery scans connected sources and automatically applies tags (for example EMAIL, PII) to columns, tables and files. [Source](https://docs.privacera.com/data-security/user-guide/discovery/scanning/classification/tags.html), read 13 Nov 2026. - [Securiti](/platforms/securiti/), 29.5: Securiti says discovery finds personal and sensitive data in structured and unstructured systems. [Source](https://securiti.ai/products/data-discovery/), read 13 Nov 2026. - [OneTrust](/platforms/onetrust/), 26.5: OneTrust says Data Use Governance classifies structured and unstructured sources with AI-driven techniques, using four contexts: business, regulatory, consent and data. [Source](https://www.onetrust.com/solutions/data-use-governance/), read 13 Nov 2026. ## Partial - [DataHub](/platforms/datahub/), 61.0: DataHub docs say the built-in PII classifier was removed from ingestion; no classifier is registered by default. [Source](https://docs.datahub.com/docs/metadata-ingestion/docs/dev_guides/classification), read 13 Nov 2026. - [Select Star](/platforms/select-star/), 53.5: Select Star docs say PII rules are regular expressions matched against column names and run once a day after metadata sync (name-based, not a scan of values). [Source](https://web.archive.org/web/2026/https://docs.selectstar.com/data-management/automated-pii-detection-beta), read 13 Nov 2026. ## None found - None of the 16 on 13 Nov 2026. ## Verdict by situation - **A regulated field** ([a governance lead who must show where a regulated field ends up](/best-for/regulated-field/)): Atlan and Euno tie at 68.5. Atlan and Euno tie on total: Atlan is ahead on Acts on it (7 to 5), Euno is ahead on Carries classification downstream (8 to 7). Atlan and Euno tie at 68.5 on total. The published tie rule (higher score on the heaviest criterion, then by name) puts Atlan ahead: the two tie on Follows sensitive data into BI too, so the name decides. - **Agents on analytics** ([a company connecting AI agents to its analytics data this year](/best-for/agents-on-analytics/)): Euno leads at 66.0, ahead of Atlan at 65.0. Euno leads on Price transparency (4 to 0) and Carries classification downstream (8 to 7), while Atlan is ahead on Acts on it (7 to 5). - **A Microsoft estate** ([a Microsoft estate: Fabric, Power BI and Purview](/best-for/microsoft-estate/)): Atlan leads at 68.5, ahead of Euno at 67.5. Atlan leads on Acts on it (7 to 5), while Euno is ahead on Carries classification downstream (8 to 7). - **A mixed stack** ([a mixed stack: Snowflake or Databricks with dbt and two or more BI tools](/best-for/mixed-stack/)): Euno leads at 68.5, ahead of Atlan at 65.5. Euno leads on Carries classification downstream (8 to 7) and Price transparency (4 to 0), while Atlan is ahead on Acts on it (7 to 5). - **A lean team** ([a lean data team with no governance hire](/best-for/lean-team/)): Euno leads at 62.5, ahead of Atlan at 59.0. Euno leads on Price transparency (4 to 0) and Carries classification downstream (8 to 7), while Atlan is ahead on Acts on it (7 to 5). ## Sources - https://documentation.alation.com/en/latest/governance/SnowflakeTags/index.md: https://documentation.alation.com/en/latest/governance/SnowflakeTags/index.md (read 13 Nov 2026) - https://docs.ataccama.com/one/latest/data-quality/rules.html: https://docs.ataccama.com/one/latest/data-quality/rules.html (read 13 Nov 2026) - https://docs.ataccama.com/ataccama-one-agentic/latest/data-catalog/detect-terms.html: https://docs.ataccama.com/ataccama-one-agentic/latest/data-catalog/detect-terms.html (read 13 Nov 2026) - https://docs.atlan.com/llms/governance/tags/what-are-tags/llms.txt: https://docs.atlan.com/llms/governance/tags/what-are-tags/llms.txt (read 13 Nov 2026) - https://docs.atlan.com/data/product-change-log/llms.txt: https://docs.atlan.com/data/product-change-log/llms.txt (read 13 Nov 2026) - https://docs.atlan.com/llms/governance/access-control/what-are-purposes/llms.txt: https://docs.atlan.com/llms/governance/access-control/what-are-purposes/llms.txt (read 13 Nov 2026) - https://www.collibra.com/products/data-catalog: https://www.collibra.com/products/data-catalog (read 13 Nov 2026) - https://github.com/collibra/chip: https://github.com/collibra/chip (read 13 Nov 2026) - https://docs.databricks.com/aws/en/data-governance/unity-catalog/data-classification: https://docs.databricks.com/aws/en/data-governance/unity-catalog/data-classification (read 13 Nov 2026) - https://docs.datahub.com/docs/metadata-ingestion/docs/dev_guides/classification: https://docs.datahub.com/docs/metadata-ingestion/docs/dev_guides/classification (read 13 Nov 2026) - https://datahub.com/products/data-governance/: https://datahub.com/products/data-governance/ (read 13 Nov 2026) - https://docs.datahub.com/integrations: https://docs.datahub.com/integrations (read 13 Nov 2026) - https://docs.euno.ai/sources/data-security/cyera-integration/cyera-integration-use-cases.md: https://docs.euno.ai/sources/data-security/cyera-integration/cyera-integration-use-cases.md (read 13 Nov 2026) - https://docs.euno.ai/sources/data-security/bigid-integration/bigid-integration-use-cases.md: https://docs.euno.ai/sources/data-security/bigid-integration/bigid-integration-use-cases.md (read 13 Nov 2026) - https://documentation.immuta.com/saas/configuration/tags/data-discovery.md: https://documentation.immuta.com/saas/configuration/tags/data-discovery.md (read 13 Nov 2026) - https://www.informatica.com/about-us/news/news-releases/2024/02/20240229-informatica-launches-cloud-data-access-management-industrys-first-ai-powered-solution-for-automating-data-access-policy-enforcement-at-scale.html: https://www.informatica.com/about-us/news/news-releases/2024/02/20240229-informatica-launches-cloud-data-access-management-industrys-first-ai-powered-solution-for-automating-data-access-policy-enforcement-at-scale.html (read 13 Nov 2026) - https://www.informatica.com/blogs/how-idmc-supports-native-security-controls-in-snowflake.html: https://www.informatica.com/blogs/how-idmc-supports-native-security-controls-in-snowflake.html (read 13 Nov 2026) - https://learn.microsoft.com/purview/data-map-classification: https://learn.microsoft.com/purview/data-map-classification (read 13 Nov 2026) - https://learn.microsoft.com/purview/register-scan-snowflake: https://learn.microsoft.com/purview/register-scan-snowflake (read 13 Nov 2026) - https://learn.microsoft.com/purview/register-scan-azure-databricks-unity-catalog: https://learn.microsoft.com/purview/register-scan-azure-databricks-unity-catalog (read 13 Nov 2026) - https://learn.microsoft.com/power-bi/enterprise/service-security-sensitivity-label-inheritance-from-data-sources: https://learn.microsoft.com/power-bi/enterprise/service-security-sensitivity-label-inheritance-from-data-sources (read 13 Nov 2026) - https://www.onetrust.com/solutions/data-use-governance/: https://www.onetrust.com/solutions/data-use-governance/ (read 13 Nov 2026) - https://www.onetrust.com/integrations/: https://www.onetrust.com/integrations/ (read 13 Nov 2026) - https://developer.onetrust.com/onetrust/reference/getallusingget_1.md: https://developer.onetrust.com/onetrust/reference/getallusingget_1.md (read 13 Nov 2026) - https://docs.privacera.com/data-security/user-guide/discovery/scanning/classification/tags.html: https://docs.privacera.com/data-security/user-guide/discovery/scanning/classification/tags.html (read 13 Nov 2026) - https://docs.privacera.com/data-security/user-guide/discovery/scanning/classification/index.html: https://docs.privacera.com/data-security/user-guide/discovery/scanning/classification/index.html (read 13 Nov 2026) - https://docs.secoda.co/resource-and-metadata-management/tags/auto-pii-tagging.md: https://docs.secoda.co/resource-and-metadata-management/tags/auto-pii-tagging.md (read 13 Nov 2026) - https://docs.secoda.co/integrations/data-quality-tools/cyera.md: https://docs.secoda.co/integrations/data-quality-tools/cyera.md (read 13 Nov 2026) - https://securiti.ai/products/data-discovery/: https://securiti.ai/products/data-discovery/ (read 13 Nov 2026) - https://securiti.ai/products/data-classification/: https://securiti.ai/products/data-classification/ (read 13 Nov 2026) - https://web.archive.org/web/2026/https://docs.selectstar.com/data-management/automated-pii-detection-beta: https://web.archive.org/web/2026/https://docs.selectstar.com/data-management/automated-pii-detection-beta (read 13 Nov 2026) - https://docs.snowflake.com/en/user-guide/classify-intro.md: https://docs.snowflake.com/en/user-guide/classify-intro.md (read 13 Nov 2026) Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/exposure-map/column/ --- # 1 of 16 tools document a sensitive field through the transformation layer EXPOSURE MAP, BY STAGE, read 13 Nov 2026 **The short answer.** At the transformation stage, 1 of 16 tools document it (Informatica), 12 are partial and 3 show none found on 13 Nov 2026. Transformation is where the classification most often falls off. None found means nothing was found in the documentation read, not that the feature is missing. The transformation layer is the models, views and pipelines that build new tables from the classified column. A tool covers this stage when its documentation shows the classification surviving into the derived tables or models. Documented here means the documentation shows the classification carried into derived tables or models, in dbt or in the warehouse. Partial means it is shown for one transformation tool, or only when the model keeps the column name, or with a limit the documentation states. ## Documented - [Informatica](/platforms/informatica/), 30.0: Informatica says lineage can be derived from code in SQL scripts, stored procedures and AI/ML code, and inferred where documentation is missing. [Source](https://www.informatica.com/products/data-catalog/data-lineage.html), read 13 Nov 2026. ## Partial - [Euno](/platforms/euno/), 67.0: Euno docs describe a Propagated Boolean tag that carries a value such as contains_pii along a direction of lineage. [Source](https://docs.euno.ai/using-euno/metadata-activation/metadata-tags.md?utm_source=aidatagovernancetools.com&utm_medium=referral&utm_campaign=map), read 13 Nov 2026. - [Atlan](/platforms/atlan/), 65.5: When attaching a tag, a user can allow propagation to child and downstream assets through lineage. [Source](https://docs.atlan.com/llms/governance/tags/attach-a-tag/llms.txt), read 13 Nov 2026. - [DataHub](/platforms/datahub/), 61.0: DataHub docs say column-level lineage tracks each specific column, shown inside table-level lineage. [Source](https://docs.datahub.com/docs/features/feature-guides/lineage), read 13 Nov 2026. - [Snowflake Horizon](/platforms/snowflake/), 55.5: Snowflake documents automatic tag propagation: a tag set on a source object is assigned to target objects such as views and tables created from it (Enterprise Edition or higher). [Source](https://docs.snowflake.com/en/user-guide/object-tagging/propagation.md), read 13 Nov 2026. - [Databricks Unity Catalog](/platforms/databricks/), 55.0: Databricks says Unity Catalog captures runtime lineage to the column level for tables, jobs, notebooks, dashboards, models and external assets, with some limits. [Source](https://docs.databricks.com/aws/en/data-governance/unity-catalog/data-lineage), read 13 Nov 2026. - [Microsoft Purview](/platforms/microsoft-purview/), 54.5: Microsoft documents that scanning Snowflake brings in tables, views, streams and stored procedures with static lineage between them. [Source](https://learn.microsoft.com/purview/register-scan-snowflake), read 13 Nov 2026. - [Alation](/platforms/alation/), 54.0: Alation docs describe lineage extraction for dbt Cloud and dbt Core through the dbt Gen2 connector. [Source](https://documentation.alation.com/en/latest/OpenConnectorFramework/ELTConnectors/dbtOCFConnector/dbtOCFConnectorConfigLineage.md), read 13 Nov 2026. - [Select Star](/platforms/select-star/), 53.5: Select Star docs say lineage is built by parsing SQL statements that ran in the source, which is how warehouse and transformation steps are linked. [Source](https://web.archive.org/web/20260715110406/https://docs.selectstar.com/llms-full.txt), read 13 Nov 2026. - [Secoda](/platforms/secoda/), 47.5: Secoda docs say lineage is built automatically from SQL queries, and dbt's manifest.json is used to widen coverage. [Source](https://docs.secoda.co/features/data-lineage.md), read 13 Nov 2026. - [Collibra](/platforms/collibra/), 46.5: Collibra docs list the adapters that dbt lineage supports (including Snowflake, Databricks, Postgres, BigQuery, Redshift); the page does not mention snapshot nodes. [Source](https://web.archive.org/web/20260421071225/https://productresources.collibra.com/docs/collibra/latest/Content/CollibraDataLineage/DataSources/dbtCore/ref_dbt-core-supported-transformations.htm), read 13 Nov 2026. - [Ataccama ONE](/platforms/ataccama/), 41.5: Ataccama lists dbt lineage as design-time through the underlying database scanner. [Source](https://docs.ataccama.com/one/latest/lineage/supported-lineage-technologies.html), read 13 Nov 2026. - [Securiti](/platforms/securiti/), 29.5: Securiti says lineage is extracted automatically from source systems, BI tools and ETL tools. [Source](https://securiti.ai/products/data-lineage/), read 13 Nov 2026. ## None found - [Immuta](/platforms/immuta/), 45.0: none found on 13 Nov 2026. - [Privacera](/platforms/privacera/), 30.0: none found on 13 Nov 2026. - [OneTrust](/platforms/onetrust/), 26.5: none found on 13 Nov 2026. ## Verdict by situation - **A regulated field** ([a governance lead who must show where a regulated field ends up](/best-for/regulated-field/)): Atlan and Euno tie at 68.5. Atlan and Euno tie on total: Atlan is ahead on Acts on it (7 to 5), Euno is ahead on Carries classification downstream (8 to 7). Atlan and Euno tie at 68.5 on total. The published tie rule (higher score on the heaviest criterion, then by name) puts Atlan ahead: the two tie on Follows sensitive data into BI too, so the name decides. - **Agents on analytics** ([a company connecting AI agents to its analytics data this year](/best-for/agents-on-analytics/)): Euno leads at 66.0, ahead of Atlan at 65.0. Euno leads on Price transparency (4 to 0) and Carries classification downstream (8 to 7), while Atlan is ahead on Acts on it (7 to 5). - **A Microsoft estate** ([a Microsoft estate: Fabric, Power BI and Purview](/best-for/microsoft-estate/)): Atlan leads at 68.5, ahead of Euno at 67.5. Atlan leads on Acts on it (7 to 5), while Euno is ahead on Carries classification downstream (8 to 7). - **A mixed stack** ([a mixed stack: Snowflake or Databricks with dbt and two or more BI tools](/best-for/mixed-stack/)): Euno leads at 68.5, ahead of Atlan at 65.5. Euno leads on Carries classification downstream (8 to 7) and Price transparency (4 to 0), while Atlan is ahead on Acts on it (7 to 5). - **A lean team** ([a lean data team with no governance hire](/best-for/lean-team/)): Euno leads at 62.5, ahead of Atlan at 59.0. Euno leads on Price transparency (4 to 0) and Carries classification downstream (8 to 7), while Atlan is ahead on Acts on it (7 to 5). ## Sources - https://documentation.alation.com/en/latest/OpenConnectorFramework/ELTConnectors/dbtOCFConnector/dbtOCFConnectorConfigLineage.md: https://documentation.alation.com/en/latest/OpenConnectorFramework/ELTConnectors/dbtOCFConnector/dbtOCFConnectorConfigLineage.md (read 13 Nov 2026) - https://docs.ataccama.com/one/latest/lineage/supported-lineage-technologies.html: https://docs.ataccama.com/one/latest/lineage/supported-lineage-technologies.html (read 13 Nov 2026) - https://docs.atlan.com/llms/governance/tags/attach-a-tag/llms.txt: https://docs.atlan.com/llms/governance/tags/attach-a-tag/llms.txt (read 13 Nov 2026) - https://docs.atlan.com/llms/governance/tags/what-are-tags/llms.txt: https://docs.atlan.com/llms/governance/tags/what-are-tags/llms.txt (read 13 Nov 2026) - https://docs.atlan.com/product/capabilities/lineage/how-tos/propagate-metadata-through-lineage: https://docs.atlan.com/product/capabilities/lineage/how-tos/propagate-metadata-through-lineage (read 13 Nov 2026) - https://web.archive.org/web/20260421071225/https://productresources.collibra.com/docs/collibra/latest/Content/CollibraDataLineage/DataSources/dbtCore/ref_dbt-core-supported-transformations.htm: https://web.archive.org/web/20260421071225/https://productresources.collibra.com/docs/collibra/latest/Content/CollibraDataLineage/DataSources/dbtCore/ref_dbt-core-supported-transformations.htm (read 13 Nov 2026) - https://productresources.collibra.com/docs/collibra/latest/Content/Home.htm: https://productresources.collibra.com/docs/collibra/latest/Content/Home.htm (read 13 Nov 2026) - https://docs.databricks.com/aws/en/data-governance/unity-catalog/data-lineage: https://docs.databricks.com/aws/en/data-governance/unity-catalog/data-lineage (read 13 Nov 2026) - https://docs.databricks.com/aws/en/admin/governed-tags/tag-propagation: https://docs.databricks.com/aws/en/admin/governed-tags/tag-propagation (read 13 Nov 2026) - https://docs.datahub.com/docs/features/feature-guides/lineage: https://docs.datahub.com/docs/features/feature-guides/lineage (read 13 Nov 2026) - https://docs.datahub.com/docs/automations/glossary-term-propagation: https://docs.datahub.com/docs/automations/glossary-term-propagation (read 13 Nov 2026) - https://docs.euno.ai/using-euno/metadata-activation/metadata-tags.md: https://docs.euno.ai/using-euno/metadata-activation/metadata-tags.md (read 13 Nov 2026) - https://docs.euno.ai/sources/data-security/cyera-integration/cyera-integration-use-cases.md: https://docs.euno.ai/sources/data-security/cyera-integration/cyera-integration-use-cases.md (read 13 Nov 2026) - https://documentation.immuta.com/saas/: https://documentation.immuta.com/saas/ (read 13 Nov 2026) - https://www.informatica.com/products/data-catalog/data-lineage.html: https://www.informatica.com/products/data-catalog/data-lineage.html (read 13 Nov 2026) - https://learn.microsoft.com/purview/register-scan-snowflake: https://learn.microsoft.com/purview/register-scan-snowflake (read 13 Nov 2026) - https://learn.microsoft.com/purview/how-to-lineage-powerbi: https://learn.microsoft.com/purview/how-to-lineage-powerbi (read 13 Nov 2026) - https://learn.microsoft.com/purview/: https://learn.microsoft.com/purview/ (read 13 Nov 2026) - https://developer.onetrust.com/onetrust/llms.txt: https://developer.onetrust.com/onetrust/llms.txt (read 13 Nov 2026) - https://docs.privacera.com/data-security/index.html: https://docs.privacera.com/data-security/index.html (read 13 Nov 2026) - https://docs.secoda.co/features/data-lineage.md: https://docs.secoda.co/features/data-lineage.md (read 13 Nov 2026) - https://docs.secoda.co/features/automations.md: https://docs.secoda.co/features/automations.md (read 13 Nov 2026) - https://securiti.ai/products/data-lineage/: https://securiti.ai/products/data-lineage/ (read 13 Nov 2026) - https://securiti.ai/products/sensitive-data-catalog/: https://securiti.ai/products/sensitive-data-catalog/ (read 13 Nov 2026) - https://web.archive.org/web/20260715110406/https://docs.selectstar.com/llms-full.txt: https://web.archive.org/web/20260715110406/https://docs.selectstar.com/llms-full.txt (read 13 Nov 2026) - https://docs.snowflake.com/en/user-guide/object-tagging/propagation.md: https://docs.snowflake.com/en/user-guide/object-tagging/propagation.md (read 13 Nov 2026) - https://docs.snowflake.com/en/user-guide/ui-snowsight-lineage.md: https://docs.snowflake.com/en/user-guide/ui-snowsight-lineage.md (read 13 Nov 2026) Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/exposure-map/transformation/ --- # 3 of 16 tools document the BI field built on a sensitive column EXPOSURE MAP, BY STAGE, read 13 Nov 2026 **The short answer.** At the BI field stage, 3 of 16 tools document it (Euno, Alation, Select Star), 10 are partial and 3 show none found on 13 Nov 2026. The BI field is the first place most warehouse policies lose sight of the data. None found means nothing was found in the documentation read, not that the feature is missing. The BI field is the dimension, measure or column inside a dashboard tool that is built on the warehouse column. A tool covers this stage when it shows the field in a named BI tool and ties it back to the classified column. Documented here means the documentation names a BI tool and shows the field linked to the classified source column. Partial means it is shown for one BI tool, or for some field types, or with a limit the documentation states. ## Documented - [Euno](/platforms/euno/), 67.0: Euno docs say BigID classifications do not automatically appear on Looker, Tableau or Power BI assets, and that Euno propagates them to downstream fields and reports. [Source](https://docs.euno.ai/sources/data-security/bigid-integration/bigid-integration-use-cases.md?utm_source=aidatagovernancetools.com&utm_medium=referral&utm_campaign=map), read 13 Nov 2026. - [Alation](/platforms/alation/), 54.0: Alation docs say Tableau lineage can show links from warehouse table columns to BI report fields in Tableau views (column-level lineage on by default from 2024.1.5). [Source](https://documentation.alation.com/en/latest/OpenConnectorFramework/BIConnectors/TableauOCFConnector/TableauServerandOnlineConnectorConfigureLineage.md), read 13 Nov 2026. - [Select Star](/platforms/select-star/), 53.5: Select Star says its Looker integration gives column-level lineage from source views down to LookML views, explores and dashboards. [Source](https://www.selectstar.com/integrations/looker), read 13 Nov 2026. ## Partial - [Atlan](/platforms/atlan/), 65.5: Atlan says it captures column-level lineage automatically across warehouses, pipelines and BI tools. [Source](https://docs.atlan.com/product/capabilities/lineage/concepts/what-is-column-level-lineage), read 13 Nov 2026. - [DataHub](/platforms/datahub/), 61.0: The Looker source docs list column-level lineage as enabled by default. [Source](https://docs.datahub.com/docs/generated/ingestion/sources/looker), read 13 Nov 2026. - [Snowflake Horizon](/platforms/snowflake/), 55.5: The Tableau connector reads workbooks, data sources, fields and lineage through Tableau's REST and Metadata APIs. [Source](https://docs.snowflake.com/en/user-guide/snowflake-horizon/connectors/tableau), read 13 Nov 2026. - [Databricks Unity Catalog](/platforms/databricks/), 55.0: Databricks says external assets such as Tableau or Power BI dashboards can be registered as external metadata objects and linked into the lineage graph. [Source](https://docs.databricks.com/aws/en/data-governance/unity-catalog/external-lineage), read 13 Nov 2026. - [Microsoft Purview](/platforms/microsoft-purview/), 54.5: Microsoft says column-level lineage and transformation detail inside Power BI datasets are captured only when Azure SQL Database is the source. [Source](https://learn.microsoft.com/purview/how-to-lineage-powerbi), read 13 Nov 2026. - [Secoda](/platforms/secoda/), 47.5: Secoda docs say column-level lineage into BI tools is currently supported only for Looker and Tableau. [Source](https://docs.secoda.co/features/data-lineage.md), read 13 Nov 2026. - [Collibra](/platforms/collibra/), 46.5: Collibra docs list supported lineage sources including warehouses (Snowflake, Databricks Unity Catalog, BigQuery), dbt and Looker, Power BI, Qlik, Sigma, Tableau and ThoughtSpot; the docs state column-level lineage is not generated for tables created by SQL statements. [Source](https://productresources.collibra.com/docs/collibra/latest/Content/CollibraDataLineage/ref_technical-lineage-supported-data-sources.htm), read 13 Nov 2026. - [Ataccama ONE](/platforms/ataccama/), 41.5: Ataccama docs say the Tableau scanner maps column fields to database columns, giving column-to-field lineage. [Source](https://docs.ataccama.com/one/latest/lineage/tableau-lineage-scanner.html), read 13 Nov 2026. - [Informatica](/platforms/informatica/), 30.0: Informatica says CDAM pushes policies into Snowflake, Databricks, Power BI and more. [Source](https://www.informatica.com/products/data-governance/data-access-management.html), read 13 Nov 2026. - [Securiti](/platforms/securiti/), 29.5: Securiti says lineage is extracted automatically from source systems, BI tools and ETL tools. [Source](https://securiti.ai/products/data-lineage/), read 13 Nov 2026. ## None found - [Immuta](/platforms/immuta/), 45.0: none found on 13 Nov 2026. - [Privacera](/platforms/privacera/), 30.0: none found on 13 Nov 2026. - [OneTrust](/platforms/onetrust/), 26.5: none found on 13 Nov 2026. ## Verdict by situation - **A regulated field** ([a governance lead who must show where a regulated field ends up](/best-for/regulated-field/)): Atlan and Euno tie at 68.5. Atlan and Euno tie on total: Atlan is ahead on Acts on it (7 to 5), Euno is ahead on Carries classification downstream (8 to 7). Atlan and Euno tie at 68.5 on total. The published tie rule (higher score on the heaviest criterion, then by name) puts Atlan ahead: the two tie on Follows sensitive data into BI too, so the name decides. - **Agents on analytics** ([a company connecting AI agents to its analytics data this year](/best-for/agents-on-analytics/)): Euno leads at 66.0, ahead of Atlan at 65.0. Euno leads on Price transparency (4 to 0) and Carries classification downstream (8 to 7), while Atlan is ahead on Acts on it (7 to 5). - **A Microsoft estate** ([a Microsoft estate: Fabric, Power BI and Purview](/best-for/microsoft-estate/)): Atlan leads at 68.5, ahead of Euno at 67.5. Atlan leads on Acts on it (7 to 5), while Euno is ahead on Carries classification downstream (8 to 7). - **A mixed stack** ([a mixed stack: Snowflake or Databricks with dbt and two or more BI tools](/best-for/mixed-stack/)): Euno leads at 68.5, ahead of Atlan at 65.5. Euno leads on Carries classification downstream (8 to 7) and Price transparency (4 to 0), while Atlan is ahead on Acts on it (7 to 5). - **A lean team** ([a lean data team with no governance hire](/best-for/lean-team/)): Euno leads at 62.5, ahead of Atlan at 59.0. Euno leads on Price transparency (4 to 0) and Carries classification downstream (8 to 7), while Atlan is ahead on Acts on it (7 to 5). ## Sources - https://documentation.alation.com/en/latest/OpenConnectorFramework/BIConnectors/TableauOCFConnector/TableauServerandOnlineConnectorConfigureLineage.md: https://documentation.alation.com/en/latest/OpenConnectorFramework/BIConnectors/TableauOCFConnector/TableauServerandOnlineConnectorConfigureLineage.md (read 13 Nov 2026) - https://docs.ataccama.com/one/latest/lineage/tableau-lineage-scanner.html: https://docs.ataccama.com/one/latest/lineage/tableau-lineage-scanner.html (read 13 Nov 2026) - https://docs.ataccama.com/one/latest/lineage/get-started.html: https://docs.ataccama.com/one/latest/lineage/get-started.html (read 13 Nov 2026) - https://docs.atlan.com/product/capabilities/lineage/concepts/what-is-column-level-lineage: https://docs.atlan.com/product/capabilities/lineage/concepts/what-is-column-level-lineage (read 13 Nov 2026) - https://docs.atlan.com/llms/connectors/tableau/what-does-atlan-crawl-from-tableau/llms.txt: https://docs.atlan.com/llms/connectors/tableau/what-does-atlan-crawl-from-tableau/llms.txt (read 13 Nov 2026) - https://docs.atlan.com/llms/connectors/looker/what-does-atlan-crawl-from-looker/llms.txt: https://docs.atlan.com/llms/connectors/looker/what-does-atlan-crawl-from-looker/llms.txt (read 13 Nov 2026) - https://docs.atlan.com/llms/connectors/microsoft-power-bi/what-does-atlan-crawl-from-microsoft-power-bi/llms.txt: https://docs.atlan.com/llms/connectors/microsoft-power-bi/what-does-atlan-crawl-from-microsoft-power-bi/llms.txt (read 13 Nov 2026) - https://productresources.collibra.com/docs/collibra/latest/Content/CollibraDataLineage/ref_technical-lineage-supported-data-sources.htm: https://productresources.collibra.com/docs/collibra/latest/Content/CollibraDataLineage/ref_technical-lineage-supported-data-sources.htm (read 13 Nov 2026) - https://docs.databricks.com/aws/en/data-governance/unity-catalog/external-lineage: https://docs.databricks.com/aws/en/data-governance/unity-catalog/external-lineage (read 13 Nov 2026) - https://docs.datahub.com/docs/generated/ingestion/sources/looker: https://docs.datahub.com/docs/generated/ingestion/sources/looker (read 13 Nov 2026) - https://docs.datahub.com/docs/generated/ingestion/sources/powerbi: https://docs.datahub.com/docs/generated/ingestion/sources/powerbi (read 13 Nov 2026) - https://docs.euno.ai/sources/data-security/bigid-integration/bigid-integration-use-cases.md: https://docs.euno.ai/sources/data-security/bigid-integration/bigid-integration-use-cases.md (read 13 Nov 2026) - https://euno.ai/blog/euno-is-officially-live-on-cyeras-integrations: https://euno.ai/blog/euno-is-officially-live-on-cyeras-integrations (read 13 Nov 2026) - https://documentation.immuta.com/saas/: https://documentation.immuta.com/saas/ (read 13 Nov 2026) - https://www.informatica.com/products/data-governance/data-access-management.html: https://www.informatica.com/products/data-governance/data-access-management.html (read 13 Nov 2026) - https://www.informatica.com/blogs/activate-enterprise-data-with-trusted-context-new-capabilities-in-idmcs-spring-2026-release.html: https://www.informatica.com/blogs/activate-enterprise-data-with-trusted-context-new-capabilities-in-idmcs-spring-2026-release.html (read 13 Nov 2026) - https://learn.microsoft.com/purview/how-to-lineage-powerbi: https://learn.microsoft.com/purview/how-to-lineage-powerbi (read 13 Nov 2026) - https://learn.microsoft.com/purview/: https://learn.microsoft.com/purview/ (read 13 Nov 2026) - https://developer.onetrust.com/onetrust/llms.txt: https://developer.onetrust.com/onetrust/llms.txt (read 13 Nov 2026) - https://docs.privacera.com/data-security/connectors/overview/index.html: https://docs.privacera.com/data-security/connectors/overview/index.html (read 13 Nov 2026) - https://docs.secoda.co/features/data-lineage.md: https://docs.secoda.co/features/data-lineage.md (read 13 Nov 2026) - https://docs.secoda.co/integrations/data-visualization-tools/tableau-integration/metadata-extracted.md: https://docs.secoda.co/integrations/data-visualization-tools/tableau-integration/metadata-extracted.md (read 13 Nov 2026) - https://securiti.ai/products/data-lineage/: https://securiti.ai/products/data-lineage/ (read 13 Nov 2026) - https://securiti.ai/connectors/tableau/: https://securiti.ai/connectors/tableau/ (read 13 Nov 2026) - https://www.selectstar.com/integrations/looker: https://www.selectstar.com/integrations/looker (read 13 Nov 2026) - https://www.selectstar.com/integrations/tableau: https://www.selectstar.com/integrations/tableau (read 13 Nov 2026) - https://www.selectstar.com/integrations: https://www.selectstar.com/integrations (read 13 Nov 2026) - https://docs.snowflake.com/en/user-guide/snowflake-horizon/connectors/tableau: https://docs.snowflake.com/en/user-guide/snowflake-horizon/connectors/tableau (read 13 Nov 2026) - https://docs.snowflake.com/en/user-guide/snowflake-horizon/connectors/powerbi: https://docs.snowflake.com/en/user-guide/snowflake-horizon/connectors/powerbi (read 13 Nov 2026) Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/exposure-map/bi-field/ --- # 4 of 16 tools document the report that shows a sensitive field EXPOSURE MAP, BY STAGE, read 13 Nov 2026 **The short answer.** At the report stage, 4 of 16 tools document it (Euno, Microsoft Purview, Alation, Select Star), 8 are partial and 4 show none found on 13 Nov 2026. The report is where an auditor asks to see the field with their own eyes. None found means nothing was found in the documentation read, not that the feature is missing. The report or dashboard is what a person opens. A tool covers this stage when it can list the reports and dashboards that show a given sensitive field, not only the fields underneath them. Documented here means the documentation shows reports or dashboards listed against a sensitive field or its classification. Partial means it lists reports for one BI tool only, or lists data sources without the reports built on them, or states another limit. ## Documented - [Euno](/platforms/euno/), 67.0: Euno docs say Cyera classifies sensitive data in the warehouse and Euno propagates those classifications through column-level lineage into BI fields, dashboards and reports. [Source](https://docs.euno.ai/sources/data-security/cyera-integration/cyera-integration-use-cases.md?utm_source=aidatagovernancetools.com&utm_medium=referral&utm_campaign=map), read 13 Nov 2026. - [Microsoft Purview](/platforms/microsoft-purview/), 54.5: Microsoft says a Power BI scan fetches static lineage between workspaces, dashboards, reports, datasets, dataflows, datamarts and external data source assets. [Source](https://learn.microsoft.com/purview/register-scan-power-bi-tenant), read 13 Nov 2026. - [Alation](/platforms/alation/), 54.0: Alation docs describe cross-source and column-level lineage for the Power BI Scanner connector, with supported expressions and limitations. [Source](https://documentation.alation.com/en/latest/OpenConnectorFramework/BIConnectors/PowerBIScannerOCFConnector/PowerBIScannerConnectorConfigLineage.md), read 13 Nov 2026. - [Select Star](/platforms/select-star/), 53.5: Select Star docs describe a Downstream Dashboards lineage view that lists every dependent dashboard with its top user and popularity. [Source](https://web.archive.org/web/20260715110406/https://docs.selectstar.com/llms-full.txt), read 13 Nov 2026. ## Partial - [Atlan](/platforms/atlan/), 65.5: The Metadata Propagator can be restricted by asset type to keep metadata out of report-level assets, which implies it can reach them when not restricted. [Source](https://docs.atlan.com/product/capabilities/lineage/how-tos/propagate-metadata-through-lineage), read 13 Nov 2026. - [DataHub](/platforms/datahub/), 61.0: DataHub docs limit asset-level glossary term propagation to datasets; charts, dashboards, pipelines and tasks are excluded. [Source](https://docs.datahub.com/docs/automations/glossary-term-propagation), read 13 Nov 2026. - [Snowflake Horizon](/platforms/snowflake/), 55.5: The Tableau connector reads workbooks, data sources, fields and lineage through Tableau's REST and Metadata APIs. [Source](https://docs.snowflake.com/en/user-guide/snowflake-horizon/connectors/tableau), read 13 Nov 2026. - [Databricks Unity Catalog](/platforms/databricks/), 55.0: Databricks says external assets such as Tableau or Power BI dashboards can be registered as external metadata objects and linked into the lineage graph. [Source](https://docs.databricks.com/aws/en/data-governance/unity-catalog/external-lineage), read 13 Nov 2026. - [Secoda](/platforms/secoda/), 47.5: Secoda docs say a user can run impact analysis from a warehouse column to the affected dashboard or chart, for Looker and Tableau only. [Source](https://docs.secoda.co/features/data-lineage.md), read 13 Nov 2026. - [Collibra](/platforms/collibra/), 46.5: Collibra says its lineage traces root causes and downstream impacts at table, column and report level. [Source](https://www.collibra.com/products/data-lineage), read 13 Nov 2026. - [Immuta](/platforms/immuta/), 45.0: Immuta says Tableau dashboard viewers see data according to their personal policies when the published data source prompts the user for credentials. [Source](https://documentation.immuta.com/saas/configuration/application-configuration/how-to-guides/bi-tools/tableau.md), read 13 Nov 2026. - [Ataccama ONE](/platforms/ataccama/), 41.5: Ataccama docs say protected attributes block rendering of visualizations for unauthorized users, but this is inside ONE Data Stories, Ataccama's own visualization component. [Source](https://docs.ataccama.com/one/latest/data-stories/data-protection-classification-in-data-stories.html), read 13 Nov 2026. ## None found - [Informatica](/platforms/informatica/), 30.0: none found on 13 Nov 2026. - [Privacera](/platforms/privacera/), 30.0: none found on 13 Nov 2026. - [Securiti](/platforms/securiti/), 29.5: none found on 13 Nov 2026. - [OneTrust](/platforms/onetrust/), 26.5: none found on 13 Nov 2026. ## Verdict by situation - **A regulated field** ([a governance lead who must show where a regulated field ends up](/best-for/regulated-field/)): Atlan and Euno tie at 68.5. Atlan and Euno tie on total: Atlan is ahead on Acts on it (7 to 5), Euno is ahead on Carries classification downstream (8 to 7). Atlan and Euno tie at 68.5 on total. The published tie rule (higher score on the heaviest criterion, then by name) puts Atlan ahead: the two tie on Follows sensitive data into BI too, so the name decides. - **Agents on analytics** ([a company connecting AI agents to its analytics data this year](/best-for/agents-on-analytics/)): Euno leads at 66.0, ahead of Atlan at 65.0. Euno leads on Price transparency (4 to 0) and Carries classification downstream (8 to 7), while Atlan is ahead on Acts on it (7 to 5). - **A Microsoft estate** ([a Microsoft estate: Fabric, Power BI and Purview](/best-for/microsoft-estate/)): Atlan leads at 68.5, ahead of Euno at 67.5. Atlan leads on Acts on it (7 to 5), while Euno is ahead on Carries classification downstream (8 to 7). - **A mixed stack** ([a mixed stack: Snowflake or Databricks with dbt and two or more BI tools](/best-for/mixed-stack/)): Euno leads at 68.5, ahead of Atlan at 65.5. Euno leads on Carries classification downstream (8 to 7) and Price transparency (4 to 0), while Atlan is ahead on Acts on it (7 to 5). - **A lean team** ([a lean data team with no governance hire](/best-for/lean-team/)): Euno leads at 62.5, ahead of Atlan at 59.0. Euno leads on Price transparency (4 to 0) and Carries classification downstream (8 to 7), while Atlan is ahead on Acts on it (7 to 5). ## Sources - https://documentation.alation.com/en/latest/OpenConnectorFramework/BIConnectors/PowerBIScannerOCFConnector/PowerBIScannerConnectorConfigLineage.md: https://documentation.alation.com/en/latest/OpenConnectorFramework/BIConnectors/PowerBIScannerOCFConnector/PowerBIScannerConnectorConfigLineage.md (read 13 Nov 2026) - https://docs.ataccama.com/one/latest/data-stories/data-protection-classification-in-data-stories.html: https://docs.ataccama.com/one/latest/data-stories/data-protection-classification-in-data-stories.html (read 13 Nov 2026) - https://docs.ataccama.com/one/latest/reports/reports-from-power-bi.html: https://docs.ataccama.com/one/latest/reports/reports-from-power-bi.html (read 13 Nov 2026) - https://docs.atlan.com/product/capabilities/lineage/how-tos/propagate-metadata-through-lineage: https://docs.atlan.com/product/capabilities/lineage/how-tos/propagate-metadata-through-lineage (read 13 Nov 2026) - https://docs.atlan.com/llms/connectors/tableau/what-does-atlan-crawl-from-tableau/llms.txt: https://docs.atlan.com/llms/connectors/tableau/what-does-atlan-crawl-from-tableau/llms.txt (read 13 Nov 2026) - https://www.collibra.com/products/data-lineage: https://www.collibra.com/products/data-lineage (read 13 Nov 2026) - https://docs.databricks.com/aws/en/data-governance/unity-catalog/external-lineage: https://docs.databricks.com/aws/en/data-governance/unity-catalog/external-lineage (read 13 Nov 2026) - https://docs.databricks.com/aws/en/data-governance/unity-catalog/data-lineage: https://docs.databricks.com/aws/en/data-governance/unity-catalog/data-lineage (read 13 Nov 2026) - https://docs.datahub.com/docs/automations/glossary-term-propagation: https://docs.datahub.com/docs/automations/glossary-term-propagation (read 13 Nov 2026) - https://docs.datahub.com/docs/features/feature-guides/lineage: https://docs.datahub.com/docs/features/feature-guides/lineage (read 13 Nov 2026) - https://docs.euno.ai/sources/data-security/cyera-integration/cyera-integration-use-cases.md: https://docs.euno.ai/sources/data-security/cyera-integration/cyera-integration-use-cases.md (read 13 Nov 2026) - https://docs.euno.ai/sources/data-security/bigid-integration/bigid-integration-use-cases.md: https://docs.euno.ai/sources/data-security/bigid-integration/bigid-integration-use-cases.md (read 13 Nov 2026) - https://documentation.immuta.com/saas/configuration/application-configuration/how-to-guides/bi-tools/tableau.md: https://documentation.immuta.com/saas/configuration/application-configuration/how-to-guides/bi-tools/tableau.md (read 13 Nov 2026) - https://documentation.immuta.com/saas/configuration/application-configuration/how-to-guides/bi-tools/power-bi.md: https://documentation.immuta.com/saas/configuration/application-configuration/how-to-guides/bi-tools/power-bi.md (read 13 Nov 2026) - https://learn.microsoft.com/purview/register-scan-power-bi-tenant: https://learn.microsoft.com/purview/register-scan-power-bi-tenant (read 13 Nov 2026) - https://learn.microsoft.com/power-bi/enterprise/service-security-sensitivity-label-downstream-inheritance: https://learn.microsoft.com/power-bi/enterprise/service-security-sensitivity-label-downstream-inheritance (read 13 Nov 2026) - https://learn.microsoft.com/power-bi/enterprise/service-security-sensitivity-label-overview: https://learn.microsoft.com/power-bi/enterprise/service-security-sensitivity-label-overview (read 13 Nov 2026) - https://developer.onetrust.com/onetrust/llms.txt: https://developer.onetrust.com/onetrust/llms.txt (read 13 Nov 2026) - https://docs.privacera.com/data-security/connectors/overview/index.html: https://docs.privacera.com/data-security/connectors/overview/index.html (read 13 Nov 2026) - https://docs.secoda.co/features/data-lineage.md: https://docs.secoda.co/features/data-lineage.md (read 13 Nov 2026) - https://securiti.ai/what-is-data-lineage/: https://securiti.ai/what-is-data-lineage/ (read 13 Nov 2026) - https://web.archive.org/web/20260715110406/https://docs.selectstar.com/llms-full.txt: https://web.archive.org/web/20260715110406/https://docs.selectstar.com/llms-full.txt (read 13 Nov 2026) - https://www.selectstar.com/product/data-lineage: https://www.selectstar.com/product/data-lineage (read 13 Nov 2026) - https://docs.snowflake.com/en/user-guide/snowflake-horizon/connectors/tableau: https://docs.snowflake.com/en/user-guide/snowflake-horizon/connectors/tableau (read 13 Nov 2026) Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/exposure-map/report/ --- # 0 of 16 tools document who opened the report with a sensitive field EXPOSURE MAP, BY STAGE, read 13 Nov 2026 **The short answer.** At the viewer stage, 0 of 16 tools document it, 14 are partial and 2 show none found on 13 Nov 2026. Who could see a report and who did see it are different records. None found means nothing was found in the documentation read, not that the feature is missing. The viewer is the person who opened a report or ran a query. A tool covers this stage when it shows viewers per report or per asset from usage or access logs, not only the permission list. Documented here means the documentation shows viewers per report or asset, drawn from usage or access logs. Partial means it shows query-log users but not BI viewers, or counts views without naming viewers, or states another limit. ## Documented - None of the 16 on 13 Nov 2026. ## Partial - [Euno](/platforms/euno/), 67.0: Euno docs say Tableau impression records give counts and distinct users per resource over 14, 30 and 60 days. [Source](https://docs.euno.ai/using-euno/usage-optimization/tableau-usage-data.md?utm_source=aidatagovernancetools.com&utm_medium=referral&utm_campaign=map), read 13 Nov 2026. - [Atlan](/platforms/atlan/), 65.5: Atlan computes a popularity score from distinct users and read queries over the last 30 days for supported sources. [Source](https://docs.atlan.com/llms/catalog/usage-and-popularity/interpret-usage-metrics/llms.txt), read 13 Nov 2026. - [DataHub](/platforms/datahub/), 61.0: The Looker source docs say it can pull historical dashboard usage from Looker system activity. [Source](https://docs.datahub.com/docs/generated/ingestion/sources/looker), read 13 Nov 2026. - [Snowflake Horizon](/platforms/snowflake/), 55.5: Snowflake documents ACCESS_HISTORY, a view of object and column access by user, kept for 365 days (Enterprise Edition). [Source](https://docs.snowflake.com/en/sql-reference/account-usage/access_history.md), read 13 Nov 2026. - [Databricks Unity Catalog](/platforms/databricks/), 55.0: Databricks logs AI/BI dashboard view events in the audit log, including a user accessing the published version of a dashboard. [Source](https://docs.databricks.com/aws/en/admin/account-settings/audit-logs), read 13 Nov 2026. - [Microsoft Purview](/platforms/microsoft-purview/), 54.5: Microsoft says the Power BI activity log records who took what action on which item, exposed through the ActivityEvents REST API. [Source](https://learn.microsoft.com/power-bi/enterprise/service-admin-auditing), read 13 Nov 2026. - [Alation](/platforms/alation/), 54.0: Alation docs say Tableau report popularity comes from Tableau view counts, which count views but do not name viewers. [Source](https://documentation.alation.com/en/latest/OpenConnectorFramework/BIConnectors/TableauOCFConnector/TableauOCFPopularity.md), read 13 Nov 2026. - [Select Star](/platforms/select-star/), 53.5: Select Star docs say a table's Top Users split into table users by query count and dashboard users by views or queries of directly downstream dashboards. [Source](https://web.archive.org/web/20260715110406/https://docs.selectstar.com/llms-full.txt), read 13 Nov 2026. - [Secoda](/platforms/secoda/), 47.5: Secoda docs say a catalog resource shows the number of queries run and its frequent users. [Source](https://docs.secoda.co/features/popularity.md), read 13 Nov 2026. - [Collibra](/platforms/collibra/), 46.5: Collibra docs say Usage Analytics shows behavioral data about users and popular resources inside Collibra; the page does not mention BI reports. [Source](https://productresources.collibra.com/docs/collibra/latest/Content/UsageAnalytics/to_usage-analytics.htm), read 13 Nov 2026. - [Immuta](/platforms/immuta/), 45.0: Immuta says its universal audit model records query, authentication, policy, project and tag events with a consistent structure. [Source](https://documentation.immuta.com/saas/govern/detect-introduction/index.md), read 13 Nov 2026. - [Informatica](/platforms/informatica/), 30.0: Informatica says CDAM operational logging records who, what, when and why of data access in platforms such as Snowflake (data access, not report viewers). [Source](https://www.informatica.com/blogs/how-idmc-supports-native-security-controls-in-snowflake.html), read 13 Nov 2026. - [Privacera](/platforms/privacera/), 30.0: Access audits record who accessed what, whether allowed or denied, at table/column/path level across integrated platforms, with tags used in the decision. [Source](https://docs.privacera.com/data-security/user-guide/access-management/audits/access_audits.html), read 13 Nov 2026. - [Securiti](/platforms/securiti/), 29.5: Securiti says it shows who has data access at file and table level using a graph. [Source](https://securiti.ai/products/access-intelligence/), read 13 Nov 2026. ## None found - [Ataccama ONE](/platforms/ataccama/), 41.5: none found on 13 Nov 2026. - [OneTrust](/platforms/onetrust/), 26.5: none found on 13 Nov 2026. ## Verdict by situation - **A regulated field** ([a governance lead who must show where a regulated field ends up](/best-for/regulated-field/)): Atlan and Euno tie at 68.5. Atlan and Euno tie on total: Atlan is ahead on Acts on it (7 to 5), Euno is ahead on Carries classification downstream (8 to 7). Atlan and Euno tie at 68.5 on total. The published tie rule (higher score on the heaviest criterion, then by name) puts Atlan ahead: the two tie on Follows sensitive data into BI too, so the name decides. - **Agents on analytics** ([a company connecting AI agents to its analytics data this year](/best-for/agents-on-analytics/)): Euno leads at 66.0, ahead of Atlan at 65.0. Euno leads on Price transparency (4 to 0) and Carries classification downstream (8 to 7), while Atlan is ahead on Acts on it (7 to 5). - **A Microsoft estate** ([a Microsoft estate: Fabric, Power BI and Purview](/best-for/microsoft-estate/)): Atlan leads at 68.5, ahead of Euno at 67.5. Atlan leads on Acts on it (7 to 5), while Euno is ahead on Carries classification downstream (8 to 7). - **A mixed stack** ([a mixed stack: Snowflake or Databricks with dbt and two or more BI tools](/best-for/mixed-stack/)): Euno leads at 68.5, ahead of Atlan at 65.5. Euno leads on Carries classification downstream (8 to 7) and Price transparency (4 to 0), while Atlan is ahead on Acts on it (7 to 5). - **A lean team** ([a lean data team with no governance hire](/best-for/lean-team/)): Euno leads at 62.5, ahead of Atlan at 59.0. Euno leads on Price transparency (4 to 0) and Carries classification downstream (8 to 7), while Atlan is ahead on Acts on it (7 to 5). ## Sources - https://documentation.alation.com/en/latest/OpenConnectorFramework/BIConnectors/TableauOCFConnector/TableauOCFPopularity.md: https://documentation.alation.com/en/latest/OpenConnectorFramework/BIConnectors/TableauOCFConnector/TableauOCFPopularity.md (read 13 Nov 2026) - https://docs.ataccama.com/: https://docs.ataccama.com/ (read 13 Nov 2026) - https://docs.atlan.com/llms/catalog/usage-and-popularity/interpret-usage-metrics/llms.txt: https://docs.atlan.com/llms/catalog/usage-and-popularity/interpret-usage-metrics/llms.txt (read 13 Nov 2026) - https://docs.atlan.com/llms/connectors/microsoft-power-bi/mine-microsoft-power-bi/llms.txt: https://docs.atlan.com/llms/connectors/microsoft-power-bi/mine-microsoft-power-bi/llms.txt (read 13 Nov 2026) - https://docs.atlan.com/llms/platform/atlan-mcp-overview/mcp-asset-attributes/llms.txt: https://docs.atlan.com/llms/platform/atlan-mcp-overview/mcp-asset-attributes/llms.txt (read 13 Nov 2026) - https://productresources.collibra.com/docs/collibra/latest/Content/UsageAnalytics/to_usage-analytics.htm: https://productresources.collibra.com/docs/collibra/latest/Content/UsageAnalytics/to_usage-analytics.htm (read 13 Nov 2026) - https://docs.databricks.com/aws/en/admin/account-settings/audit-logs: https://docs.databricks.com/aws/en/admin/account-settings/audit-logs (read 13 Nov 2026) - https://docs.databricks.com/aws/en/admin/system-tables/query-history: https://docs.databricks.com/aws/en/admin/system-tables/query-history (read 13 Nov 2026) - https://docs.databricks.com/aws/en/admin/system-tables/: https://docs.databricks.com/aws/en/admin/system-tables/ (read 13 Nov 2026) - https://docs.datahub.com/docs/generated/ingestion/sources/looker: https://docs.datahub.com/docs/generated/ingestion/sources/looker (read 13 Nov 2026) - https://docs.euno.ai/using-euno/usage-optimization/tableau-usage-data.md: https://docs.euno.ai/using-euno/usage-optimization/tableau-usage-data.md (read 13 Nov 2026) - https://docs.euno.ai/using-euno/usage-optimization/power-bi-usage-data.md: https://docs.euno.ai/using-euno/usage-optimization/power-bi-usage-data.md (read 13 Nov 2026) - https://docs.euno.ai/sources/data-security/cyera-integration/cyera-integration-use-cases.md: https://docs.euno.ai/sources/data-security/cyera-integration/cyera-integration-use-cases.md (read 13 Nov 2026) - https://documentation.immuta.com/saas/govern/detect-introduction/index.md: https://documentation.immuta.com/saas/govern/detect-introduction/index.md (read 13 Nov 2026) - https://documentation.immuta.com/saas/: https://documentation.immuta.com/saas/ (read 13 Nov 2026) - https://www.informatica.com/blogs/how-idmc-supports-native-security-controls-in-snowflake.html: https://www.informatica.com/blogs/how-idmc-supports-native-security-controls-in-snowflake.html (read 13 Nov 2026) - https://learn.microsoft.com/power-bi/enterprise/service-admin-auditing: https://learn.microsoft.com/power-bi/enterprise/service-admin-auditing (read 13 Nov 2026) - https://learn.microsoft.com/purview/: https://learn.microsoft.com/purview/ (read 13 Nov 2026) - https://developer.onetrust.com/onetrust/llms.txt: https://developer.onetrust.com/onetrust/llms.txt (read 13 Nov 2026) - https://www.onetrust.com/solutions/data-use-governance/: https://www.onetrust.com/solutions/data-use-governance/ (read 13 Nov 2026) - https://docs.privacera.com/data-security/user-guide/access-management/audits/access_audits.html: https://docs.privacera.com/data-security/user-guide/access-management/audits/access_audits.html (read 13 Nov 2026) - https://docs.privacera.com/data-security/user-guide/access-management/audits/index.html: https://docs.privacera.com/data-security/user-guide/access-management/audits/index.html (read 13 Nov 2026) - https://docs.secoda.co/features/popularity.md: https://docs.secoda.co/features/popularity.md (read 13 Nov 2026) - https://docs.secoda.co/integrations/data-visualization-tools/power-bi/metadata-extracted.md: https://docs.secoda.co/integrations/data-visualization-tools/power-bi/metadata-extracted.md (read 13 Nov 2026) - https://securiti.ai/products/access-intelligence/: https://securiti.ai/products/access-intelligence/ (read 13 Nov 2026) - https://web.archive.org/web/20260715110406/https://docs.selectstar.com/llms-full.txt: https://web.archive.org/web/20260715110406/https://docs.selectstar.com/llms-full.txt (read 13 Nov 2026) - https://docs.snowflake.com/en/sql-reference/account-usage/access_history.md: https://docs.snowflake.com/en/sql-reference/account-usage/access_history.md (read 13 Nov 2026) - https://docs.snowflake.com/en/user-guide/snowflake-horizon/connectors/tableau: https://docs.snowflake.com/en/user-guide/snowflake-horizon/connectors/tableau (read 13 Nov 2026) Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/exposure-map/viewer/ --- # 6 of 16 tools document the agent that was told a sensitive field EXPOSURE MAP, BY STAGE, read 13 Nov 2026 **The short answer.** At the agent stage, 6 of 16 tools document it (Atlan, DataHub, Snowflake Horizon, Databricks Unity Catalog and others), 10 are partial and 0 show none found on 13 Nov 2026. Agent calls are the newest record and the one regulators ask about next. The agent is the AI assistant or MCP client that received data or context. A tool covers this stage when it records or controls what an agent was told, per call and per person asking. Documented here means the documentation shows per-call logging or per-person control of what an agent receives. Partial means it shows an agent log without the person behind it, or control for one agent path only, or states another limit. ## Documented - [Atlan](/platforms/atlan/), 65.5: Atlan says MCP forwards the caller's identity so the same persona, role and domain policies as the UI apply to every tool call. [Source](https://docs.atlan.com/product/capabilities/atlan-ai/references/mcp-security), read 13 Nov 2026. - [DataHub](/platforms/datahub/), 61.0: DataHub docs say Cloud admins can create scoped MCP servers with their own URL, hidden tools, custom instructions and a saved View; this needs the Context add-on. [Source](https://docs.datahub.com/docs/features/feature-guides/scoped-mcp-servers), read 13 Nov 2026. - [Snowflake Horizon](/platforms/snowflake/), 55.5: Snowflake says that when an AI agent queries data, the role's access control, masking and row-access policies are enforced in the query engine, and metadata access is managed separately. [Source](https://docs.snowflake.com/en/user-guide/snowflake-horizon/horizon-context.md), read 13 Nov 2026. - [Databricks Unity Catalog](/platforms/databricks/), 55.0: Databricks says row filters and column masks defined in Unity Catalog are enforced per user automatically in a Genie Agent, regardless of how it is shared. [Source](https://docs.databricks.com/aws/en/genie/set-up), read 13 Nov 2026. - [Alation](/platforms/alation/), 54.0: Alation docs say agents and tools hold no data permissions of their own and act as the caller on each run. [Source](https://documentation.alation.com/en/latest/agentstudio/security/identity-and-permissions.md), read 13 Nov 2026. - [Securiti](/platforms/securiti/), 29.5: Securiti says its copilot respects source file entitlements at ingestion and at user consumption. [Source](https://securiti.ai/gencore/safe-enterprise-ai-copilot/), read 13 Nov 2026. ## Partial - [Euno](/platforms/euno/), 67.0: Euno docs say Euno MCP uses the active persona to determine what data and actions are available. [Source](https://docs.euno.ai/ai/mcp-setup.md?utm_source=aidatagovernancetools.com&utm_medium=referral&utm_campaign=map), read 13 Nov 2026. - [Microsoft Purview](/platforms/microsoft-purview/), 54.5: Microsoft says supported AI apps use existing access controls so data is never returned to a user, or used by the LLM, if that user lacks access. [Source](https://learn.microsoft.com/purview/ai-microsoft-purview), read 13 Nov 2026. - [Select Star](/platforms/select-star/), 53.5: Select Star docs say the Ask AI chatbot sees all data assets by default, and admins can narrow it by data source, schema or folder for the whole instance. [Source](https://web.archive.org/web/20260715110406/https://docs.selectstar.com/llms-full.txt), read 13 Nov 2026. - [Secoda](/platforms/secoda/), 47.5: Secoda docs say its AI follows team-based permissions: a user asking about a team they are not in gets no results. [Source](https://docs.secoda.co/features/ai-assistant/security.md), read 13 Nov 2026. - [Collibra](/platforms/collibra/), 46.5: The chip README says tools work with the default scopes of any authenticated Collibra user, and a permission error means the connecting user lacks a scope such as dgc.ai-copilot or dgc.classify. [Source](https://github.com/collibra/chip), read 13 Nov 2026. - [Immuta](/platforms/immuta/), 45.0: Immuta says its agentic data access is a centralized authorization framework governing how AI agents and LLMs interact with sensitive data. [Source](https://documentation.immuta.com/saas/agentic-data-access/introduction.md), read 13 Nov 2026. - [Ataccama ONE](/platforms/ataccama/), 41.5: Ataccama docs say each MCP request runs under the user's own identity. [Source](https://docs.ataccama.com/one/latest/generative-ai/mcp-dqc.html), read 13 Nov 2026. - [Informatica](/platforms/informatica/), 30.0: Informatica says governance travels with the agent in its headless design, with security and privacy controls built into the infrastructure. [Source](https://www.informatica.com/headless.html), read 13 Nov 2026. - [Privacera](/platforms/privacera/), 30.0: Trust3 AI Governance docs say it discovers agents on Databricks, Microsoft Copilot Studio and Azure Foundry, scores them and tracks policy violations. [Source](https://docs.trust3.ai/get-started/overview.html), read 13 Nov 2026. - [OneTrust](/platforms/onetrust/), 26.5: OneTrust says its AI Governance module governs agents with defined purpose, permissions and allowed actions across MCP-enabled environments. [Source](https://www.onetrust.com/products/ai-governance/), read 13 Nov 2026. ## None found - None of the 16 on 13 Nov 2026. ## Verdict by situation - **A regulated field** ([a governance lead who must show where a regulated field ends up](/best-for/regulated-field/)): Atlan and Euno tie at 68.5. Atlan and Euno tie on total: Atlan is ahead on Acts on it (7 to 5), Euno is ahead on Carries classification downstream (8 to 7). Atlan and Euno tie at 68.5 on total. The published tie rule (higher score on the heaviest criterion, then by name) puts Atlan ahead: the two tie on Follows sensitive data into BI too, so the name decides. - **Agents on analytics** ([a company connecting AI agents to its analytics data this year](/best-for/agents-on-analytics/)): Euno leads at 66.0, ahead of Atlan at 65.0. Euno leads on Price transparency (4 to 0) and Carries classification downstream (8 to 7), while Atlan is ahead on Acts on it (7 to 5). - **A Microsoft estate** ([a Microsoft estate: Fabric, Power BI and Purview](/best-for/microsoft-estate/)): Atlan leads at 68.5, ahead of Euno at 67.5. Atlan leads on Acts on it (7 to 5), while Euno is ahead on Carries classification downstream (8 to 7). - **A mixed stack** ([a mixed stack: Snowflake or Databricks with dbt and two or more BI tools](/best-for/mixed-stack/)): Euno leads at 68.5, ahead of Atlan at 65.5. Euno leads on Carries classification downstream (8 to 7) and Price transparency (4 to 0), while Atlan is ahead on Acts on it (7 to 5). - **A lean team** ([a lean data team with no governance hire](/best-for/lean-team/)): Euno leads at 62.5, ahead of Atlan at 59.0. Euno leads on Price transparency (4 to 0) and Carries classification downstream (8 to 7), while Atlan is ahead on Acts on it (7 to 5). ## Sources - https://documentation.alation.com/en/latest/agentstudio/security/identity-and-permissions.md: https://documentation.alation.com/en/latest/agentstudio/security/identity-and-permissions.md (read 13 Nov 2026) - https://docs.ataccama.com/one/latest/generative-ai/mcp-dqc.html: https://docs.ataccama.com/one/latest/generative-ai/mcp-dqc.html (read 13 Nov 2026) - https://docs.atlan.com/product/capabilities/atlan-ai/references/mcp-security: https://docs.atlan.com/product/capabilities/atlan-ai/references/mcp-security (read 13 Nov 2026) - https://docs.atlan.com/llms/platform/agents/monitor-your-ai-agents-with-atlan/llms.txt: https://docs.atlan.com/llms/platform/agents/monitor-your-ai-agents-with-atlan/llms.txt (read 13 Nov 2026) - https://github.com/collibra/chip: https://github.com/collibra/chip (read 13 Nov 2026) - https://docs.databricks.com/aws/en/genie/set-up: https://docs.databricks.com/aws/en/genie/set-up (read 13 Nov 2026) - https://docs.databricks.com/aws/en/agents/mcp-tools/authentication-networking: https://docs.databricks.com/aws/en/agents/mcp-tools/authentication-networking (read 13 Nov 2026) - https://docs.databricks.com/aws/en/ai-gateway/govern-mcp-service: https://docs.databricks.com/aws/en/ai-gateway/govern-mcp-service (read 13 Nov 2026) - https://docs.datahub.com/docs/features/feature-guides/scoped-mcp-servers: https://docs.datahub.com/docs/features/feature-guides/scoped-mcp-servers (read 13 Nov 2026) - https://docs.datahub.com/docs/features/feature-guides/mcp: https://docs.datahub.com/docs/features/feature-guides/mcp (read 13 Nov 2026) - https://docs.euno.ai/ai/mcp-setup.md: https://docs.euno.ai/ai/mcp-setup.md (read 13 Nov 2026) - https://documentation.immuta.com/saas/agentic-data-access/introduction.md: https://documentation.immuta.com/saas/agentic-data-access/introduction.md (read 13 Nov 2026) - https://www.informatica.com/headless.html: https://www.informatica.com/headless.html (read 13 Nov 2026) - https://www.informatica.com/blogs/powering-agentic-workflows-on-aws-with-informatica-mcps.html: https://www.informatica.com/blogs/powering-agentic-workflows-on-aws-with-informatica-mcps.html (read 13 Nov 2026) - https://learn.microsoft.com/purview/ai-microsoft-purview: https://learn.microsoft.com/purview/ai-microsoft-purview (read 13 Nov 2026) - https://learn.microsoft.com/power-bi/developer/mcp/mcp-servers-overview: https://learn.microsoft.com/power-bi/developer/mcp/mcp-servers-overview (read 13 Nov 2026) - https://learn.microsoft.com/purview/ai-agents: https://learn.microsoft.com/purview/ai-agents (read 13 Nov 2026) - https://www.onetrust.com/products/ai-governance/: https://www.onetrust.com/products/ai-governance/ (read 13 Nov 2026) - https://developer.onetrust.com/onetrust/docs/ai-guard.md: https://developer.onetrust.com/onetrust/docs/ai-guard.md (read 13 Nov 2026) - https://github.com/onetrust-oss/ai-guard-sdk: https://github.com/onetrust-oss/ai-guard-sdk (read 13 Nov 2026) - https://developer.onetrust.com/onetrust/reference/mcp.md: https://developer.onetrust.com/onetrust/reference/mcp.md (read 13 Nov 2026) - https://developer.onetrust.com/onetrust/docs/ai-guard-authentication.md: https://developer.onetrust.com/onetrust/docs/ai-guard-authentication.md (read 13 Nov 2026) - https://developer.onetrust.com/onetrust/docs/ai-guard-faq.md: https://developer.onetrust.com/onetrust/docs/ai-guard-faq.md (read 13 Nov 2026) - https://docs.trust3.ai/get-started/overview.html: https://docs.trust3.ai/get-started/overview.html (read 13 Nov 2026) - https://trust3.ai/: https://trust3.ai/ (read 13 Nov 2026) - https://docs.trust3.ai/how-to-guides/mcp-configuration.html: https://docs.trust3.ai/how-to-guides/mcp-configuration.html (read 13 Nov 2026) - https://docs.secoda.co/features/ai-assistant/security.md: https://docs.secoda.co/features/ai-assistant/security.md (read 13 Nov 2026) - https://docs.secoda.co/resource-and-metadata-management/tags/auto-pii-tagging.md: https://docs.secoda.co/resource-and-metadata-management/tags/auto-pii-tagging.md (read 13 Nov 2026) - https://securiti.ai/gencore/safe-enterprise-ai-copilot/: https://securiti.ai/gencore/safe-enterprise-ai-copilot/ (read 13 Nov 2026) Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/exposure-map/agent/ --- # Five questions give a shortlist of five tools, each with its reason THE FINDER, read 13 Nov 2026 **The short answer.** The Finder asks five questions: your stack, whether the data is regulated, whether agents are on it, who owns governance and whether a DSPM is in place. It blends the matching situation weights, scores all 16 tools on the blend and returns five with a reason each. Nothing is stored or sent. **Where Euno is behind.** Euno is not a policy engine or a DSPM: it reads metadata only, so it does not scan data contents or mask at the warehouse, which leaves it behind Atlan on acting on findings (5 to 7), and it publishes no dollar prices. Pick an answer for each question. The shortlist updates as you change them, and it uses the same scores and the same weights as the index. Without JavaScript, read the table below the form, which gives the shortlist for each starting point. The Finder is a form of five questions on the web page; its logic and the shortlist for each starting point are printed below. ## The shortlist for each starting point | Starting point | First | Second | Third | | --- | --- | --- | --- | | The site weights | Euno 67.0 | Atlan 65.5 | DataHub 61.0 | | [A governance lead who must show where a regulated field ends up](/best-for/regulated-field/) | Atlan 68.5 | Euno 68.5 | DataHub 63.0 | | [A company connecting AI agents to its analytics data this year](/best-for/agents-on-analytics/) | Euno 66.0 | Atlan 65.0 | DataHub 59.5 | | [A Microsoft estate: Fabric, Power BI and Purview](/best-for/microsoft-estate/) | Atlan 68.5 | Euno 67.5 | DataHub 61.0 | | [A mixed stack: Snowflake or Databricks with dbt and two or more BI tools](/best-for/mixed-stack/) | Euno 68.5 | Atlan 65.5 | DataHub 61.5 | | [A lean data team with no governance hire](/best-for/lean-team/) | Euno 62.5 | Atlan 59.0 | Snowflake Horizon 59.0 | What the Finder returns when one situation applies, or none. Several answers blend their situation weights. ## How the Finder decides - A Microsoft estate answer adds the Microsoft estate situation weights. A mixed stack answer adds the mixed stack weights. The other two stack answers add nothing. - Regulated data adds the regulated field weights. Agents in production or planned adds the agents on analytics weights. A data team with no governance hire adds the lean team weights. - The weights of every situation that applies are averaged, criterion by criterion. If none applies, the site weights are used. - Each tool's total is its eight scores multiplied by the blended weights and divided by 10. Ties go to the higher score on the criterion with the largest blended weight, then to the name. - The five highest totals are shown. The reason for each names a criterion where it beats the tool ranked just below it, preferring criteria with a blended weight of 10 or more and the largest weighted gap; if it beats that tool on none, it names its own top score. A tie with the next tool is stated, and so are the Power BI, BI-tool and DSPM notes when your answers make them matter. ## What each answer changes - **Which stack do you run?:** Chooses the Microsoft estate or mixed stack weights, or neither. - **Is the data regulated (financial, health, telecom, payment cards)?:** Adds the regulated field weights, which put 35 on following the field into BI. - **Are AI agents on your analytics data?:** Adds the agents on analytics weights, which put 40 on controlling what an agent is told. - **Who owns governance?:** A data team with no governance hire adds the lean team weights; a governance or security team adds nothing. - **Is a DSPM in place (Cyera, BigID, Varonis or similar)?:** Changes no weight. It adds a note on whether each tool names Cyera, BigID or Varonis among the security tools it reads. ## What the Finder does not do The Finder ranks documented behavior on 13 Nov 2026. It does not know your licenses, your contracts or your regulator, and it cannot say that a tool is a fit. It is a shortlist to test, in the order the weights give. The page runs in your browser. The answers are not stored, not sent and not logged, and closing the tab discards them. {"sitNames":{"regulated-field":"A governance lead who must show where a regulated field ends up","agents-on-analytics":"A company connecting AI agents to its analytics data this year","microsoft-estate":"A Microsoft estate: Fabric, Power BI and Purview","mixed-stack":"A mixed stack: Snowflake or Databricks with dbt and two or more BI tools","lean-team":"A lean data team with no governance hire"},"crit":["bi_follow","agent_scope","viewers","propagation","action","coverage","evidence","price"],"names":["Follows sensitive data into BI","Controls what an agent is told","Shows who actually saw it","Carries classification downstream","Acts on it","Coverage of the stack","Evidence beyond the vendor","Price transparency"],"site":[25,20,15,15,10,5,5,5],"sit":{"regulated-field":[35,5,20,20,10,5,5,0],"agents-on-analytics":[15,40,15,10,10,5,0,5],"microsoft-estate":[30,10,15,20,15,10,0,0],"mixed-stack":[30,10,10,20,5,20,0,5],"lean-team":[20,10,10,15,20,5,5,15]},"tools":[{"slug":"alation","name":"Alation","s":[7,6,4,4,4,5,8,4],"wh":["Snowflake","Databricks","Google BigQuery","Amazon Redshift","Azure Synapse","Oracle","SQL Server","PostgreSQL","Teradata","SAP HANA","Amazon Athena"],"bi":["Tableau","Power BI","Looker","AWS QuickSight","Qlik Sense Cloud"],"sec":[]},{"slug":"ataccama","name":"Ataccama ONE","s":[5,5,1,3,5,4,8,4],"wh":["Snowflake","Databricks","BigQuery","Amazon Redshift","Azure Synapse Analytics","Amazon Athena","Teradata","Oracle"],"bi":["Tableau","Power BI","Power BI Report Server"],"sec":[]},{"slug":"atlan","name":"Atlan","s":[7,7,6,7,7,7,8,0],"wh":["Snowflake","Databricks","Google BigQuery","Amazon Redshift","Microsoft Azure Synapse Analytics","Amazon Athena","Trino","Starburst Enterprise","Teradata","Oracle","PostgreSQL","Microsoft SQL Server","Dremio","Iceberg"],"bi":["Tableau","Microsoft Power BI","Looker","Amazon QuickSight","Qlik Sense Cloud","Sigma","ThoughtSpot","Metabase","Mode","MicroStrategy","Microsoft Fabric","IBM Cognos Analytics","Domo","SAP Analytics Cloud"],"sec":["BigID","Cyera","ALTR","Immuta"]},{"slug":"collibra","name":"Collibra","s":[5,5,3,3,7,6,8,2],"wh":["Snowflake","Databricks Unity Catalog","Google BigQuery","Amazon Redshift","Azure Synapse Analytics","Azure SQL Server","Microsoft SQL Server","Oracle","PostgreSQL","MySQL","Teradata","SAP HANA"],"bi":["Tableau","Power BI","Looker","Qlik","Sigma","ThoughtSpot","Strategy","SSRS-PBRS"],"sec":["Okta","Microsoft Entra ID"]},{"slug":"databricks","name":"Databricks Unity Catalog","s":[4,7,6,5,6,4,9,4],"wh":["Databricks SQL warehouses","Snowflake","BigQuery","AWS Glue","MySQL","PostgreSQL","Salesforce"],"bi":["Tableau","Power BI","Sigma","Databricks AI/BI dashboards"],"sec":[]},{"slug":"datahub","name":"DataHub","s":[8,7,4,6,4,6,9,1],"wh":["Snowflake","BigQuery","Databricks","Redshift"],"bi":["Tableau","Power BI","Looker","Preset"],"sec":[]},{"slug":"euno","name":"Euno","s":[7,7,6,8,5,7,8,4],"wh":["Snowflake","BigQuery","Databricks","Redshift (private preview)","MySQL","SQL Server"],"bi":["Tableau","Looker","Power BI","ThoughtSpot","Sigma","Omni","Cube Core","Salesforce","Hex"],"sec":["Cyera","BigID","Microsoft Purview","Monte Carlo","Elementary","Okta","Google Workspace"]},{"slug":"immuta","name":"Immuta","s":[2,6,5,4,8,5,8,0],"wh":["Snowflake","Databricks Unity Catalog","Databricks Spark","Google BigQuery","Amazon Redshift","Amazon Athena","AWS Lake Formation","Amazon S3","Starburst","Trino","Azure Synapse Analytics","Oracle","SQL Server","Teradata","MySQL","MariaDB","PostgreSQL"],"bi":["Tableau","Power BI"],"sec":["Alation","Atlan","Collibra","Microsoft Purview"]},{"slug":"informatica","name":"Informatica","s":[2,2,3,3,4,3,9,4],"wh":["Snowflake","Databricks (Unity Catalog)","Amazon Redshift","Salesforce Data 360"],"bi":["Tableau","Power BI"],"sec":[]},{"slug":"microsoft-purview","name":"Microsoft Purview","s":[3,6,6,6,7,5,8,7],"wh":["Snowflake","Azure Synapse Analytics","Azure SQL Database","Azure Databricks Unity Catalog","Azure Databricks Hive Metastore","Google BigQuery","Amazon Redshift","Oracle","Teradata","SQL Server"],"bi":["Power BI","Looker"],"sec":["Microsoft Purview Information Protection","Microsoft Purview DLP","Microsoft Defender for Cloud Apps"]},{"slug":"onetrust","name":"OneTrust","s":[0,3,3,3,6,3,5,3],"wh":["Snowflake","Databricks Unity Catalog","Amazon Redshift","Amazon Athena","Amazon RDS for SQL Server","Google BigQuery","Azure Databricks","Teradata"],"bi":[],"sec":["Palo Alto Networks"]},{"slug":"privacera","name":"Privacera","s":[0,2,4,4,8,4,8,0],"wh":["Snowflake","Databricks Unity Catalog","Databricks SQL","Google BigQuery","AWS Redshift","AWS Athena","Azure Synapse","Trino","Starburst","Dremio","Oracle","Microsoft SQL Server","PostgreSQL","MySQL","Vertica"],"bi":[],"sec":["Collibra","Okta","Azure AD","LDAP","Apache Ranger"]},{"slug":"secoda","name":"Secoda","s":[6,4,3,4,5,6,9,3],"wh":["Snowflake","BigQuery","Databricks","Redshift","Azure Synapse","ClickHouse","MotherDuck","Apache Hive"],"bi":["Tableau","Looker","Looker Studio","Power BI","Metabase","Mode","Sigma","ThoughtSpot","QuickSight","Superset","Hex","Omni","MicroStrategy One"],"sec":["Cyera"]},{"slug":"securiti","name":"Securiti","s":[1,4,3,3,6,2,5,1],"wh":["Snowflake","Google BigQuery","Databricks"],"bi":["Tableau"],"sec":["Microsoft security center (sensitivity labels)"]},{"slug":"select-star","name":"Select Star","s":[7,2,6,6,5,6,9,3],"wh":["Snowflake","Databricks","BigQuery","Amazon Redshift","PostgreSQL","Microsoft SQL Server (beta)","MySQL (beta)","Oracle (beta)","Salesforce (beta)","IBM Db2 (beta)","AWS Glue"],"bi":["Tableau","Microsoft Power BI","Looker","Looker Studio","Mode","Sigma","Sisense / Periscope","Metabase","ThoughtSpot","Amazon QuickSight","Hex","Salesforce CRM Analytics (beta)"],"sec":[]},{"slug":"snowflake","name":"Snowflake Horizon","s":[5,6,4,5,7,5,9,7],"wh":["Snowflake","Amazon Redshift","BigQuery","Databricks","IBM Db2","MySQL","Oracle","PostgreSQL","SQL Server"],"bi":["Amazon QuickSight","Hex","Looker","Metabase","Microsoft Power BI","Omni","Sigma","Tableau Cloud","Tableau Server","ThoughtSpot"],"sec":[]}]}(function(){let D=JSON.parse(document.getElementById('nk-finder-data').textContent);function finderRank(D, a) { let picks = []; if (a.stack === 'microsoft') picks.push('microsoft-estate'); else if (a.stack === 'mixed') picks.push('mixed-stack'); if (a.regulated === 'yes') picks.push('regulated-field'); if (a.agents === 'yes') picks.push('agents-on-analytics'); if (a.owner === 'data-team') picks.push('lean-team'); let w = D.crit.map(function (_, i) { return picks.length ? picks.reduce(function (t, k) { return t + D.sit[k][i]; }, 0) / picks.length : D.site[i]; }); let heavy = 0; w.forEach(function (x, i) { if (x > w[heavy]) heavy = i; }); let rows = D.tools.map(function (t) { let total = t.s.reduce(function (acc, x, i) { return acc + x * w[i]; }, 0) / 10; return { t: t, total: Math.round(total * 10) / 10 }; }); rows.sort(function (x, y) { return y.total - x.total || y.t.s[heavy] - x.t.s[heavy] || (x.t.name 0 && (w[i] >= 10 ? 1 : 0) * 1e6 + d > (best >= 0 ? (w[best] >= 10 ? 1 : 0) * 1e6 + bd : 0)) { bd = d; best = i; } }); let top = D.crit.map(function (_, i) { return i; }).sort(function (i, j) { return r.t.s[j] - r.t.s[i] || w[j] - w[i]; })[0]; let why = best >= 0 ? 'Beats ' + nx.t.name + ' on ' + D.names[best] + ' (' + r.t.s[best] + ' to ' + nx.t.s[best] + ' at weight ' + Math.round(w[best]) + ').' : 'Its top score under your weights is ' + D.names[top] + ', ' + r.t.s[top] + ' of 10.'; if (r.total === nx.total) why += ' Tied with ' + nx.t.name + ' at ' + r.total.toFixed(1) + '; the tie goes to the higher score on ' + D.names[heavy] + ', then the name.'; let notes = []; if (a.stack === 'microsoft') notes.push(r.t.bi.some(function (b) { return /power bi/i.test(b); }) ? 'names Power BI as a BI source' : 'names no Power BI source in its evidence on 13 Nov 2026'); if (a.stack === 'mixed') notes.push('names ' + r.t.bi.length + ' BI tools and ' + r.t.wh.length + ' warehouses'); if (a.dspm === 'yes') { let d = r.t.sec.filter(function (b) { return /cyera|bigid|varonis/i.test(b); }); notes.push(d.length ? 'reads classifications from ' + d.join(' and ') : 'names no DSPM among its security sources on 13 Nov 2026'); } return { rank: n + 1, slug: r.t.slug, name: r.t.name, total: r.total, reason: why + (notes.length ? ' It ' + notes.join('; ') + '.' : '') }; }); return { picks: picks, pickNames: picks.map(function (k) { return (D.sitNames && D.sitNames[k]) || k; }), weights: w.map(function (x) { return Math.round(x * 10) / 10; }), top: out }; } let f=document.getElementById('nk-finder'),o=document.getElementById('nk-finder-out');if(!f||!o)return; function run(){let a={};['stack','regulated','agents','owner','dspm'].forEach(function(k){a[k]=f.elements[k].value;});let r=finderRank(D,a); while(o.firstChild)o.removeChild(o.firstChild); let h=document.createElement('p');h.className='nk-key';h.textContent=r.picks.length?'Weights blended from: '+r.pickNames.join('; ')+'.':'No situation applies, so the site weights are used.';o.appendChild(h); let ol=document.createElement('ol');ol.className='nk-short';r.top.forEach(function(x){let li=document.createElement('li');let a1=document.createElement('a');a1.href='/platforms/'+x.slug+'/';a1.textContent=x.name;let b=document.createElement('b');b.textContent=' '+x.total.toFixed(1);li.appendChild(a1);li.appendChild(b);let p=document.createElement('span');p.textContent=' '+x.reason;li.appendChild(p);ol.appendChild(li);});o.appendChild(ol);} f.addEventListener('submit',function(e){e.preventDefault();run();});f.addEventListener('change',run);run();})(); ## Sources - Method: weights and situations: https://aidatagovernancetools.com/method/ (read 13 Nov 2026) - Ranked list, CSV: https://aidatagovernancetools.com/datasets/need-to-know-ranked-list.csv (read 13 Nov 2026) Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/finder/ --- # A financial-services auditor traces a customer field to every dashboard and every user who could open it SECTOR, read 13 Nov 2026 **The short answer.** Auditors of U.S. financial firms read the FTC Safeguards Rule at 16 CFR 314.4 and New York's 23 NYCRR 500.7 and 500.14. Five asks follow from their own wording: who may reach customer data, where the data sits, and what was logged. Each maps to cells of the PII Exposure Map. A financial-services auditor starts with a customer field such as an account number or a tax ID and asks where it ends up. The answer has to run past the warehouse table into the transformation that copies it, the BI field that displays it and the report that carries it. Two rule sets set the frame: the FTC Safeguards Rule for non-bank financial institutions and New York's cybersecurity regulation for firms licensed by its Department of Financial Services. The second half of the walk is about people. The text of both rules talks about authorized users, not only about outsiders, so the evidence is a list of who could open a given report and a log of who did. An AI agent that reads analytics data counts as one more user on that list. The five asks below quote the rules and name the map stages that answer each. ## What an auditor asks - **Which customer information can each authorized user reach, and when did you last review that?** Basis: 16 CFR 314.4(c)(1) calls for "Implementing and periodically reviewing access controls" that "Limit authorized users' access only to customer information" they need to do their jobs. ([16 CFR 314.4 (Cornell LII)](https://www.law.cornell.edu/cfr/text/16/314.4), read 13 Nov 2026). Map stages: [BI field](/exposure-map/bi-field/), [Report](/exposure-map/report/), [Viewer](/exposure-map/viewer/). Show a current list of who can open each report that displays a customer field, and the date of the last review. The BI field, report and viewer cells answer this; 0 of 16 tools document the viewer stage on 13 Nov 2026. - **Do you know where customer data sits across your systems, ranked by importance?** Basis: 16 CFR 314.4(c)(2) says to "Identify and manage the data, personnel, devices, systems, and facilities" that serve business purposes, in line with their relative importance. ([16 CFR 314.4 (Cornell LII)](https://www.law.cornell.edu/cfr/text/16/314.4), read 13 Nov 2026). Map stages: [Warehouse column](/exposure-map/column/), [Transformation](/exposure-map/transformation/). Bring the field inventory: which warehouse columns hold customer data and which transformation models copy them. The column and transformation cells answer this; 14 tools document the column stage and 1 document the transformation stage. - **Can you show a log of what authorized users did with customer information?** Basis: 16 CFR 314.4(c)(8) requires controls "designed to monitor and log the activity of authorized users and detect unauthorized access or use of, or tampering with, customer information." ([16 CFR 314.4(c)(8) (Cornell LII)](https://www.law.cornell.edu/cfr/text/16/314.4), read 13 Nov 2026). Map stages: [Viewer](/exposure-map/viewer/), [Agent](/exposure-map/agent/). Show log lines that name a user or an agent and the report or dataset opened. Warehouse query history covers the database layer only. The viewer and agent cells show whether a tool joins the report view and the agent call to the field. - **Which users can read nonpublic information, and who limited their privileges?** Basis: 23 NYCRR 500.7(a)(1) tells each covered entity to "limit user access privileges to information systems that provide access to nonpublic information to only those necessary to perform the user's job." ([23 NYCRR 500.7 (Cornell LII)](https://www.law.cornell.edu/regulations/new-york/23-NYCRR-500.7), read 13 Nov 2026). Map stages: [Viewer](/exposure-map/viewer/), [Agent](/exposure-map/agent/). Show role and group mappings for the BI tool and for any agent service account, with the approver of each grant. See [who saw it against who could see it](/guides/who-saw-it-against-who-could-see-it/) and [approving an agent's access](/guides/approving-an-agents-access/). - **How do you monitor authorized users of systems that hold nonpublic information?** Basis: 23 NYCRR 500.14(a)(1) requires "risk-based policies, procedures and controls designed to monitor the activity of authorized users." ([23 NYCRR 500.14 (Cornell LII)](https://www.law.cornell.edu/regulations/new-york/23-NYCRR-500.14), read 13 Nov 2026). Map stages: [Report](/exposure-map/report/), [Viewer](/exposure-map/viewer/). Show a recurring review of report-open events for reports that carry nonpublic fields, with exceptions followed up. The report and viewer cells show which tools produce that evidence. ## The map cells that answer these asks These asks need 6 of the six stages: warehouse column, transformation, BI field, report, viewer, agent. None of the 16 tools documents all 6 on 13 Nov 2026; the most is 4, by Alation. | Tool | Warehouse column | Transformation | BI field | Report | Viewer | Agent | Documented | Total | | --- | --- | --- | --- | --- | --- | --- | --- | --- | | [Alation](/platforms/alation/) | documented | partial | documented | documented | partial | documented | 4 of 6 | 54.0 | | [Euno](/platforms/euno/) | documented | partial | documented | documented | partial | partial | 3 of 6 | 67.0 | | [Atlan](/platforms/atlan/) | documented | partial | partial | partial | partial | documented | 2 of 6 | 65.5 | | [Snowflake Horizon](/platforms/snowflake/) | documented | partial | partial | partial | partial | documented | 2 of 6 | 55.5 | | [Databricks Unity Catalog](/platforms/databricks/) | documented | partial | partial | partial | partial | documented | 2 of 6 | 55.0 | | [Microsoft Purview](/platforms/microsoft-purview/) | documented | partial | partial | documented | partial | partial | 2 of 6 | 54.5 | | [Select Star](/platforms/select-star/) | partial | partial | documented | documented | partial | partial | 2 of 6 | 53.5 | | [Informatica](/platforms/informatica/) | documented | documented | partial | none found | partial | partial | 2 of 6 | 30.0 | | [Securiti](/platforms/securiti/) | documented | partial | partial | none found | partial | documented | 2 of 6 | 29.5 | | [DataHub](/platforms/datahub/) | partial | partial | partial | partial | partial | documented | 1 of 6 | 61.0 | | [Secoda](/platforms/secoda/) | documented | partial | partial | partial | partial | partial | 1 of 6 | 47.5 | | [Collibra](/platforms/collibra/) | documented | partial | partial | partial | partial | partial | 1 of 6 | 46.5 | | [Immuta](/platforms/immuta/) | documented | none found | none found | partial | partial | partial | 1 of 6 | 45.0 | | [Ataccama ONE](/platforms/ataccama/) | documented | partial | partial | partial | none found | partial | 1 of 6 | 41.5 | | [Privacera](/platforms/privacera/) | documented | none found | none found | none found | partial | partial | 1 of 6 | 30.0 | | [OneTrust](/platforms/onetrust/) | documented | none found | none found | none found | none found | partial | 1 of 6 | 26.5 | Tools sorted by stages documented, then by the Need to Know total. Read 13 Nov 2026. ## Other sectors - [Healthcare](/sectors/healthcare/) - [SaaS](/sectors/saas/) - [Telecom](/sectors/telecom/) - [Retail](/sectors/retail/) ## Sources - 16 CFR 314.4, Elements (Cornell LII): https://www.law.cornell.edu/cfr/text/16/314.4 (read 13 Nov 2026) - 23 NYCRR 500.7, Access privileges (Cornell LII): https://www.law.cornell.edu/regulations/new-york/23-NYCRR-500.7 (read 13 Nov 2026) - 23 NYCRR 500.14, Monitoring and training (Cornell LII): https://www.law.cornell.edu/regulations/new-york/23-NYCRR-500.14 (read 13 Nov 2026) - 16 CFR 314.4 (eCFR): https://www.ecfr.gov/current/title-16/chapter-I/subchapter-C/part-314/section-314.4 (read 13 Nov 2026) Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/sectors/financial-services/ --- # A healthcare auditor asks which reports show protected health information and which people or programs opened them SECTOR, read 13 Nov 2026 **The short answer.** HIPAA auditors read 45 CFR 164.312 on access control and audit controls, 164.308 on activity review and 164.502 and 164.514 on minimum necessary. Five asks follow, each tied to the Security Rule's own words and to the PII Exposure Map stages that hold the evidence. A HIPAA auditor wants the path of a protected health information field from the system of record to the people who see it. In analytics that means the warehouse column, the model that reshapes it, the dashboard field and the report extract. The Security Rule talks about electronic systems that maintain the data, so a reporting database is in scope the same way the clinical system is. The rule also names software programs next to persons in its access control standard. An AI agent that queries a reporting layer is a software program, and an auditor can ask for its access rights in the same breath as a nurse manager's. The five asks below use the rule text and say which stages of the map carry the proof. ## What an auditor asks - **Who or what has been granted access rights to systems holding ePHI?** Basis: 45 CFR 164.312(a)(1) requires technical policies that "allow access only to those persons or software programs that have been granted access rights." ([45 CFR 164.312(a)(1) (Cornell LII)](https://www.law.cornell.edu/cfr/text/45/164.312), read 13 Nov 2026). Map stages: [Viewer](/exposure-map/viewer/), [Agent](/exposure-map/agent/). List the users, groups and agent identities with access to each report or dataset that carries a PHI field. The viewer and agent cells show whether a tool documents those grants; 6 of 16 tools document the agent stage on 13 Nov 2026. - **What mechanism records and examines activity in systems that use ePHI?** Basis: 45 CFR 164.312(b) requires "mechanisms that record and examine activity in information systems that contain or use electronic protected health information." ([45 CFR 164.312(b) (Cornell LII)](https://www.law.cornell.edu/cfr/text/45/164.312), read 13 Nov 2026). Map stages: [Report](/exposure-map/report/), [Viewer](/exposure-map/viewer/). Show the audit record for a report that carries PHI: who opened it, when and in which tool. The report and viewer cells show which tools tie a viewer to a report. - **How often does someone review the records of system activity?** Basis: 45 CFR 164.308(a)(1)(ii)(D) requires procedures to "regularly review records of information system activity, such as audit logs, access reports, and security incident tracking reports." ([45 CFR 164.308 (Cornell LII)](https://www.law.cornell.edu/cfr/text/45/164.308), read 13 Nov 2026). Map stages: [Viewer](/exposure-map/viewer/), [Agent](/exposure-map/agent/). Show dated review sign-offs and the access reports they used. An access report is only usable if it names the PHI-bearing report and not just the warehouse table; see [access history](/glossary/access-history/). - **How do you limit PHI in a use or request to the minimum necessary?** Basis: 45 CFR 164.502(b) says a covered entity "must make reasonable efforts to limit protected health information to the minimum necessary to accomplish the intended purpose." ([45 CFR 164.502(b) (Cornell LII)](https://www.law.cornell.edu/cfr/text/45/164.502), read 13 Nov 2026). Map stages: [Warehouse column](/exposure-map/column/), [Transformation](/exposure-map/transformation/), [Agent](/exposure-map/agent/). Show masking or removal of PHI columns before they reach a model or an agent's context. The column and transformation cells show where a tool follows the tag; the agent cell shows what an agent is told. - **Which workforce roles need which categories of PHI?** Basis: 45 CFR 164.514(d)(2) requires a covered entity to identify the "persons or classes of persons" who need access and, for each, the categories of PHI needed. ([45 CFR 164.514(d) (Cornell LII)](https://www.law.cornell.edu/cfr/text/45/164.514), read 13 Nov 2026). Map stages: [BI field](/exposure-map/bi-field/), [Report](/exposure-map/report/). Show a role-to-field matrix that matches what each dashboard displays. The BI field and report cells show whether a tool can say which fields a given report exposes. ## The map cells that answer these asks These asks need 6 of the six stages: warehouse column, transformation, BI field, report, viewer, agent. None of the 16 tools documents all 6 on 13 Nov 2026; the most is 4, by Alation. | Tool | Warehouse column | Transformation | BI field | Report | Viewer | Agent | Documented | Total | | --- | --- | --- | --- | --- | --- | --- | --- | --- | | [Alation](/platforms/alation/) | documented | partial | documented | documented | partial | documented | 4 of 6 | 54.0 | | [Euno](/platforms/euno/) | documented | partial | documented | documented | partial | partial | 3 of 6 | 67.0 | | [Atlan](/platforms/atlan/) | documented | partial | partial | partial | partial | documented | 2 of 6 | 65.5 | | [Snowflake Horizon](/platforms/snowflake/) | documented | partial | partial | partial | partial | documented | 2 of 6 | 55.5 | | [Databricks Unity Catalog](/platforms/databricks/) | documented | partial | partial | partial | partial | documented | 2 of 6 | 55.0 | | [Microsoft Purview](/platforms/microsoft-purview/) | documented | partial | partial | documented | partial | partial | 2 of 6 | 54.5 | | [Select Star](/platforms/select-star/) | partial | partial | documented | documented | partial | partial | 2 of 6 | 53.5 | | [Informatica](/platforms/informatica/) | documented | documented | partial | none found | partial | partial | 2 of 6 | 30.0 | | [Securiti](/platforms/securiti/) | documented | partial | partial | none found | partial | documented | 2 of 6 | 29.5 | | [DataHub](/platforms/datahub/) | partial | partial | partial | partial | partial | documented | 1 of 6 | 61.0 | | [Secoda](/platforms/secoda/) | documented | partial | partial | partial | partial | partial | 1 of 6 | 47.5 | | [Collibra](/platforms/collibra/) | documented | partial | partial | partial | partial | partial | 1 of 6 | 46.5 | | [Immuta](/platforms/immuta/) | documented | none found | none found | partial | partial | partial | 1 of 6 | 45.0 | | [Ataccama ONE](/platforms/ataccama/) | documented | partial | partial | partial | none found | partial | 1 of 6 | 41.5 | | [Privacera](/platforms/privacera/) | documented | none found | none found | none found | partial | partial | 1 of 6 | 30.0 | | [OneTrust](/platforms/onetrust/) | documented | none found | none found | none found | none found | partial | 1 of 6 | 26.5 | Tools sorted by stages documented, then by the Need to Know total. Read 13 Nov 2026. ## Other sectors - [Financial services](/sectors/financial-services/) - [SaaS](/sectors/saas/) - [Telecom](/sectors/telecom/) - [Retail](/sectors/retail/) ## Sources - 45 CFR 164.312, Technical safeguards (Cornell LII): https://www.law.cornell.edu/cfr/text/45/164.312 (read 13 Nov 2026) - 45 CFR 164.308, Administrative safeguards (Cornell LII): https://www.law.cornell.edu/cfr/text/45/164.308 (read 13 Nov 2026) - 45 CFR 164.502, Uses and disclosures (Cornell LII): https://www.law.cornell.edu/cfr/text/45/164.502 (read 13 Nov 2026) - 45 CFR 164.514, Other requirements (Cornell LII): https://www.law.cornell.edu/cfr/text/45/164.514 (read 13 Nov 2026) Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/sectors/healthcare/ --- # A SaaS auditor asks how a customer's personal data is minimized, recorded and tracked through reporting SECTOR, read 13 Nov 2026 **The short answer.** Software vendors answer to customers, the UK and EU regulators and California. The UK data protection regulator's guides on design, records, minimisation and security, plus California's CCPA page, give five asks that map to the PII Exposure Map from warehouse column to agent. A SaaS company is often a processor for its customers and a controller for its own users and staff. The auditor is usually a customer's security team or a regulator, and the first request is a record of what personal data the product stores and where it flows. Product analytics, support exports and customer dashboards all copy personal fields out of the production database. The European regulation's articles are quoted in this sector through the UK regulator's guides, which follow the same Articles 5, 25, 30 and 32. Customer security questionnaires may also cite a SOC 2 report; that is an attestation, not a regulator, so the asks below stay with regulator text. Each ask lists the evidence and the map stages that hold it. ## What an auditor asks - **Did you design the reporting layer so that personal data protection is built in?** Basis: The ICO guide to data protection by design and by default (UK GDPR, mirroring Article 25) says it is about "considering data protection and privacy at the start of everything you do." ([ICO: data protection by design and by default](https://ico.org.uk/for-organisations/uk-gdpr-guidance-and-resources/accountability-and-governance/guide-to-accountability-and-governance/data-protection-by-design-and-default/), read 13 Nov 2026). Map stages: [Warehouse column](/exposure-map/column/), [Transformation](/exposure-map/transformation/). Show that a sensitivity tag set on a source column travels into the models that copy it. The column and transformation cells show which tools carry the tag; see [where a policy stops](/guides/where-a-policy-stops/). - **Does your record of processing list the recipients of each category of personal data?** Basis: The ICO guide on documentation, covering Article 30, says to document "The categories of recipients of personal data" along with purposes and security measures. ([ICO: documentation (Article 30)](https://ico.org.uk/for-organisations/uk-gdpr-guidance-and-resources/accountability-and-governance/guide-to-accountability-and-governance/documentation/), read 13 Nov 2026). Map stages: [Report](/exposure-map/report/), [Viewer](/exposure-map/viewer/), [Agent](/exposure-map/agent/). Show a record that names internal dashboards, customer-facing exports and any agent as recipients. The report, viewer and agent cells show which tools can feed that list. - **Do you hold only data that is adequate, relevant and limited to your purpose?** Basis: The ICO data minimisation guide asks "How do we decide what is adequate, relevant and limited?" and ties the answer to your specified purpose. ([ICO: principle (c), data minimisation](https://ico.org.uk/for-organisations/uk-gdpr-guidance-and-resources/data-protection-principles/a-guide-to-the-data-protection-principles/data-minimisation/), read 13 Nov 2026). Map stages: [Warehouse column](/exposure-map/column/), [BI field](/exposure-map/bi-field/). Show which personal columns reach a dashboard field and the purpose each serves. The column and BI field cells show whether a tool can list unused personal fields in reports. - **What technical and organizational security measures, including access controls, protect the data?** Basis: The ICO data security guide, covering Article 32, lists data security as "ensuring appropriate access controls are in place and that data is held securely." ([ICO: a guide to data security](https://ico.org.uk/for-organisations/uk-gdpr-guidance-and-resources/security/a-guide-to-data-security/), read 13 Nov 2026). Map stages: [Viewer](/exposure-map/viewer/), [Agent](/exposure-map/agent/). Show who can open customer-facing dashboards and what scope an agent connection has. The viewer and agent cells show which tools document either. - **Can you delete a person's data and make your service providers do the same?** Basis: California's CCPA page says the right to delete lets you ask businesses to "delete personal information they collected from you and tell their service providers to do the same." ([California Attorney General: CCPA](https://oag.ca.gov/privacy/ccpa), read 13 Nov 2026). Map stages: [Transformation](/exposure-map/transformation/), [Report](/exposure-map/report/). Show how a deletion reaches derived tables and saved report extracts. The transformation and report cells show which tools follow a field into those copies. ## The map cells that answer these asks These asks need 6 of the six stages: warehouse column, transformation, BI field, report, viewer, agent. None of the 16 tools documents all 6 on 13 Nov 2026; the most is 4, by Alation. | Tool | Warehouse column | Transformation | BI field | Report | Viewer | Agent | Documented | Total | | --- | --- | --- | --- | --- | --- | --- | --- | --- | | [Alation](/platforms/alation/) | documented | partial | documented | documented | partial | documented | 4 of 6 | 54.0 | | [Euno](/platforms/euno/) | documented | partial | documented | documented | partial | partial | 3 of 6 | 67.0 | | [Atlan](/platforms/atlan/) | documented | partial | partial | partial | partial | documented | 2 of 6 | 65.5 | | [Snowflake Horizon](/platforms/snowflake/) | documented | partial | partial | partial | partial | documented | 2 of 6 | 55.5 | | [Databricks Unity Catalog](/platforms/databricks/) | documented | partial | partial | partial | partial | documented | 2 of 6 | 55.0 | | [Microsoft Purview](/platforms/microsoft-purview/) | documented | partial | partial | documented | partial | partial | 2 of 6 | 54.5 | | [Select Star](/platforms/select-star/) | partial | partial | documented | documented | partial | partial | 2 of 6 | 53.5 | | [Informatica](/platforms/informatica/) | documented | documented | partial | none found | partial | partial | 2 of 6 | 30.0 | | [Securiti](/platforms/securiti/) | documented | partial | partial | none found | partial | documented | 2 of 6 | 29.5 | | [DataHub](/platforms/datahub/) | partial | partial | partial | partial | partial | documented | 1 of 6 | 61.0 | | [Secoda](/platforms/secoda/) | documented | partial | partial | partial | partial | partial | 1 of 6 | 47.5 | | [Collibra](/platforms/collibra/) | documented | partial | partial | partial | partial | partial | 1 of 6 | 46.5 | | [Immuta](/platforms/immuta/) | documented | none found | none found | partial | partial | partial | 1 of 6 | 45.0 | | [Ataccama ONE](/platforms/ataccama/) | documented | partial | partial | partial | none found | partial | 1 of 6 | 41.5 | | [Privacera](/platforms/privacera/) | documented | none found | none found | none found | partial | partial | 1 of 6 | 30.0 | | [OneTrust](/platforms/onetrust/) | documented | none found | none found | none found | none found | partial | 1 of 6 | 26.5 | Tools sorted by stages documented, then by the Need to Know total. Read 13 Nov 2026. ## Other sectors - [Financial services](/sectors/financial-services/) - [Healthcare](/sectors/healthcare/) - [Telecom](/sectors/telecom/) - [Retail](/sectors/retail/) ## Sources - ICO, data protection by design and by default: https://ico.org.uk/for-organisations/uk-gdpr-guidance-and-resources/accountability-and-governance/guide-to-accountability-and-governance/data-protection-by-design-and-default/ (read 13 Nov 2026) - ICO, documentation: https://ico.org.uk/for-organisations/uk-gdpr-guidance-and-resources/accountability-and-governance/guide-to-accountability-and-governance/documentation/ (read 13 Nov 2026) - ICO, data minimisation: https://ico.org.uk/for-organisations/uk-gdpr-guidance-and-resources/data-protection-principles/a-guide-to-the-data-protection-principles/data-minimisation/ (read 13 Nov 2026) - ICO, a guide to data security: https://ico.org.uk/for-organisations/uk-gdpr-guidance-and-resources/security/a-guide-to-data-security/ (read 13 Nov 2026) - California Attorney General, CCPA: https://oag.ca.gov/privacy/ccpa (read 13 Nov 2026) - EDPB, Guidelines 4/2019 on Article 25: https://www.edpb.europa.eu/our-work-tools/our-documents/guidelines/guidelines-42019-article-25-data-protection-design-and_en (read 13 Nov 2026) Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/sectors/saas/ --- # A telecom auditor asks who opened customer network information and whether any third party saw it SECTOR, read 13 Nov 2026 **The short answer.** FCC auditors of carriers read 47 CFR 64.2009, 64.2010 and 64.2011 on customer proprietary network information. Five asks follow from the rule text: approval status, records of third-party access, supervisory review, protection against unauthorized access and breach notice. Each maps to the PII Exposure Map. The FCC rules treat customer proprietary network information, CPNI, as data about the services a customer uses, including call details and billing. A carrier's analytics team builds churn, usage and fraud reports from exactly that data. The auditor asks which of those reports show CPNI and who in the business opened them. The rule is specific about records. A carrier must be able to say when CPNI was provided to third parties or when they were allowed access, and an officer certifies compliance each year. For an analytics stack that makes the viewer stage and the agent stage central: the question is who, or which program, saw call-level fields. ## What an auditor asks - **Can you show the customer's approval status before CPNI is used?** Basis: 47 CFR 64.2009(a) requires "a system by which the status of a customer's CPNI approval can be clearly established prior to the use of CPNI." ([47 CFR 64.2009 (Cornell LII)](https://www.law.cornell.edu/cfr/text/47/64.2009), read 13 Nov 2026). Map stages: [Warehouse column](/exposure-map/column/), [Transformation](/exposure-map/transformation/). Show the approval flag as a column and trace it into the models that build marketing audiences. The column and transformation cells show which tools follow a flag across that step. - **Do you keep a record of every time CPNI was disclosed to or accessed by third parties?** Basis: 47 CFR 64.2009(c) says carriers "shall maintain a record of all instances where CPNI was disclosed or provided to third parties, or where third parties were allowed access to CPNI." ([47 CFR 64.2009(c) (Cornell LII)](https://www.law.cornell.edu/cfr/text/47/64.2009), read 13 Nov 2026). Map stages: [Report](/exposure-map/report/), [Viewer](/exposure-map/viewer/), [Agent](/exposure-map/agent/). Show a log that names each external recipient of a CPNI-bearing report or dataset, including a connected agent. The report, viewer and agent cells show where tools document that. - **Who reviews compliance before CPNI is used for outbound marketing?** Basis: 47 CFR 64.2009(d) requires carriers to "establish a supervisory review process" for outbound marketing and keep records for a minimum of one year. ([47 CFR 64.2009(d) (Cornell LII)](https://www.law.cornell.edu/cfr/text/47/64.2009), read 13 Nov 2026). Map stages: [BI field](/exposure-map/bi-field/), [Report](/exposure-map/report/). Show reviewer approvals tied to the dashboards or audience extracts built from CPNI fields. The BI field and report cells show whether a tool can point to those fields in a report. - **What reasonable measures protect against unauthorized access to CPNI?** Basis: 47 CFR 64.2010(a) says carriers "must take reasonable measures to discover and protect against attempts to gain unauthorized access to CPNI." ([47 CFR 64.2010 (Cornell LII)](https://www.law.cornell.edu/cfr/text/47/64.2010), read 13 Nov 2026). Map stages: [Viewer](/exposure-map/viewer/), [Agent](/exposure-map/agent/). Show access rules and alerts for the BI tool and any agent connection that reaches call detail. The viewer and agent cells show which tools document them; see [what an agent is told](/guides/approving-an-agents-access/). - **If CPNI is breached, can you say which records were exposed?** Basis: 47 CFR 64.2011 sets the notification process for CPNI breaches, starting with law enforcement; the section is the basis for an ask about scope. ([47 CFR 64.2011 (Cornell LII)](https://www.law.cornell.edu/cfr/text/47/64.2011), read 13 Nov 2026). Map stages: [Report](/exposure-map/report/), [Viewer](/exposure-map/viewer/). Show that you can list the reports and viewers who touched a CPNI field in a given window. The report and viewer cells show where that list exists. ## The map cells that answer these asks These asks need 6 of the six stages: warehouse column, transformation, BI field, report, viewer, agent. None of the 16 tools documents all 6 on 13 Nov 2026; the most is 4, by Alation. | Tool | Warehouse column | Transformation | BI field | Report | Viewer | Agent | Documented | Total | | --- | --- | --- | --- | --- | --- | --- | --- | --- | | [Alation](/platforms/alation/) | documented | partial | documented | documented | partial | documented | 4 of 6 | 54.0 | | [Euno](/platforms/euno/) | documented | partial | documented | documented | partial | partial | 3 of 6 | 67.0 | | [Atlan](/platforms/atlan/) | documented | partial | partial | partial | partial | documented | 2 of 6 | 65.5 | | [Snowflake Horizon](/platforms/snowflake/) | documented | partial | partial | partial | partial | documented | 2 of 6 | 55.5 | | [Databricks Unity Catalog](/platforms/databricks/) | documented | partial | partial | partial | partial | documented | 2 of 6 | 55.0 | | [Microsoft Purview](/platforms/microsoft-purview/) | documented | partial | partial | documented | partial | partial | 2 of 6 | 54.5 | | [Select Star](/platforms/select-star/) | partial | partial | documented | documented | partial | partial | 2 of 6 | 53.5 | | [Informatica](/platforms/informatica/) | documented | documented | partial | none found | partial | partial | 2 of 6 | 30.0 | | [Securiti](/platforms/securiti/) | documented | partial | partial | none found | partial | documented | 2 of 6 | 29.5 | | [DataHub](/platforms/datahub/) | partial | partial | partial | partial | partial | documented | 1 of 6 | 61.0 | | [Secoda](/platforms/secoda/) | documented | partial | partial | partial | partial | partial | 1 of 6 | 47.5 | | [Collibra](/platforms/collibra/) | documented | partial | partial | partial | partial | partial | 1 of 6 | 46.5 | | [Immuta](/platforms/immuta/) | documented | none found | none found | partial | partial | partial | 1 of 6 | 45.0 | | [Ataccama ONE](/platforms/ataccama/) | documented | partial | partial | partial | none found | partial | 1 of 6 | 41.5 | | [Privacera](/platforms/privacera/) | documented | none found | none found | none found | partial | partial | 1 of 6 | 30.0 | | [OneTrust](/platforms/onetrust/) | documented | none found | none found | none found | none found | partial | 1 of 6 | 26.5 | Tools sorted by stages documented, then by the Need to Know total. Read 13 Nov 2026. ## Other sectors - [Financial services](/sectors/financial-services/) - [Healthcare](/sectors/healthcare/) - [SaaS](/sectors/saas/) - [Retail](/sectors/retail/) ## Sources - 47 CFR 64.2009, Safeguards required (Cornell LII): https://www.law.cornell.edu/cfr/text/47/64.2009 (read 13 Nov 2026) - 47 CFR 64.2010, Safeguards on release of CPNI (Cornell LII): https://www.law.cornell.edu/cfr/text/47/64.2010 (read 13 Nov 2026) - 47 CFR 64.2011, Notification of CPNI security breaches (Cornell LII): https://www.law.cornell.edu/cfr/text/47/64.2011 (read 13 Nov 2026) - 47 CFR 64.2005, Use of CPNI without customer approval (Cornell LII): https://www.law.cornell.edu/cfr/text/47/64.2005 (read 13 Nov 2026) Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/sectors/telecom/ --- # A retail auditor asks where card and customer data show up in reports and who or what can open them SECTOR, read 13 Nov 2026 **The short answer.** Retail auditors check PCI DSS requirements 7 and 10 from the PCI Security Standards Council and three consumer rights on California's CCPA page: know, limit sensitive data, and reasonable security. Five asks follow, each mapped to the PII Exposure Map stages that hold the evidence. A retailer's sensitive data comes in two kinds: payment account data under PCI DSS and shoppers' personal information under state privacy law. Analytics teams copy both into sales, loyalty and fraud dashboards. The auditor's first question is whether card data left the cardholder data environment and ended up in a report. The privacy side asks a different question: what the business collected, why and with whom it shared it. California's attorney general frames those as consumer rights, and each one needs a map from a customer to the tables, reports and recipients that hold their data. ## What an auditor asks - **Is access to cardholder data restricted by business need to know?** Basis: PCI DSS v4.x Requirement 7 covers restricting access to system components and cardholder data by business need to know; the Council's PCI DSS page describes the standard as a "baseline of technical and operational requirements designed to protect payment account data." ([PCI Security Standards Council: PCI DSS](https://www.pcisecuritystandards.org/standards/pci-dss/), read 13 Nov 2026). Map stages: [BI field](/exposure-map/bi-field/), [Report](/exposure-map/report/), [Viewer](/exposure-map/viewer/). Show which dashboards and reports carry card-related fields and the role list allowed to open them. The BI field, report and viewer cells show which tools document that link. - **Do you log and monitor all access to cardholder data?** Basis: PCI DSS v4.x Requirement 10 covers logging and monitoring access to system components and cardholder data; the full text is in the PCI DSS document in the Council's library. ([PCI Security Standards Council: document library](https://www.pcisecuritystandards.org/document_library/), read 13 Nov 2026). Map stages: [Viewer](/exposure-map/viewer/), [Agent](/exposure-map/agent/). Show log entries naming the user or agent that opened a report with card-adjacent fields. The viewer and agent cells show which tools record this beyond warehouse query logs. - **What can a shopper learn about who your business shared their data with?** Basis: California's CCPA page says the right to know covers "The categories of third parties with whom the business shares the personal information." ([California Attorney General: CCPA, right to know](https://oag.ca.gov/privacy/ccpa), read 13 Nov 2026). Map stages: [Report](/exposure-map/report/), [Agent](/exposure-map/agent/). Show that you can list the external recipients of reports and agent outputs built from customer tables. The report and agent cells show where a tool documents recipients. - **Can a shopper limit how you use their sensitive personal information?** Basis: California's CCPA page lists a right to direct businesses to limit their use of your sensitive personal information, for example "financial account information" and "precise geolocation data." ([California Attorney General: CCPA, sensitive information](https://oag.ca.gov/privacy/ccpa), read 13 Nov 2026). Map stages: [Warehouse column](/exposure-map/column/), [BI field](/exposure-map/bi-field/). Show sensitive-field tags on loyalty and location columns and the dashboard fields that display them. The column and BI field cells show which tools carry the tag that far. - **Do you maintain reasonable security procedures for personal information?** Basis: California's CCPA page says consumers may sue when personal information was stolen in a data breach because of a failure "to maintain reasonable security procedures and practices." ([California Attorney General: CCPA, data breach](https://oag.ca.gov/privacy/ccpa), read 13 Nov 2026). Map stages: [Viewer](/exposure-map/viewer/), [Transformation](/exposure-map/transformation/). Show the access reviews and the masked copies that limit what a stolen extract would hold. The viewer and transformation cells show where tools document those controls. ## The map cells that answer these asks These asks need 6 of the six stages: warehouse column, transformation, BI field, report, viewer, agent. None of the 16 tools documents all 6 on 13 Nov 2026; the most is 4, by Alation. | Tool | Warehouse column | Transformation | BI field | Report | Viewer | Agent | Documented | Total | | --- | --- | --- | --- | --- | --- | --- | --- | --- | | [Alation](/platforms/alation/) | documented | partial | documented | documented | partial | documented | 4 of 6 | 54.0 | | [Euno](/platforms/euno/) | documented | partial | documented | documented | partial | partial | 3 of 6 | 67.0 | | [Atlan](/platforms/atlan/) | documented | partial | partial | partial | partial | documented | 2 of 6 | 65.5 | | [Snowflake Horizon](/platforms/snowflake/) | documented | partial | partial | partial | partial | documented | 2 of 6 | 55.5 | | [Databricks Unity Catalog](/platforms/databricks/) | documented | partial | partial | partial | partial | documented | 2 of 6 | 55.0 | | [Microsoft Purview](/platforms/microsoft-purview/) | documented | partial | partial | documented | partial | partial | 2 of 6 | 54.5 | | [Select Star](/platforms/select-star/) | partial | partial | documented | documented | partial | partial | 2 of 6 | 53.5 | | [Informatica](/platforms/informatica/) | documented | documented | partial | none found | partial | partial | 2 of 6 | 30.0 | | [Securiti](/platforms/securiti/) | documented | partial | partial | none found | partial | documented | 2 of 6 | 29.5 | | [DataHub](/platforms/datahub/) | partial | partial | partial | partial | partial | documented | 1 of 6 | 61.0 | | [Secoda](/platforms/secoda/) | documented | partial | partial | partial | partial | partial | 1 of 6 | 47.5 | | [Collibra](/platforms/collibra/) | documented | partial | partial | partial | partial | partial | 1 of 6 | 46.5 | | [Immuta](/platforms/immuta/) | documented | none found | none found | partial | partial | partial | 1 of 6 | 45.0 | | [Ataccama ONE](/platforms/ataccama/) | documented | partial | partial | partial | none found | partial | 1 of 6 | 41.5 | | [Privacera](/platforms/privacera/) | documented | none found | none found | none found | partial | partial | 1 of 6 | 30.0 | | [OneTrust](/platforms/onetrust/) | documented | none found | none found | none found | none found | partial | 1 of 6 | 26.5 | Tools sorted by stages documented, then by the Need to Know total. Read 13 Nov 2026. ## Other sectors - [Financial services](/sectors/financial-services/) - [Healthcare](/sectors/healthcare/) - [SaaS](/sectors/saas/) - [Telecom](/sectors/telecom/) ## Sources - PCI Security Standards Council, PCI DSS: https://www.pcisecuritystandards.org/standards/pci-dss/ (read 13 Nov 2026) - PCI Security Standards Council, document library: https://www.pcisecuritystandards.org/document_library/ (read 13 Nov 2026) - California Attorney General, CCPA: https://oag.ca.gov/privacy/ccpa (read 13 Nov 2026) - California Attorney General, privacy: https://oag.ca.gov/privacy (read 13 Nov 2026) Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/sectors/retail/ --- # Five sectors, five audit walks along the same sensitive field SECTORS, read 13 Nov 2026 **The short answer.** An auditor in financial services, healthcare, SaaS, telecom or retail asks where a regulated field surfaces and who or what saw it. Each sector page lists the asks with the regulation or regulator page behind each, and the exposure map cells that answer them, read 13 Nov 2026. - [Financial services](/sectors/financial-services/): 5 audit asks; stages needed: warehouse column, transformation, BI field, report, viewer, agent - [Healthcare](/sectors/healthcare/): 5 audit asks; stages needed: warehouse column, transformation, BI field, report, viewer, agent - [SaaS](/sectors/saas/): 5 audit asks; stages needed: warehouse column, transformation, BI field, report, viewer, agent - [Telecom](/sectors/telecom/): 5 audit asks; stages needed: warehouse column, transformation, BI field, report, viewer, agent - [Retail](/sectors/retail/): 5 audit asks; stages needed: warehouse column, transformation, BI field, report, viewer, agent Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/sectors/ --- # A warehouse policy decides who can run a query on a column, and stops there GUIDE, read 13 Nov 2026 **The short answer.** Snowflake masking, Databricks column masks and Immuta policies decide what a query returns to a role. None of them sees the metric, the BI field, the report, the person who opened it or the agent that quoted it. Power BI row-level security skips workspace Admin, Member and Contributor roles, so even a correct rule has gaps. **Where Euno is behind.** Euno is not a policy engine or a DSPM: it reads metadata only, so it does not scan data contents or mask at the warehouse, which leaves it behind Atlan on acting on findings (5 to 7), and it publishes no dollar prices. ## A policy answers one question: what does this role get back from this query Every policy in the warehouse runs at query time. Snowflake says that when an AI agent queries data, the role's access control, masking and row-access policies are enforced at the query engine, and that access to metadata is managed separately from access to the underlying data. Snowflake also documents tag-based masking: a masking policy set on a tag protects every tagged column of a matching data type. Databricks says row filters and column masks defined in Unity Catalog are enforced per user in a Genie Agent, however the agent is shared. Immuta works on the same plane. Per its docs, identification runs inside the data platform and tags columns by name, pattern or dictionary, and masking policies are then written against those tags. The input is a column, a role and a moment. The output is rows and values. Nothing in that exchange names a metric, a dashboard or a person reading one. ## Each control stops at the edge of the layer it runs in The table sets out the five business-layer stages of the [exposure map](/exposure-map/) against what a policy at each layer decides and what it cannot see. The last column is the part a governance lead has to supply some other way. The first row is the strongest control in the stack, and 14 of the 16 ranked tools document column-level classification or policy work. The stages after it thin out fast: 4 document the report stage and 0 document the viewer stage. | Layer | What a policy there decides | What it cannot see | | --- | --- | --- | | Warehouse column | Which role gets raw, masked or filtered values when a query runs | Which downstream objects were built from the column | | Transformation model | Whether a derived table inherits a tag, where propagation is switched on | A model that renames or joins the column before any tag reaches it | | BI field | Which users the semantic model or live connection lets through | The sensitivity of a calculated field built on a classified column | | Report | Who may open the item and, with a label, who may export it | Whether the data on the page is the classified field or a total derived from it | | Viewer | Which identity the report passes to the warehouse | A shared service account that stands for many people | | Agent | What the signed-in user or service principal may query | What the agent put into its answer after the query returned | ## Power BI shows the first break: row-level security skips three workspace roles Microsoft's Fabric documentation says row-level security in a Power BI semantic model restricts data only for users with Viewer permissions. It does not apply to workspace Admin, Member or Contributor roles (page read 13 Nov 2026). A governance lead who reads "RLS is on" in a review therefore still needs the workspace role list, because anyone holding one of those three roles sees every row the semantic model holds. Immuta documents the same dependency from the other side. For Tableau, viewers see data under their personal policies only when the published data source prompts for credentials. For Power BI, users must connect with personal credentials after publishing. If the report connects through one embedded account, the warehouse policy sees that account and nobody else. Immuta's cells read none found at the BI field stage and partial at the report stage. ## Four of the stages need a record that lives outside the policy engine The BI field, the report, the viewer and the agent each need their own record, because the policy engine holds none of them. A BI field needs a link to the column it uses. A report needs a list of the fields it shows. A viewer needs an identity that survives the connection. An agent needs a log of what it was told. Ranked tools that supply part of that record differ in where they start. Microsoft Purview documents a label on a Power BI semantic model or report flowing to dependent items, and Microsoft Purview reads documented at the report stage. Select Star reads documented at the BI field stage. Euno, a context platform that reads metadata and query logs only, reads documented there, and none of the three enforces access. Euno's docs say it propagates warehouse classifications from tools such as Cyera and BigID into BI fields and reports; that is a map of exposure, not a mask. ## A check list for the sign-off meeting Ask for evidence at each stage and write down which stage has none. A policy review that stops at the warehouse will pass, because the warehouse is the layer where policies work best. The gaps sit in the stages the policy never touches, and the person signing off carries them. The list below is short enough to run in an hour on one regulated field. - Pick one classified column. Name the metric, BI field and report that use it, and the tool that produced each link. - List the workspace roles on that report and confirm which of them bypass row-level security. - Find the identity the report uses to reach the warehouse and check it maps to a person, not a shared account. - Ask which agent can quote the report's numbers, and which role it queries under. - Record every stage where the answer is "none found" and decide who owns the gap. ## Sources - Snowflake Horizon Context docs: https://docs.snowflake.com/en/user-guide/snowflake-horizon/horizon-context.md (read 13 Nov 2026) - Snowflake tag-based masking: https://docs.snowflake.com/en/user-guide/tag-based-masking-policies.md (read 13 Nov 2026) - Databricks Genie setup: https://docs.databricks.com/aws/en/genie/set-up (read 13 Nov 2026) - Immuta data identification: https://documentation.immuta.com/saas/configuration/tags/data-discovery.md (read 13 Nov 2026) - Immuta Tableau setup: https://documentation.immuta.com/saas/configuration/application-configuration/how-to-guides/bi-tools/tableau.md (read 13 Nov 2026) - Immuta Power BI setup: https://documentation.immuta.com/saas/configuration/application-configuration/how-to-guides/bi-tools/power-bi.md (read 13 Nov 2026) - Microsoft, row-level security in Power BI: https://learn.microsoft.com/en-us/fabric/security/service-admin-row-level-security (read 13 Nov 2026) - Microsoft, downstream label inheritance: https://learn.microsoft.com/power-bi/enterprise/service-security-sensitivity-label-downstream-inheritance (read 13 Nov 2026) - Euno docs, Cyera use cases: https://docs.euno.ai/sources/data-security/cyera-integration/cyera-integration-use-cases.md (read 13 Nov 2026) Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/guides/where-a-policy-stops/ --- # A classification travels only as far as the last tool that reads it and passes it on GUIDE, read 13 Nov 2026 **The short answer.** A column is classified once, in the warehouse or by a scanner. Whether the label reaches the transformation model, the BI field, the report and the agent's answer depends on which tool carries it. Snowflake's own classification tags are system tags, and its docs say system tags are not propagated. **Where Euno is behind.** Euno is not a policy engine or a DSPM: it reads metadata only, so it does not scan data contents or mask at the warehouse, which leaves it behind Atlan on acting on findings (5 to 7), and it publishes no dollar prices. ## Four kinds of tool create the first classification The governance question is who writes the label and who reads it afterward. Warehouse scanners write it inside the platform. Snowflake says its classification discovers sensitive data and makes it easy to apply tags and masking policies. Databricks says that with automatic tagging on, all existing and future detections get class tags, and a reviewed result can seed a masking policy. Immuta's identification runs inside the data platform and tags by column name, pattern or dictionary. Data security posture tools, such as Cyera and BigID, scan from outside. Microsoft documents more than 200 built-in classifications in the Purview Data Map. Catalogs add a fourth source: Select Star matches PII rules against column names once a day, which is name-based, not a scan of values. Each source writes into a different place, and a downstream tool can only carry what it can read. ## Tools differ on whether they take classifications in from elsewhere Several ranked tools import labels rather than create them. Atlan says its Cyera connector imports Cyera classifications onto assets and that it syncs tags from Snowflake, Databricks, BigQuery and dbt. Secoda says its Cyera integration tags matching resources with the same classifications. Immuta says it ingests tags from Alation, Atlan, Collibra and Microsoft Purview, polling the catalog every 24 hours. Privacera's docs describe a Collibra connector that keeps tags synchronized. Informatica says its governance catalog can extract Unity Catalog tags, and its page does not say they are then propagated along lineage. Euno documents Cyera and BigID imports and then carries the labels forward through column-level lineage. Per Euno's docs, BigID classifications do not appear on Looker, Tableau or Power BI assets on their own, and Euno propagates them to downstream fields and reports. Euno reads documented at the column stage and documented at the BI field stage. ## Snowflake's own classification tags are the ones its propagation skips This is the one check most Snowflake teams can run in ten minutes. Snowflake's classification page says it marks classified columns with two system-defined tags, SNOWFLAKE.CORE.SEMANTIC_CATEGORY and SNOWFLAKE.CORE.PRIVACY_CATEGORY. Snowflake's propagation page lists its limits, and the first one reads "System tags are not propagated" (both pages read 13 Nov 2026). Read together, the documents say the label a scan writes does not itself travel to a view or table built from the column. The route the classification page documents is a tag map: when a system tag takes a value, a user-defined tag is applied as well. Propagation can then carry the user-defined tag. The same page gives a second limit: one transaction propagates a tag to at most 10,000 downstream objects. A team that turned on classification and propagation and never built the map has a gap that no report will show. Test it on one view before an audit asks. ## Past the warehouse, every ranked tool carries it a different distance Databricks says tag propagation (Beta) copies a governed tag from a source table or column to derived tables and views, and that a propagated tag makes a matching column mask apply to the derived column. Propagation is off by default and enabled per governed tag. Atlan likewise says propagation is off by default and chosen per tag. Microsoft documents label inheritance from data sources to Power BI semantic models for only three source types, and its downstream inheritance stops above 80 items. Immuta's docs say its policies attach by tag to tables made by dbt, but that it receives no DDL events, which leaves a window it calls policy downtime. DataHub's term propagation covers datasets and excludes charts and dashboards. The table counts the ranked tools by the cell each reads on the exposure map. | Stage | Documented | Partial | None found | | --- | --- | --- | --- | | Column (classification exists) | 14 of 16 | 2 of 16 | 0 of 16 | | Transformation model | 1 of 16 | 12 of 16 | 3 of 16 | | BI field | 3 of 16 | 10 of 16 | 3 of 16 | | Report | 4 of 16 | 8 of 16 | 4 of 16 | | Viewer | 0 of 16 | 14 of 16 | 2 of 16 | | Agent | 6 of 16 | 10 of 16 | 0 of 16 | ## The chain usually breaks at the BI field and the agent's sentence The counts show where the chain breaks. The column stage is the fullest, with 14 of 16 documented. The BI field and report stages are where Immuta, Privacera and OneTrust read none found, none found and none found: their controls sit on the data, and the label does not follow it into the dashboard. The agent stage is the second break. 6 of the 16 tools read documented there, for example Snowflake Horizon and Databricks Unity Catalog, because the agent queries under enforced policies, but a policy enforced on the query does not label the sentence the agent writes afterward. The practical reading is that a classification is a claim made at one stage and re-made at each later one. Each re-making needs a named tool, a setting that is switched on, and a place to look when it fails. Where none of the three exists, treat the downstream field as unclassified, whatever the warehouse says. Check three things in a trial. Ask the vendor to show a classified column and its label on the BI field. Ask what happens to a label when a model renames or joins the column. Ask whether the agent's tool response carries the label or only obeys the mask. See the [exposure map](/exposure-map/) for each tool's row, and the [glossary entry on label inheritance](/glossary/label-downstream-inheritance/). ## Sources - Snowflake classification: https://docs.snowflake.com/en/user-guide/classify-intro (read 13 Nov 2026) - Snowflake tag propagation limits: https://docs.snowflake.com/en/user-guide/object-tagging/propagation (read 13 Nov 2026) - Databricks tag propagation: https://docs.databricks.com/aws/en/admin/governed-tags/tag-propagation (read 13 Nov 2026) - Databricks Data Classification: https://docs.databricks.com/aws/en/data-governance/unity-catalog/data-classification (read 13 Nov 2026) - Microsoft downstream label inheritance: https://learn.microsoft.com/power-bi/enterprise/service-security-sensitivity-label-downstream-inheritance (read 13 Nov 2026) - Microsoft label inheritance from data sources: https://learn.microsoft.com/power-bi/enterprise/service-security-sensitivity-label-inheritance-from-data-sources (read 13 Nov 2026) - Immuta external catalog tags: https://documentation.immuta.com/saas/configuration/tags/catalogs.md (read 13 Nov 2026) - Immuta dbt transform workflow: https://documentation.immuta.com/saas/govern/authoring-policies-in-secure/dbt-transform-workflow.md (read 13 Nov 2026) - Euno docs, BigID use cases: https://docs.euno.ai/sources/data-security/bigid-integration/bigid-integration-use-cases.md (read 13 Nov 2026) - DataHub term propagation: https://docs.datahub.com/docs/automations/glossary-term-propagation (read 13 Nov 2026) Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/guides/classification-from-warehouse-to-agent/ --- # An access list shows who could see a field, and only a log shows who did GUIDE, read 13 Nov 2026 **The short answer.** An access list says who could open a field, report or agent. A log says who did, and each layer keeps its own with its own window. Power BI's activity events API returns only the last 28 days, so a request for 90 days of report viewers needs a second source. **Where Euno is behind.** Euno is not a policy engine or a DSPM: it reads metadata only, so it does not scan data contents or mask at the warehouse, which leaves it behind Atlan on acting on findings (5 to 7), and it publishes no dollar prices. ## A list of entitlements and a record of events answer different questions An access list is a statement of permission: these roles can read this column, these users can open this report. A log is a statement of fact: this person ran this query at this time. An auditor who asks "show me who opened this report in the last 90 days" wants the second. A list can be complete and still say nothing about whether anyone looked, and a log can show a viewer who is on no list at all, which is how a shared link or an inherited role gets found. The two disagree most at the report stage. Membership of a workspace role grants access, and the people holding the role may have used it never or daily. Only the event stream tells you which. ## Each layer keeps a different log with a different window Snowflake documents ACCESS_HISTORY, a view of object and column access by user, kept 365 days on Enterprise Edition, and its page says latency for the view may be up to 180 minutes. Its QUERY_HISTORY view carries an agent_type column that names CORTEX_AGENT, CORTEX_LITE_AGENT or EXTERNAL_AGENT for a query an agent invoked directly, and is null otherwise. That column is a finding worth testing: a warehouse query log can separate an agent's queries from a person's, on Snowflake, without any extra tool. Databricks logs AI/BI dashboard view events in its audit log, and its query history system table records who ran each statement. Databricks documents no viewer log for Tableau or Power BI reports built on its tables (none found on 13 Nov 2026 in its system tables or audit pages). For Power BI, Microsoft says the activity log records who took what action on which item, exposed through the ActivityEvents REST API, with delays of up to 60 minutes. The API reference limits a request to a single UTC day within the last 28 days. Microsoft's Purview Audit page lists 180-day retention for standard audit records. The 90-day question therefore has an answer in Power BI only if someone exported the events or the tenant searches the Purview audit log. Immuta says its audit logs expire after 90 days unless exported to S3 or ADLS Gen2, and its audit is by user query on data sources; none found on 13 Nov 2026 for per-report viewer lists. ## Ranked tools document the viewer and agent stages unevenly The table gives each tool's exposure-map cell for the two stages that need a log, then what its documentation describes. Euno's docs also say shared BI service accounts hide who accessed sensitive data, and that Euno resolves the individuals behind BI access and usage events. Atlan's docs add that its MCP can return the source-system usernames that recently or most often queried an asset. | Tool | Viewer | Agent | What the docs describe | | --- | --- | --- | --- | | Euno | partial | partial | Distinct users per Tableau and Power BI resource over 14, 30 and 60 days; none found for a per-agent log of fields served | | Atlan | partial | documented | Popularity from distinct users over 30 days; no Tableau unique-viewer counts; every MCP tool call logged with client, model and denial reasons | | Snowflake Horizon | partial | documented | Column access by user for 365 days; BI popularity, not named viewers; agent_type in query history | | Databricks Unity Catalog | partial | documented | Dashboard view events in the audit log; tokens identify the user or service principal behind an MCP call | | Microsoft Purview | partial | partial | Power BI activity log through the API; AI interaction events in the unified audit log | | Immuta | partial | partial | Query audit with a 90-day default; agent activity logged with the on-behalf-of user, per Immuta's page | ## The agent stage is the hardest to log because a person asked and a machine answered A good agent record has four parts: the person, the agent, the tool call and the data returned. Atlan says each tool call is logged with tool, client, model, tenant and duration. Immuta says agent activity carries the on-behalf-of user, the vended role and request times. Snowflake's agent_type separates agent queries inside the warehouse. None of the three records, as documented, the sensitivity label of what came back; the label sits in the catalog, the call in the log, and joining them is work you do. ## What to check in a trial Most reviews test the access list and skip the log, because the list is easy to export. Reverse the order. A log you cannot produce for a date range is a finding on its own, and it is cheaper to learn that in a trial than in an audit. Run the auditor's question yourself before you sign. Name one regulated report and ask each vendor to produce the following. - Every named viewer in the last 90 days, with the date range the product can reach, not the one the brochure states. - The identity behind a report that connects through a shared account, and how it is resolved to a person. - Every agent call that touched one classified field, with the human who asked. - The log delay: Snowflake documents up to 180 minutes on one view and Microsoft up to 60 minutes, so ask what an incident review sees an hour later. - The export path and retention for each log, since a 28-day API window and a 90-day expiry are both shorter than a quarterly review. ## Sources - Snowflake ACCESS_HISTORY: https://docs.snowflake.com/en/sql-reference/account-usage/access_history.md (read 13 Nov 2026) - Snowflake QUERY_HISTORY: https://docs.snowflake.com/en/sql-reference/account-usage/query_history (read 13 Nov 2026) - Databricks audit log events: https://docs.databricks.com/aws/en/admin/account-settings/audit-logs (read 13 Nov 2026) - Microsoft, Power BI auditing: https://learn.microsoft.com/power-bi/enterprise/service-admin-auditing (read 13 Nov 2026) - Power BI Get Activity Events API: https://learn.microsoft.com/en-us/rest/api/power-bi/admin/get-activity-events (read 13 Nov 2026) - Microsoft Purview audit overview: https://learn.microsoft.com/en-us/purview/audit-solutions-overview (read 13 Nov 2026) - Immuta audit: https://documentation.immuta.com/saas/govern/detect-introduction/index.md (read 13 Nov 2026) - Atlan MCP security: https://docs.atlan.com/product/capabilities/atlan-ai/references/mcp-security (read 13 Nov 2026) - Euno docs, Cyera use cases: https://docs.euno.ai/sources/data-security/cyera-integration/cyera-integration-use-cases.md (read 13 Nov 2026) - Euno docs, Power BI usage data: https://docs.euno.ai/using-euno/usage-optimization/power-bi-usage-data.md (read 13 Nov 2026) Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/guides/who-saw-it-against-who-could-see-it/ --- # An agent's access is approvable only when identity, scope, log and revocation each have evidence GUIDE, read 13 Nov 2026 **The short answer.** Sign-off on an AI agent's connection to analytics data rests on four documents: the identity it runs as, what each call may carry, what each call writes to a log, and who can revoke it. Of the 16 ranked tools, Atlan, Alation, DataHub and Ataccama document per-user identity, while Select Star and Secoda document shared tokens. ## The approver's first question is whose identity the agent runs as An agent connection runs as one of two things: the person who asked, or a service account that stands for the agent. The choice decides what every later control can see. A policy keyed on the person works only if the person's identity reaches the data layer. A shared account makes every policy and every log line read the same name. Vendor documents split on this. Atlan says its MCP server forwards the caller's identity so persona, role and domain policies apply to every tool call, and that a service-account token must carry exactly one persona. Alation says two users on the same MCP server can see different tool lists and results. DataHub says Cloud MCP uses OAuth2 so each user connects with a personal login, with tokens scoped to that user. Ataccama says each MCP request runs under the user's own identity, with Amazon Bedrock as the exception, which uses a shared service account. Informatica documents a gateway pattern with service-to-service OAuth 2.0, a service identity that is not stated per end user. Ask the vendor for the sentence in the docs that names the identity, and for the exceptions. Ataccama's Bedrock line is the kind of exception that never reaches a sales deck and decides an audit finding. On the exposure map, the agent stage reads documented for Atlan, documented for Alation, documented for DataHub and partial for Ataccama ONE. See [the agent column of the map](/exposure-map/agent/) for all 16. ## What the agent can be told is set per tool, not per connection Connecting to a server and being allowed to use its tools are separate grants in some products. Snowflake documents that access to a managed MCP server does not grant access to its tools, and that each tool needs its own grant. Snowflake also warns that exposing SYSTEM_EXECUTE_SQL on a server lets the client bypass the agent's semantic views and verified queries. An approver should read the tool list, not the server name. DataHub says its MCP mutation tools, which add tags, terms and owners, stay off unless a setting enables them. Atlan scores 7 out of 10 on the site's agent scope criterion and Databricks Unity Catalog 7; the criterion is described on the [method page](/method/). Alation adds a limit worth recording. Its docs say tool approvals are not enforced over MCP and each client must enforce its own tool restrictions. If the approval you are giving depends on a client prompt asking a human, the server will not back it up. ## A per-call log is the evidence an auditor will ask for Atlan says every MCP tool call is logged with tool, client, model, tenant and duration, and that access denials are logged with reasons. Databricks says its audit log writes one event per Genie One MCP tool call. Immuta says its audit model records query, authentication, policy, project and tag events in one structure, and that logs expire after 90 days unless exported to S3 or ADLS Gen2. Two checks follow. First, ask for a sample log line from a denied call, since a denial is the case that proves a control ran. Second, ask the retention figure and who owns the export. Immuta's 90-day default is stated and therefore easy to plan around; a vendor that names no figure leaves the question open. ## Revocation depends on what the credential is Immuta says access for an agent is ephemeral: a role is created in the data platform and deleted after the action. Revocation there is the default state. At the other end, Select Star's docs say API tokens have no expiration and the MCP connection uses one, and Secoda's server code forwards a single API token as a bearer credential on each tool call. For those, revoking one agent means rotating a token that every client shares. The reasoned verdict for the approval form: a credential that never expires and is shared by clients cannot be revoked per agent, so approve it only with a rotation date and a named owner. Ask each vendor to show the revoke step on a test agent and the log line that proves the next call failed. ## Approval itself should be a written rule with a log Immuta's release notes for 4 Nov 2026 describe dynamic review flows that approve, deny or route a request, including requests from agents for pre-approved, non-sensitive datasets (see the [news item](/news/immuta-dynamic-review-flows-agent-access-requests/)). What to request is the rule, its editor list and the decision log. If the product approves by tag, ask which tags it reads and what happens to data with no tag yet. ## A checklist table turns the questions into evidence requests Use one row per question. A blank cell in the vendor's answer is a finding, written as none found on 13 Nov 2026. | Question | Evidence to ask for | Documented in the ranked set | | --- | --- | --- | | Whose identity does each call carry? | The doc sentence naming user or service account, plus exceptions | Atlan, Alation, DataHub, Ataccama (per user); Informatica pattern (service) | | What can a call carry? | Tool list, per-tool grants, a denied-call example | Snowflake (per-tool grants), DataHub (mutation tools off by default) | | What is logged per call? | A sample record with user, tool, outcome and reason | Atlan (tool, client, model, duration), Databricks (one event per call) | | How long is the log kept? | Retention figure and export path | Immuta (90 days, then export) | | Who can revoke, and how fast? | A test revoke and the next-call failure in the log | Immuta (ephemeral role); Select Star and Secoda use long-lived tokens | | How is a request approved? | The rule, its editors and the decision log | Immuta (dynamic review flows) | ## Sources - Atlan: MCP security: https://docs.atlan.com/product/capabilities/atlan-ai/references/mcp-security (read 13 Nov 2026) - Alation: using the MCP server: https://documentation.alation.com/en/latest/agentstudio/integrations/mcp/using-the-mcp-server.md (read 13 Nov 2026) - DataHub: MCP server guide: https://docs.datahub.com/docs/features/feature-guides/mcp (read 13 Nov 2026) - Ataccama: DQ&C MCP server: https://docs.ataccama.com/one/latest/generative-ai/mcp-dqc.html (read 13 Nov 2026) - Informatica: MCPs on AWS AgentCore: https://www.informatica.com/blogs/powering-agentic-workflows-on-aws-with-informatica-mcps.html (read 13 Nov 2026) - Snowflake: managed MCP server: https://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-agents-mcp.md (read 13 Nov 2026) - Databricks: audit log: https://docs.databricks.com/aws/en/admin/account-settings/audit-logs (read 13 Nov 2026) - Immuta: agentic data access: https://documentation.immuta.com/saas/agentic-data-access/introduction.md (read 13 Nov 2026) - Immuta: Detect audit model: https://documentation.immuta.com/saas/govern/detect-introduction/index.md (read 13 Nov 2026) - Immuta: release notes: https://documentation.immuta.com/saas/releases/index.md (read 13 Nov 2026) - Select Star: API authentication: https://web.archive.org/web/2026/https://docs.selectstar.com/select-star-api/authentication (read 13 Nov 2026) - Secoda: MCP server code: https://raw.githubusercontent.com/secoda/secoda-mcp/main/server.py (read 13 Nov 2026) Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/guides/approving-an-agents-access/ --- # A DSPM finds sensitive data in stores and stops short of the BI field, the report and the viewer GUIDE, read 13 Nov 2026 **The short answer.** Data security posture management tools such as Cyera, BigID and Varonis find and classify sensitive data in stores and rate who can reach it. Their documents describe stores and identities, not BI fields or report viewers. Of the 16 ranked tools, Euno, Atlan and Secoda name Cyera, and Euno and Atlan name BigID. **Where Euno is behind.** Euno is not a policy engine or a DSPM: it reads metadata only, so it does not scan data contents or mask at the warehouse, which leaves it behind Atlan on acting on findings (5 to 7), and it publishes no dollar prices. ## A DSPM covers the store: discovery, classification, exposure and access Data security posture management (DSPM) tools scan the places data is kept, decide what is sensitive, and report how exposed it is. The usual outputs are an inventory of stores, a classification per column or file, a view of who or what can reach each store, and a risk ranking. Their reader is a security team that has to find regulated data before an attacker or an auditor does. That scope fits the first stage of the [exposure map](/exposure-map/). A classification on a warehouse column is the input every later stage needs. It is not the answer to the question this site asks, which is where the value shows up after the warehouse: in a BI field, a report, a viewer's screen or an agent's reply. ## Three vendors describe the same scope in different words Cyera's platform page says it identifies sensitive and proprietary data with AI-native classification, and that it maps human, machine and agent identities to the data and resources they can reach, to uncover excessive privileges and prioritize risky access. The page names data, identities and agents as its three objects. Its capability list includes enriched classification, remediation and an access trail, and the page names no BI tool, report or report viewer. BigID's page says it can find and classify sensitive, regulated, critical and high-risk data across modern environments, and cites a classification engine with 1,500+ classifiers. It says it ties sensitivity, exposure, access and activity together and covers structured, unstructured and semi-structured data across multicloud, SaaS, IaaS, PaaS, hybrid and AI environments. These are BigID's own claims on a marketing page, and the page names no BI layer. Varonis describes its Data Security Platform as the trust layer for connecting AI to critical data, and lists AI classification that it says reaches 98%+ accuracy with no rules to write, permissions analysis of every identity and permission level, and a real-time audit trail. On 15 Oct 2026 the company announced a definitive agreement to be acquired by Proofpoint, and said nothing changes today in contracts or support. None of the 16 ranked tools lists Varonis among the security tools it names. ## What the three leave out for analytics is the part auditors ask about For analytics data, four things sit outside a store-level scan. The BI field is a new object that inherits a column's value under a new name. The report is a layer of fields and filters. The viewer is a person, often hidden behind a shared BI service account. The agent's answer is generated text assembled from several of those. A DSPM can tell you the warehouse column is a national identifier. It cannot, on the documents above, tell you which dashboard shows it or who opened that dashboard last week. This is a scope boundary, not a defect. A tool built to secure stores is judged on stores. The practical consequence is that the DSPM label needs a second tool to carry it downstream, and the reader should find out which one before buying either. ## Securiti calls itself DSPM-based, so its page is a ranked platform page Securiti is one of the 16 ranked tools. Its own page says its DSPM covers 1000+ integrations across data systems, and it says GigaOm named it a Leader in the 2026 DSPM Radar. Its exposure-map row reads documented at the column stage, partial at the BI field, none found at the report and partial at the viewer. Its main-ranking total is 29.5, rank 15 of 16. Read [the Securiti platform page](/platforms/securiti/) for the row-by-row evidence. ## Ranked tools read DSPM output and carry it to the BI field Euno, Atlan and Secoda name Cyera in the security tools their documents list. Euno and Atlan also name BigID. Euno's docs say Cyera classifications are mapped onto Snowflake and BigQuery resources and traced forward through column-level lineage into BI fields, dashboards and reports. Atlan's connector imports Cyera-discovered classifications onto Atlan assets. Secoda's docs say its Cyera integration retrieves sensitivity tags and applies matching tags to resources in Secoda. DataHub lists a BigID connector labeled Alpha that adds glossary terms, tags and risk scores to datasets. The stages these tools reach differ. On the map, the BI field stage reads documented for Euno, partial for Atlan, partial for Secoda and partial for DataHub. Euno's docs add one limit that applies to the whole pattern: BigID classifications do not appear on Looker, Tableau or Power BI assets by themselves, so the carrying step has to be set up and verified. Euno reads metadata and query logs only. ## Questions to put to a DSPM vendor about downstream exposure Put these to any DSPM vendor in writing, and compare the answers with the pages cited above. - Which BI tools does the classification reach, and is that in your docs or in a partner's? Ask for the page. - If a classified column feeds a dashboard field, where does the label show, and who can see it? - Can the product list the viewers of a report, or only the store's identities? Ask for a sample output. - What happens to the label when a column is renamed, cast or joined in a model? - Which catalog or context tool do your best customers use to carry the label, and what does the hand-off cost in setup time? - For an AI agent, can the classification be read at call time, or only after a scan? ## Sources - Cyera: platform: https://www.cyera.com/platform (read 13 Nov 2026) - BigID: data security posture management: https://bigid.com/data-security-posture-management/ (read 13 Nov 2026) - Varonis: Data Security Platform: https://www.varonis.com/platform/data-security-platform (read 13 Nov 2026) - Varonis: joining Proofpoint, 15 Oct 2026: https://www.varonis.com/blog/proofpoint (read 13 Nov 2026) - Securiti: DSPM: https://securiti.ai/dspm/ (read 13 Nov 2026) - Securiti: GigaOm 2026 DSPM Radar release: https://securiti.ai/press-release/veeams-securiti-ai-named-a-leader-and-fast-mover-in-gigaoms-2026-dspm-radar-with-top-scores-among-evaluated-vendors/ (read 13 Nov 2026) - Euno docs: Cyera integration: https://docs.euno.ai/sources/data-security/cyera-integration/cyera-integration-use-cases.md (read 13 Nov 2026) - Euno docs: BigID integration: https://docs.euno.ai/sources/data-security/bigid-integration/bigid-integration-use-cases.md (read 13 Nov 2026) - Atlan: product change log (Cyera connector): https://docs.atlan.com/data/product-change-log/llms.txt (read 13 Nov 2026) - Secoda docs: Cyera: https://docs.secoda.co/integrations/data-quality-tools/cyera.md (read 13 Nov 2026) - DataHub: integrations: https://docs.datahub.com/integrations (read 13 Nov 2026) Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/guides/what-a-dspm-covers/ --- # Snowflake enforces a sensitive field at query time, and its own record stops where the BI tool begins GUIDE, read 13 Nov 2026 **The short answer.** Snowflake classifies columns, masks them by tag, filters rows and logs column access for 365 days, and it applies those controls to agent queries too. Its own features stop at the BI field, the report and the person viewing it. This guide maps each stage and names the ranked tools that carry the field further. **Where Euno is behind.** Euno is not a policy engine or a DSPM: it reads metadata only, so it does not scan data contents or mask at the warehouse, which leaves it behind Atlan on acting on findings (5 to 7), and it publishes no dollar prices. ## Snowflake's own controls are strongest between the column and the query Snowflake says its classification feature discovers sensitive data automatically and lets you attach tags and masking policies to it. Per Snowflake's docs, a masking policy set on a tag protects every tagged column of a matching data type, and a policy attached to a tag is applied when classification applies that tag. Row access policies add row-level filtering on Enterprise Edition. Snowflake Horizon holds the column stage at documented and the agent stage at documented in the [exposure map](/exposure-map/). Snowflake says that when an AI agent queries data, the role's masking and row access policies are enforced in the query engine, the same as for a person. The managed MCP server adds its own grants: access to the server does not grant access to a tool, and each tool needs its own grant. ## The stage table shows where Snowflake's record ends Read left to right: each row is one stage of the path a sensitive column takes, with what Snowflake's features do and where they stop. | Stage | What Snowflake's own features do | Where it stops | | --- | --- | --- | | Column | Sensitive data classification writes SEMANTIC_CATEGORY and PRIVACY_CATEGORY tags; tag-based masking and row access policies act on them | Classification skips tables with more than 10,000 columns, and AI mode skips VARIANT, OBJECT and ARRAY columns | | Transformation | Tag propagation copies a tag from a source table to views and tables built on it (Enterprise Edition) | Tags set through CTAS, INSERT, MERGE or COPY INTO are not updated afterward; propagation fails past 10,000 downstream objects | | BI field | Horizon connectors read workbook and field metadata from Tableau and Power BI | None found on 13 Nov 2026: sensitivity tags carried onto BI fields; the Horizon Context page marks these connectors Preview | | Report | Connectors collect view and workbook usage and popularity | Popularity is a count, not a list of people | | Viewer | ACCESS_HISTORY records which user touched which columns, for 365 days | Latency up to 180 minutes; none found on 13 Nov 2026: named viewers per BI report | | Agent | Masking and row policies run in the engine; each MCP tool needs its own grant | SYSTEM_EXECUTE_SQL on the same server lets the client bypass the agent's semantic views | ## Classification writes system tags, and Snowflake says system tags do not propagate This is the detail most teams find late. Snowflake's classification page calls SNOWFLAKE.CORE.SEMANTIC_CATEGORY and SNOWFLAKE.CORE.PRIVACY_CATEGORY system-defined tags. Its tag propagation page lists "System tags are not propagated" under limitations. Read together, a freshly classified column does not pass its classification tag to a view on its own. The documented route is a tag map: the classification page shows a user-defined tag (such as a pii tag with the value Highly confidential) applied whenever a given system tag is applied, and user-defined tags can propagate. The same limitations list warns that a tag tied to a masking policy can sit on both a source table and a target view, so the policy may execute twice. Snowflake documents a tag removed at the source being removed from the target, which keeps a withdrawn label from lingering. Test this order in a non-production account before you rely on it, since the two pages are written separately. ## ACCESS_HISTORY answers who read a column, and a BI service account hides the viewer ACCESS_HISTORY lists the user, the objects and columns accessed, and a policies_referenced field showing which masking or row access policy applied to the query. Snowflake documents latency of up to 180 minutes, so an incident review at hour one will miss recent reads. On 20 Oct 2026 Snowflake made two Trust Center reports generally available: one lists the users and roles with privileges on tables holding sensitive data, the other lists users who accessed those tables in a chosen lookback period. Both need Enterprise Edition. Where a BI tool connects with one shared service user, the user in these records is that account. This is a reasoned reading, not a Snowflake statement: the person who opened the dashboard sits in the BI tool's own log, which is why the viewer cell reads partial. ## Which ranked tools extend it past the warehouse Four kinds of tool carry the field beyond Snowflake. Column-level lineage into BI fields is documented by Alation for Tableau and Power BI (documented at the BI field stage), by Select Star for Looker and Sigma (documented), and by Secoda for Looker and Tableau only (partial). Atlan documents column-level lineage from Tableau datasource to worksheet to dashboard and syncs Snowflake tags into its catalog; its tag propagation is off by default and chosen per tag. Euno is a context platform that reads metadata and query logs only. Per Euno's docs, it takes classifications from Cyera and BigID, maps them onto Snowflake resources, and traces them forward through column-level lineage into BI fields and reports. It ranks 1 of 16 on this site; its BI field cell reads documented and its viewer cell partial. For enforcement outside Snowflake's own policies, Immuta says it ingests Snowflake table and column tags and authors masks by tag; its Tableau setup needs a live connection, and viewers see data under their own policies when the published data source prompts for credentials. Snowflake's reach at the viewer is partial. ## Check four things before an agent connects to Snowflake data First, query SNOWFLAKE.CORE.PRIVACY_CATEGORY on the columns you care about and confirm a user-defined tag mapped to it is the one your masking policy uses. Second, expose a Cortex Agent as the client-facing tool and keep SYSTEM_EXECUTE_SQL on a separate server with a least-privileged role, as Snowflake recommends. Third, ask your BI owner whether the Tableau or Power BI connection uses per-user credentials, because that decides what ACCESS_HISTORY can say. Fourth, note the 180-minute latency in any audit runbook. ## Sources - Snowflake: sensitive data classification and system tags: https://docs.snowflake.com/en/user-guide/classify-intro.md (read 13 Nov 2026) - Snowflake: automatic tag propagation and limitations: https://docs.snowflake.com/en/user-guide/object-tagging/propagation.md (read 13 Nov 2026) - Snowflake: ACCESS_HISTORY view: https://docs.snowflake.com/en/sql-reference/account-usage/access_history.md (read 13 Nov 2026) - Snowflake: managed MCP server and grants: https://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-agents-mcp.md (read 13 Nov 2026) - Snowflake: tag-based masking policies: https://docs.snowflake.com/en/user-guide/tag-based-masking-policies.md (read 13 Nov 2026) - Snowflake: Horizon Context: https://docs.snowflake.com/en/user-guide/snowflake-horizon/horizon-context.md (read 13 Nov 2026) - Snowflake release note, 20 Oct 2026: Trust Center sensitive data reports: https://docs.snowflake.com/en/release-notes/2026/other/2026-10-20-sensitive-data-entitlement-access-reports-ga (read 13 Nov 2026) - Atlan: what it crawls from Tableau: https://docs.atlan.com/llms/connectors/tableau/what-does-atlan-crawl-from-tableau/llms.txt (read 13 Nov 2026) - Euno docs: Cyera integration: https://docs.euno.ai/sources/data-security/cyera-integration/cyera-integration-use-cases.md (read 13 Nov 2026) - Immuta docs: Tableau: https://documentation.immuta.com/saas/configuration/application-configuration/how-to-guides/bi-tools/tableau.md (read 13 Nov 2026) Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/guides/sensitive-fields-in-snowflake/ --- # Databricks carries a classified field into derived tables and Genie, and a dashboard's default setting can run it as the publisher GUIDE, read 13 Nov 2026 **The short answer.** Databricks classifies columns, turns tags into column masks and row filters, copies governed tags to derived tables in Beta, and logs MCP calls and dashboard views. Its own features stop at the publish setting of AI/BI dashboards and at Tableau and Power BI reports. This guide maps each stage and the ranked tools that extend it. **Where Euno is behind.** Euno is not a policy engine or a DSPM: it reads metadata only, so it does not scan data contents or mask at the warehouse, which leaves it behind Atlan on acting on findings (5 to 7), and it publishes no dollar prices. ## Databricks links classification, tags and masks into one chain Databricks says Data Classification tags columns automatically with class.* governed tags, covering existing and future detections, and that new tables and columns are typically classified within 24 hours. A classification result can be turned into a masking policy whose form is pre-filled with the reviewed tag. On 15 Sep 2026 Databricks added Beta scanning of Unity Catalog views. ABAC policies attach at catalog, schema or table level and support row filters and column masks, with DENY policies in Beta. In the [exposure map](/exposure-map/), Databricks Unity Catalog reads documented at the column stage and documented at the agent stage. ## The stage table shows what each Databricks layer covers Each row is one stage between the warehouse column and the agent. | Stage | What Databricks' own features do | Where it stops | | --- | --- | --- | | Column | Data Classification writes class.* governed tags; ABAC masks and filters act on them | Classification of views is Beta; none found on 13 Nov 2026: a named integration that feeds third-party labels into Unity Catalog tags | | Transformation | Tag propagation (Beta) copies a governed tag along lineage to derived tables and views, and a matching ABAC policy then applies | Serverless compute only; off by default and enabled tag by tag; custom ungoverned tags are not propagated | | BI field | AI/BI dashboards appear as downstream consumers in lineage | Tableau and Power BI assets need manual registration as external metadata objects; none found on 13 Nov 2026: automatic harvesting | | Report | Dashboard view events appear in the audit log | Scheduled-email PDF snapshots are excluded from the view event | | Viewer | Audit log and a query history system table name the user | None found on 13 Nov 2026: viewer logs for Tableau or Power BI reports on Databricks tables | | Agent | Genie enforces row filters and column masks per user; managed MCP calls are written to the audit log | The Genie Agent MCP bypasses Unity Gateway; Sensitive Data Detection on MCP is Beta | ## The default dashboard publish setting changes who a mask is applied to Databricks documents two publish settings for AI/BI dashboards. Under the default, Share data permissions, viewers run queries with the publisher's data permissions, and Databricks warns this might expose data to users who have not been granted direct access. Under Individual data permissions, each viewer runs queries with their own credentials, so a column mask or row filter evaluates for the person looking. The dashboard audit event carries a credentials_embedded parameter. The practical reading: a mask that works in Genie, which enforces policies per user, can behave differently in a dashboard published with the default. For each dashboard that draws on a classified column, record which setting it uses. This is a check a governance lead can run from the dashboard's share settings and the audit log without buying anything. Databricks also says the audit event for opening a published dashboard covers workspace users and account users, so the log can show who looked even when the query ran as someone else. Whether the masked value was shown depends on the publish setting, not on the log. ## The managed MCP audit event links a tool call to a SQL statement Databricks' audit log documents a managedMcp service whose mcpRequest event records the server type (Databricks SQL, Unity Catalog functions, AI Search or Genie), the MCP method, the tool name, and, where relevant, a sql_statement_id and the Genie conversation and message IDs. Internal service-to-service requests are excluded. Genie One MCP calls are logged one event per tool call. Databricks says MCP clients authenticate as a user or service principal, and OAuth calls run as the signed-in user. The useful join is mcpRequest to the query history system table through the statement ID, which ties an agent's request to the statement text and the user. Databricks announced on 26 Aug 2026 that statement text in system tables is masked by default, so an auditor needs the databricks_pii_access group or an account admin to read it. ## Which ranked tools extend it Databricks documents external lineage for Tableau and Power BI only by manual registration, so its BI stages read partial and partial. Tools that read the BI layer themselves close part of that gap. Alation documents column-level lineage for Tableau and Power BI (BI field documented, report documented). Select Star documents lineage and top users per dashboard (documented, documented). Atlan syncs Databricks tags and documents Tableau column-level lineage. Informatica says it extracts governance tags from Unity Catalog and pushes policies into Databricks, Power BI and Tableau, and the page read does not say the tags are propagated along lineage. Immuta says its ABAC policies appear as native Unity Catalog controls and that it ingests Unity Catalog tags. Per Euno's docs, Euno, a context platform reading metadata and query logs only, maps Cyera classifications onto warehouse resources and traces them forward into BI fields and reports; its report cell reads documented. ## Check three settings before an agent reads Databricks data Confirm the tag propagation preview is on and the governed tag is enabled for propagation, since ABAC policies do not apply to a derived column until the tag appears there. Confirm each dashboard's publish setting. Confirm whether your agent reaches data through Unity Gateway or the Genie Agent MCP, because the second relies on permissions on the Genie Agent and its data instead. ## Sources - Databricks: Data Classification: https://docs.databricks.com/aws/en/data-governance/unity-catalog/data-classification (read 13 Nov 2026) - Databricks: governed tag propagation: https://docs.databricks.com/aws/en/admin/governed-tags/tag-propagation (read 13 Nov 2026) - Databricks: attribute-based access control: https://docs.databricks.com/aws/en/data-governance/unity-catalog/abac/ (read 13 Nov 2026) - Databricks: audit log reference: https://docs.databricks.com/aws/en/admin/account-settings/audit-logs (read 13 Nov 2026) - Databricks: share and publish AI/BI dashboards: https://docs.databricks.com/aws/en/dashboards/share/ (read 13 Nov 2026) - Databricks: Genie set up: https://docs.databricks.com/aws/en/genie/set-up (read 13 Nov 2026) - Databricks: managed MCP servers: https://docs.databricks.com/aws/en/agents/mcp-tools/built-in-mcp-services (read 13 Nov 2026) - Databricks: external lineage: https://docs.databricks.com/aws/en/data-governance/unity-catalog/external-lineage (read 13 Nov 2026) - Databricks release notes, August 2026: https://docs.databricks.com/aws/en/release-notes/product/2026/august (read 13 Nov 2026) - Databricks release notes, September 2026: https://docs.databricks.com/aws/en/release-notes/product/2026/september (read 13 Nov 2026) - Immuta docs: tag ingestion from catalogs: https://documentation.immuta.com/saas/configuration/tags/catalogs.md (read 13 Nov 2026) Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/guides/sensitive-fields-in-databricks/ --- # Sensitivity labels follow a field downstream inside Power BI, but the inheritance rules and the shift from Purview to Fabric limit how far GUIDE, read 13 Nov 2026 **The short answer.** Microsoft's labels pass from three source types into Power BI semantic models, then to reports, dashboards and supported exports, and the activity log records who acted. Inheritance stops above 80 downstream items, and Microsoft says Purview Data Governance support ends 12 Nov 2027. This guide maps the stages and the ranked tools that extend them. **Where Euno is behind.** Euno is not a policy engine or a DSPM: it reads metadata only, so it does not scan data contents or mask at the warehouse, which leaves it behind Atlan on acting on findings (5 to 7), and it publishes no dollar prices. ## Labels are the Microsoft estate's way to follow a field, and they start from three sources Microsoft documents that a Power BI semantic model inherits a sensitivity label from only three source types: Excel on OneDrive or SharePoint, Azure Synapse Analytics and Azure SQL Database. Labels in Azure SQL and Synapse are applied through a two-step Purview flow, and a tenant setting must be on in Power BI. A Snowflake, Databricks or BigQuery column labeled somewhere else does not arrive this way. Microsoft Purview reads documented at the column stage and partial at the BI field in the [exposure map](/exposure-map/). The [Microsoft estate view](/best-for/microsoft-estate/) ranks the tools for this stack. ## The stage table shows how far Microsoft's own features reach Each row is one stage of the path from the source column to the person and the agent. | Stage | What Microsoft's own features do | Where it stops | | --- | --- | --- | | Column | Purview Data Map classifies assets in scans with more than 200 built-in classifications | Applying labels to Data Map assets is in preview, with pay-as-you-go billing | | Transformation | A label on a semantic model flows to dependent models, reports and dashboards, shown in lineage view | Stops entirely above 80 downstream items; never overwrites a manual label or applies a less restrictive one | | BI field | Column-level Power BI lineage in Purview | Only when Azure SQL Database is the source; none found on 13 Nov 2026: Snowflake column to Power BI field lineage | | Report | New reports and dashboards inherit the parent label; Power BI applies the label to Excel, PDF and PowerPoint exports | Encryption applies only to supported export paths; the admin must block the rest. Protection policies cover semantic models but not reports or dashboards | | Viewer | The Power BI activity log records who took which action on which item | Events can arrive up to 60 minutes late, and the API returns one day per request; RLS does not restrict workspace Admin, Member or Contributor roles | | Agent | AI interaction events reach the unified audit log; Copilot for Power BI is supported, other Fabric Copilots in preview | The Power BI Authoring MCP server can edit security roles and is not for consumption | ## Row-level security and labels answer different questions Microsoft's RLS page says row-level security only restricts data access for users with Viewer permissions and does not apply to workspace Admin, Member or Contributor roles. A label says how a file must be handled once it leaves; RLS decides which rows a Viewer sees. The label overview adds that users granted access to a report reach the entire underlying semantic model unless RLS limits them. Labeled content inside the service is visible, but the encryption settings are not applied there. They apply to data that leaves through a supported export path. The overview says the admin can block export from unsupported paths. So a sensitive field in a Power BI report is only as protected as the export settings on the tenant. Ask the Power BI admin for the export setting before you rely on any label as a control. ## Purview's governance catalog is retiring, so the label source and the governance surface now split Microsoft's 2026 announcement says Purview Data Governance will be retired, that Microsoft Fabric is now its data governance solution, and that support ends Nov. 12, 2027. Microsoft's Learn banner says new Unified Catalog accounts can no longer be created and existing capabilities stay in maintenance mode through that date. Microsoft also says the Purview brand stays focused on data security and compliance: classifying, labeling, protecting data, DLP and AI. Labels and the activity log therefore remain in Purview, while the catalog side moves. For a plan that runs past 2027, treat Information Protection labels and the Power BI activity log as the durable parts, and do not build new work on the Unified Catalog. DSPM for AI is a separate piece: Microsoft's what's-new page says the new DSPM is generally available while partner solutions for non-Microsoft sources and the Data Security Posture Agent remain in preview. ## Which ranked tools extend it Euno, a context platform that reads metadata and query logs only, says in its docs that its Purview integration discovers Purview DLP policies and links them to Power BI resources, and that it collects Power BI impressions from the Fabric user activity log with distinct users over 14, 30 and 60 days. It ranks 1 of 16 here, with BI field documented and viewer partial. Immuta says it ingests tags from Microsoft Purview and requires personal credentials for Power BI after publishing, so its policies follow the viewer (BI field none found). Atlan documents a Power BI miner that reads activity events for usage metrics (partial at the report stage). Securiti says it can import sensitivity labels from a Microsoft security center (viewer partial). Informatica says it pushes policies into Power BI. Alation documents column-level lineage for its Power BI scanner (documented). Select Star and Ataccama document Power BI metadata and lineage, with Ataccama's connection one-way. ## Check the inheritance mode, the 80-item limit and the export setting first Three items decide how far a label travels. Open the downstream inheritance setting: labels from data sources propagate downstream only in fully automated mode, and the default asks the user for consent. Count the downstream items of your most sensitive semantic model against the limit of 80. Then ask for the tenant's export setting. Add a calendar line for 12 Nov 2027 to any plan that depends on the Unified Catalog. ## Sources - Microsoft Learn: label inheritance from data sources: https://learn.microsoft.com/power-bi/enterprise/service-security-sensitivity-label-inheritance-from-data-sources (read 13 Nov 2026) - Microsoft Learn: downstream inheritance: https://learn.microsoft.com/power-bi/enterprise/service-security-sensitivity-label-downstream-inheritance (read 13 Nov 2026) - Microsoft Learn: sensitivity labels in Power BI: https://learn.microsoft.com/power-bi/enterprise/service-security-sensitivity-label-overview (read 13 Nov 2026) - Microsoft Learn: row-level security in Fabric and Power BI: https://learn.microsoft.com/en-us/fabric/security/service-admin-row-level-security (read 13 Nov 2026) - Microsoft Learn: Power BI auditing: https://learn.microsoft.com/power-bi/enterprise/service-admin-auditing (read 13 Nov 2026) - Microsoft Learn: protection policies: https://learn.microsoft.com/fabric/governance/protection-policies-overview (read 13 Nov 2026) - Microsoft Learn: Purview for AI interactions: https://learn.microsoft.com/purview/ai-microsoft-purview (read 13 Nov 2026) - Microsoft: next step in data governance strategy: https://techcommunity.microsoft.com/blog/microsoft-security-blog/a-next-step-in-the-evolution-of-the-microsoft-data-governance-strategy/4572227 (read 13 Nov 2026) - Microsoft Learn: Purview what's new: https://learn.microsoft.com/purview/whats-new (read 13 Nov 2026) - Euno docs: Microsoft Purview integration: https://docs.euno.ai/sources/data-security/microsoft-purview-integration.md (read 13 Nov 2026) Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/guides/sensitive-fields-in-fabric-and-power-bi/ --- # Tableau shows a sensitivity label that a person sets, and its audit record is a 90-day log of who opened what GUIDE, read 13 Nov 2026 **The short answer.** Tableau Catalog lets an administrator attach a sensitivity label to a column or table and shows it on downstream content, but a person sets it. Row-level security uses user filters or data policies, and Admin Insights logs view access for 90 days. This guide maps each stage and names the ranked tools that document Tableau. **Where Euno is behind.** Euno is not a policy engine or a DSPM: it reads metadata only, so it does not scan data contents or mask at the warehouse, which leaves it behind Atlan on acting on findings (5 to 7), and it publishes no dollar prices. ## Tableau's sensitivity label is metadata set by a person and read downstream Tableau offers sensitivity labels as a category of data label in Tableau Cloud and Tableau Server, with a Data Management license. Tableau's docs say you can attach them to databases, tables, columns, data sources, flows and virtual connections, and that a label on an asset also shows on downstream assets that use it. A user must be a server or site administrator or hold the Overwrite capability on the asset to set one. The single built-in label is Sensitive data, and administrators can add more through the label manager or the REST API. The pages read describe a person choosing the label in a dialog. Importing sensitivity labels from a classifier, Microsoft Purview or Snowflake tags into Tableau's data labels: none found on 13 Nov 2026 in those pages. The REST API's label methods would let a tool write labels, but this guide found no ranked tool that documents doing so. ## The stage table shows where Tableau's own record ends Each row is one stage between the source column and the viewer. | Stage | What Tableau's own features do | Where it stops | | --- | --- | --- | | Column | Tableau Catalog lets stewards label tables and columns as sensitive | The label is set by hand; none found on 13 Nov 2026: automatic classification | | Transformation | Tableau Catalog indexes flows, data sources and virtual connections and shows their lineage | Limited to content on the Tableau site and the external assets it identifies | | BI field | Quality warnings and sensitivity labels appear on downstream data sources and workbooks | A label on a column warns authors; it does not mask the field | | Report | High-visibility labels notify anyone who opens a published view; they can be included in subscription emails | Needs the admin option for subscriptions; exported files: none found on 13 Nov 2026 in the pages read | | Viewer | TS Events in Admin Insights lists actor user name, item type and item for each event | Tableau Cloud only; 90 days by default, 365 days with Advanced Management | | Agent | Not covered by the pages read | None found on 13 Nov 2026: a Tableau-native record of which agent received a labeled field | ## Row-level security in Tableau protects rows, not columns Tableau documents user filters and entitlement tables for row-level security in Desktop. Virtual connections add data policies, which Tableau says support row-level security at the connection level and apply to any workbook, data source or flow that uses the connection. A policy condition is evaluated for every row at query time. Virtual connections and data policies are licensed through Data Management. Column masking: none found on 13 Nov 2026 in the virtual connection page. Immuta's docs add the other half: it needs a live connection to enforce policies in Tableau, and viewers see data under their own policies only when the published data source prompts them for credentials. On a reasoned reading, an extract holds whatever its author could query. When you review a Tableau report, check connection type and credential prompt before you trust a policy. ## Admin Insights is the who-saw-it record, and its window is short Tableau's TS Events data source is described as the primary audit source, with each row one event: sign-in, publishing, accessing views. It carries the actor's email, site role and license role, the item type (data source, workbook or view), the item's current and historical name, and the item owner. Admin Insights holds up to 90 days by default and up to 365 days with an Advanced Management license, per the Tableau page. A regulated field shown on a dashboard viewed 400 days ago may have no Tableau record. A team with a 7-year retention rule should export the events to a store it controls. The Tableau record names a viewer of a view. It does not say whether the sensitive field was on that view, which is why the lineage tools below matter. ## Which ranked tools document Tableau Six ranked tools list Tableau among their BI systems with column or field detail. Atlan documents column-level lineage from datasource to worksheet to dashboard (BI field partial, report partial), though it does not support Tableau unique-viewer counts. Alation documents column-level lineage to Tableau report fields (documented) and says report popularity is a view count that does not name viewers. Secoda documents column-level lineage into Tableau, one of two BI tools (partial). Select Star tracks Tableau models and dashboards back to source (documented). Ataccama maps Tableau fields to database columns (partial). DataHub notes that a site role below Site Administrator Explorer limits field metadata and column-level lineage. Informatica says its Spring 2026 release adds Policy Pushdown for Tableau. Securiti says its Tableau connector classifies data in Tableau's PII object, a data-subject-request use, not report scanning (partial). Euno reads metadata and query logs only; per Euno's docs it propagates BigID and Cyera classifications to Tableau fields and reports and gives distinct Tableau users per resource over 14, 30 and 60 days (documented, partial). Microsoft Purview lists Tableau with no scan capability (partial). Snowflake Horizon and Databricks Unity Catalog each read Tableau metadata through connectors or manual registration. ## Check three things on a Tableau report that shows a regulated field Find out who set the sensitivity label and when, since it is manual. Check whether the data source uses a live connection with a credential prompt or an extract. Export Admin Insights events on a schedule shorter than 90 days. Then ask a lineage tool from the list above which dashboards the labeled column feeds. ## Sources - Tableau Help: Data Labels: https://help.tableau.com/current/online/en-us/dm_labels.htm (read 13 Nov 2026) - Tableau Help: Sensitivity Labels: https://help.tableau.com/current/online/en-us/dm_labels_sensitivity.htm (read 13 Nov 2026) - Tableau Help: Admin Insights custom views: https://help.tableau.com/current/online/en-us/adminview_insights.htm (read 13 Nov 2026) - Tableau Help: TS Events data source: https://help.tableau.com/current/online/en-us/adminview_insights_events.htm (read 13 Nov 2026) - Tableau Help: virtual connections and data policies: https://help.tableau.com/current/online/en-us/dm_vconn_overview.htm (read 13 Nov 2026) - Tableau Help: user filters and row-level security: https://help.tableau.com/current/pro/desktop/en-us/publish_userfilters.htm (read 13 Nov 2026) - Atlan: what it crawls from Tableau: https://docs.atlan.com/llms/connectors/tableau/what-does-atlan-crawl-from-tableau/llms.txt (read 13 Nov 2026) - Alation docs: Tableau popularity: https://documentation.alation.com/en/latest/OpenConnectorFramework/BIConnectors/TableauOCFConnector/TableauOCFPopularity.md (read 13 Nov 2026) - Secoda docs: data lineage: https://docs.secoda.co/features/data-lineage.md (read 13 Nov 2026) - Immuta docs: Tableau: https://documentation.immuta.com/saas/configuration/application-configuration/how-to-guides/bi-tools/tableau.md (read 13 Nov 2026) Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/guides/sensitive-fields-in-tableau/ --- # Looker restricts a sensitive field through access rules, not labels, and keeps 90 days of query history GUIDE, read 13 Nov 2026 **The short answer.** Looker's LookML tags are not used by the Looker model, and hidden is not a security feature, per Google Cloud's docs. Access grants, access filters and sql_always_where do the restricting, and System Activity keeps the History table for 90 days. Atlan, Alation, DataHub, Select Star, Secoda and Collibra document Looker. **Where Euno is behind.** Euno is not a policy engine or a DSPM: it reads metadata only, so it does not scan data contents or mask at the warehouse, which leaves it behind Atlan on acting on findings (5 to 7), and it publishes no dollar prices. ## Looker marks fields with tags that its own model ignores LookML lets a developer add a tags parameter to a dimension or measure. Google Cloud's docs say these strings are not used by the Looker model. They can be passed to other applications through integrated services on the Action panel or through API calls. A tag named pii therefore describes a field to outside software and enforces nothing in Looker. The hidden parameter is a similar trap. The docs say a hidden field is still accessible in the UI if someone adds it to the URL, and that hidden keeps the field picker clean and is not a security feature. A governance review that counts hidden fields as protected fields is counting the wrong thing. ## Access grants, user attributes and filters do the restricting An access grant is defined in a model file against a user attribute and a list of allowed values. Adding required_access_grants to an Explore, join, view or field limits it to users who hold every listed grant. Users without them do not see the field in the picker, and a Look that uses it shows a warning that the field no longer exists or is not accessible. An access_filter applies a user attribute as a filter on a field, per Explore. Google's page is direct about the failure mode: if you forget to add access_filter to an Explore that should have it, the data will not be restricted and users can see all of it in that Explore. The sql_always_where parameter inserts a condition into the WHERE clause that users cannot change, applies to dashboards, scheduled Looks and embedded content on that Explore, and is not shown unless the user reads the generated SQL. Content access is a separate setting. It decides who may view or manage a folder, and the admin docs say data access, feature access and content access combine to set what a user can do. A field protected by an access grant can still sit in a folder many people can open, so review the three together. ## The warehouse sees Looker's identity, not always the viewer's Looker connects to BigQuery either with a service account or with per-user Google OAuth. Looker's BigQuery page says OAuth lets database administrators audit which Looker users are running queries and enforce role-based controls with Google permissions. With a service account, BigQuery sees one principal for everyone. BigQuery column-level security with policy tags is checked against the identity that runs the query, so policy tags protect a Looker user's view only where that user's own identity reaches BigQuery. A second BigQuery rule matters for rebuilt tables. BigQuery's docs say a write with the WRITE_TRUNCATE disposition removes existing policy tags unless the destination schema supplies them, while WRITE_APPEND preserves them. Ask the Looker team whether any table a model reads is overwritten that way. ## System Activity answers who ran what, for a limited window System Activity gives admins Explores over Looker's internal database. The usage docs state that the History table is truncated to the past 90 days, that most tables are truncated on a schedule, and that Elite System Activity is the route to longer retention. The Explore refreshes every 12 hours. The History Explore covers only content executed within the retention window, so a dashboard nobody opened recently appears in the Dashboard Explore and not in History. One detail is easy to miss and affects audit work. The Role view reflects current role assignments, so joining History to Role shows a user's current role next to their past queries, not the role they held when the query ran. An auditor asking who could see a field last quarter gets an answer that may be wrong for anyone whose role changed. Export History on a schedule and store the role snapshot beside it. ## Ranked tools that document Looker, and what each adds Atlan documents field-level lineage for Looker views, explores, looks, tiles and dashboards. DataHub lists column-level lineage for Looker as enabled by default and can pull historical dashboard usage from Looker System Activity, which is the 90-day History data described above. Select Star says its Looker integration gives column-level lineage from source views to LookML views, explores and dashboards. Alation, Collibra, Secoda and Euno also list Looker among the BI tools they read. None of these descriptions says the tool reads LookML access grants or access filters; none found on 13 Nov 2026 in the evidence files for this site, so ask each vendor whether the lineage view shows which fields are restricted. On the exposure map, the BI field stage reads partial for Atlan, documented for Alation, partial for DataHub, documented for Select Star, partial for Secoda, partial for Collibra and documented for Euno. The report stage reads partial, documented, partial, documented, partial, partial and documented in the same order. See [the BI field column](/exposure-map/bi-field/) for the rows behind each cell. Take the field-level view from the tools above, not the restriction view: the restriction is in LookML and the connection. ## Sign-off for Looker comes down to four checks Before sign-off, list the explores that expose a sensitive source column, confirm each has an access_filter or a required_access_grants entry, confirm the connection uses per-user OAuth where policy tags are the control, and schedule the History export before the 90-day window drops the evidence. ## Sources - Google Cloud: LookML field tags: https://cloud.google.com/looker/docs/reference/param-field-tags (read 13 Nov 2026) - Google Cloud: LookML field hidden: https://cloud.google.com/looker/docs/reference/param-field-hidden (read 13 Nov 2026) - Google Cloud: required_access_grants for fields: https://cloud.google.com/looker/docs/reference/param-field-required-access-grants (read 13 Nov 2026) - Google Cloud: LookML access_filter: https://cloud.google.com/looker/docs/reference/param-explore-access-filter (read 13 Nov 2026) - Google Cloud: LookML sql_always_where: https://cloud.google.com/looker/docs/reference/param-explore-sql-always-where (read 13 Nov 2026) - Google Cloud: Looker access control: https://cloud.google.com/looker/docs/access-control-and-permission-management (read 13 Nov 2026) - Google Cloud: Looker BigQuery connection: https://cloud.google.com/looker/docs/db-config-google-bigquery (read 13 Nov 2026) - Google Cloud: BigQuery column-level security: https://cloud.google.com/bigquery/docs/column-level-security-intro (read 13 Nov 2026) - Google Cloud: System Activity Explores: https://cloud.google.com/looker/docs/usage-reports-with-system-activity-explores (read 13 Nov 2026) - Atlan: what Atlan crawls from Looker: https://docs.atlan.com/llms/connectors/looker/what-does-atlan-crawl-from-looker/llms.txt (read 13 Nov 2026) - DataHub: Looker source: https://docs.datahub.com/docs/generated/ingestion/sources/looker (read 13 Nov 2026) - Select Star: Looker integration: https://www.selectstar.com/integrations/looker (read 13 Nov 2026) Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/guides/sensitive-fields-in-looker/ --- # dbt records a sensitive column by hand and does not carry the mark from a source column into the models GUIDE, read 13 Nov 2026 **The short answer.** dbt holds sensitivity as hand-written tags and meta on columns, and its docs say a column's tags and meta do not inherit from the parent resource. Grants run at build time and masking is left to warehouse policies. Of the 16 ranked tools, ten name dbt among the transformation tools they read. **Where Euno is behind.** Euno is not a policy engine or a DSPM: it reads metadata only, so it does not scan data contents or mask at the warehouse, which leaves it behind Atlan on acting on findings (5 to 7), and it publishes no dollar prices. ## dbt marks sensitivity with tags and meta that a person writes dbt's reference docs show the pattern directly: a source column is designated as containing PII by setting a meta key such as contains_pii to true in YAML,; the tags config can mark whole models the same way. Automatic detection of sensitive columns in dbt's docs: none found on 13 Nov 2026. A person decides, types the key and keeps it current. That makes the mark as good as the process around it. A column added next sprint carries no mark until someone adds one, and nothing in dbt's docs raises a flag when the warehouse's own classification disagrees with the YAML. ## A column's tags and meta stop at the column dbt's columns reference says columns are not resources, so their tags and meta are not true configurations. In its words, they do not inherit the tags or meta values of their parent resources. The same reasoning extends across models: a source column marked contains_pii true does not hand that mark to the model column that selects it. Each model that exposes the value needs its own entry, or a tool outside dbt has to read the lineage and copy the mark. Two related limits are easy to miss. dbt's meta docs say changes to meta, including at the column level, do not trigger state:modified, because dbt treats meta and tags as metadata only. A pull request that adds or removes a PII flag will not, by that rule alone, select the model in a state-based CI run. And the persist_docs config, which writes descriptions into the warehouse as comments, is documented as not implemented for sources, and it writes descriptions, not meta keys. A PII flag kept only in meta never reaches the warehouse through that route. ## Contracts and access control structure, not readers A model contract is checked at build time: a model that does not match its declared columns and types fails to build. Contracts, access and versions apply to models only, not to sources, seeds or snapshots, so the layer where raw sensitive columns land is outside them. Contracts can declare constraints such as not_null, but the docs describe them as column shape, not as sensitivity. The access modifiers (private, protected, public) govern who may ref() a model: the same group, the same project, or anyone. dbt's docs state that model access is not user access. They also say that when a macro is invoked with dbt run-operation, dbt does not enforce model access or group controls. An approver who reads private as hidden from analysts has read a feature that governs project references, not warehouse queries. ## Grants and masking happen in the warehouse, and dbt only issues them The grants config applies privileges at build time: when a model finishes building, dbt ensures the grants on the table or view match the configuration exactly, and the grants are included in the manifest. That gives a reviewable record of who can select from each model. It works at table level. For row- and column-level access and masking policies, dbt's grants page points to hooks and says to write the statements manually. The policy itself lives in the warehouse. For Databricks, dbt Labs documents a databricks_tags config (dbt-databricks 1.11 or higher) that applies Unity Catalog tags to materialized views and streaming tables, which is one route for a model-level mark to reach the platform's tag-based controls. Immuta's docs describe a related timing issue: its policies attach by tag to tables created by dbt, but it does not receive DDL events from the data platform, which leaves a window it calls policy downtime that its documented steps are meant to shorten. ## Docs and exposures describe consumers without describing sensitivity dbt exposures declare downstream uses such as dashboards, with an owner and a maturity of high, medium or low. Exposures carry no sensitivity field. An exposure tells a reviewer that a dashboard depends on a model. Whether the model holds a regulated value is back to the hand-written tag. ## Ten ranked tools read dbt and some carry the mark further The tools that list dbt among the transformation tools they read are Euno, Collibra, Atlan, Alation, Ataccama ONE, Databricks Unity Catalog, Snowflake Horizon, DataHub, Select Star and Secoda. The rest of the 16 name none: Informatica, Immuta, Privacera, Securiti, OneTrust and Microsoft Purview list no dbt connector in their evidence files. On the exposure map, the transformation stage reads partial for Euno, partial for Atlan, partial for Collibra, partial for Alation, partial for Ataccama ONE, partial for Databricks, partial for Snowflake, partial for DataHub, partial for Select Star and partial for Secoda. What they add differs. Atlan says it crawls and syncs tags from sources including dbt. Select Star says dbt tags are synced and can be matched to its own tags, with PII tags as an example. Euno's AlphaSense write-up describes a rule that flags anything depending on a PII column upstream as not AI-ready, which reads upstream dependency instead of a hand-written tag on the downstream model. See [the transformation column](/exposure-map/transformation/) and the [classification guide](/guides/classification-from-warehouse-to-agent/) for the full set. ## Checks before you rely on a dbt tag for a regulated field Count the models that select a tagged source column and see how many carry their own tag. Run a CI check that fails a pull request when a PII source column is selected by an untagged model column. Confirm the warehouse policy, not the YAML, is what hides the value. Ask each tool you use which mark it trusts when dbt and the warehouse classification disagree. ## Sources - dbt docs: meta: https://docs.getdbt.com/reference/resource-configs/meta (read 13 Nov 2026) - dbt docs: columns: https://docs.getdbt.com/reference/resource-properties/columns (read 13 Nov 2026) - dbt docs: persist_docs: https://docs.getdbt.com/reference/resource-configs/persist_docs (read 13 Nov 2026) - dbt docs: model contracts: https://docs.getdbt.com/docs/mesh/govern/model-contracts (read 13 Nov 2026) - dbt docs: model access: https://docs.getdbt.com/docs/mesh/govern/model-access (read 13 Nov 2026) - dbt docs: grants: https://docs.getdbt.com/reference/resource-configs/grants (read 13 Nov 2026) - dbt docs: Databricks configs: https://docs.getdbt.com/reference/resource-configs/databricks-configs (read 13 Nov 2026) - dbt docs: exposures: https://docs.getdbt.com/docs/build/exposures (read 13 Nov 2026) - Immuta: dbt transform workflow: https://documentation.immuta.com/saas/govern/authoring-policies-in-secure/dbt-transform-workflow.md (read 13 Nov 2026) - Atlan: tags: https://docs.atlan.com/llms/governance/tags/what-are-tags/llms.txt (read 13 Nov 2026) - Select Star: docs: https://web.archive.org/web/20260715110406/https://docs.selectstar.com/llms-full.txt (read 13 Nov 2026) - Euno: AlphaSense and dbt write-up: https://euno.ai/blog/alphasense-x-euno-dbt-summit-26 (read 13 Nov 2026) Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/guides/sensitive-fields-in-dbt/ --- # 11 guides for the lead who has to prove where a regulated field went GUIDES, read 13 Nov 2026 **The short answer.** Eleven guides cover where a policy stops and the business layer starts, how a classification travels to the report and the agent, who saw a field against who could see it, approving an agent before it connects, what a DSPM leaves out, and how far six stacks follow a sensitive field. - [Where a warehouse policy stops and the business layer starts](/guides/where-a-policy-stops/): Snowflake masking, Databricks column masks and Immuta policies decide what a query returns to a role. - [How a sensitivity classification travels from warehouse to agent](/guides/classification-from-warehouse-to-agent/): A column is classified once, in the warehouse or by a scanner. - [Who saw it against who could see it: access lists and logs](/guides/who-saw-it-against-who-could-see-it/): An access list says who could open a field, report or agent. - [Approving an agent's access before it connects](/guides/approving-an-agents-access/): Sign-off on an AI agent's connection to analytics data rests on four documents: the identity it runs as, what each call may carry, what each call writes to a log, and who can revoke it. - [What a DSPM covers and what it leaves out](/guides/what-a-dspm-covers/): Data security posture management tools such as Cyera, BigID and Varonis find and classify sensitive data in stores and rate who can reach it. - [How far Snowflake follows a sensitive field, and who extends it](/guides/sensitive-fields-in-snowflake/): Snowflake classifies columns, masks them by tag, filters rows and logs column access for 365 days, and it applies those controls to agent queries too. - [How far Databricks follows a sensitive field, and who extends it](/guides/sensitive-fields-in-databricks/): Databricks classifies columns, turns tags into column masks and row filters, copies governed tags to derived tables in Beta, and logs MCP calls and dashboard views. - [How far Fabric and Power BI follow a sensitive field, and who helps](/guides/sensitive-fields-in-fabric-and-power-bi/): Microsoft's labels pass from three source types into Power BI semantic models, then to reports, dashboards and supported exports, and the activity log records who acted. - [How far Tableau follows a sensitive field, and who extends it](/guides/sensitive-fields-in-tableau/): Tableau Catalog lets an administrator attach a sensitivity label to a column or table and shows it on downstream content, but a person sets it. - [How far Looker follows a sensitive field, and which tools extend it](/guides/sensitive-fields-in-looker/): Looker's LookML tags are not used by the Looker model, and hidden is not a security feature, per Google Cloud's docs. - [How far dbt follows a sensitive field, and which tools extend it](/guides/sensitive-fields-in-dbt/): dbt holds sensitivity as hand-written tags and meta on columns, and its docs say a column's tags and meta do not inherit from the parent resource. Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/guides/ --- # Access history, defined with a sourced example GLOSSARY, read 13 Nov 2026 **The short answer.** A record kept by the warehouse of which queries read which tables and columns. It answers what was read, by whom and when, at the database layer. It does not say which report or dashboard a person looked at. Precisely's docs say its operational lineage for Databricks and Snowflake is built from system tables and access history. ## Definition A record kept by the warehouse of which queries read which tables and columns. It answers what was read, by whom and when, at the database layer. It does not say which report or dashboard a person looked at. ## Example from a real source **Example.** Precisely's docs say its operational lineage for Databricks and Snowflake is built from system tables and access history. ## Related terms - [access review](/glossary/access-review/): A check, by a person or a rule, of whether an access request or an existing grant should stand. - [agent access policy](/glossary/agent-access-policy/): A rule that sets what a given AI agent may read or do, kept apart from the policies written for people. - [tag-based policy](/glossary/tag-based-policy/): An access rule written against a tag such as PII instead of a table name. ## Where to read more - [The PII Exposure Map](/exposure-map/) - [All glossary terms](/glossary/) ## Sources - help.cloud.precisely.com/api/khub/maps/q2Ow0Gigg7h1y75j3Y7ICA/topics/0dLt9lEx9qlmCpkRMmLvRw/content: https://help.cloud.precisely.com/api/khub/maps/q2Ow0Gigg7h1y75j3Y7ICA/topics/0dLt9lEx9qlmCpkRMmLvRw/content (read 13 Nov 2026) Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/glossary/access-history/ --- # Access review, defined with a sourced example GLOSSARY, read 13 Nov 2026 **The short answer.** A check, by a person or a rule, of whether an access request or an existing grant should stand. It produces a decision and a record. Agent requests need the same review as human ones. Immuta says a dynamic review flow can auto-approve, deny or route access requests, including agent requests, to a human reviewer. ## Definition A check, by a person or a rule, of whether an access request or an existing grant should stand. It produces a decision and a record. Agent requests need the same review as human ones. ## Example from a real source **Example.** Immuta says a dynamic review flow can auto-approve, deny or route access requests, including agent requests, to a human reviewer. ## Related terms - [agent access policy](/glossary/agent-access-policy/): A rule that sets what a given AI agent may read or do, kept apart from the policies written for people. - [AI data governance](/glossary/ai-data-governance/): The rules and records that decide which data an AI system may read, what it may be told about that data, and who can prove it afterward. - [access history](/glossary/access-history/): A record kept by the warehouse of which queries read which tables and columns. ## Where to read more - [The PII Exposure Map](/exposure-map/) - [All glossary terms](/glossary/) ## Sources - documentation.immuta.com/saas/releases/index.md: https://documentation.immuta.com/saas/releases/index.md (read 13 Nov 2026) Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/glossary/access-review/ --- # Agent access policy, defined with a sourced example GLOSSARY, read 13 Nov 2026 **The short answer.** A rule that sets what a given AI agent may read or do, kept apart from the policies written for people. It names the agent, the data it may reach and the actions it may take. OvalEdge's docs say that after OAuth 2.0 sign-in to its MCP server, role-based access, policies and audit logging still apply. ## Definition A rule that sets what a given AI agent may read or do, kept apart from the policies written for people. It names the agent, the data it may reach and the actions it may take. Reviewers use it to approve an agent before it connects. ## Example from a real source **Example.** OvalEdge's docs say that after OAuth 2.0 sign-in to its MCP server, role-based access, policies and audit logging still apply. ## Related terms - [AI data governance](/glossary/ai-data-governance/): The rules and records that decide which data an AI system may read, what it may be told about that data, and who can prove it afterward. - [attribute-based access control (ABAC)](/glossary/attribute-based-access-control/): A way to grant access by comparing attributes of the person, the data and the situation, rather than by listing who may open which table. - [access review](/glossary/access-review/): A check, by a person or a rule, of whether an access request or an existing grant should stand. ## Where to read more - [The PII Exposure Map](/exposure-map/) - [All glossary terms](/glossary/) ## Sources - docs.ovaledge.com/release8.3/mcp-server/whats-new.md: https://docs.ovaledge.com/release8.3/mcp-server/whats-new.md (read 13 Nov 2026) Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/glossary/agent-access-policy/ --- # AI data governance, defined with a sourced example GLOSSARY, read 13 Nov 2026 **The short answer.** The rules and records that decide which data an AI system may read, what it may be told about that data, and who can prove it afterward. Trust3 AI's overview, per Privacera's docs, describes an agent inventory that records which agents can access sensitive data and an approval workflow before production. ## Definition The rules and records that decide which data an AI system may read, what it may be told about that data, and who can prove it afterward. For analytics data it covers sensitivity, access, audit and the reports where regulated fields show up. It is narrower than governing the models themselves. ## Example from a real source **Example.** Trust3 AI's overview, per Privacera's docs, describes an agent inventory that records which agents can access sensitive data and an approval workflow before production. ## Related terms - [attribute-based access control (ABAC)](/glossary/attribute-based-access-control/): A way to grant access by comparing attributes of the person, the data and the situation, rather than by listing who may open which table. - [audit log](/glossary/audit-log/): A time-ordered record of who did what in a system, such as a sign-in, a query or a policy change. - [agent access policy](/glossary/agent-access-policy/): A rule that sets what a given AI agent may read or do, kept apart from the policies written for people. ## Where to read more - [The PII Exposure Map](/exposure-map/) - [All glossary terms](/glossary/) ## Sources - docs.trust3.ai/get-started/overview.html: https://docs.trust3.ai/get-started/overview.html (read 13 Nov 2026) Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/glossary/ai-data-governance/ --- # Attribute-based access control (ABAC), defined with a sourced example GLOSSARY, read 13 Nov 2026 **The short answer.** A way to grant access by comparing attributes of the person, the data and the situation, rather than by listing who may open which table. One rule can cover many tables because it reads tags such as sensitivity. Informatica's September 2024 post says its policy pushdown controls access to Snowflake tables and views by data and user-group attributes. ## Definition A way to grant access by comparing attributes of the person, the data and the situation, rather than by listing who may open which table. One rule can cover many tables because it reads tags such as sensitivity. New data that carries the tag is covered the day it appears. ## Example from a real source **Example.** Informatica's September 2024 post says its policy pushdown controls access to Snowflake tables and views by data and user-group attributes. ## Related terms - [audit log](/glossary/audit-log/): A time-ordered record of who did what in a system, such as a sign-in, a query or a policy change. - [BI field exposure](/glossary/bi-field-exposure/): The presence of a sensitive source column in a field that a report, dashboard or semantic model shows. - [AI data governance](/glossary/ai-data-governance/): The rules and records that decide which data an AI system may read, what it may be told about that data, and who can prove it afterward. ## Where to read more - [The PII Exposure Map](/exposure-map/) - [All glossary terms](/glossary/) ## Sources - www.informatica.com/blogs/how-idmc-supports-native-security-controls-in-snowflake.html: https://www.informatica.com/blogs/how-idmc-supports-native-security-controls-in-snowflake.html (read 13 Nov 2026) Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/glossary/attribute-based-access-control/ --- # Audit log, defined with a sourced example GLOSSARY, read 13 Nov 2026 **The short answer.** A time-ordered record of who did what in a system, such as a sign-in, a query or a policy change. Auditors ask for it to show that controls ran. Databricks' docs say its audit log records AI/BI dashboard view events, including a user opening the published version of a dashboard. ## Definition A time-ordered record of who did what in a system, such as a sign-in, a query or a policy change. Auditors ask for it to show that controls ran. What it can show depends on which events the product chooses to write. ## Example from a real source **Example.** Databricks' docs say its audit log records AI/BI dashboard view events, including a user opening the published version of a dashboard. ## Related terms - [BI field exposure](/glossary/bi-field-exposure/): The presence of a sensitive source column in a field that a report, dashboard or semantic model shows. - [classification inheritance](/glossary/classification-inheritance/): A new data field takes its sensitivity classification from a type or parent it is linked to, instead of a person labeling each field. - [attribute-based access control (ABAC)](/glossary/attribute-based-access-control/): A way to grant access by comparing attributes of the person, the data and the situation, rather than by listing who may open which table. ## Where to read more - [The PII Exposure Map](/exposure-map/) - [All glossary terms](/glossary/) ## Sources - docs.databricks.com/aws/en/admin/account-settings/audit-logs: https://docs.databricks.com/aws/en/admin/account-settings/audit-logs (read 13 Nov 2026) Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/glossary/audit-log/ --- # BI field exposure, defined with a sourced example GLOSSARY, read 13 Nov 2026 **The short answer.** The presence of a sensitive source column in a field that a report, dashboard or semantic model shows. A column classified in the warehouse can reach a BI field with no label attached. Euno's docs say BigID classifications do not appear on Looker, Tableau or Power BI assets by themselves, and that Euno propagates them to downstream fields and reports. ## Definition The presence of a sensitive source column in a field that a report, dashboard or semantic model shows. A column classified in the warehouse can reach a BI field with no label attached. Listing those fields is how a team answers which reports show a regulated value. ## Example from a real source **Example.** Euno's docs say BigID classifications do not appear on Looker, Tableau or Power BI assets by themselves, and that Euno propagates them to downstream fields and reports. ## Related terms - [classification inheritance](/glossary/classification-inheritance/): A new data field takes its sensitivity classification from a type or parent it is linked to, instead of a person labeling each field. - [column mask](/glossary/column-mask/): A rule attached to a column that changes the value a reader sees, for example by hashing it or hiding all but a few characters. - [audit log](/glossary/audit-log/): A time-ordered record of who did what in a system, such as a sign-in, a query or a policy change. ## Where to read more - [The PII Exposure Map](/exposure-map/) - [All glossary terms](/glossary/) ## Sources - docs.euno.ai/sources/data-security/bigid-integration/bigid-integration-use-cases.md: https://docs.euno.ai/sources/data-security/bigid-integration/bigid-integration-use-cases.md (read 13 Nov 2026) Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/glossary/bi-field-exposure/ --- # Classification inheritance, defined with a sourced example GLOSSARY, read 13 Nov 2026 **The short answer.** A new data field takes its sensitivity classification from a type or parent it is linked to, instead of a person labeling each field. This works at the moment the link is made. Precisely's docs say a semantic type can carry a sensitivity classification that a field inherits when the type is assigned. ## Definition A new data field takes its sensitivity classification from a type or parent it is linked to, instead of a person labeling each field. This works at the moment the link is made. It covers one level of assignment, and says nothing about copies made later. ## Example from a real source **Example.** Precisely's docs say a semantic type can carry a sensitivity classification that a field inherits when the type is assigned. ## Related terms - [column mask](/glossary/column-mask/): A rule attached to a column that changes the value a reader sees, for example by hashing it or hiding all but a few characters. - [consent and purpose limitation](/glossary/consent-and-purpose-limitation/): Personal data is collected for a stated reason and used only in ways that fit it. - [BI field exposure](/glossary/bi-field-exposure/): The presence of a sensitive source column in a field that a report, dashboard or semantic model shows. ## Where to read more - [The PII Exposure Map](/exposure-map/) - [All glossary terms](/glossary/) ## Sources - help.cloud.precisely.com/api/khub/maps/q2Ow0Gigg7h1y75j3Y7ICA/topics/jPctSPYe1Yv7PE4wqNfaYg/content: https://help.cloud.precisely.com/api/khub/maps/q2Ow0Gigg7h1y75j3Y7ICA/topics/jPctSPYe1Yv7PE4wqNfaYg/content (read 13 Nov 2026) Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/glossary/classification-inheritance/ --- # Column mask, defined with a sourced example GLOSSARY, read 13 Nov 2026 **The short answer.** A rule attached to a column that changes the value a reader sees, for example by hashing it or hiding all but a few characters. The stored data stays whole. Atlan's docs say its data policies can apply column-level masking such as hashing, redaction or showing only the last four characters. ## Definition A rule attached to a column that changes the value a reader sees, for example by hashing it or hiding all but a few characters. The stored data stays whole. Who sees the real value is decided by role, group or tag. ## Example from a real source **Example.** Atlan's docs say its data policies can apply column-level masking such as hashing, redaction or showing only the last four characters. ## Related terms - [consent and purpose limitation](/glossary/consent-and-purpose-limitation/): Personal data is collected for a stated reason and used only in ways that fit it. - [copilot oversharing](/glossary/copilot-oversharing/): An AI assistant returns content a person is technically allowed to open but should never have been shown, because file or report permissions were set too wide. - [classification inheritance](/glossary/classification-inheritance/): A new data field takes its sensitivity classification from a type or parent it is linked to, instead of a person labeling each field. ## Where to read more - [The PII Exposure Map](/exposure-map/) - [All glossary terms](/glossary/) ## Sources - docs.atlan.com/llms/governance/access-control/data-policy/llms.txt: https://docs.atlan.com/llms/governance/access-control/data-policy/llms.txt (read 13 Nov 2026) Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/glossary/column-mask/ --- # Consent and purpose limitation, defined with a sourced example GLOSSARY, read 13 Nov 2026 **The short answer.** Personal data is collected for a stated reason and used only in ways that fit it. Consent is one legal basis for that reason. GDPR Article 5(1)(b), as published at gdpr-info.eu, says personal data must be collected for specified, explicit and legitimate purposes and not processed further in a way that is incompatible with them. ## Definition Personal data is collected for a stated reason and used only in ways that fit it. Consent is one legal basis for that reason. A new use, such as training a model, needs a check against the original purpose. ## Example from a real source **Example.** GDPR Article 5(1)(b), as published at gdpr-info.eu, says personal data must be collected for specified, explicit and legitimate purposes and not processed further in a way that is incompatible with them. ## Related terms - [copilot oversharing](/glossary/copilot-oversharing/): An AI assistant returns content a person is technically allowed to open but should never have been shown, because file or report permissions were set too wide. - [data access governance](/glossary/data-access-governance/): The practice of deciding, approving and recording who can read which data, with the rules enforced in the systems that hold it. - [column mask](/glossary/column-mask/): A rule attached to a column that changes the value a reader sees, for example by hashing it or hiding all but a few characters. ## Where to read more - [The PII Exposure Map](/exposure-map/) - [All glossary terms](/glossary/) ## Sources - gdpr-info.eu/art-5-gdpr/: https://gdpr-info.eu/art-5-gdpr/ (read 13 Nov 2026) Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/glossary/consent-and-purpose-limitation/ --- # Copilot oversharing, defined with a sourced example GLOSSARY, read 13 Nov 2026 **The short answer.** An AI assistant returns content a person is technically allowed to open but should never have been shown, because file or report permissions were set too wide. Microsoft's docs describe Fabric protection policies that tie a sensitivity label to an allow-list of users and groups and block everyone else from labeled items. ## Definition An AI assistant returns content a person is technically allowed to open but should never have been shown, because file or report permissions were set too wide. The assistant makes old permission mistakes easy to find. Fixing it means tightening labels and access before turning the assistant on. ## Example from a real source **Example.** Microsoft's docs describe Fabric protection policies that tie a sensitivity label to an allow-list of users and groups and block everyone else from labeled items. ## Related terms - [data access governance](/glossary/data-access-governance/): The practice of deciding, approving and recording who can read which data, with the rules enforced in the systems that hold it. - [data classification](/glossary/data-classification/): Sorting data into categories such as public, internal, personal or restricted, usually by scanning column names and values. - [consent and purpose limitation](/glossary/consent-and-purpose-limitation/): Personal data is collected for a stated reason and used only in ways that fit it. ## Where to read more - [The PII Exposure Map](/exposure-map/) - [All glossary terms](/glossary/) ## Sources - learn.microsoft.com/fabric/governance/protection-policies-overview: https://learn.microsoft.com/fabric/governance/protection-policies-overview (read 13 Nov 2026) Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/glossary/copilot-oversharing/ --- # Data access governance, defined with a sourced example GLOSSARY, read 13 Nov 2026 **The short answer.** The practice of deciding, approving and recording who can read which data, with the rules enforced in the systems that hold it. Collibra announced in its press release that it acquired Raito, a data access governance company, which underlies its Data Access product for masking and filtering. ## Definition The practice of deciding, approving and recording who can read which data, with the rules enforced in the systems that hold it. It sits between data owners who know what is sensitive and platforms that serve queries. It is about access, not about describing or cataloging data. ## Example from a real source **Example.** Collibra announced in its press release that it acquired Raito, a data access governance company, which underlies its Data Access product for masking and filtering. ## Related terms - [data classification](/glossary/data-classification/): Sorting data into categories such as public, internal, personal or restricted, usually by scanning column names and values. - [data loss prevention (DLP)](/glossary/data-loss-prevention/): Controls that detect sensitive content and warn, alert or block before it leaves its allowed place. - [copilot oversharing](/glossary/copilot-oversharing/): An AI assistant returns content a person is technically allowed to open but should never have been shown, because file or report permissions were set too wide. ## Where to read more - [The PII Exposure Map](/exposure-map/) - [All glossary terms](/glossary/) ## Sources - www.prnewswire.com/news-releases/collibra-announces-the-acquisition-of-raito-and-new-powerful-advancements-in-unified-governance-for-data-and-ai-across-every-data-citizen-302472460.html: https://www.prnewswire.com/news-releases/collibra-announces-the-acquisition-of-raito-and-new-powerful-advancements-in-unified-governance-for-data-and-ai-across-every-data-citizen-302472460.html (read 13 Nov 2026) Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/glossary/data-access-governance/ --- # Data classification, defined with a sourced example GLOSSARY, read 13 Nov 2026 **The short answer.** Sorting data into categories such as public, internal, personal or restricted, usually by scanning column names and values. The category then drives handling rules like masking or deny. Accuracy depends on the scanner and on a person reviewing the result. Databricks says its Data Classification feature tags columns with class.* governed tags when automatic tagging is enabled. ## Definition Sorting data into categories such as public, internal, personal or restricted, usually by scanning column names and values. The category then drives handling rules like masking or deny. Accuracy depends on the scanner and on a person reviewing the result. ## Example from a real source **Example.** Databricks says its Data Classification feature tags columns with class.* governed tags when automatic tagging is enabled. ## Related terms - [data loss prevention (DLP)](/glossary/data-loss-prevention/): Controls that detect sensitive content and warn, alert or block before it leaves its allowed place. - [data minimization](/glossary/data-minimization/): Collect, keep and expose only the data a task needs. - [data access governance](/glossary/data-access-governance/): The practice of deciding, approving and recording who can read which data, with the rules enforced in the systems that hold it. ## Where to read more - [The PII Exposure Map](/exposure-map/) - [All glossary terms](/glossary/) ## Sources - docs.databricks.com/aws/en/data-governance/unity-catalog/data-classification: https://docs.databricks.com/aws/en/data-governance/unity-catalog/data-classification (read 13 Nov 2026) Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/glossary/data-classification/ --- # Data loss prevention (DLP), defined with a sourced example GLOSSARY, read 13 Nov 2026 **The short answer.** Controls that detect sensitive content and warn, alert or block before it leaves its allowed place. Typical triggers are a file, a message or a paste into a website. Microsoft documents DLP for Fabric and Power BI that can attach policy tips, alert admins and restrict access to items with sensitive content. ## Definition Controls that detect sensitive content and warn, alert or block before it leaves its allowed place. Typical triggers are a file, a message or a paste into a website. In BI the item is a report or semantic model with sensitive content. ## Example from a real source **Example.** Microsoft documents DLP for Fabric and Power BI that can attach policy tips, alert admins and restrict access to items with sensitive content. ## Related terms - [data minimization](/glossary/data-minimization/): Collect, keep and expose only the data a task needs. - [data residency](/glossary/data-residency/): The requirement that data stay in a stated country or region, or move out only under set conditions. - [data classification](/glossary/data-classification/): Sorting data into categories such as public, internal, personal or restricted, usually by scanning column names and values. ## Where to read more - [The PII Exposure Map](/exposure-map/) - [All glossary terms](/glossary/) ## Sources - learn.microsoft.com/purview/dlp-powerbi-get-started: https://learn.microsoft.com/purview/dlp-powerbi-get-started (read 13 Nov 2026) Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/glossary/data-loss-prevention/ --- # Data minimization, defined with a sourced example GLOSSARY, read 13 Nov 2026 **The short answer.** Collect, keep and expose only the data a task needs. For analytics, it means leaving out columns that a report or agent has no use for. GDPR Article 5(1)(c), as published at gdpr-info.eu, requires personal data to be adequate, relevant and limited to what is necessary for the purposes of processing. ## Definition Collect, keep and expose only the data a task needs. For analytics, it means leaving out columns that a report or agent has no use for. It is easier to prove when exposed fields are listed. ## Example from a real source **Example.** GDPR Article 5(1)(c), as published at gdpr-info.eu, requires personal data to be adequate, relevant and limited to what is necessary for the purposes of processing. ## Related terms - [data residency](/glossary/data-residency/): The requirement that data stay in a stated country or region, or move out only under set conditions. - [data subject request](/glossary/data-subject-request/): A request from a person asking a company what personal data it holds about them, or asking for a copy, correction or deletion. - [data loss prevention (DLP)](/glossary/data-loss-prevention/): Controls that detect sensitive content and warn, alert or block before it leaves its allowed place. ## Where to read more - [The PII Exposure Map](/exposure-map/) - [All glossary terms](/glossary/) ## Sources - gdpr-info.eu/art-5-gdpr/: https://gdpr-info.eu/art-5-gdpr/ (read 13 Nov 2026) Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/glossary/data-minimization/ --- # Data residency, defined with a sourced example GLOSSARY, read 13 Nov 2026 **The short answer.** The requirement that data stay in a stated country or region, or move out only under set conditions. GDPR Article 44, as published at gdpr-info.eu, sets a general principle that transfers of personal data to a third country or international organization may take place only if the regulation's conditions are met. ## Definition The requirement that data stay in a stated country or region, or move out only under set conditions. It applies to stored copies and to where processing happens. Teams check it for warehouses, BI services and any hosted AI service that receives the data. ## Example from a real source **Example.** GDPR Article 44, as published at gdpr-info.eu, sets a general principle that transfers of personal data to a third country or international organization may take place only if the regulation's conditions are met. ## Related terms - [data subject request](/glossary/data-subject-request/): A request from a person asking a company what personal data it holds about them, or asking for a copy, correction or deletion. - [dynamic data masking](/glossary/dynamic-data-masking/): Hiding or altering a value at the moment a query runs, based on who is asking. - [data minimization](/glossary/data-minimization/): Collect, keep and expose only the data a task needs. ## Where to read more - [The PII Exposure Map](/exposure-map/) - [All glossary terms](/glossary/) ## Sources - gdpr-info.eu/art-44-gdpr/: https://gdpr-info.eu/art-44-gdpr/ (read 13 Nov 2026) Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/glossary/data-residency/ --- # Data subject request, defined with a sourced example GLOSSARY, read 13 Nov 2026 **The short answer.** A request from a person asking a company what personal data it holds about them, or asking for a copy, correction or deletion. GDPR Article 15, as published at gdpr-info.eu, gives the data subject the right to obtain confirmation of whether personal data about them is processed and, if so, access to it. ## Definition A request from a person asking a company what personal data it holds about them, or asking for a copy, correction or deletion. The company must find that person's data across its systems, including analytics copies. A deadline applies, so search has to be fast. ## Example from a real source **Example.** GDPR Article 15, as published at gdpr-info.eu, gives the data subject the right to obtain confirmation of whether personal data about them is processed and, if so, access to it. ## Related terms - [dynamic data masking](/glossary/dynamic-data-masking/): Hiding or altering a value at the moment a query runs, based on who is asking. - [exposure path](/glossary/exposure-path/): The chain from a sensitive source column through transformations to the report, dashboard or agent answer where it can be seen. - [data residency](/glossary/data-residency/): The requirement that data stay in a stated country or region, or move out only under set conditions. ## Where to read more - [The PII Exposure Map](/exposure-map/) - [All glossary terms](/glossary/) ## Sources - gdpr-info.eu/art-15-gdpr/: https://gdpr-info.eu/art-15-gdpr/ (read 13 Nov 2026) Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/glossary/data-subject-request/ --- # Dynamic data masking, defined with a sourced example GLOSSARY, read 13 Nov 2026 **The short answer.** Hiding or altering a value at the moment a query runs, based on who is asking. The stored data is untouched, and two readers of the same column can see different results. It is applied by policy, not by copying a cleaned table. Snowflake documents Dynamic Data Masking as masking column data at query time by policy. ## Definition Hiding or altering a value at the moment a query runs, based on who is asking. The stored data is untouched, and two readers of the same column can see different results. It is applied by policy, not by copying a cleaned table. ## Example from a real source **Example.** Snowflake documents Dynamic Data Masking as masking column data at query time by policy. ## Related terms - [exposure path](/glossary/exposure-path/): The chain from a sensitive source column through transformations to the report, dashboard or agent answer where it can be seen. - [label downstream inheritance](/glossary/label-downstream-inheritance/): A report or dataset picks up the sensitivity label of the source it was built from. - [data subject request](/glossary/data-subject-request/): A request from a person asking a company what personal data it holds about them, or asking for a copy, correction or deletion. ## Where to read more - [The PII Exposure Map](/exposure-map/) - [All glossary terms](/glossary/) ## Sources - docs.snowflake.com/en/user-guide/security-column-intro.md: https://docs.snowflake.com/en/user-guide/security-column-intro.md (read 13 Nov 2026) Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/glossary/dynamic-data-masking/ --- # Exposure path, defined with a sourced example GLOSSARY, read 13 Nov 2026 **The short answer.** The chain from a sensitive source column through transformations to the report, dashboard or agent answer where it can be seen. Following the path shows every place a regulated value can surface. Euno's docs say Cyera classifies sensitive data in the warehouse and Euno propagates those classifications through column-level lineage into BI fields, dashboards and reports. ## Definition The chain from a sensitive source column through transformations to the report, dashboard or agent answer where it can be seen. Following the path shows every place a regulated value can surface. A break in the chain, such as a column renamed in a view, hides the rest. ## Example from a real source **Example.** Euno's docs say Cyera classifies sensitive data in the warehouse and Euno propagates those classifications through column-level lineage into BI fields, dashboards and reports. ## Related terms - [label downstream inheritance](/glossary/label-downstream-inheritance/): A report or dataset picks up the sensitivity label of the source it was built from. - [least privilege](/glossary/least-privilege/): Give each person, service or agent only the access the job needs, and nothing more. - [dynamic data masking](/glossary/dynamic-data-masking/): Hiding or altering a value at the moment a query runs, based on who is asking. ## Where to read more - [The PII Exposure Map](/exposure-map/) - [All glossary terms](/glossary/) ## Sources - docs.euno.ai/sources/data-security/cyera-integration/cyera-integration-use-cases.md: https://docs.euno.ai/sources/data-security/cyera-integration/cyera-integration-use-cases.md (read 13 Nov 2026) Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/glossary/exposure-path/ --- # Label downstream inheritance, defined with a sourced example GLOSSARY, read 13 Nov 2026 **The short answer.** A report or dataset picks up the sensitivity label of the source it was built from. It stops the label from being lost at the BI layer. Microsoft documents that Power BI semantic models inherit sensitivity labels from only three source types: Excel on OneDrive or SharePoint, Azure Synapse Analytics and Azure SQL Database. ## Definition A report or dataset picks up the sensitivity label of the source it was built from. It stops the label from being lost at the BI layer. Coverage varies by source type, so many reports still need a person to set it. ## Example from a real source **Example.** Microsoft documents that Power BI semantic models inherit sensitivity labels from only three source types: Excel on OneDrive or SharePoint, Azure Synapse Analytics and Azure SQL Database. ## Related terms - [least privilege](/glossary/least-privilege/): Give each person, service or agent only the access the job needs, and nothing more. - [need to know](/glossary/need-to-know/): The principle that having clearance is not enough: a person sees a piece of sensitive data only if their work requires it. - [exposure path](/glossary/exposure-path/): The chain from a sensitive source column through transformations to the report, dashboard or agent answer where it can be seen. ## Where to read more - [The PII Exposure Map](/exposure-map/) - [All glossary terms](/glossary/) ## Sources - learn.microsoft.com/power-bi/enterprise/service-security-sensitivity-label-inheritance-from-data-sources: https://learn.microsoft.com/power-bi/enterprise/service-security-sensitivity-label-inheritance-from-data-sources (read 13 Nov 2026) Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/glossary/label-downstream-inheritance/ --- # Least privilege, defined with a sourced example GLOSSARY, read 13 Nov 2026 **The short answer.** Give each person, service or agent only the access the job needs, and nothing more. The test is the smallest role that still works. For agents it argues against reusing a person's broad token. OpenMetadata's docs recommend a Bot service-account token for unattended agents, with access set by a role-based policy assigned to the bot. ## Definition Give each person, service or agent only the access the job needs, and nothing more. The test is the smallest role that still works. For agents it argues against reusing a person's broad token. ## Example from a real source **Example.** OpenMetadata's docs recommend a Bot service-account token for unattended agents, with access set by a role-based policy assigned to the bot. ## Related terms - [need to know](/glossary/need-to-know/): The principle that having clearance is not enough: a person sees a piece of sensitive data only if their work requires it. - [on-behalf-of authentication](/glossary/on-behalf-of-authentication/): A pattern where an agent calls a data system as itself but for a named person, so the request carries both identities. - [label downstream inheritance](/glossary/label-downstream-inheritance/): A report or dataset picks up the sensitivity label of the source it was built from. ## Where to read more - [The PII Exposure Map](/exposure-map/) - [All glossary terms](/glossary/) ## Sources - docs.open-metadata.org/v2.0.x/how-to-guides/mcp.md: https://docs.open-metadata.org/v2.0.x/how-to-guides/mcp.md (read 13 Nov 2026) Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/glossary/least-privilege/ --- # Need to know, defined with a sourced example GLOSSARY, read 13 Nov 2026 **The short answer.** The principle that having clearance is not enough: a person sees a piece of sensitive data only if their work requires it. It narrows access below the level a role would give. This site is named for it. Ataccama's docs say classification tags on terms hide data in sensitive attributes from unauthorized users. ## Definition The principle that having clearance is not enough: a person sees a piece of sensitive data only if their work requires it. It narrows access below the level a role would give. This site is named for it. ## Example from a real source **Example.** Ataccama's docs say classification tags on terms hide data in sensitive attributes from unauthorized users. ## Related terms - [on-behalf-of authentication](/glossary/on-behalf-of-authentication/): A pattern where an agent calls a data system as itself but for a named person, so the request carries both identities. - [PCI data](/glossary/pci-data/): Payment card data covered by the PCI DSS standard, mainly the card number and the items stored with it. - [least privilege](/glossary/least-privilege/): Give each person, service or agent only the access the job needs, and nothing more. ## Where to read more - [The PII Exposure Map](/exposure-map/) - [All glossary terms](/glossary/) ## Sources - docs.ataccama.com/one/latest/user-access-management/data-protection-classification.html: https://docs.ataccama.com/one/latest/user-access-management/data-protection-classification.html (read 13 Nov 2026) Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/glossary/need-to-know/ --- # On-behalf-of authentication, defined with a sourced example GLOSSARY, read 13 Nov 2026 **The short answer.** A pattern where an agent calls a data system as itself but for a named person, so the request carries both identities. The system can then limit the answer to what that person may see. Immuta says an on-behalf-of agent gets the union of the agent's permissions and the requesting user's entitlements, through a vended role. ## Definition A pattern where an agent calls a data system as itself but for a named person, so the request carries both identities. The system can then limit the answer to what that person may see. Logs record the person, not just the agent. ## Example from a real source **Example.** Immuta says an on-behalf-of agent gets the union of the agent's permissions and the requesting user's entitlements, through a vended role. ## Related terms - [PCI data](/glossary/pci-data/): Payment card data covered by the PCI DSS standard, mainly the card number and the items stored with it. - [PHI](/glossary/phi/): Protected health information: health data tied to an identifiable person and held by a covered entity or its business associate under HIPAA. - [need to know](/glossary/need-to-know/): The principle that having clearance is not enough: a person sees a piece of sensitive data only if their work requires it. ## Where to read more - [The PII Exposure Map](/exposure-map/) - [All glossary terms](/glossary/) ## Sources - documentation.immuta.com/saas/agentic-data-access/introduction.md: https://documentation.immuta.com/saas/agentic-data-access/introduction.md (read 13 Nov 2026) Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/glossary/on-behalf-of-authentication/ --- # PCI data, defined with a sourced example GLOSSARY, read 13 Nov 2026 **The short answer.** Payment card data covered by the PCI DSS standard, mainly the card number and the items stored with it. Handling it triggers extra controls on where it sits and who can read it. The PCI Security Standards Council glossary says cardholder data consists, at a minimum, of the full primary account number. ## Definition Payment card data covered by the PCI DSS standard, mainly the card number and the items stored with it. Handling it triggers extra controls on where it sits and who can read it. Analytics copies of card data fall inside those controls. ## Example from a real source **Example.** The PCI Security Standards Council glossary says cardholder data consists, at a minimum, of the full primary account number. ## Related terms - [PHI](/glossary/phi/): Protected health information: health data tied to an identifiable person and held by a covered entity or its business associate under HIPAA. - [PII](/glossary/pii/): Personally identifiable information: data that can point to a specific person, alone or when combined, such as a name, email or ID number. - [on-behalf-of authentication](/glossary/on-behalf-of-authentication/): A pattern where an agent calls a data system as itself but for a named person, so the request carries both identities. ## Where to read more - [The PII Exposure Map](/exposure-map/) - [All glossary terms](/glossary/) ## Sources - www.pcisecuritystandards.org/pci_security/glossary/: https://www.pcisecuritystandards.org/pci_security/glossary/ (read 13 Nov 2026) Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/glossary/pci-data/ --- # PHI, defined with a sourced example GLOSSARY, read 13 Nov 2026 **The short answer.** Protected health information: health data tied to an identifiable person and held by a covered entity or its business associate under HIPAA. The rule applies in analytics copies as much as in the clinical system. Title 45 CFR 160.103, as published by Cornell's Legal Information Institute, defines protected health information as individually identifiable health information. ## Definition Protected health information: health data tied to an identifiable person and held by a covered entity or its business associate under HIPAA. The rule applies in analytics copies as much as in the clinical system. A de-identified table falls outside it only if the removal standard is met. ## Example from a real source **Example.** Title 45 CFR 160.103, as published by Cornell's Legal Information Institute, defines protected health information as individually identifiable health information. ## Related terms - [PII](/glossary/pii/): Personally identifiable information: data that can point to a specific person, alone or when combined, such as a name, email or ID number. - [purpose-based access](/glossary/purpose-based-access/): Access that depends on the reason for the request as well as the role. - [PCI data](/glossary/pci-data/): Payment card data covered by the PCI DSS standard, mainly the card number and the items stored with it. ## Where to read more - [The PII Exposure Map](/exposure-map/) - [All glossary terms](/glossary/) ## Sources - www.law.cornell.edu/cfr/text/45/160.103: https://www.law.cornell.edu/cfr/text/45/160.103 (read 13 Nov 2026) Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/glossary/phi/ --- # PII, defined with a sourced example GLOSSARY, read 13 Nov 2026 **The short answer.** Personally identifiable information: data that can point to a specific person, alone or when combined, such as a name, email or ID number. Tools find it by pattern match, by column name or by classification tags. Monte Carlo says its PII inventory combines its own in-warehouse scans with existing warehouse classification tags from Snowflake and Databricks. ## Definition Personally identifiable information: data that can point to a specific person, alone or when combined, such as a name, email or ID number. Tools find it by pattern match, by column name or by classification tags. Each method misses some columns. ## Example from a real source **Example.** Monte Carlo says its PII inventory combines its own in-warehouse scans with existing warehouse classification tags from Snowflake and Databricks. ## Related terms - [purpose-based access](/glossary/purpose-based-access/): Access that depends on the reason for the request as well as the role. - [report viewer log](/glossary/report-viewer-log/): A record that names each person who opened a given report or dashboard, and when. - [PHI](/glossary/phi/): Protected health information: health data tied to an identifiable person and held by a covered entity or its business associate under HIPAA. ## Where to read more - [The PII Exposure Map](/exposure-map/) - [All glossary terms](/glossary/) ## Sources - docs.getmontecarlo.com/docs/pii-detection: https://docs.getmontecarlo.com/docs/pii-detection (read 13 Nov 2026) Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/glossary/pii/ --- # Purpose-based access, defined with a sourced example GLOSSARY, read 13 Nov 2026 **The short answer.** Access that depends on the reason for the request as well as the role. The same person may see real values for one approved purpose and masked values for another. The purpose has to be recorded to be auditable. Collibra says its Data Access product masks sensitive fields by user role or access purpose. ## Definition Access that depends on the reason for the request as well as the role. The same person may see real values for one approved purpose and masked values for another. The purpose has to be recorded to be auditable. ## Example from a real source **Example.** Collibra says its Data Access product masks sensitive fields by user role or access purpose. ## Related terms - [report viewer log](/glossary/report-viewer-log/): A record that names each person who opened a given report or dashboard, and when. - [retention policy](/glossary/retention-policy/): A rule for how long a kind of record is kept before it is deleted or archived. - [PII](/glossary/pii/): Personally identifiable information: data that can point to a specific person, alone or when combined, such as a name, email or ID number. ## Where to read more - [The PII Exposure Map](/exposure-map/) - [All glossary terms](/glossary/) ## Sources - www.collibra.com/products/data-access: https://www.collibra.com/products/data-access (read 13 Nov 2026) Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/glossary/purpose-based-access/ --- # Report viewer log, defined with a sourced example GLOSSARY, read 13 Nov 2026 **The short answer.** A record that names each person who opened a given report or dashboard, and when. It is the evidence an auditor wants after a sensitive field is found in a report. Alation's docs say Tableau report popularity comes from view counts, which count views but do not name viewers. ## Definition A record that names each person who opened a given report or dashboard, and when. It is the evidence an auditor wants after a sensitive field is found in a report. Many BI tools keep only counts, or log the shared account instead of the person. ## Example from a real source **Example.** Alation's docs say Tableau report popularity comes from view counts, which count views but do not name viewers. ## Related terms - [retention policy](/glossary/retention-policy/): A rule for how long a kind of record is kept before it is deleted or archived. - [role-based access control (RBAC)](/glossary/role-based-access-control/): Access is granted to roles, and people or services are given roles. - [purpose-based access](/glossary/purpose-based-access/): Access that depends on the reason for the request as well as the role. ## Where to read more - [The PII Exposure Map](/exposure-map/) - [All glossary terms](/glossary/) ## Sources - documentation.alation.com/en/latest/OpenConnectorFramework/BIConnectors/TableauOCFConnector/TableauOCFPopularity.md: https://documentation.alation.com/en/latest/OpenConnectorFramework/BIConnectors/TableauOCFConnector/TableauOCFPopularity.md (read 13 Nov 2026) Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/glossary/report-viewer-log/ --- # Retention policy, defined with a sourced example GLOSSARY, read 13 Nov 2026 **The short answer.** A rule for how long a kind of record is kept before it is deleted or archived. It applies to data and also to the logs that prove access. Immuta says its audit logs expire after 90 days unless exported to S3 or ADLS Gen2. ## Definition A rule for how long a kind of record is kept before it is deleted or archived. It applies to data and also to the logs that prove access. Too short and the audit trail is gone, too long and the record becomes its own exposure. ## Example from a real source **Example.** Immuta says its audit logs expire after 90 days unless exported to S3 or ADLS Gen2. ## Related terms - [role-based access control (RBAC)](/glossary/role-based-access-control/): Access is granted to roles, and people or services are given roles. - [row access policy](/glossary/row-access-policy/): A policy attached to a table that decides which rows a query may return for the person running it. - [report viewer log](/glossary/report-viewer-log/): A record that names each person who opened a given report or dashboard, and when. ## Where to read more - [The PII Exposure Map](/exposure-map/) - [All glossary terms](/glossary/) ## Sources - documentation.immuta.com/saas/govern/detect-introduction/index.md: https://documentation.immuta.com/saas/govern/detect-introduction/index.md (read 13 Nov 2026) Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/glossary/retention-policy/ --- # Role-based access control (RBAC), defined with a sourced example GLOSSARY, read 13 Nov 2026 **The short answer.** Access is granted to roles, and people or services are given roles. It is simple to review and to explain. Alone it cannot say that one column is sensitive, which is why teams add tag or attribute rules. Snowflake documents role-based access control for its managed MCP server and its tools. ## Definition Access is granted to roles, and people or services are given roles. It is simple to review and to explain. Alone it cannot say that one column is sensitive, which is why teams add tag or attribute rules. ## Example from a real source **Example.** Snowflake documents role-based access control for its managed MCP server and its tools. ## Related terms - [row access policy](/glossary/row-access-policy/): A policy attached to a table that decides which rows a query may return for the person running it. - [row filter](/glossary/row-filter/): A rule that removes rows from a result based on who is asking, for example showing only one region's customers. - [retention policy](/glossary/retention-policy/): A rule for how long a kind of record is kept before it is deleted or archived. ## Where to read more - [The PII Exposure Map](/exposure-map/) - [All glossary terms](/glossary/) ## Sources - docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-agents-mcp.md: https://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-agents-mcp.md (read 13 Nov 2026) Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/glossary/role-based-access-control/ --- # Row access policy, defined with a sourced example GLOSSARY, read 13 Nov 2026 **The short answer.** A policy attached to a table that decides which rows a query may return for the person running it. It is evaluated on each query, so one table can serve many teams. Snowflake's name for row-level security. Snowflake documents row access policies for row-level security, available in Enterprise Edition. ## Definition A policy attached to a table that decides which rows a query may return for the person running it. It is evaluated on each query, so one table can serve many teams. Snowflake's name for row-level security. ## Example from a real source **Example.** Snowflake documents row access policies for row-level security, available in Enterprise Edition. ## Related terms - [row filter](/glossary/row-filter/): A rule that removes rows from a result based on who is asking, for example showing only one region's customers. - [sensitive data](/glossary/sensitive-data/): Data whose exposure could harm a person or the company, such as personal, health, financial or secret business records. - [role-based access control (RBAC)](/glossary/role-based-access-control/): Access is granted to roles, and people or services are given roles. ## Where to read more - [The PII Exposure Map](/exposure-map/) - [All glossary terms](/glossary/) ## Sources - docs.snowflake.com/en/user-guide/security-row-intro.md: https://docs.snowflake.com/en/user-guide/security-row-intro.md (read 13 Nov 2026) Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/glossary/row-access-policy/ --- # Row filter, defined with a sourced example GLOSSARY, read 13 Nov 2026 **The short answer.** A rule that removes rows from a result based on who is asking, for example showing only one region's customers. The rows stay in the table. It is the row-side partner of a column mask. Collibra says its Data Access product applies masking and row filtering automatically from data classifications such as PII and PHI. ## Definition A rule that removes rows from a result based on who is asking, for example showing only one region's customers. The rows stay in the table. It is the row-side partner of a column mask. ## Example from a real source **Example.** Collibra says its Data Access product applies masking and row filtering automatically from data classifications such as PII and PHI. ## Related terms - [sensitive data](/glossary/sensitive-data/): Data whose exposure could harm a person or the company, such as personal, health, financial or secret business records. - [sensitivity label](/glossary/sensitivity-label/): A tag that states how carefully an item must be handled, such as public, internal or highly confidential. - [row access policy](/glossary/row-access-policy/): A policy attached to a table that decides which rows a query may return for the person running it. ## Where to read more - [The PII Exposure Map](/exposure-map/) - [All glossary terms](/glossary/) ## Sources - www.collibra.com/products/data-access: https://www.collibra.com/products/data-access (read 13 Nov 2026) Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/glossary/row-filter/ --- # Sensitive data, defined with a sourced example GLOSSARY, read 13 Nov 2026 **The short answer.** Data whose exposure could harm a person or the company, such as personal, health, financial or secret business records. What counts depends on law and policy. A tool can only protect it after something has marked it. Informatica says its CLAIRE engine automates sensitive data classification, covering PII and personal and financial records, as part of its CDAM product. ## Definition Data whose exposure could harm a person or the company, such as personal, health, financial or secret business records. What counts depends on law and policy. A tool can only protect it after something has marked it. ## Example from a real source **Example.** Informatica says its CLAIRE engine automates sensitive data classification, covering PII and personal and financial records, as part of its CDAM product. ## Related terms - [sensitivity label](/glossary/sensitivity-label/): A tag that states how carefully an item must be handled, such as public, internal or highly confidential. - [service principal](/glossary/service-principal/): A non-human identity that a program, pipeline or agent uses to sign in. - [row filter](/glossary/row-filter/): A rule that removes rows from a result based on who is asking, for example showing only one region's customers. ## Where to read more - [The PII Exposure Map](/exposure-map/) - [All glossary terms](/glossary/) ## Sources - www.informatica.com/about-us/news/news-releases/2024/02/20240229-informatica-launches-cloud-data-access-management-industrys-first-ai-powered-solution-for-automating-data-access-policy-enforcement-at-scale.html: https://www.informatica.com/about-us/news/news-releases/2024/02/20240229-informatica-launches-cloud-data-access-management-industrys-first-ai-powered-solution-for-automating-data-access-policy-enforcement-at-scale.html (read 13 Nov 2026) Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/glossary/sensitive-data/ --- # Sensitivity label, defined with a sourced example GLOSSARY, read 13 Nov 2026 **The short answer.** A tag that states how carefully an item must be handled, such as public, internal or highly confidential. Systems read it to decide who may open or share the item. A label helps only where it is set and where tools honor it. Informatica says its Metadata Enrichment Agent will generate business descriptions and sensitivity labels as data flows. ## Definition A tag that states how carefully an item must be handled, such as public, internal or highly confidential. Systems read it to decide who may open or share the item. A label helps only where it is set and where tools honor it. ## Example from a real source **Example.** Informatica says its Metadata Enrichment Agent will generate business descriptions and sensitivity labels as data flows. ## Related terms - [service principal](/glossary/service-principal/): A non-human identity that a program, pipeline or agent uses to sign in. - [tag-based policy](/glossary/tag-based-policy/): An access rule written against a tag such as PII instead of a table name. - [sensitive data](/glossary/sensitive-data/): Data whose exposure could harm a person or the company, such as personal, health, financial or secret business records. ## Where to read more - [The PII Exposure Map](/exposure-map/) - [All glossary terms](/glossary/) ## Sources - www.informatica.com/about-us/news/news-releases/2026/05/20260520-informatica-from-salesforce-delivers-the-trusted-data-foundation-every-ai-agent-needs-now-across-every-surface-every-platform-everywhere.html: https://www.informatica.com/about-us/news/news-releases/2026/05/20260520-informatica-from-salesforce-delivers-the-trusted-data-foundation-every-ai-agent-needs-now-across-every-surface-every-platform-everywhere.html (read 13 Nov 2026) Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/glossary/sensitivity-label/ --- # Service principal, defined with a sourced example GLOSSARY, read 13 Nov 2026 **The short answer.** A non-human identity that a program, pipeline or agent uses to sign in. It has its own permissions and is not tied to a person. When an agent runs as a service principal, the log shows the principal, not the person who asked. Databricks says MCP clients authenticate with a token that identifies a user or service principal. ## Definition A non-human identity that a program, pipeline or agent uses to sign in. It has its own permissions and is not tied to a person. When an agent runs as a service principal, the log shows the principal, not the person who asked. ## Example from a real source **Example.** Databricks says MCP clients authenticate with a token that identifies a user or service principal. ## Related terms - [tag-based policy](/glossary/tag-based-policy/): An access rule written against a tag such as PII instead of a table name. - [access history](/glossary/access-history/): A record kept by the warehouse of which queries read which tables and columns. - [sensitivity label](/glossary/sensitivity-label/): A tag that states how carefully an item must be handled, such as public, internal or highly confidential. ## Where to read more - [The PII Exposure Map](/exposure-map/) - [All glossary terms](/glossary/) ## Sources - docs.databricks.com/aws/en/agents/mcp-tools/authentication-networking: https://docs.databricks.com/aws/en/agents/mcp-tools/authentication-networking (read 13 Nov 2026) Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/glossary/service-principal/ --- # Tag-based policy, defined with a sourced example GLOSSARY, read 13 Nov 2026 **The short answer.** An access rule written against a tag such as PII instead of a table name. Any data that gets the tag is covered at once. The tag must be correct and current, or the rule protects the wrong things. Privacera's docs say Discovery tags are synced to Apache Ranger so that tag-based policies can use them. ## Definition An access rule written against a tag such as PII instead of a table name. Any data that gets the tag is covered at once. The tag must be correct and current, or the rule protects the wrong things. ## Example from a real source **Example.** Privacera's docs say Discovery tags are synced to Apache Ranger so that tag-based policies can use them. ## Related terms - [access history](/glossary/access-history/): A record kept by the warehouse of which queries read which tables and columns. - [access review](/glossary/access-review/): A check, by a person or a rule, of whether an access request or an existing grant should stand. - [service principal](/glossary/service-principal/): A non-human identity that a program, pipeline or agent uses to sign in. ## Where to read more - [The PII Exposure Map](/exposure-map/) - [All glossary terms](/glossary/) ## Sources - docs.privacera.com/data-security/get-started/discovery/config_sync_tags_to_ranger.html: https://docs.privacera.com/data-security/get-started/discovery/config_sync_tags_to_ranger.html (read 13 Nov 2026) Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/glossary/tag-based-policy/ --- # 36 governance terms, each with an example from a real source GLOSSARY, read 13 Nov 2026 **The short answer.** Thirty-six governance terms, each with a plain definition and a sourced example from a vendor's documentation, a regulator or a standard. The terms cover sensitivity, access, audit and agents, and they are the words the exposure map and the guides use, read 13 Nov 2026. - [access history](/glossary/access-history/): A record kept by the warehouse of which queries read which tables and columns. - [access review](/glossary/access-review/): A check, by a person or a rule, of whether an access request or an existing grant should stand. - [agent access policy](/glossary/agent-access-policy/): A rule that sets what a given AI agent may read or do, kept apart from the policies written for people. - [AI data governance](/glossary/ai-data-governance/): The rules and records that decide which data an AI system may read, what it may be told about that data, and who can prove it afterward. - [attribute-based access control (ABAC)](/glossary/attribute-based-access-control/): A way to grant access by comparing attributes of the person, the data and the situation, rather than by listing who may open which table. - [audit log](/glossary/audit-log/): A time-ordered record of who did what in a system, such as a sign-in, a query or a policy change. - [BI field exposure](/glossary/bi-field-exposure/): The presence of a sensitive source column in a field that a report, dashboard or semantic model shows. - [classification inheritance](/glossary/classification-inheritance/): A new data field takes its sensitivity classification from a type or parent it is linked to, instead of a person labeling each field. - [column mask](/glossary/column-mask/): A rule attached to a column that changes the value a reader sees, for example by hashing it or hiding all but a few characters. - [consent and purpose limitation](/glossary/consent-and-purpose-limitation/): Personal data is collected for a stated reason and used only in ways that fit it. - [copilot oversharing](/glossary/copilot-oversharing/): An AI assistant returns content a person is technically allowed to open but should never have been shown, because file or report permissions were set too wide. - [data access governance](/glossary/data-access-governance/): The practice of deciding, approving and recording who can read which data, with the rules enforced in the systems that hold it. - [data classification](/glossary/data-classification/): Sorting data into categories such as public, internal, personal or restricted, usually by scanning column names and values. - [data loss prevention (DLP)](/glossary/data-loss-prevention/): Controls that detect sensitive content and warn, alert or block before it leaves its allowed place. - [data minimization](/glossary/data-minimization/): Collect, keep and expose only the data a task needs. - [data residency](/glossary/data-residency/): The requirement that data stay in a stated country or region, or move out only under set conditions. - [data subject request](/glossary/data-subject-request/): A request from a person asking a company what personal data it holds about them, or asking for a copy, correction or deletion. - [dynamic data masking](/glossary/dynamic-data-masking/): Hiding or altering a value at the moment a query runs, based on who is asking. - [exposure path](/glossary/exposure-path/): The chain from a sensitive source column through transformations to the report, dashboard or agent answer where it can be seen. - [label downstream inheritance](/glossary/label-downstream-inheritance/): A report or dataset picks up the sensitivity label of the source it was built from. - [least privilege](/glossary/least-privilege/): Give each person, service or agent only the access the job needs, and nothing more. - [need to know](/glossary/need-to-know/): The principle that having clearance is not enough: a person sees a piece of sensitive data only if their work requires it. - [on-behalf-of authentication](/glossary/on-behalf-of-authentication/): A pattern where an agent calls a data system as itself but for a named person, so the request carries both identities. - [PCI data](/glossary/pci-data/): Payment card data covered by the PCI DSS standard, mainly the card number and the items stored with it. - [PHI](/glossary/phi/): Protected health information: health data tied to an identifiable person and held by a covered entity or its business associate under HIPAA. - [PII](/glossary/pii/): Personally identifiable information: data that can point to a specific person, alone or when combined, such as a name, email or ID number. - [purpose-based access](/glossary/purpose-based-access/): Access that depends on the reason for the request as well as the role. - [report viewer log](/glossary/report-viewer-log/): A record that names each person who opened a given report or dashboard, and when. - [retention policy](/glossary/retention-policy/): A rule for how long a kind of record is kept before it is deleted or archived. - [role-based access control (RBAC)](/glossary/role-based-access-control/): Access is granted to roles, and people or services are given roles. - [row access policy](/glossary/row-access-policy/): A policy attached to a table that decides which rows a query may return for the person running it. - [row filter](/glossary/row-filter/): A rule that removes rows from a result based on who is asking, for example showing only one region's customers. - [sensitive data](/glossary/sensitive-data/): Data whose exposure could harm a person or the company, such as personal, health, financial or secret business records. - [sensitivity label](/glossary/sensitivity-label/): A tag that states how carefully an item must be handled, such as public, internal or highly confidential. - [service principal](/glossary/service-principal/): A non-human identity that a program, pipeline or agent uses to sign in. - [tag-based policy](/glossary/tag-based-policy/): An access rule written against a tag such as PII instead of a table name. Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/glossary/ --- # Immuta adds dynamic review flows for data access requests, including agent requests NEWS, 4 NOV 2026, read 13 Nov 2026 **The short answer.** Immuta released dynamic review flows on 4 Nov 2026, a decision tree builder that approves, denies or routes data access requests to a human. Branching can use request type, consumer identity, form answers and AI-generated recommendations. Immuta lists agent requests for pre-approved, non-sensitive datasets as an auto-approve case. Opt-in runs 4 Nov to 3 Dec. Immuta's deployment notes for 4 Nov 2026 describe dynamic review flows as a visual, AI-assisted builder for access governance. Admins set conditional branches that approve, deny or send a request to a reviewer. Immuta says the aim is to cut wait times and steward queue volume for routine requests. Branching rules read the request type, the consumer identity, the request form answers and an AI-generated recommendation. One example in the notes checks group membership and governance tags: a user in the Data Analysts group asking for a table with no PII tags is approved at once. A second example covers agents, where a request for a pre-approved, non-sensitive dataset is approved and edge cases go to a person. The feature brings breaking API changes, so it follows Immuta's behavior change process: opt-in 4 Nov to 3 Dec, on by default 4 Dec to 3 Jan, enabled for all accounts on 4 Jan. For a governance lead signing off on an agent, the useful part is that the approval rule is written down and keyed on tags. Ask which tags the rule reads, who can edit the tree, and whether each automatic decision is logged with the rule that fired. The AI-generated recommendation is an input, not a decision, so confirm it cannot override a PII tag. The notes do not say how decisions are audited; none found on 13 Nov 2026. ## More governance news - [Privacera release 9.2.48.1 changes PolicySync audit fields and Snowflake masking role evaluation](/news/trust3-privacera-9-2-48-1-policysync-audit-snowflake-masking/): 4 Nov 2026 - [Immuta custom securables extend access policies to dashboards, files and APIs](/news/immuta-custom-securables-dashboards-apis/): 28 Oct 2026 - [Immuta warns Snowflake CREATE OR REPLACE can drop masking and row policies](/news/immuta-snowflake-create-or-replace-masking-policies/): 26 Oct 2026 - [Atlan adds SharePoint as a read-only knowledge source for its agents](/news/atlan-sharepoint-knowledge-source-for-agents/): 26 Oct 2026 ## Sources - documentation.immuta.com/saas/releases/index.md: https://documentation.immuta.com/saas/releases/index.md (read 13 Nov 2026) Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/news/immuta-dynamic-review-flows-agent-access-requests/ --- # Privacera release 9.2.48.1 changes PolicySync audit fields and Snowflake masking role evaluation NEWS, 4 NOV 2026, read 13 Nov 2026 **The short answer.** Privacera, now branded Trust3 AI, shipped release 9.2.48.1 on 4 Nov 2026 with breaking changes. PolicySync audit events drop errorCode in favor of extraInfo.response[]. A Snowflake setting is replaced, so masking and row-level filter policies may switch role evaluation method. A DataServer fix now authorizes and audits S3 bulk deletes key by key. Privacera's rolling release notes list 9.2.48.1 as released on 4 Nov 2026, flagged with breaking changes. The docs now carry the Trust3 AI name. The first break is in the PolicySync Connector: audit events no longer include a single errorCode field, and each event lists outcomes in extraInfo.response[] with a numbered code. Privacera tells customers to update any report, alert or script that reads errorCode, and to support both formats during upgrade. The second break is Snowflake: the use.current.available.roles property is removed and replaced by CONNECTOR_SNOWFLAKE_ROLE_EVALUATION_MODE. If it was set to false, masking and row-level filter policies switch from IS_ROLE_IN_SESSION() to CURRENT_AVAILABLE_ROLES() when next updated, unless the new mode is set to ROLE_IN_SESSION before upgrading. The DataServer notes also say S3 bulk delete_objects calls were evaluated against the bucket alone, and clients created through boto3.Session() bypassed the signer; Privacera says every key is now authorized and audited individually and signing applies on every path. For a governance lead, the audit change is the one to chase. Dashboards or evidence packs that count failed policy applications by errorCode will go quiet after upgrade without any error. The role evaluation change can widen or narrow who sees unmasked values in Snowflake, so ask for a before and after test with a user holding several roles. ## More governance news - [Immuta adds dynamic review flows for data access requests, including agent requests](/news/immuta-dynamic-review-flows-agent-access-requests/): 4 Nov 2026 - [Immuta custom securables extend access policies to dashboards, files and APIs](/news/immuta-custom-securables-dashboards-apis/): 28 Oct 2026 - [Immuta warns Snowflake CREATE OR REPLACE can drop masking and row policies](/news/immuta-snowflake-create-or-replace-masking-policies/): 26 Oct 2026 - [Atlan adds SharePoint as a read-only knowledge source for its agents](/news/atlan-sharepoint-knowledge-source-for-agents/): 26 Oct 2026 ## Sources - docs.privacera.com/data-security/resources/releases/release9.2.48.1.html: https://docs.privacera.com/data-security/resources/releases/release9.2.48.1.html (read 13 Nov 2026) Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/news/trust3-privacera-9-2-48-1-policysync-audit-snowflake-masking/ --- # Immuta custom securables extend access policies to dashboards, files and APIs NEWS, 28 OCT 2026, read 13 Nov 2026 **The short answer.** Immuta announced custom securables on 28 Oct 2026, letting subscription policies decide who should reach assets outside its native integrations, such as dashboards, files, APIs and SaaS applications. Customer tooling pulls access decisions through Immuta APIs or webhooks and enforces them in the hosting system. Immuta manages the policy and the decision, and the integration does the enforcing. Per Immuta's deployment notes dated 28 Oct 2026, subscription policies can now govern assets that sit outside the platforms Immuta integrates with natively. The notes name dashboards, files, APIs and SaaS applications. A dashboard can be registered as a custom securable and given a policy like any table. The notes give three steps: register the asset, define the subscription policy, then connect tooling that retrieves access decisions or receives access-change notifications and applies them in the target system. Immuta states the split plainly: it manages policies and determines access, and the customer's integration handles enforcement. That means Immuta does not itself grant or revoke access in the BI tool. This matters when an auditor asks who can open the dashboard that shows a regulated field. One policy language can now answer for the table and the dashboard, but only as far as your enforcement code is correct. A governance lead should ask for the integration owner, a test showing a revoked user loses access, and the log that proves it. Immuta's notes do not describe built-in enforcement for any named BI tool; none found on 13 Nov 2026. ## More governance news - [Immuta adds dynamic review flows for data access requests, including agent requests](/news/immuta-dynamic-review-flows-agent-access-requests/): 4 Nov 2026 - [Privacera release 9.2.48.1 changes PolicySync audit fields and Snowflake masking role evaluation](/news/trust3-privacera-9-2-48-1-policysync-audit-snowflake-masking/): 4 Nov 2026 - [Immuta warns Snowflake CREATE OR REPLACE can drop masking and row policies](/news/immuta-snowflake-create-or-replace-masking-policies/): 26 Oct 2026 - [Atlan adds SharePoint as a read-only knowledge source for its agents](/news/atlan-sharepoint-knowledge-source-for-agents/): 26 Oct 2026 ## Sources - documentation.immuta.com/saas/releases/index.md: https://documentation.immuta.com/saas/releases/index.md (read 13 Nov 2026) Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/news/immuta-custom-securables-dashboards-apis/ --- # Immuta warns Snowflake CREATE OR REPLACE can drop masking and row policies NEWS, 26 OCT 2026, read 13 Nov 2026 **The short answer.** Immuta told customers on 26 Oct 2026 to change Snowflake CREATE OR REPLACE statements before Snowflake's 2026_08 behavior change reaches their account. Snowflake will copy grants to the replacement object by default, but masking and row access policies are not retained. Immuta says users may query the new object unmasked until policies are reapplied. Immuta's 26 Oct 2026 notice covers Snowflake behavior change BCR-2433, part of the 2026_08 bundle. Snowflake is changing CREATE OR REPLACE so it copies existing access grants to the replacement object, as if COPY GRANTS had been written. Before, the statement dropped grants, so access stayed revoked until Immuta detected the change and reapplied policies. Immuta says Snowflake masking policies and row access policies are not retained on the replacement object. Users whose grants carry over may therefore query the new table or view without the intended masking or row restrictions until the policies are reapplied. Immuta states this is Snowflake behavior and applies whether or not Immuta manages the policies. The fix it gives is to add the IGNORE GRANTS clause to CREATE OR REPLACE statements on protected tables and views. Snowflake lists the change as disabled by default for now, so teams can test it first. A governance lead should treat this as an exposure check, not a vendor note. Ask the platform team which pipelines and deployment scripts use CREATE OR REPLACE on tables that hold regulated fields, and whether those statements will be updated before the bundle is enabled. Also ask for query history showing who read each replaced object between replacement and policy reapplication. Any agent or BI tool reading those objects inherits the gap. ## More governance news - [Immuta adds dynamic review flows for data access requests, including agent requests](/news/immuta-dynamic-review-flows-agent-access-requests/): 4 Nov 2026 - [Privacera release 9.2.48.1 changes PolicySync audit fields and Snowflake masking role evaluation](/news/trust3-privacera-9-2-48-1-policysync-audit-snowflake-masking/): 4 Nov 2026 - [Immuta custom securables extend access policies to dashboards, files and APIs](/news/immuta-custom-securables-dashboards-apis/): 28 Oct 2026 - [Atlan adds SharePoint as a read-only knowledge source for its agents](/news/atlan-sharepoint-knowledge-source-for-agents/): 26 Oct 2026 ## Sources - documentation.immuta.com/saas/releases/index.md: https://documentation.immuta.com/saas/releases/index.md (read 13 Nov 2026) Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/news/immuta-snowflake-create-or-replace-masking-policies/ --- # Atlan adds SharePoint as a read-only knowledge source for its agents NEWS, 26 OCT 2026, read 13 Nov 2026 **The short answer.** Atlan's product changelog for 26 Oct 2026 adds SharePoint as a knowledge source for Atlan agents, through OneLake shortcuts in Microsoft Fabric or directly through Microsoft Graph. Atlan says access is read-only on document libraries and agents read files live on each run, without syncing or indexing the content. Both routes use an app registered in Entra. Atlan's changelog entry dated 26 Oct 2026 says SharePoint can be connected as a knowledge source for agents. Atlan describes two routes: OneLake shortcuts in Microsoft Fabric, or Microsoft Graph directly. Both use an app registered in the customer's Microsoft Entra tenant. Per Atlan, the connection gives read-only access to document libraries, and agents read files live on each run without syncing or indexing SharePoint content. Customers that already use Atlan's Fabric connector can reuse its app registration for the OneLake route. The changelog also lists Confluence on 25 Oct 2026 through Atlassian's Rovo MCP server, and GitHub on 12 Oct 2026, as knowledge sources. What an agent is told now includes whatever the Entra app can read. A governance lead should ask which document libraries the app registration is scoped to, whether SharePoint sensitivity labels are respected when the agent reads a file, and where the read is logged. The entry states live reads but says nothing about labels or logging; none found on 13 Nov 2026. ## More governance news - [Immuta adds dynamic review flows for data access requests, including agent requests](/news/immuta-dynamic-review-flows-agent-access-requests/): 4 Nov 2026 - [Privacera release 9.2.48.1 changes PolicySync audit fields and Snowflake masking role evaluation](/news/trust3-privacera-9-2-48-1-policysync-audit-snowflake-masking/): 4 Nov 2026 - [Immuta custom securables extend access policies to dashboards, files and APIs](/news/immuta-custom-securables-dashboards-apis/): 28 Oct 2026 - [Immuta warns Snowflake CREATE OR REPLACE can drop masking and row policies](/news/immuta-snowflake-create-or-replace-masking-policies/): 26 Oct 2026 ## Sources - docs.atlan.com/data/product-change-log/llms.txt: https://docs.atlan.com/data/product-change-log/llms.txt (read 13 Nov 2026) Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/news/atlan-sharepoint-knowledge-source-for-agents/ --- # Snowflake Trust Center reports show who can reach and who read sensitive tables NEWS, 20 OCT 2026, read 13 Nov 2026 **The short answer.** Snowflake made two Trust Center reports generally available on 20 Oct 2026. The Sensitive Data Entitlement report lists users, roles and privileges that grant access to tables containing sensitive data. The Sensitive Data Access report lists users who accessed those tables during a configurable lookback period. Both require Enterprise Edition or higher. Snowflake's release note dated 20 Oct 2026 announces general availability of the Sensitive Data Entitlement report and the Sensitive Data Access report in the Trust Center. Both need Enterprise Edition or higher. Snowflake points to its page on using the Trust Center to set up sensitive data classification. Per the note, the entitlement report lists the users, roles and privileges that grant access to tables containing sensitive data. The access report lists users who accessed such tables in a lookback period an admin can configure. The word sensitive here depends on classification having run, so both reports follow the classification setup. These two reports map to the two questions an auditor asks: who could see the field, and who did. For an agent sign-off, check whether the agent's service role appears in the entitlement report and whether its reads appear in the access report. The note names tables only; it does not mention views, dashboards or BI tools, so exposure through those needs separate evidence. None found on 13 Nov 2026 for lookback limits. ## More governance news - [Immuta adds dynamic review flows for data access requests, including agent requests](/news/immuta-dynamic-review-flows-agent-access-requests/): 4 Nov 2026 - [Privacera release 9.2.48.1 changes PolicySync audit fields and Snowflake masking role evaluation](/news/trust3-privacera-9-2-48-1-policysync-audit-snowflake-masking/): 4 Nov 2026 - [Immuta custom securables extend access policies to dashboards, files and APIs](/news/immuta-custom-securables-dashboards-apis/): 28 Oct 2026 - [Immuta warns Snowflake CREATE OR REPLACE can drop masking and row policies](/news/immuta-snowflake-create-or-replace-masking-policies/): 26 Oct 2026 ## Sources - docs.snowflake.com/en/release-notes/2026/other/2026-10-20-sensitive-data-entitlement-access-reports-ga: https://docs.snowflake.com/en/release-notes/2026/other/2026-10-20-sensitive-data-entitlement-access-reports-ga (read 13 Nov 2026) Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/news/snowflake-sensitive-data-entitlement-and-access-reports-ga/ --- # Snowflake makes provided governance tags generally available, with sensitivity among them NEWS, 20 OCT 2026, read 13 Nov 2026 **The short answer.** Snowflake announced general availability of Snowflake-provided tags on 20 Oct 2026. The out-of-the-box tags live in the SNOWFLAKE.TAGS schema and cover cost center, certification status, sensitivity, environment and project. Snowflake says accounts no longer need to create equivalent tags themselves. The SKIP_TAG_PROPAGATION option requires Enterprise Edition or higher. Snowflake's release note of 20 Oct 2026 says Snowflake-provided tags are generally available. They are tags in the SNOWFLAKE.TAGS schema that ship with the platform, so an account does not create and maintain its own copies. Snowflake lists the governance uses as cost center, certification status, sensitivity, environment and project. The note adds that SKIP_TAG_PROPAGATION requires Enterprise Edition or higher, which signals that tag propagation is part of how these tags behave downstream. The note does not publish the allowed values for the sensitivity tag; none found on 13 Nov 2026. A shared sensitivity vocabulary helps when masking policies, catalogs and agent controls must agree on what a label means. A governance lead should check whether the tag values match the labels in the policy document, whether propagation reaches views that dashboards read, and who may set or remove a tag. A tag that can be changed by any table owner is a weak control for an agent. ## More governance news - [Immuta adds dynamic review flows for data access requests, including agent requests](/news/immuta-dynamic-review-flows-agent-access-requests/): 4 Nov 2026 - [Privacera release 9.2.48.1 changes PolicySync audit fields and Snowflake masking role evaluation](/news/trust3-privacera-9-2-48-1-policysync-audit-snowflake-masking/): 4 Nov 2026 - [Immuta custom securables extend access policies to dashboards, files and APIs](/news/immuta-custom-securables-dashboards-apis/): 28 Oct 2026 - [Immuta warns Snowflake CREATE OR REPLACE can drop masking and row policies](/news/immuta-snowflake-create-or-replace-masking-policies/): 26 Oct 2026 ## Sources - docs.snowflake.com/en/release-notes/2026/other/2026-10-20-snowflake-provided-tags-ga: https://docs.snowflake.com/en/release-notes/2026/other/2026-10-20-snowflake-provided-tags-ga (read 13 Nov 2026) Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/news/snowflake-provided-tags-ga-sensitivity-vocabulary/ --- # DataHub 1.8.0 requires new privileges to read query SQL and usage statistics NEWS, 12 OCT 2026, read 13 Nov 2026 **The short answer.** DataHub v1.8.0, released on 12 Oct 2026 with an availability date of 22 Oct 2026, changes who can read query text and usage data. Reading a query, a view definition or topSqlQueries now requires View Entity Queries or View All Queries. Dataset profile, usage and operations reads need matching View privileges. Tokens can no longer be created without expiry. The DataHub release notes list v1.8.0 as released on 2026-10-12, with a release availability date of 22 Oct 2026. Under Platform, DataHub says reading a query, a view definition or topSqlQueries requires the View Entity Queries privilege on a subject dataset, or the platform privilege View All Queries. On upgrade, policies that already grant View Entity Page are backfilled with both privileges. A policy created after the upgrade that grants only View Entity Page does not reveal query SQL. The notes add that reads of dataset profile, usage and operations, and dashboard usage statistics, now require the matching View privileges on Rest.li and OpenAPI as well as GraphQL. Creating an access token with no expiry is disabled; existing tokens, including never-expiring ones, keep working. Query text and usage statistics show which columns people touch, so they are sensitive in their own right. A governance lead can check which service accounts and agent tokens hold View All Queries after the backfill. The never-expiring tokens that keep working are the item to inventory and rotate, since an agent token is exactly where they tend to sit. ## More governance news - [Immuta adds dynamic review flows for data access requests, including agent requests](/news/immuta-dynamic-review-flows-agent-access-requests/): 4 Nov 2026 - [Privacera release 9.2.48.1 changes PolicySync audit fields and Snowflake masking role evaluation](/news/trust3-privacera-9-2-48-1-policysync-audit-snowflake-masking/): 4 Nov 2026 - [Immuta custom securables extend access policies to dashboards, files and APIs](/news/immuta-custom-securables-dashboards-apis/): 28 Oct 2026 - [Immuta warns Snowflake CREATE OR REPLACE can drop masking and row policies](/news/immuta-snowflake-create-or-replace-masking-policies/): 26 Oct 2026 ## Sources - docs.datahub.com/docs/releases: https://docs.datahub.com/docs/releases (read 13 Nov 2026) Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/news/datahub-1-8-0-view-privileges-query-sql-usage-statistics/ --- # Databricks extends ABAC row filters and column masks to views in Beta NEWS, 29 SEP 2026, read 13 Nov 2026 **The short answer.** Databricks announced on 29 Sep 2026 that attribute-based access control row filters and column masks now extend to views as well as tables, in Beta. Workspace admins turn on the ABAC on Views preview from the Previews page, and the feature needs Databricks Runtime 19 or above. Databricks says this controls sensitive data exposed through views. Databricks' September 2026 release notes, entry dated 29 Sep 2026, say ABAC row filters and column masks in Unity Catalog now apply to views, not only tables. The feature is in Beta. Workspace admins enable it from the workspace settings Previews page, and it requires Databricks Runtime 19 or above. Views are where many dashboards and agent tools read from, so the gap mattered. Databricks states the purpose as controlling access to sensitive data exposed through views. Other September entries sit alongside it: metastore-level ABAC policies in Beta (17 Sep 2026), ABAC DENY policies in Beta (8 Sep 2026), and ABAC policies enforced on time travel queries in Beta (23 Sep 2026). For sign-off, the word Beta is the limit. A policy on views that is a preview feature, tied to one runtime version, is not yet something to cite as a control for an agent that queries a view. Ask which views feed the agent, which clusters or warehouses run below Runtime 19, and whether the Previews setting is on in that workspace. Test with a user who should see masked values and keep the result as evidence. ## More governance news - [Immuta adds dynamic review flows for data access requests, including agent requests](/news/immuta-dynamic-review-flows-agent-access-requests/): 4 Nov 2026 - [Privacera release 9.2.48.1 changes PolicySync audit fields and Snowflake masking role evaluation](/news/trust3-privacera-9-2-48-1-policysync-audit-snowflake-masking/): 4 Nov 2026 - [Immuta custom securables extend access policies to dashboards, files and APIs](/news/immuta-custom-securables-dashboards-apis/): 28 Oct 2026 - [Immuta warns Snowflake CREATE OR REPLACE can drop masking and row policies](/news/immuta-snowflake-create-or-replace-masking-policies/): 26 Oct 2026 ## Sources - docs.databricks.com/aws/en/release-notes/product/2026/september: https://docs.databricks.com/aws/en/release-notes/product/2026/september (read 13 Nov 2026) Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/news/databricks-abac-row-filters-column-masks-views/ --- # Alation Governed Collections makes SharePoint, Confluence and S3 documents available to agents by reference NEWS, 17 SEP 2026, read 13 Nov 2026 **The short answer.** Alation announced six AIOS products on 17 Sep 2026, including Governed Collections. Alation says documents from Confluence, SharePoint and S3 become governed catalog objects that agents consume by reference, reading the current version when a source document changes. Governed Collections is in early access. AI Governance adds agent lineage tracing and six native connectors. Alation's press release of 17 Sep 2026, issued at its revAlation conference, announces AI Governance, Ontologies, Intelligent Feeds, Console, Governed Collections and Semantic Model Mastering. Alation says Governed Collections makes unstructured content such as compliance policies, standard operating procedures and business glossaries available to agents as governed, current context. Per Alation, documents from Confluence, SharePoint and S3 become governed catalog objects and agents read them by reference, so a changed source document is picked up automatically. Alation says AI Governance adds agent lineage tracing and six native connectors into a cross-platform registry: Amazon Bedrock, Amazon SageMaker, Databricks MLflow, Microsoft Copilot Studio, Microsoft Foundry and Snowflake Cortex. Semantic Model Mastering and AI Governance updates are available now; Ontologies, Intelligent Feeds, Console and Governed Collections are in early access. For a governance lead, the claim to test is that an agent consumes a document only through a governed catalog object. Ask whether a document's source permissions and sensitivity labels carry into the catalog object, and whether the log shows which agent read which document. The release does not describe either; none found on 13 Nov 2026. Early access also means the control is not yet generally available. ## More governance news - [Immuta adds dynamic review flows for data access requests, including agent requests](/news/immuta-dynamic-review-flows-agent-access-requests/): 4 Nov 2026 - [Privacera release 9.2.48.1 changes PolicySync audit fields and Snowflake masking role evaluation](/news/trust3-privacera-9-2-48-1-policysync-audit-snowflake-masking/): 4 Nov 2026 - [Immuta custom securables extend access policies to dashboards, files and APIs](/news/immuta-custom-securables-dashboards-apis/): 28 Oct 2026 - [Immuta warns Snowflake CREATE OR REPLACE can drop masking and row policies](/news/immuta-snowflake-create-or-replace-masking-policies/): 26 Oct 2026 ## Sources - www.alation.com/news-and-press/alation-launches-aios-tm-expansion-with-six-products-that-accelerate-ai-transformation/: https://www.alation.com/news-and-press/alation-launches-aios-tm-expansion-with-six-products-that-accelerate-ai-transformation/ (read 13 Nov 2026) Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/news/alation-governed-collections-agents-read-governed-documents/ --- # Databricks Data Classification now scans Unity Catalog views in Beta NEWS, 15 SEP 2026, read 13 Nov 2026 **The short answer.** Databricks said on 15 Sep 2026 that Data Classification can scan Unity Catalog views as well as tables, classifying columns for sensitive data with the same detection engine. The release is Beta. Databricks points to a Classify views page for setup. The note gives no accuracy figures or pricing. The Databricks September 2026 release notes carry an entry dated 15 Sep 2026: Data Classification now scans Unity Catalog views in addition to tables. It classifies columns for sensitive data with the same detection engine, and Databricks labels the feature Beta. The note is short and publishes no detection accuracy figures, no list of supported classes and no pricing; none found on 13 Nov 2026. Databricks directs readers to its Classify views documentation for how to run it. The entry sits beside the ABAC on views entry of 29 Sep 2026, which is how a classification tag on a view column could feed a mask. A governance lead asked to approve an agent that reads from views needs to know which columns are tagged as sensitive. Ask for the scan results on the specific views the agent reads, the false negative check the team ran, and who reviews the tags. Do not infer from the note that tags are applied automatically to downstream masks; the entry does not say so. ## More governance news - [Immuta adds dynamic review flows for data access requests, including agent requests](/news/immuta-dynamic-review-flows-agent-access-requests/): 4 Nov 2026 - [Privacera release 9.2.48.1 changes PolicySync audit fields and Snowflake masking role evaluation](/news/trust3-privacera-9-2-48-1-policysync-audit-snowflake-masking/): 4 Nov 2026 - [Immuta custom securables extend access policies to dashboards, files and APIs](/news/immuta-custom-securables-dashboards-apis/): 28 Oct 2026 - [Immuta warns Snowflake CREATE OR REPLACE can drop masking and row policies](/news/immuta-snowflake-create-or-replace-masking-policies/): 26 Oct 2026 ## Sources - docs.databricks.com/aws/en/release-notes/product/2026/september: https://docs.databricks.com/aws/en/release-notes/product/2026/september (read 13 Nov 2026) Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/news/databricks-data-classification-scans-unity-catalog-views/ --- # Databricks masks SQL query text by default in system tables and APIs NEWS, 26 AUG 2026, read 13 Nov 2026 **The short answer.** Databricks announced on 26 Aug 2026 that SQL query text is masked by default in system tables and APIs, since statements can contain sensitive information. The statement_text and query_text fields return REDACTED, and SQL definition keys are dropped from the audit table. Account admins and the databricks_pii_access group can read the unmasked text. Databricks' August 2026 release notes, entry dated 26 Aug 2026, say query text is now masked by default. Databricks gives the reason as SQL statements that may contain sensitive information. It lists three places: statement_text in system.query.history, query_text in the Query History and List Queries APIs, and SQL definition keys in request_params of system.access.audit. The first two return the value REDACTED, and the audit keys are omitted. Account admins and members of the databricks_pii_access account group can read the unmasked text; an account admin creates that group and adds members. Dedicated access mode compute must run Databricks Runtime 15.4 LTS or above and the workspace must be enabled for serverless compute, or queries against the masked fields fail with an error. This changes what an audit trail shows. A governance lead who relies on query history to prove who looked at a regulated field should confirm who sits in databricks_pii_access and whether the audit evidence still answers the question with masked text. Agent and copilot queries are logged in the same tables, so the group's membership decides who can reread the questions an agent asked. ## More governance news - [Immuta adds dynamic review flows for data access requests, including agent requests](/news/immuta-dynamic-review-flows-agent-access-requests/): 4 Nov 2026 - [Privacera release 9.2.48.1 changes PolicySync audit fields and Snowflake masking role evaluation](/news/trust3-privacera-9-2-48-1-policysync-audit-snowflake-masking/): 4 Nov 2026 - [Immuta custom securables extend access policies to dashboards, files and APIs](/news/immuta-custom-securables-dashboards-apis/): 28 Oct 2026 - [Immuta warns Snowflake CREATE OR REPLACE can drop masking and row policies](/news/immuta-snowflake-create-or-replace-masking-policies/): 26 Oct 2026 ## Sources - docs.databricks.com/aws/en/release-notes/product/2026/august: https://docs.databricks.com/aws/en/release-notes/product/2026/august (read 13 Nov 2026) Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/news/databricks-query-text-masked-by-default-system-tables/ --- # 12 governance releases and announcements, each from its primary source NEWS, read 13 Nov 2026 **The short answer.** Twelve dated governance releases and announcements from vendors' own release notes and blogs, from 26 Aug 2026 to 4 Nov 2026. Each item says what shipped, what a governance lead should check about it, and where the source says nothing, it says none found on 13 Nov 2026. - [Immuta adds dynamic review flows for data access requests, including agent requests](/news/immuta-dynamic-review-flows-agent-access-requests/): 4 Nov 2026 - [Privacera release 9.2.48.1 changes PolicySync audit fields and Snowflake masking role evaluation](/news/trust3-privacera-9-2-48-1-policysync-audit-snowflake-masking/): 4 Nov 2026 - [Immuta custom securables extend access policies to dashboards, files and APIs](/news/immuta-custom-securables-dashboards-apis/): 28 Oct 2026 - [Immuta warns Snowflake CREATE OR REPLACE can drop masking and row policies](/news/immuta-snowflake-create-or-replace-masking-policies/): 26 Oct 2026 - [Atlan adds SharePoint as a read-only knowledge source for its agents](/news/atlan-sharepoint-knowledge-source-for-agents/): 26 Oct 2026 - [Snowflake Trust Center reports show who can reach and who read sensitive tables](/news/snowflake-sensitive-data-entitlement-and-access-reports-ga/): 20 Oct 2026 - [Snowflake makes provided governance tags generally available, with sensitivity among them](/news/snowflake-provided-tags-ga-sensitivity-vocabulary/): 20 Oct 2026 - [DataHub 1.8.0 requires new privileges to read query SQL and usage statistics](/news/datahub-1-8-0-view-privileges-query-sql-usage-statistics/): 12 Oct 2026 - [Databricks extends ABAC row filters and column masks to views in Beta](/news/databricks-abac-row-filters-column-masks-views/): 29 Sep 2026 - [Alation Governed Collections makes SharePoint, Confluence and S3 documents available to agents by reference](/news/alation-governed-collections-agents-read-governed-documents/): 17 Sep 2026 - [Databricks Data Classification now scans Unity Catalog views in Beta](/news/databricks-data-classification-scans-unity-catalog-views/): 15 Sep 2026 - [Databricks masks SQL query text by default in system tables and APIs](/news/databricks-query-text-masked-by-default-system-tables/): 26 Aug 2026 Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/news/ --- # 30 governance questions, answered with names and numbers FAQ, read 13 Nov 2026 **The short answer.** Thirty questions a governance lead asks before choosing a tool, answered with names and numbers from the published scores and the exposure map, read 13 Nov 2026. Each answer draws on the data files, so a score quoted here is the score on the index page. **Where Euno is behind.** Euno is not a policy engine or a DSPM: it reads metadata only, so it does not scan data contents or mask at the warehouse, which leaves it behind Atlan on acting on findings (5 to 7), and it publishes no dollar prices. **What is AI data governance?** AI data governance is the work of knowing which data is sensitive, where it surfaces, who saw it and what an AI agent may be told about it. It covers the warehouse column, the transformation, the BI field, the report, the viewer and the agent. This site ranks 16 tools on how far each follows a sensitive field along that path. See [the glossary entry](/glossary/ai-data-governance/). **What do data governance tools do?** Data governance tools, also sold as data governance software or a data governance platform, record what data exists, label it by sensitivity, set who may use it and keep a trail of access. Some act at the warehouse by masking or filtering. Others follow a label into dashboards. They differ most in how far past the warehouse they see, which is what the ranking measures on 25 percent of its weight. **What is data access governance, and how does it differ from classification?** Data access governance decides and records who may reach which data: roles, masks, row filters, requests, reviews and audit. Classification only says what a column contains. A tool can classify well and still leave access to other systems. The [data access governance entry](/glossary/data-access-governance/) defines the term. On this site, access actions are scored under acting, weighted 10 percent. **What does data governance for AI add to ordinary governance?** Ordinary governance asks who may read a table. Data governance for AI adds two questions: what an agent is told about a field when a person asks it something, and whether the label on a source column still reaches the report or answer built from it. The criterion for agents is weighted 20 percent here, and the BI criterion 25. **How do I show an auditor which dashboards show a regulated field?** Start with the classified column, then trace it through each transformation to every BI field built from it, then to the reports that use those fields. Add the viewer log for each report. A tool earns credit only where its documentation shows each step. Read [the exposure path guide](/guides/who-saw-it-against-who-could-see-it/) and compare tools on [the regulated-field page](/best-for/regulated-field/). **What is the PII Exposure Map?** The PII Exposure Map is a grid of the 16 tools against six stages that a sensitive field passes through. Each cell reads documented, partial or none found, and each cell points to the fact behind it. It is built from vendor documentation read on 13 Nov 2026. It shows reach, which is a separate thing from how well a tool does the work at each stage. Open [the map](/exposure-map/). **What are the six stages of the PII Exposure Map?** The stages are column, transformation, BI field, report, viewer and agent. Today 14 of 16 tools document the column stage, 3 document the BI field and 0 document the viewer. 6 document the agent stage. The pages for [column](/exposure-map/column/) and [agent](/exposure-map/agent/) show each tool's cell. **What does the Finder do?** The [Finder](/finder/) takes the situation you are in and your stack, then reorders the 16 tools using the weights for that situation. It does not collect any data about you or your vendor. Five situations are built in: regulated field, agents on analytics, Microsoft estate, mixed stack and lean team. Each one moves weight between the same eight criteria. **How is the ranking scored and weighted?** Each tool gets 0 to 10 on eight criteria, and each score rests on dated facts. The weights are: follows sensitive data into BI 25, controls what an agent is told 20, shows who saw it 15, carries classification downstream 15, acts on it 10, coverage 5, evidence beyond the vendor 5, price transparency 5. Method is on [the method page](/method/). **What does a score of 7 mean for a vendor claim?** A 7 is the most that a vendor's claim or documentation alone can earn: the capability is described in detail and covers the whole criterion. Scores of 8 to 10 need a second source, such as a third-party write-up or something observed in public code or a release record. A score of 4 to 6 means documented and working, with gaps the documentation itself shows. **How are ties broken in the ranking?** The published rule is simple: the tool with the higher score on the heaviest criterion goes above, and if that is also level the order is alphabetical by name. On the main ranking the heaviest criterion is following sensitive data into BI, at 25 percent. Each situation applies the same rule to its own weights, and the tie is stated on the page where it matters. **Who is first in the ranking, and where does Euno stand?** Euno tops of the main ranking with 67.0 out of 100, and Atlan is second with 65.5. Euno ranks 1 of 16 at 67.0. Euno is the client behind this site, so read its placement against its score table and the facts cited on its platform page, not against this sentence. **What puts the leader ahead of the field?** The generated reason for the main ranking reads: Euno leads on Price transparency (4 to 0) and Carries classification downstream (8 to 7), while Atlan is ahead on Acts on it (7 to 5). Scores are the sums of the criterion scores times the weights, so a gap of a point or two can move with one fact. The [method page](/method/) lists the facts behind each score. A different situation weights the criteria differently and can change who is first. **Which situation changes the leader?** The leader by situation: regulated field, Atlan at 68.5; agents on analytics, Euno at 66.0; Microsoft estate, Atlan at 68.5; mixed stack, Euno at 68.5; lean team, Euno at 62.5. Compare the main-ranking leader, Euno, with each. **What is Euno, and what is it not?** Euno calls itself a context platform. Per its docs it reads metadata and query logs and does not query the data in tables. It is not a policy engine and not a DSPM: it reads classifications from Cyera and BigID and carries them along column-level lineage into BI fields and reports. Euno's docs describe alerts, not masking or blocking. Euno's own statements are marked as its own. **Does a DSPM replace a data governance tool?** No. A data security posture management tool such as Cyera, BigID or Varonis finds and classifies sensitive data in stores. It does not by itself show which dashboards display the field or what an agent was told. Some tools here read those classifications and carry them forward. The [guide to what a DSPM covers](/guides/what-a-dspm-covers/) separates the two jobs. **What does a tool that masks at the warehouse see downstream?** A mask or row filter at the warehouse protects the query that runs there. It does not tell you which BI fields or reports were built from the column. Immuta says its rules are enforced at the data tier, so prompts cannot bypass them. For Immuta, the BI field cell reads none found and the report cell partial. See [where a policy stops](/guides/where-a-policy-stops/). **Do data governance tools publish prices?** It varies. Price transparency is scored 0 to 10 and weighted 5 percent. Euno scores 4 and Snowflake Horizon 7. Microsoft Purview scores 7. Atlan scores 0, Immuta 0 and Privacera 0. A low score means no public price or pricing model was found, not that the product is expensive. **What should I know about Microsoft Purview for AI data governance?** Microsoft Purview ranks 6 of 16 at 54.5. Microsoft documents that Power BI semantic models inherit sensitivity labels from only three source types: Excel on OneDrive or SharePoint, Azure Synapse and Azure SQL Database. Its Power BI activity log records who took which action on which item. Microsoft also says Purview Data Governance is being retired in favor of Fabric. See [the Purview page](/platforms/microsoft-purview/). **What should I know about Immuta for AI data governance?** Immuta ranks 11 of 16 at 45.0. Immuta says an agent acting for a person gets a role created in the data platform for that action and deleted afterward. Its agentic access feature is in public preview and enabled on request. On 13 Nov 2026 no column lineage into BI fields was found in its documentation. See [the Immuta page](/platforms/immuta/). **What should I know about Privacera for AI data governance?** Privacera ranks 14 of 16 at 30.0. Trust3 AI docs say Discovery scans connected sources and applies tags such as EMAIL and PII to columns, tables and files, and that masking and deny policies apply to anything carrying a tag. Connectors for Power BI, Tableau or Looker were none found on 13 Nov 2026. See [the Privacera page](/platforms/privacera/). **What should I know about Securiti for AI data governance?** Securiti ranks 15 of 16 at 29.5. Securiti says its copilot respects source file entitlements at ingestion and at the moment a user asks. Propagation of classifications along lineage to downstream assets was none found on 13 Nov 2026 in the public product pages, and its documentation is behind a login. Securiti says Veeam acquired it. See [the Securiti page](/platforms/securiti/). **What should I know about OneTrust for AI data governance?** OneTrust ranks 16 of 16 at 26.5. OneTrust says Data Use Governance pushes masking and row-filtering logic into Snowflake or Databricks and relies on the platform's own audit logs for enforcement. Its BI field cell reads none found and its viewer cell none found. See [the OneTrust page](/platforms/onetrust/). **What should I know about Atlan for AI data governance?** Atlan ranks 2 of 16 at 65.5. Atlan says purposes apply policies to every asset carrying a tag, so a PII tag can trigger masking, and that its MCP server forwards the caller's identity on each tool call. Its docs say tag propagation is chosen per tag. A published price was none found on 13 Nov 2026. See [the Atlan page](/platforms/atlan/). **What should I know about Collibra for AI data governance?** Collibra ranks 10 of 16 at 46.5. Collibra says its Data Access product applies masking and row filtering automatically from classifications such as PII and PHI, across Snowflake, Databricks and BigQuery. Automatic propagation of a sensitivity classification to BI fields or reports was none found on 13 Nov 2026. See [the Collibra page](/platforms/collibra/). **What should I know about Snowflake Horizon for AI data governance?** Snowflake Horizon ranks 4 of 16 at 55.5. Snowflake says masking and row access policies are enforced in the query engine when an agent queries data, and documents ACCESS_HISTORY, which shows object and column access by user and is kept for 365 days on Enterprise Edition. Named viewers per BI report were none found on 13 Nov 2026. See [the Snowflake page](/platforms/snowflake/). **What should I know about Databricks Unity Catalog for AI data governance?** Databricks Unity Catalog ranks 5 of 16 at 55.0. Databricks says tag propagation (Beta) copies a governed tag along lineage to derived tables and views, and that row filters and column masks are enforced per user in Genie. Viewer logs for Tableau or Power BI reports built on its tables were none found on 13 Nov 2026. See [the Databricks page](/platforms/databricks/). **What does none found on 13 Nov 2026 mean?** It means a search of that vendor's public documentation, product pages and release notes on 13 Nov 2026 turned up nothing for the capability. It does not say the feature is missing, only that nobody outside the vendor can confirm it from public pages. Each such entry names where the search ran. If a vendor shows a page we missed, the cell and score move. **How often is the data re-read?** Every fact carries the date it was read, and every read in this edition is dated 13 Nov 2026. Older facts would keep their own date, so you can see how stale a score is. Scores change only when a re-read changes a fact, and a changed token moves every rank, gap and sentence on the site together. The [method page](/method/) explains the process. **How do I cite the datasets?** Cite the page URL, the page title and the edition date, 13 Nov 2026. For one claim about a vendor, also cite the source URL and read date shown beside the fact, since the vendor's own page is the primary source. Quote scores with the weights used: the main ranking or a named situation. The [exposure-map methodology](/exposure-map/methodology/) lists what each cell value means. Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/faq/ --- # Four datasets, CSV and JSON, free to reuse with a citation DATASETS, read 13 Nov 2026 **The short answer.** Need to Know publishes four datasets under CC BY 4.0, read 13 Nov 2026: the PII Exposure Map (16 tools, six stages), the blind scores (16 tools, eight criteria, with weights), the ranked list with totals, and the evidence (749 facts, each with its source URL and read date). | Dataset | Rows | CSV | JSON | | --- | --- | --- | --- | | The PII Exposure Map | 16 | pii-exposure-map.csv | pii-exposure-map.json | | Need to Know scores | 128 | need-to-know-scores.csv | need-to-know-scores.json | | Need to Know ranked list | 16 | need-to-know-ranked-list.csv | need-to-know-ranked-list.json | | Need to Know evidence | 749 | need-to-know-evidence.csv | need-to-know-evidence.json | ## Cite this Cite as: Need to Know, PII Exposure Map and AI data governance scores, edition 13 Nov 2026, https://aidatagovernancetools.com/datasets/. Licensed CC BY 4.0. Each row carries the fact ids and the read date of its sources. Each JSON file carries the edition, the read date, the license and the cite line. The ranked-views file records the weights every published ranking used. ## Sources - Map methodology: https://aidatagovernancetools.com/exposure-map/methodology/ (read 13 Nov 2026) - Scoring method: https://aidatagovernancetools.com/method/ (read 13 Nov 2026) Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/datasets/ --- # Need to Know ranks AI data governance tools by how far they follow a sensitive field ABOUT NEED TO KNOW, read 13 Nov 2026 **The short answer.** Need to Know is a reference for the director of data and AI governance who must say, before an agent connects, where sensitive data surfaces and who or what has seen it. It publishes a ranked index of 16 tools, the PII Exposure Map and a Finder, with sources and dates on every fact. The site has three parts. The index ranks 16 tools on eight published weights. The PII Exposure Map shows, tool by tool, how far each follows a sensitive column to the BI field, the report, the viewer and the agent. The Finder turns five answers about a stack into a shortlist with a reason for each tool. Every fact carries a source link and the date it was read. A vendor's claim is labeled as the vendor's. Where a search found nothing the page says none found on the read date. Pages are reviewed on the date shown at the foot of each one. The name comes from an access principle: a person or a system gets the data it needs for the task and no more. The site asks the same of tools, and of the reader who has to sign off on them. Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/about/ --- # The editorial policy: weights first, sources on every fact, scores that move only on a sourced change EDITORIAL POLICY, read 13 Nov 2026 **The short answer.** Weights and criteria are fixed before any tool is scored. Every fact has a source URL and a read date. A vendor's own claim scores at most 7 of 10 until a second source confirms it, and nothing found scores 0 and reads none found on the date. A score changes only when a sourced fact changes. Choosing the tools: the set is every tool a governance lead is likely to shortlist for sensitive data in analytics, from warehouse-native governance to catalogs, access control platforms and privacy suites. A DSPM is a different category and gets a paragraph in a guide, not a score. Handling claims: a claim from a vendor is written as the vendor's, Euno's included. A claim becomes a fact for scoring above 7 only when a third-party source or public code confirms it. The page for each tool states one strength and one gap in one sentence each. Handling gaps: where a search finds nothing, the cell reads none found on the date and scores 0. The site never writes that a tool lacks a feature. Changing a score: a score changes when a sourced fact changes, and the change is logged. Weights and criteria never change after the first score. Every build checks the published rankings against the scores and the weights history. ## Sources - Method: https://aidatagovernancetools.com/method/ (read 13 Nov 2026) Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/editorial-policy/ --- # Corrections: send the page, the sentence and the source, and a fix is dated on the page CORRECTIONS, read 13 Nov 2026 **The short answer.** A reader, a vendor or a researcher can report an error by email with the page address, the sentence and a source. A confirmed error is fixed on the page, the data file is updated and the change is dated here. No corrections have been issued as of 13 Nov 2026. Send corrections to editor@aidatagovernancetools.com. Include the page address, the sentence you think is wrong and a link to the source that shows it. A vendor that wants a fact re-read should send the documentation page and the date it was published. A confirmed error is corrected on the page and in the dataset. If the change moves a score, the score change is logged with the fact that caused it, and every ranking that depends on it is rebuilt. Weights and criteria are not reopened. Corrections log: none issued as of 13 Nov 2026. ## Sources - Method: https://aidatagovernancetools.com/method/ (read 13 Nov 2026) Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/corrections/ --- # Contact the editor at editor@aidatagovernancetools.com CONTACT, read 13 Nov 2026 **The short answer.** Write to the editor at editor@aidatagovernancetools.com about a correction, a source, a dataset citation or a tool that should be scored. Include the page address and, for a correction, the sentence and the source. The address is shown as text only, and a reply goes to the sender. Email: editor@aidatagovernancetools.com. For a correction, use the format on the corrections page. For a tool that should be scored, say what it does for sensitive data in analytics and send the documentation page; tools are added when their documentation can be read to the same depth as the other sixteen. For a dataset citation, use the cite line on the datasets page. Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/contact/ --- # Privacy: server logs only, and nothing from the Finder or the pages you read PRIVACY, read 13 Nov 2026 **The short answer.** The site sets no cookies, runs no analytics script and has no accounts. The host keeps standard web server logs for 90 days, with the address requested, the time, the browser string and the referrer. The Finder runs in your browser and stores and sends nothing. Email you send to the editor is kept to answer it. What is collected: the content delivery network writes a standard access log, which holds the requested address, the time, the response code, the browser string, the referring site and the visitor's IP address. Logs expire after 90 days. They are read in aggregate to count visits and crawler requests. What is not collected: cookies, fingerprints, advertising identifiers and third-party scripts. The Finder and the other tools on the site run in your browser. The answers you pick are not stored and not sent. Email: if you write to the editor, the message and your address are kept to answer you and to log a correction. Ask for deletion by writing to the same address. ## Sources - Method: https://aidatagovernancetools.com/method/ (read 13 Nov 2026) Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/privacy/ --- # Terms of use: read, cite and reuse the datasets with attribution TERMS OF USE, read 13 Nov 2026 **The short answer.** The pages are free to read and to quote with a link. The datasets are licensed CC BY 4.0: reuse them with the cite line on the datasets page. Scores describe public documentation on the read date shown. Links to other sites are cited sources, and those sites have their own terms. Reading and quoting: you may read the site and quote short passages with a link to the page. Datasets: the CSV and JSON files are licensed under CC BY 4.0. Cite them with the line on the datasets page, which names the edition and the read date. Scores: a score is a reading of public documentation on one date. It describes that documentation, and a later release can change the picture. The read date is printed on every page. Automated access: the site welcomes search and AI crawlers, as robots.txt lists, and serves a markdown copy of each page at the same address with index.md added. Changes: the terms may be updated, and the date at the foot of this page shows the last review. ## Sources - Method: https://aidatagovernancetools.com/method/ (read 13 Nov 2026) Last reviewed 13 Nov 2026. Canonical: https://aidatagovernancetools.com/terms/