Normalyze
Sign In
a
Normalyze DSPM Powered by Snowflake now available on Snowflake Marketplace. Read More.
M

CSPM vs DSPM

Shadow Data

Request Demo
Sign In
What is DSPM?

FEATURED

Gartner® Innovation Insight: Data Security Posture Management
Get Report
PLATFORM
The Normalyze Platform
Supported Environments
Platform Benefits
USE CASES

Reduce Data Access Risks
Enforce Data Governance
Eliminate Abandoned Data

Secure PaaS Data

Enable Use of AI
DSPM for Snowflake

MARKETS

Healthcare
Retail
Technology
Media
M&A

RESOURCES

FEATURED

DSPM-chat-Richard Stiennon-Ravi-Ithal-Normalyze
DSPM for Dummies:

Your guide to Data Security Posture Management

Get Your Copy

COMPANY

FEATURED

CYBER 60: The fastest-growing startups in cybersecurity
Get Report

Snowflake Connected Application

Details to enable Connected Application for Snowflake Account.

Enterprises based on their security and compliance requirements might need to have results of the Data Scan Operation stored on Snowflake itself but in a separate database. To achieve this, Normalyze leverages the Snowflakes’ Connected Application feature to send the data scan results metadata to Snowflake database.

More details on Snowflake Connected Application feature are available on https://www.snowflake.com/guides/connected-apps/ for reference.

This feature is applicable only for Snowflake accounts.

Snowflake Setup for Storing the Data Scan Results:

  1. Create a Database, Schema that will be used for storing the data scan results on Snowflake.
  2. The following Tables are created under the schema from Step 1:
  • Datastores – Stores the account id value for the Onboarded account on Normalyze, Timestamp to store when the record is created (first instance of Data Scan Run), Timestamp to store when the record is updated (subsequent instance of Data Scan and Stores the metadata of the Data scan results (in JSON format).
  • Databases – Stores the Database names along with the detected Entities, Profiles and Classification tag associated with each one of them respectively.
  • Tables – Stores that Table name along with the associated Database, Schema, Type of table,Entities, Profiles and Classification tag associated with each one of them respectively.
  • Columns – Stores that Column name along with the associated Database, Schema, Table, Description (if available),Entities, Profiles and Classification tag associated with each one of them respectively.
  • Debug_Info – This table will capture the details for debug purposes in case of an event of app crash or any issues that the app encounter during the execution. This will be used for understanding the cause of the issue. Data from this table is not exposed on the UI of the Native App.

3. Grant the privileges on the Tables to the role defined for Normalyze usage.

SQL Script for setting up the aforementioned objects on the snowflake account:

This completes the set up on the Snowflake account for the Connected App requirement.

The role being granted the privileges for the objects (NORMALYZEROLE in this script) should be the same as created for the Snowflake onboarding as part of the prerequisites.

Steps to Enable Connected App Feature on Normalyze:

The functionality to use Snowflake Connected Application by Normalyze can be enabled once the Snowflake Account Onboarding is completed. The steps to be done to enable it are as follows:

 

  1. From the Normalyze Application navigate to Workspace – Accounts.
  2. Select the Snowflake Account for which the feature need to be enabled.
  3. Select “Edit Account” from pane.
  4. Toggle Enable Snowflake Connected App option to Yes ( by default this is set to No ).

6. Select Update to complete the steps.

Once the above steps are completed, Normalyze will be able to send the metadata of the data scan results back to the Snowflake database.


The database objects being created are done so to ensure all the Normalyze data resides in the specific entity. For this reason the Database, Schema and the Table name has to be exactly as-is provided in the script.