Tagging Columns to Anonymize PII Data in Catalog and Immuta

0 out of 4 steps completed0%
4 Lessons

About this Course

Approximate Time to Completion: .5 hour


  • Steve Touw, Co-Founder & CTO, Immuta
  • Eric Kriner, Solution Architect, Immuta

Course Objectives:

  • Select columns to apply PII anonymization policy
  • Create dataset for reporting needs
  • Inspect masked columns in dataset

In this course, we will discuss how an organization can leverage Collibra’s Catalog, specifically the Data Dictionary, alongside Collibra’s Policy Manager, in addition to the enforcement that’s happening within Immuta. We’ll present a story of a data owner in HR, who needs to provide the data necessary for an external business partner and for his teams’ analytics and reporting needs. Using Catalog’s native functionality, we’ll use the ingestion process for an HR table and begin to evaluate the columns. The columns will be tagged if PII data is available and the PII anonymization policy will be added as a relation. Next, we will create a dataset to provide to the HR team and external business partner. Once the dataset is approved for use, the PII data will either be masked or available, depending on the access rights of the user. Immuta captures the information pertaining to the columns tagged as PII and enforces the appropriate policy when the dataset is accessed.


You might be interested in these courses:

Course Materials