Hi, I'm Ask INFA!
What would you like to know?
ASK INFAPreview
Please to access Ask INFA.

Table of Contents

Search

  1. Preface
  2. Introduction to Data Access Management
  3. Data access policies
  4. Precedence tiers
  5. Data protections
  6. Data access asset lifecycle
  7. Audit events
  8. Pushdown enforcement
  9. Tokenization syntax reference
  10. Data types

Data Access Management

Data Access Management

Prerequisites for Databricks pushdown enforcement

Prerequisites for Databricks pushdown enforcement

You can enable
Data Governance and Catalog
to push down
data access policies
into your Databricks source system.
Complete the following configuration and authorization tasks for your Databricks source system:
  1. Configure the connection.
    For more information about creating a Databricks connection, see the
    Databricks Sources
    guide in
    Metadata Command Center
    .
  2. Ensure that the user identified in the catalog source connection that pushes the policies has Databricks workspace admin permissions on the catalog source.
  3. Configure Databricks as a catalog source.
    For each catalog and schema on which you want to apply
    data access policies
    , you have the following options for granting permissions:
    • Grant MANAGE and USAGE on the catalog and USAGE on all relevant schemas:
      GRANT USAGE ON CATALOG catalog_name TO user_or_role; GRANT MANAGE ON CATALOG catalog_name TO user_or_role; GRANT USAGE ON SCHEMA catalog_name.schema TO user_or_role;
    • Grant USAGE on the catalog and USAGE and MANAGE on all relevant schemas:
      GRANT USAGE ON CATALOG catalog_name TO user_or_role; GRANT USAGE ON SCHEMA catalog_name.schema TO user_or_role; GRANT MANAGE ON SCHEMA catalog_name.schema TO user_or_role;
  4. For
    data filter policies
    , your Databricks catalog needs to be able to enforce Databricks' row filters.
    For
    data de-identification policies
    , your Databricks catalog needs to be able to enforce Databricks' column masks.
    Data Access Management
    requires a Databricks catalog to store the necessary objects and functions.
    Data Access Management
    uses the following Databricks catalog by default:
    cdam_internal_state
  5. For
    data filter policies
    or
    data de-identification policies
    , create the following catalog and schema on your Databricks source system:
    CREATE cdam_internal_state.default
    Databricks does not allow row filters or column masks on views. Therefore, you can't apply
    data filter policies
    or
    data de-identification policies
    to views in Databricks.
  6. For
    data filter policies
    or
    data de-identification policies
    , grant the following permissions to the connection associated with your Databricks source system:
    GRANT CREATE FUNCTION ON SCHEMA cdam_internal_state.default TO user_or_role; GRANT DROP FUNCTION ON SCHEMA cdam_internal_state.default TO user_or_role;
For more information about configuring a catalog source for Databricks, see the
Databricks Sources
help in
Metadata Command Center
.

0 COMMENTS

We’d like to hear from you!