GUIDE, read 13 Nov 2026
An access list shows who could see a field, and only a log shows who did
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, read 13 Nov 2026
- Snowflake QUERY_HISTORY, read 13 Nov 2026
- Databricks audit log events, read 13 Nov 2026
- Microsoft, Power BI auditing, read 13 Nov 2026
- Power BI Get Activity Events API, read 13 Nov 2026
- Microsoft Purview audit overview, read 13 Nov 2026
- Immuta audit, read 13 Nov 2026
- Atlan MCP security, read 13 Nov 2026
- Euno docs, Cyera use cases, read 13 Nov 2026
- Euno docs, Power BI usage data, read 13 Nov 2026
Last reviewed 13 Nov 2026.