> For the complete documentation index, see [llms.txt](https://docs.euno.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.euno.ai/sources/data-security/bigid-integration/bigid-integration-use-cases.md).

# BigID Integration Use Cases

BigID classifies sensitive data in warehouses and other structured sources. Euno reads that classification metadata and connects it to warehouse tables, columns, and downstream assets through lineage.

This page describes common workflows when BigID and Euno are used together. Setup steps are in the [BigID integration setup guide](/sources/data-security/bigid-integration.md).

## What the integration provides

After a scheduled sync, Euno adds `bigid_*` properties to matching **BigQuery**, **Snowflake**, and **Databricks** table resources for each structured BigID catalog row that passes filters (even when BigID metadata is empty). Column observations are added only when BigID reports attributes and/or sensitivity tags for that column. You can filter on these properties in Discover and EQL, and—where the Sensitive Data sidepanel is enabled—review classifications on a resource.

Lineage then shows how classified columns flow into BI fields, dashboards, reports, and other downstream resources.

## Use cases

### Incident response

When a table is flagged in BigID, you can use Euno to find downstream dashboards, reports, and pipelines that depend on that table or its columns. Combined with Euno usage and identity metadata where available, this reduces manual tracing across the warehouse and BI layers.

### Stale or unused BI assets

Euno can surface BI resources with low or no recent usage that still reference BigID-classified columns. Teams use this to prioritize review, restriction, or retirement of assets that may no longer need access to sensitive fields.

### Governance in the BI layer

Warehouse classifications from BigID do not automatically appear on Looker, Tableau, or Power BI assets. Euno propagates BigID metadata on source columns to downstream fields and reports so governance and security teams can see exposure outside the warehouse.

### Identity and access context

Where Euno has usage and identity data, you can relate BI access patterns to tables and columns classified by BigID—for example, which users or service accounts have access to or have viewed assets built on sensitive source columns.

### AI and self-service analytics

When AI or natural-language interfaces query data modeled in Euno, BigID sensitivity and attribute metadata on upstream tables and columns provides additional context about which assets carry classified data before results are shown or summarized.

## How it works

1. Euno authenticates to your BigID instance with a system user token and base URL.
2. On each run, the integration fetches BigID catalog and classification metadata for supported warehouse types.
3. Euno maps classified objects to existing table and column URIs and writes `bigid_*` properties (see [discovered resources](/sources/data-security/bigid-integration/bigid-integration-discovered-resources.md)).
4. Existing lineage and usage data in Euno connect those properties to downstream resources.

Schedule the source to keep metadata aligned with BigID (daily or every 12 hours is a common choice).

## Related documentation

* [BigID integration setup](/sources/data-security/bigid-integration.md)
* [Discovered resources and EQL](/sources/data-security/bigid-integration/bigid-integration-discovered-resources.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.euno.ai/sources/data-security/bigid-integration/bigid-integration-use-cases.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.