Governance

Governance by default

Snowflake-provided tags and Trust Center sensitive data reports are GA

As of October 21, 2026

What shipped

On October 20, 2026, Snowflake-provided tags became generally available (Snowflake-provided tags release note (opens in a new tab)). These out-of-the-box tags in the SNOWFLAKE.TAGS schema give you a consistent vocabulary for common governance use cases, including cost center, certification status, sensitivity, environment, and project, without creating and maintaining equivalent tags in each account.

The same day, the Trust Center Sensitive Data Entitlement and Access reports became generally available (Sensitive Data Entitlement and Access reports release note (opens in a new tab)). These reports require Enterprise Edition or higher. The Sensitive Data Entitlement report lists the 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.

Why standard tags matter

Cost center, sensitivity, and environment labels only help when they mean the same thing in every account. A shared cost center tag is what keeps cost allocation consistent across accounts, and the same shared names keep sensitivity and environment labeling aligned.

Using the reports in security reviews

In a security review, one report shows who can reach the tables. The other shows who reached them in the period you set.

Caveats

The Trust Center reports and SKIP_TAG_PROPAGATION require Enterprise Edition or higher.

Rollout checklist

  1. Decide which provided tags to adopt. Start from the vocabulary in SNOWFLAKE.TAGS: cost center, certification status, sensitivity, environment, and project. Treat SKIP_TAG_PROPAGATION as its own decision.
  2. Map them to existing custom tags. Where an account already has a custom tag for the same job, write down which provided tag replaces it, and which custom tags you will keep.
  3. Manage tag assignments as code. Keep the assignments in Terraform, and promote them through CI/CD with Azure DevOps Pipelines or GitHub Actions.
  4. Apply them on dbt models where that fits. Set the tags through dbt config or meta on the models that should carry them.
  5. Review the Trust Center reports on a schedule. Read the Sensitive Data Entitlement report and the Sensitive Data Access report on a cadence you choose.

How MyOrgLab helps

MyOrgLab builds governed analytics in the customer's own account. That work still sits on sound data infrastructure: Terraform, CI/CD, dbt, agile delivery, Azure DevOps, GitHub Actions, and Airflow.

Sources

Snowflake and Cortex are trademarks of Snowflake Inc.; MyOrgLab is not affiliated.

All Snowflake updates

MyOrgLab

MyOrgLab deploys governed analytics products, like Semantic HR's split-screen copilot with embedded BI and on-demand visualizations, in your Snowflake account, alongside semantic layers, BI galleries, and Cortex agents, including composable agent architectures, specialist analysts, orchestration, and governed MCP exposure, not a hosted multi-tenant agent product. Scoped partnerships with operable deliverables, not multi-tenant SaaS subscriptions or open-ended SI retainers. That work still sits on sound data infrastructure: Terraform, CI/CD, dbt, agile delivery, Azure DevOps, GitHub Actions, and Airflow.

© 2026 MyOrgLab. All rights reserved.

Platform partners for enterprise analytics, semantic intelligence, and AI.