Chapter 1 - Configure Immuta
This chapter guides you through configuring your data warehouse and compute, Identity Manager, and external catalog integrations.
Once configuration is complete, Data Governors can use tags to drive policies and generate Immuta Reports.
Immuta Best Practices: Users, Permissions, Attributes, and Tags
Best Practices: Users, Permissions, Attributes, and Tags
The best practices outlined below will also appear in callouts within relevant tutorials.
- If Sensitive Data Discovery has been enabled, then manually adding tags to columns in the Data Dictionary will be unnecessary in most cases. The Data Owner will need to verify that the Discovered tags are correct.
- Turning on Sensitive Data Discovery can improve your data's securing with its automated tagging. Immuta highly recommends the use of this feature in tandem with vigilant verification of tags on all data sources.
- Use an external IAM for authentication and Immuta's internal IAM to manage attributes.
- Use the minimum number of tags possible to achieve the data privacy needed.
- Start organizing attributes and groups in Immuta and transfer them to your IAM.
Chapter 1 Use Case Scenario
Use Case
The use case described below will be presented throughout this chapter in this call-out to illustrate specific tutorials. However, the solutions presented can be adjusted to meet your specific needs.
An organization has purchased Immuta to manage data access across multiple environments (Dev, Test, and Prod), each of which requires different users with different permissions to gain access.
To set up Immuta to accommodate these requirements, a System Administrator will create users and assign permissions, attributes, and groups added to them. Then, Data Governors will create tags to identify the environments. The data and user attributes created will be used to build Global Policies in Chapter 2.
Chapter Objectives
In this chapter, you will complete tutorials that demonstrate how to