<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Ankit Gupta on Medium]]></title>
        <description><![CDATA[Stories by Ankit Gupta on Medium]]></description>
        <link>https://medium.com/@a.gupta_99847?source=rss-7216b5a2bbcd------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*dmbNkD5D-u45r44go_cf0g.png</url>
            <title>Stories by Ankit Gupta on Medium</title>
            <link>https://medium.com/@a.gupta_99847?source=rss-7216b5a2bbcd------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 04:57:14 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@a.gupta_99847/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Announcing Public Preview of Automatic Sensitive Data Classification]]></title>
            <link>https://medium.com/snowflake/announcing-public-preview-of-automatic-sensitive-data-classification-b75da8865ae0?source=rss-7216b5a2bbcd------2</link>
            <guid isPermaLink="false">https://medium.com/p/b75da8865ae0</guid>
            <category><![CDATA[snowflake]]></category>
            <category><![CDATA[data-classification]]></category>
            <category><![CDATA[data-governance]]></category>
            <category><![CDATA[snowflake-horizon-catalog]]></category>
            <category><![CDATA[sensitive-data-discovery]]></category>
            <dc:creator><![CDATA[Ankit Gupta]]></dc:creator>
            <pubDate>Tue, 26 Nov 2024 18:54:43 GMT</pubDate>
            <atom:updated>2024-11-26T18:54:43.766Z</atom:updated>
            <content:encoded><![CDATA[<p>Thousands of customers rely on Snowflake Horizon Catalog Governance capabilities to manage their sensitive information that requires proper governance. Identifying and locating this sensitive data is the crucial first step towards establishing effective data governance. Subsequently, protecting this sensitive data using appropriate access control ensures that customers can empower their data teams to unlock true value from the data. <a href="https://docs.snowflake.com/en/user-guide/classify-intro">Sensitive Data Classification</a>, an existing Horizon Catalog Governance feature, enables customers to discover and appropriately tag sensitive data like <a href="https://docs.snowflake.com/en/user-guide/classify-intro#system-tags-and-categories">PII and PCI</a> across various geographies. Additionally, customers can write their own <a href="https://docs.snowflake.com/en/user-guide/classify-custom">Custom classifiers</a> to detect sensitive data that is proprietary to their domain or industry. Many Snowflake customers leverage these built-in features daily to mitigate risks and ensure compliance by classifying all their data stored within Snowflake.</p><p>Today, we are making it even more seamless to detect and protect sensitive data. We are excited to announce the <strong><em>Public Preview of a new Horizon Catalog governance feature — Automatic Sensitive Data Classification. </em></strong><a href="https://docs.snowflake.com/user-guide/classify-auto">Automatic Sensitive Data Classification</a> runs in the background and automatically tags the columns where sensitive data is found. Since Snowflake automates and manages this as a serverless feature, customers don’t need to write complex stored procedures or manually run the classification process. You just have to configure it once, and the service takes care of finding sensitive data across the schemas, tagging them with your custom taxonomy, and optionally applying masking policies to protect the data.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*STgc83DYyPEfroReuiVujw.png" /><figcaption>Automatic Sensitive Data Classification, Tagging, and Protection</figcaption></figure><p>We have been in private preview with a small set of customers and here is what they have to say about its ease of use and the time it saves to detect and protect sensitive data:</p><blockquote>We are excited about the native Data Classification capability in Snowflake. Automatic Sensitive Data Classification feature will enable us to efficiently detect sensitive data and apply classifications and tags without the data leaving Snowflake. This functionality has already proven beneficial in classifying data attributes specific to DIRECTV. We are eager to implement this capability throughout our entire data estate.</blockquote><blockquote>Pavan Vutukuru, Sr. Director, DIRECTV</blockquote><blockquote>We’re excited about leveraging Snowflake’s native Data Classification capability in our PII &amp; Federated compliance journey. Automatic Sensitive Data Classification feature has been instrumental in our enterprise-scale implementation, enabling automated sensitive data detection and protection without data movement.</blockquote><blockquote>Our implementation uniquely extends this capability to external tables in S3 through Snowflake’s external table functionality, providing a comprehensive classification approach across our entire data estate.</blockquote><blockquote>Principal Solution Architect, at a large UK based bank</blockquote><h3>How it works</h3><p><a href="https://docs.snowflake.com/en/user-guide/classify-auto">Automatic Sensitive Data Classification</a> is a serverless feature that periodically checks for the tables that meet the criteria to be scanned for sensitive data and then takes the action defined in the classification profile. The profile criteria lets users define when to classify a new table, when to re-classify a previously classified table, and the tags to apply when sensitive data is found.</p><p>Once the classification profile is associated with one or more schemas, the classification process starts to monitor the tables that meet the criteria. Based on the number of the columns in a table, the Classification process picks the right size of compute to assign the jobs to. If sensitive data is found, Snowflake’s <em>Semantic_Category</em> and <em>Privacy_Category</em> system tags are applied on to such columns. Additionally, users can also apply their own taxonomy using user-defined <a href="https://docs.snowflake.com/en/user-guide/object-tagging">Object tags</a>. For instance, if Name or Address is found in a column, then the classification process can automatically set a <em>‘Sensitivity=Highly Confidential’</em> tag on the column.</p><p>Object tags can be associated with a <a href="https://docs.snowflake.com/en/user-guide/tag-based-masking-policies">masking policy</a>. Tag based masking is one of the simplest ways to enable data protection at scale and by applying tags as part of the Classification process, you can enable automatic protection of sensitive data from unauthorized access.</p><p>Now let’s look at how to set up Automatic Sensitive Data Classification in your Snowflake account.</p><h3>Step-by-Step</h3><p>Setting up Automatic Classification involves the following steps:</p><ol><li>Create a <em>classification profile</em> that controls how often sensitive data in a schema is automatically classified, including whether system tags should be automatically applied after classification.</li><li>Optionally, use the classification profile to map user-defined tags to system tags so a column with sensitive data can be associated with a user-defined tag based on its classification. You can add the tag mapping while creating the classification profile or after.</li><li>Set the classification profile on a schema so that tables in the schema get automatically classified.</li></ol><h4>STEP 1: Create a Classification profile</h4><p>Any user with SNOWFLAKE.CLASSIFICATION_ADMIN database role can create an instance of a classification profile. To grant the right privileges, run the following command:</p><pre>USE ROLE ACCOUNTADMIN;<br><br>GRANT DATABASE ROLE SNOWFLAKE.CLASSIFICATION_ADMIN TO ROLE data_engineer;</pre><p>Create an instance of the CLASSIFICATION_PROFILE class:</p><pre>CREATE OR REPLACE SNOWFLAKE.DATA_PRIVACY.CLASSIFICATION_PROFILE<br>  my_classification_profile(<br>    {<br>      &#39;maximum_classification_validity_days&#39;: 30,<br>      &#39;minimum_object_age_for_classification_days&#39;: 1,<br>      &#39;auto_tag&#39;: true<br>    });</pre><p>If you don’t want to apply the tags automatically, then set <em>auto_tag</em> as <em>false</em>. This will still classify the columns and capture it in the CLASSIFICATION REULT but not apply the tags on the columns.</p><h4>STEP 2: Add a tag map to the profile to apply user-defined tags (optional)</h4><p>Call the SET_TAG_MAP method on the instance to add a tag map to the classification profile. This allows custom tags to be automatically applied on columns that contain sensitive data.</p><pre>CALL my_classification_profile!SET_TAG_MAP(<br>  {&#39;column_tag_map&#39;:[<br>    {<br>      &#39;tag_name&#39;:&#39;my_db.sch1.sensitivity&#39;,<br>      &#39;tag_value&#39;:&#39;Highly Confidential&#39;,<br>      &#39;semantic_categories&#39;:[&#39;NAME&#39;, &#39;EMAIL&#39;, &#39;PAYMENT_CARD&#39;, &#39;NATIONAL_IDENTIFIER&#39;]<br>    }]});</pre><p>Alternatively, you could have added the tag-map when you created the classification profile in STEP 1.</p><h4>STEP 3: Associate the profile with the schema</h4><p>This step enables Automatic Sensitive Data Classification to run in the background and monitor the tables in the schema. You can set the same profile with multiple schemas. To set the profile on the schema, you must have ‘EXECUTE AUTO CLASSIFICATION ON ACCOUNT’ privilege along with MODIFY or OWNERSHIP privilege on the schema.</p><p>Once you have the right privileges, set the profile on one or more schemas:</p><pre>ALTER SCHEMA mydb.sch <br>SET CLASSIFICATION_PROFILE = &#39;mydb.sch.my_classification_profile&#39;;</pre><p>At this step, Automatic Sensitive Data Classification has been enabled on the schema. The background process will start to fetch the qualifying tables and start classifying them. As new tables are created in the schema, they will be classified automatically based on the settings in the classification profile.</p><h4><strong>Review the Classification results</strong></h4><p>Once Automatic Classification runs, the classification results can be viewed for each table by calling the system stored procedure in the following way:</p><pre>CALL SYSTEM$GET_CLASSIFICATION_RESULT(&#39;mydb.sch.t1&#39;);</pre><h4><strong>Report for sensitive data at the account level</strong></h4><p>To generate a report on all the sensitive data across your account, you can query the <em>DATA_CLASSIFICATION_LATEST</em> ACCOUNT_USAGE view. To query this view, users must use a role that is granted the SNOWFLAKE.GOVERNANCE_VIEWER database role. For example:</p><pre>SELECT * FROM snowflake.account_usage.data_classification_latest;</pre><p>This query will return you all the tables, the database and the schema that they reside in, last time each table was classified, and the classification results.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*OEoFdvDfZNQhfLue" /></figure><p>We are continuously making improvements to Sensitive Data Classification capabilities in Snowflake so stay tuned for more updates.</p><h3>Resources</h3><p><a href="https://docs.snowflake.com/en/user-guide/classify-auto">Automatic Sensitive Data Classification</a></p><p><a href="https://docs.snowflake.com/en/user-guide/classify-intro">Introduction to Sensitive Data Classification</a></p><p><a href="https://docs.snowflake.com/en/user-guide/classify-custom">Custom classifiers</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b75da8865ae0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/snowflake/announcing-public-preview-of-automatic-sensitive-data-classification-b75da8865ae0">Announcing Public Preview of Automatic Sensitive Data Classification</a> was originally published in <a href="https://medium.com/snowflake">Snowflake Builders Blog: Data Engineers, App Developers, AI, &amp; Data Science</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Announcing Public Preview of Custom Classification and new SQL interfaces]]></title>
            <link>https://medium.com/snowflake/announcing-public-preview-of-custom-classification-and-new-sql-interfaces-8602ea89d588?source=rss-7216b5a2bbcd------2</link>
            <guid isPermaLink="false">https://medium.com/p/8602ea89d588</guid>
            <category><![CDATA[data-classification]]></category>
            <category><![CDATA[snowflake]]></category>
            <category><![CDATA[data-governance]]></category>
            <dc:creator><![CDATA[Ankit Gupta]]></dc:creator>
            <pubDate>Wed, 06 Mar 2024 20:48:22 GMT</pubDate>
            <atom:updated>2024-05-14T23:19:52.540Z</atom:updated>
            <content:encoded><![CDATA[<p><a href="https://docs.snowflake.com/en/user-guide/governance-classify-concepts">Data classification in Snowflake</a> provides a way to identify sensitive information in the data. Once the data has been classified and tagged, it makes it easier to discover and govern. It also helps in understanding the risks associated with the data thereby ensuring the right protection policies are in place to control access to the sensitive information.</p><p>To help with sensitive data classification, Snowflake provides several <a href="https://docs.snowflake.com/en/user-guide/governance-classify-concepts#system-tags-and-categories">native classifiers</a> that can identify PII (Personally Identifiable Information), PCI (Payment Card Industry) and other sensitive categories in your data like Name, Address, Social Security Number, Passport number, Credit Card numbers.</p><p>While native classifiers are great at identifying general sensitive information, there is often industry- and domain-specific data that customers want to classify and protect. For e.g., internal Employee IDs, or medical health code information associated with the patients is often considered sensitive and confidential information. We are excited to announce support for Custom Classifiers in Public Preview. Custom Classifiers can be written by the customers to extend Snowflake’s native classification capabilities and identify sensitive information across all their data in Snowflake.</p><h3>Define and use custom classifiers</h3><p>Snowflake provides the CUSTOM_CLASSIFIER class in the SNOWFLAKE.DATA_PRIVACY schema to enable data engineers to extend the data classification capabilities. Classes and instances are schema-level objects in Snowflake. You can think of a class as an extensible Snowflake object type and an instance as a Snowflake object. A class provides a public API through stored procedures and functions. Collectively they are referred to as class methods. You can learn more about Snowflake Class <a href="https://docs.snowflake.com/en/sql-reference/snowflake-db-classes">here</a>.</p><p>Once you create an instance of the class, you can call a method to define your own semantic category, specify the privacy category, and specify regular expressions to match column value patterns while optionally match the column name.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/636/1*ujBFdi6aNo5FjepVpJaygA.png" /></figure><p>As an example, to identify <a href="https://en.wikipedia.org/wiki/ICD-10">ICD-10 medical codes</a> in the data, you can create an instance medical_codes() of the class CUSTOM_CLASSIFIER like this:</p><pre>CREATE [ OR REPLACE ] SNOWFLAKE.DATA_PRIVACY.CUSTOM_CLASSIFIER medical_codes();</pre><p>Then, call the <a href="https://docs.google.com/document/d/137wNoLTPnhu2F1NRWzIp_bp2u4rFsZixaveMozVqJZE/edit#heading=h.xlnizq990wil">custom_classifier!ADD_REGEX</a> method on the instance to specify the system tags and regular expression to identify ICD-10 codes in a column. The regular expression in this example matches all possible ICD-10 codes. The column name regular expression and the description are optional:</p><pre>CALL &lt;custom_classifier&gt;!ADD_REGEX(<br>  &#39;&lt;semantic_category&gt;&#39;,<br>  &#39;&lt;privacy_category&gt;&#39;,<br>  &#39;&lt;value_regex&gt;&#39;,<br>  [ &lt;column_name_regex&gt; ]<br>  [ &lt;description&gt; ]<br>  );</pre><p>Example:</p><pre>CALL medical_codes!ADD_REGEX(<br>  &#39;ICD_10_CODES&#39;,<br>  &#39;IDENTIFIER&#39;,<br>  &#39;[A-TV-Z][0-9][0-9AB]\.?[0-9A-TV-Z]{0,4}&#39;,<br>  &#39;ICD.*&#39;,<br>  &#39;Add a regex to identify ICD-10 medical codes in a column&#39;<br>);</pre><p>Finally, call the new <a href="https://docs.snowflake.com/en/LIMITEDACCESS/custom-classification/system_classify">SYSTEM$CLASSIFY</a> stored procedure, passing in the custom classifier instances to classify the table that contains the column with medical codes, and automatically assign the custom recommended tag to the column.</p><pre>CALL SYSTEM$CLASSIFY(<br>  &#39;data.tables.patient_diagnosis&#39;,<br>  {&#39;auto_tag&#39;: true, &#39;custom_classifiers&#39;: [&#39;data.classifiers.medical_codes&#39;]}<br>  );</pre><p>Auto-tagging the columns in the table is optional. If you prefer to evaluate the classification result first, remove the auto-tag argument from the stored procedure. After you evaluate the result, assign the Semantic_Category tag to the columns using <a href="https://docs.snowflake.com/en/sql-reference/stored-procedures/associate_semantic_category_tags">ASSOCIATE_SEMANTIC_CATEGORY_TAGS</a> or set custom tags using an <a href="https://docs.snowflake.com/en/sql-reference/sql/alter-table-column">ALTER TABLE … MODIFY COLUMN … SET TAG</a> command.</p><p>Additionally, specifying each custom classifier is optional when you have multiple custom classification instances. Instead, you can specify <em>‘use_all_custom_classifiers’: true</em>.</p><p>You can learn more about Custom Classification and all the supported SQL commands by reading our <a href="http://docs.snowflake.com/user-guide/classify-custom">documentation</a>.</p><h3>New Classification SQL interfaces</h3><p>In an effort to continuously improve and simplify the classification process, we recently introduced in private preview, the <a href="https://www.snowflake.com/blog/data-classification-snowsight-ui/">native data classification in Snowsight </a>and new SQL interfaces:</p><ul><li>SYSTEM$CLASSIFY</li><li>SYSTEM$CLASSIFY_SCHEMA</li><li>SYSTEM$GET_CLASSIFICATION_RESULT</li><li>DATA_CLASSIFICATION_LATEST</li></ul><p>Currently, the classification process requires calling two separate system functions, EXTRACT_SEMANTIC_CATEGORIES to identify sensitive data, and ASSOCIATE_SEMANTIC_CATEGORIES_TAGS to associate the semantic_category tags with the corresponding columns. These APIs have to be executed for each table that you want to classify.</p><p>The new SQL stored procedure, SYSTEM$CLASSIFY, combines the two steps into one making it convenient to identify and tag sensitive information in a single step. Additionally, you can also get the most recent classification result for each object using the new SYSTEM$GET_CLASSIFICATION_RESULT function and for all objects using the new DATA_CLASSIFICATION_LATEST view in account_usage.</p><pre>CALL SYSTEM$CLASSIFY(&#39;hr.tables.empl_info&#39;, {&#39;auto_tag&#39;: true});<br><br>SELECT SYSTEM$GET_CLASSIFICATION_RESULT(&#39;hr.tables&#39;);<br><br>SELECT * from SNOWFLAKE.ACCOUNT_USAGE.DATA_CLASSIFICATION_LATEST;</pre><p>As the name suggests, SYSTEM$CLASSIFY_SCHEMA stored procedure can be used to classify all tables in a schema greatly simplifying the classification process. Repeat these steps for each schema that contains tables that you want to classify.</p><pre>CALL SYSTEM$CLASSIFY_SCHEMA(&#39;hr.tables&#39;, {&#39;auto_tag&#39;: true});</pre><p>You can learn more about the new Classification SQL APIs by reading our <a href="https://docs.snowflake.com/en/user-guide/governance-classify-using">documentation</a>.</p><p>We are continuously making improvements to the Data Classification capabilities in Snowflake so stay tuned for more updates. Feel free to reach out to us for any feedback or questions.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8602ea89d588" width="1" height="1" alt=""><hr><p><a href="https://medium.com/snowflake/announcing-public-preview-of-custom-classification-and-new-sql-interfaces-8602ea89d588">Announcing Public Preview of Custom Classification and new SQL interfaces</a> was originally published in <a href="https://medium.com/snowflake">Snowflake Builders Blog: Data Engineers, App Developers, AI, &amp; Data Science</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>