> 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.md). # BigID Euno's BigID integration enriches existing warehouse and Power BI resources with BigID attributes and classification metadata. See [BigID integration use cases](/sources/data-security/bigid-integration/bigid-integration-use-cases.md) for common workflows that combine BigID classifications with Euno lineage. ## Setting up BigID integration ### Overview BigID is a data security and privacy platform that discovers, classifies, and protects sensitive data across your data stores. The BigID integration connects to BigID's API and enriches existing warehouse and supported Power BI resources in Euno with BigID classification metadata. To discover BigID-enriched resources, Euno authenticates to the BigID API using a long-lived **API user token** and streams catalog and classification metadata from BigID's view of your datastores (BigQuery, Snowflake, and Databricks). For each structured catalog table that passes filters and maps to a supported warehouse, Euno emits a table observation with `bigid_*` properties. Column observations are emitted only when BigID reports attributes and/or column-level sensitivity tags for that column. ### Step 1: Create a BigID role for Euno Euno needs read access to the BigID catalog and scan-result findings. Create a dedicated role rather than reusing roles built for other BigID apps (for example, Jira, Databricks, or RoPA integrations). #### Prerequisites * **BigID administrator** access (to create roles and users) * Your BigID instance **base URL** (for example, `https://your-tenant.bigid.com`) #### Create the role 1. Log in to BigID as an administrator. 2. Go to **Administration → Access Management → Roles**. 3. Click **Add** (or equivalent) to create a new role. 4. Set: * **Name**: for example: `Euno Integration Role` * **Description**: Read-only catalog access for the Euno BigID source integration 5. Under **Scope**, select **`root`** unless you intentionally want to limit Euno to a narrower data scope. Named scopes restrict which catalog objects the role can see; Euno may then return a partial or empty catalog. 6. Under **Role Permissions**, enable at minimum: * **Catalog → Read, Export, Get Attributes Value, View Sensitive Values** * **Data Sources → Read** * **Scan Results Details → Read, Export** 7. Optionally enable: * **Catalog → Manual Fields → Read** - allows Euno to observe manual fields * **Catalog → Business Attributes → Read** - allows Euno to observe business attributes) 8. Save the role. ### Step 2: Create a BigID user and generate an API token #### Create the user 1. Go to **Administration → Access Management → Users**. 2. Create a new user (recommended) or select a dedicated service account. Suggested naming: * **Display name**: `Euno Integration` * **Username / email**: `euno-integration@yourdomain.com` — use a **dedicated** address, not your personal BigID login email * **Origin**: **Local** (recommended for API-only integration users) 3. Connect the **Euno Integration** role from Step 1 to this user (**Connect Role**). 4. Save the user. #### Generate the API token 1. Open the user profile in the right-hand detail panel. 2. Find the **Tokens** section. 3. Click **Generate**. 4. Set the token expiration (up to 999 days) and click **Generate** again. 5. **Copy the token value immediately** — BigID does not show it again after you close the dialog. 6. Click **Save** on the user profile so the token is active. ### Step 3: Configure New BigID Source in Euno #### Access the Sources Page 1. Go to the **Sources** page in Euno. 2. Click on **Add New Source** and select **BigID** from the list of supported platforms. #### General Configuration Asterisk (\*) means a mandatory field. | Configuration | Description | | ------------------- | --------------------------------------------------------------------------------- | | Name\* | Enter a name for your BigID source (e.g., "BigID - Data Security") | | Base URL\* | The base URL of your BigID server (e.g., `https://your-bigid-instance.bigid.com`) | | System user token\* | The API token from Step 2 (paste the raw token; do not add a `Bearer` prefix) | ### Step 4: Schedule * Enable the Schedule option. * Choose: 1. **Weekly**: Set specific days and times. 2. **Hourly**: Define the interval in hours (e.g., every 8 hours). {% hint style="info" %} **Recommended**: Schedule the BigID integration to run daily or every 12 hours to keep attribute and classification metadata in sync with BigID. {% endhint %} ### Step 5: Resource Cleanup To keep your data relevant and free of outdated resources, Euno provides automatic **resource cleanup** options. For a detailed explanation on Euno's cleanup strategies, see: [Resource Sponsorship in Euno](/developer-reference/technical-concepts/resource-sponsorship-and-cleanup-in-euno.md). * **Immediate Cleanup**: Remove resources not detected in the most recent successful source integration run. * **No Cleanup**: Keep all resources indefinitely, even if they are no longer detected. For the freshest sensitivity metadata, use **Immediate Cleanup**. If a column was detected only because of a BigID column-level sensitivity tag and BigID later removes that tag without reporting attributes for the column, the column is no longer detected by the BigID run. **No Cleanup** preserves that last observed column metadata by design. ### Step 6: Advanced Settings (Optional) For Power BI, Euno uses the same BigID token and source. Keep the Power BI service principal configured in BigID and run Euno's native Power BI source to discover targets first. Power BI matching uses native IDs and does not use **Data Source Mapping** overrides. The cleanup selection above controls internal BigID facts. Native Power BI resources retain their last-known classifications when facts disappear, including after successful empty catalog reads. See [Power BI resources](/sources/data-security/bigid-integration/bigid-integration-discovered-resources.md#power-bi-resources) for supported object types and cleanup limitations. Click on the **Advanced** section to display these additional configurations. | Configuration | Description | | ------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Local Agent | Optional. Select a connected local agent that can resolve and reach your private BigID instance. Authentication, **Test & Save**, and classification imports use that agent. If the agent is offline or cannot reach BigID, Euno does not fall back to a direct connection. Without an agent, the Base URL must be a publicly reachable host. See [Local Agents](/setup-configuration/account-settings/local-agents.md) for setup instructions. | | Data Objects Pattern | Allow/deny regular expressions applied to BigID object fully qualified names (for example, `DataSource.schema.table`) after catalog fetch. Default allow `.*` includes all objects that pass other filters. | | Attributes Pattern | Allow/deny regular expressions applied to BigID attribute names before they are copied into `bigid_attributes`. Default allow `.*` includes all attributes that pass the confidence threshold. | | Attribute Confidence Threshold | Numeric value from **0.0** to **1.0**. Attributes with BigID confidence below this threshold are dropped. Default **0.0** observes all attributes that match the attribute pattern. | | Data Source Mapping | Optional key/value map from BigID data source name to an Euno warehouse URI prefix override. Use when BigID's source label does not match the host or account Euno uses for the same warehouse (same pattern as Fivetran database mapping). | ### Step 7: Save Configuration Click the **Test & Save** button to complete the setup. Euno validates connectivity to BigID and saves the configuration. ## Discovered Resources The BigID integration augments warehouse tables and columns and supported Power BI resources with BigID attribute and sensitivity properties. For detailed information about discovered resources and their indexed properties, see [bigid-integration-discovered-resources](/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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.euno.ai/sources/data-security/bigid-integration.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.