Manage PII exposure in your data warehouse
Tokenize, mask and restrict access to sensitive data in your analytics environment in a few easy steps.
Control sensitive data in your analytics with Piiano Vault.
Problem
Data privacy doesn't have to get in the way of your analytics.
When it comes to analytics environments, access to sensitive data like PII can spiral out of control without the right infrastructure:
1. Excessive permissions
2. Multiple copies of sensitive data
3. Data can leave the environments without controls
Solution
Extract valuable insights from datasets while protecting privacy.
Piiano Vault helps you safeguard, segregate and isolate sensitive customer data with centralized controls. Integrate Vault with your favorite analytics environment so your queries seamlessly retrieve the data, either masked or in plaintext (don't worry, it's all logged and audited anyway).
You can save money, by tokenizing PII before it is stored in your analytics. That way you don't have to run right-to-be-forgotten deletion queries on your whole data warehouse. You can just delete the tokens in Vault and be done with it.
Benefits
No need to compromise on privacy or innovation.
Activity
All activity is audited and logged, know which data is accessed
Simple integration
A few lines of user-defined-functions code and you’re done
Governance
Authorize access to PII only on need-to-know basis
Seamless
SQL queries continue to work transparently while PII is vaulted
Features
Manage data exposure with Vault:
Tokenization
Tokenize PII before it reaches your data warehouse
Data masking
Apply masking according to data types or users when data is retrieved
Access policies
Configure highly granular access policies or run your own proprietary logic
Process
Easy set up
Step 1
Register for a Vault instance
Step 2
Create a collection with your sensitive data properties
Step 3
Embed Piiano’s code in your analytics
Use a predefined code snippet to configure UDFs and access policies
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
USE ROLE SYSADMIN;
CREATE OR REPLACE DATABASE my_users;
CREATE OR REPLACE TABLE my_users..customers (
first_name STRING,
last_name STRING,
email STRING,
ssn STRING,
person_id VARIANT
);
CREATE OR REPLACE WAREHOUSE my_warehouse WITH
WAREHOUSE_SIZE='X-SMALL'
AUTO_SUSPEND = 180
AUTO_RESUME = TRUE
INITIALLY_SUSPENDED=TRUE;
USE ROLE USERADMIN;
CREATE OR REPLACE ROLE developer;
CREATE OR REPLACE ROLE user1;
CREATE OR REPLACE ROLE user2;
CREATE OR REPLACE ROLE maskingadmin;
Step 4
Execute safe queries
Use Vault’s IAM to configure what each user sees based on their permissions and data sensitivity
