BigID
Euno's BigID integration supports auto-discovery of tables and columns with BigID attributes and classification metadata.
See BigID integration use cases 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 warehouse tables and columns 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
Log in to BigID as an administrator.
Go to Administration → Access Management → Roles.
Click Add (or equivalent) to create a new role.
Set:
Name: for example:
Euno Integration RoleDescription: Read-only catalog access for the Euno BigID source integration
Under Scope, select
rootunless 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.Under Role Permissions, enable at minimum:
Catalog → Read, Export, Get Attributes Value, View Sensitive Values
Data Sources → Read
Scans → Scan Activity → Read
Optionally enable:
Catalog → Manual Fields → Read - allows Euno to observe manual fields
Catalog → Business Attributes → Read - allows Euno to observe business attributes)
Save the role.
Step 2: Create a BigID user and generate an API token
Create the user
Go to Administration → Access Management → Users.
Create a new user (recommended) or select a dedicated service account. Suggested naming:
Display name:
Euno IntegrationUsername / email:
euno-integration@yourdomain.com— use a dedicated address, not your personal BigID login emailOrigin: Local (recommended for API-only integration users)
Connect the Euno Integration role from Step 1 to this user (Connect Role).
Save the user.
Generate the API token
Open the user profile in the right-hand detail panel.
Find the Tokens section.
Click Generate.
Set the token expiration (up to 999 days) and click Generate again.
Copy the token value immediately — BigID does not show it again after you close the dialog.
Click Save on the user profile so the token is active.
Step 3: Configure New BigID Source in Euno
Access the Sources Page
Go to the Sources page in Euno.
Click on Add New Source and select BigID from the list of supported platforms.
General Configuration
Asterisk (*) means a mandatory field.
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:
Weekly: Set specific days and times.
Hourly: Define the interval in hours (e.g., every 8 hours).
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.
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)
Click on the Advanced section to display these additional configurations.
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 table and column resources with BigID attribute and sensitivity properties. For detailed information about discovered resources and their indexed properties, see bigid-integration-discovered-resources.
Last updated