- PrivaceraCloud Release 7.4
- Enhancements and updates in PrivaceraCloud release 7.4
- Known Issues in PrivaceraCloud 7.4
- PrivaceraCloud User Guide
- Overview of PrivaceraCloud
- Connect applications with the setup wizard
- Connect applications
- About applications
- Connect Azure Data Lake Storage Gen 2 (ADLS) to PrivaceraCloud
- Connect Amazon Textract to PrivaceraCloud
- Athena
- Privacera Discovery with Cassandra
- Connect Databricks to PrivaceraCloud
- Databricks SQL
- Databricks SQL Overview and Configuration
- Planning and general process
- Prerequisites
- Databricks SQL with Privacera Hive
- Connect Databricks SQL application
- Grant Databricks SQL permissions to PrivaceraCloud users
- Define a resource policy
- Test the policy
- Databricks SQL PolicySync fields
- Configuring column-level access control
- View-based masking functions and row-level filtering
- Create an endpoint in Databricks SQL
- Databricks SQL Fields
- Databricks SQL Hive Service Definition
- Databricks SQL Masking Functions
- Databricks SQL Encryption
- Use a custom policy repository with Databricks
- Connect Databricks SQL to Hive policy repository on PrivaceraCloud
- Databricks SQL Overview and Configuration
- Connect Databricks Unity Catalog to PrivaceraCloud
- Connect S3 to PrivaceraCloud
- Prerequisites in AWS console
- Connect S3 application to PrivaceraCloud
- Enable Privacera Access Management for S3
- Enable Data Discovery for S3
- S3 AWS Commands - Ranger Permission Mapping
- S3
- AWS Access with IAM
- Access AWS S3 buckets from multiple AWS accounts
- Add UserInfo in S3 Requests sent via Dataserver
- Control access to S3 buckets with AWS Lambda function on PrivaceraCloud
- Dremio Plugin
- DynamoDB
- Connect Elastic MapReduce from Amazon application to PrivaceraCloud
- Connect EMR application
- EMR Spark access control types
- PrivaceraCloud configuration
- AWS IAM roles using CloudFormation setup
- Create a security configuration
- Create EMR cluster
- How to configure multiple JSON Web Tokens (JWTs) for EMR
- EMR Native Ranger Integration with PrivaceraCloud
- Connect EMRFS S3 to PrivaceraCloud
- Files
- GBQ
- Google Cloud Storage
- Connect Glue to PrivaceraCloud
- Google BigQuery for PolicySync
- Connect Kinesis to PrivaceraCloud
- Connect Lambda to PrivaceraCloud
- Microsoft SQL Server
- MySQL for Discovery
- Open Source Apache Spark
- Oracle for Discovery
- PostgreSQL
- Connect Power BI to PrivaceraCloud
- Presto
- Redshift
- Snowflake
- Starburst Enterprise with PrivaceraCloud
- Starburst Enterprise Presto
- Trino
- Connect users
- Data access Users, Groups, and Roles
- UserSync
- Portal user LDAP/AD
- Datasource
- Okta Setup for SAML-SSO
- Azure AD setup
- SCIM Server User-Provisioning
- User Management
- Identity
- Access Manager
- Access Manager
- Resource Policies
- Tag Policies
- Scheme Policies
- Service Explorer
- Reports
- Audit
- About data access users, groups, and roles resource policies
- Security zones
- Discovery
- Classifications via random sampling
- Privacera Discovery scan targets
- Propagate Privacera Discovery Tags to Ranger
- Enable offline scanning on Azure Data Lake Storage Gen 2 (ADLS)
- Enable Real-time Scanning of S3 Buckets
- Enable Real-time Scanning on Azure Data Lake Storage Gen 2 (ADLS)
- Enable Discovery Realtime Scanning Using IAM Role
- Encryption
- Overview of Privacera Encryption
- Encryption schemes
- Presentation schemes
- Masking schemes
- Create scheme policies
- Privacera-supplied encryption schemes for the Privacera API
- Privacera-supplied encryption schemes for the Bouncy Castle API
- API date input formats
- Deprecated encryption formats, algorithms, and scopes
- Privacera Encryption REST API
- PEG API endpoint
- PEG REST API encryption endpoints
- Prerequisites
- Common PEG REST API fields
- Construct the datalist for the /protect endpoint
- Deconstruct the response from the /unprotect endpoint
- Example data transformation with the /unprotect endpoint and presentation scheme
- Example PEG API endpoints
- Make encryption API calls on behalf of another user
- Privacera Encryption UDF for masking in Databricks on PrivaceraCloud
- Privacera Encryption UDFs for Trino on PrivaceraCloud
- Syntax of Privacera Encryption UDFs for Trino
- Prerequisites for installing Privacera Crypto plug-in for Trino
- Download and install Privacera Crypto jar
- Set variables in Trino etc/crypto.properties
- Restart Trino to register the Privacera encryption and masking UDFs for Trino
- Example queries to verify Privacera-supplied UDFs
- Privacera Encryption UDF for masking in Trino on PrivaceraCloud
- Encryption UDFs for Apache Spark on PrivaceraCloud
- Launch Pad
- Settings
- Dashboard
- Usage statistics
- Operational status of PrivaceraCloud and RSS feed
- How to Get Support
- Coordinated Vulnerability Disclosure (CVD) Program of Privacera
- Shared Security Model
- PrivaceraCloud Previews
- Preview: File Explorer for S3
- Preview: File Explorer for Azure
- Preview: File Explorer for GCS
- Preview: Scan Generic Records with NER Model
- Preview: Scan Electronic Health Records with NER Model
- Preview: OneLogin setup for SAML-SSO
- Preview: Azure Active Directory SCIM Server UserSync
- Preview: OneLogin UserSync
- Preview: PingFederate UserSync
- Quickstart for Databricks Unity Catalog on PrivaceraCloud
- What do I need to do in my Databricks Workspace?
- Where is the sample dataset in my Databricks Workspace?
- What should I do in the PrivaceraCloud web portal?
- Access use-case - How do I give a user access to a table or restrict from running a SQL select query?
- Access use-case - How do I restrict a user from seeing contents of a column in the result of a SQL select query?
- Column masking use-case - How do I restrict a user from seeing contents of a column by masking the values in the result of a SQL select query?
- Access use-case - How do I disallow a user from seeing certain rows of a table?
- PrivaceraCloud documentation changelog
Databricks SQL Fields
Basic fields
Field name | Type | Default | Required | Description |
---|---|---|---|---|
Databricks SQL jdbc url |
| Yes | Specifies the JDBC URL for the Databricks SQL connector. Use the following format for the JDBC URL: jdbc:spark://<WORKSPACE_URL>:443/<DATABASE>;transportMode=http;ssl=1;AuthMech=3;httpPath=/sql/1.0/endpoints/1234567890 The workspace URL and the database name are derived from your Databricks SQL configuration. | |
Databricks SQL jdbc username |
| Yes | Specifies the JDBC username to use. | |
Databricks SQL jdbc password |
| Yes | Specifies the access token of the SQL endpoint to use. | |
Databricks SQL default database |
| Yes | Specifies the name of the JDBC database to use. | |
Databricks SQL resource owner |
| No | Specifies the role that owns the resources managed by PolicySync. You must ensure that this user exists as PolicySync does not create this user.
The following resource types are supported:
| |
Databricks SQL workspace URL |
| Yes | Specifies the base URL for the Databricks SQL instance. | |
Databases to set access control policies |
| No | Specifies a comma-separated list of database names for which PolicySync manages access control. If unset, access control is managed for all databases. If specified, use the following format. You can use wildcards. Names are case-sensitive. An example list of databases might resemble the following: If specified, Databases to ignore while setting access control policies takes precedence over this setting. | |
Enable policy enforcements and user/group/role management |
|
| Yes | Specifies whether PolicySync performs grants and revokes for access control and creates, updates, and deletes queries for users, groups, and roles. The default value is |
Enable access audits |
|
| Yes | Specifies whether Privacera fetches access audit data from the data source. |
Advanced fields
Field name | Type | Default | Required | Description |
---|---|---|---|---|
Tables to set access control policies |
| No | Specifies a comma-separated list of table names for which PolicySync manages access control. You can use wildcards. Names are case-sensitive. Use the following format when specifying a table: <DATABASE_NAME>.<SCHEMA_NAME>.<TABLE_NAME> If specified, Tables to ignore while setting access control policies takes precedence over this setting. If you specify a wildcard, such as in the following example, all matched tables are managed:
The specified value, if any, is interpreted in the following ways:
| |
Databases to ignore while setting access control policies |
| No | Specifies a comma-separated list of database names that PolicySync does not provide access control for. You can specify wildcards. Names are case-sensitive. If not specified, all databases are subject to access control. For example: testdb1,testdb2,sales_db* This setting supersedes any values specified by Databases to set access control policies. | |
Tables to ignore while setting access control policies |
| No | Specifies a comma-separated list of table names that PolicySync does not provide access control for. You can specify wildcards. If not specified, all tables are subject to access control. Names are case-sensitive. Specify tables using the following format: <DATABASE_NAME>.<SCHEMA_NAME>.<TABLE_NAME> This setting supersedes any values specified by Tables to set access control policies. | |
Regex to find special characters in names |
|
| No | Specifies a regular expression to apply to a user name and replaces each matching character with the value specified by the If not specified, no find and replace operation is performed. |
String to replace with the special characters found in names |
|
| No | Specifies a string to replace the characters matched by the regex specified by the If not specified, no find and replace operation is performed. |
Regex to find special characters in user names |
|
| No | Specifies a regular expression to apply to a username and replaces each matching character with the value specified by the String to replace with the special characters found in user names setting. If not specified, no find and replace operation is performed. |
String to replace with the special characters found in user names |
|
| No | Specifies a string to replace the characters matched by the regex specified by the Regex to find special characters in user names setting. If not specified, no find and replace operation is performed. |
Regex to find special characters in group names |
|
| No | Specifies a regular expression to apply to a group and replaces each matching character with the value specified by the String to replace with the special characters found in group names setting. If not specified, no find and replace operation is performed. |
String to replace with the special characters found in group names |
|
| No | Specifies a string to replace the characters matched by the regex specified by the Regex to find special characters in group names setting. If not specified, no find and replace operation is performed. |
Regex to find special characters in role names |
|
| No | Specifies a regular expression to apply to a role name and replaces each matching character with the value specified by the String to replace with the special characters found in role names setting. If not specified, no find and replace operation is performed. |
String to replace with the special characters found in role names |
|
| No | Specifies a string to replace the characters matched by the regex specified by the Regex to find special characters in role names setting. If not specified, no find and replace operation is performed. |
Persist case sensitivity of user names |
|
| No | Specifies whether PolicySync converts user names to lowercase when creating local users. If set to |
Persist case sensitivity of group names |
|
| No | Specifies whether PolicySync converts group names to lowercase when creating local groups. If set to |
Persist case sensitivity of role names |
|
| No | Specifies whether PolicySync converts role names to lowercase when creating local roles. If set to |
Create users in Databricks SQL Endpoint by policysync |
|
| No | Specifies whether PolicySync creates local users for each user in Privacera. |
Manage users from portal |
|
| No | Specifies whether PolicySync maintains user membership in roles in the Databricks SQL data source. |
Manage groups from portal |
|
| No | Specifies whether PolicySync creates groups from Privacera in the Databricks SQL data source. |
Manage roles from portal |
|
| No | Specifies whether PolicySync creates roles from Privacera in the Databricks SQL data source. |
Users to set access control policies |
| No | Specifies a comma-separated list of user names for which PolicySync manages access control. You can use wildcards. Names are case-sensitive. If not specified, PolicySync manages access control for all users. If specified, Users to be ignored by access control policies takes precedence over this setting. An example user list might resemble the following: | |
Groups to set access control policies |
| No | Specifies a comma-separated list of group names for which PolicySync manages access control. If unset, access control is managed for all groups. If specified, use the following format. You can use wildcards. Names are case-sensitive. An example list of projects might resemble the following: If specified, Groups be ignored by access control policies takes precedence over this setting. | |
Roles to set access control policies |
| No | Specifies a comma-separated list of role names for which PolicySync manages access control. If unset, access control is managed for all roles. If specified, use the following format. You can use wildcards. Names are case-sensitive. An example list of projects might resemble the following: If specified, Roles be ignored by access control policies takes precedence over this setting. | |
Users to be ignored by access control policies |
| No | Specifies a comma-separated list of user names that PolicySync does not provide access control for. You can specify wildcards. Names are case-sensitive. If not specified, all users are subject to access control. This setting supersedes any values specified by Users to set access control policies. | |
Groups be ignored by access control policies |
| No | Specifies a comma-separated list of group names that PolicySync does not provide access control for. You can specify wildcards. Names are case-sensitive. If not specified, all groups are subject to access control. This setting supersedes any values specified by Groups to set access control policies. | |
Roles be ignored by access control policies |
| No | Specifies a comma-separated list of role names that PolicySync does not provide access control for. You can specify wildcards. Names are case-sensitive. If not specified, all roles are subject to access control. This setting supersedes any values specified by Roles to set access control policies. | |
Prefix of Databricks SQL Endpoint roles for portal groups |
|
| No | Specifies the prefix that PolicySync uses when creating local roles. For example, if you have a group named |
Prefix of Databricks SQL Endpoint roles for portal roles |
|
| No | Specifies the prefix that PolicySync uses when creating roles from Privacera in the Databricks SQL data source. For example, if you have a role in Privacera named |
Use Databricks SQL Endpoint native public group for public group access policies |
|
| No | Specifies whether PolicySync uses the Databricks SQL native public group for access grants whenever a policy refers to a public group. The default value is true. |
Set access control policies only on the users from managed groups |
|
| No | Specifies whether to manage only the users that are members of groups specified by Groups to set access control policies. The default value is false. |
Set access control policies only on the users/groups from managed roles |
|
| No | Specifies whether to manage only users that are members of the roles specified by Roles to set access control policies. The default value is false. |
Use email as service name |
|
| No | This Property is used to map the username to the email address when granting/revoking access. |
Enforce masking policies using secure views |
|
| No | Specifies whether to use secure view based masking. The default value is |
Enforce row filter policies using secure views |
|
| No | Specifies whether to use secure view based row filtering. The default value is While Databricks SQL supports native filtering, PolicySync provides additional functionality that is not available natively. Enabling this setting is recommended. |
Create secure view for all tables/views |
|
| No | Specifies whether to create secure views for all tables and views that are created by users. If enabled, PolicySync creates secure views for resources regardless of whether masking or filtering policies are enabled. |
Default masked value for numeric datatype columns |
|
| No | Specifies the default masking value for numeric column types. |
Default masked value for text/varchar/string datatype columns |
|
| No | Specifies the default masking value for text and string column types. |
Secure view name prefix |
| No | Specifies a prefix string for secure views. By default view-based row filter and masking-related secure views have the same schema name as the table schema name. If you want to change the secure view schema name prefix, specify a value for this setting. For example, if the prefix is | |
Secure view name postfix |
| No | Specifies a postfix string for secure views. By default view-based row filter and masking-related secure views have the same schema name as the table schema name. If you want to change the secure view schema name postfix, specify a value for this setting. For example, if the postfix is | |
Secure view database name prefix |
| No | Specifies a prefix string for secure views. By default view-based row filter and masking-related secure views have the same name as the table database name. For example, if the prefix is | |
Secure view database name postfix |
|
| No | Specifies a postfix string for secure views. By default view-based row filter and masking-related secure views have the same name as the table database name. For example, if the postfix is |
Enable dataadmin |
|
| No | This property is used to enable the data admin feature. With this feature enabled you can create all the policies on native tables/views, and respective grants will be made on the secure views of those native tables/views. These secure views will have row filter and masking capability. In case you need to grant permission on the native tables/views then you can select the permission you want plus data admin in the policy. Then those permissions will be granted on both the native table/view as well as its secure view. |
Users to exclude when fetching access audits |
|
| No | Specifies a comma separated list of users to exclude when fetching access audits. For example: |
Custom fields
Canonical name | Type | Default | Description |
---|---|---|---|
|
|
| Specifies how PolicySync loads resources from Databricks SQL. The following values are allowed:
|
|
|
| Specifies the interval in seconds for PolicySync to wait before checking for new resources or changes to existing resources. |
|
|
| Specifies the interval in seconds for PolicySync to wait before reconciling principals with those in the data source, such as users, groups, and roles. When differences are detected, PolicySync updates the principals in the data source accordingly. |
|
|
| Specifies the interval in seconds for PolicySync to wait before reconciling Apache Ranger access control policies with those in the data source. When differences are detected, PolicySync updates the access control permissions on data source accordingly. |
|
|
| Specifies the interval in seconds to elapse before PolicySync retrieves access audits and saves the data in Privacera. |
|
|
| Specifies how user name conversions are performed. The following options are valid:
This setting applies only if Persist case sensitivity of user names is set to |
|
|
| Specifies how group name conversions are performed. The following options are valid:
This setting applies only if Persist case sensitivity of group names is set to |
|
|
| Specifies how role name conversions are performed. The following options are valid:
This setting applies only if Persist case sensitivity of role names is set to |
|
| Specifies a suffix to remove from a table or view name. For example, if the table is named You can specify a single suffix or a comma separated list of suffixes. | |
|
| Specifies a suffix to remove from a database name. For example, if the database is named You can specify a single suffix or a comma separated list of suffixes. | |
|
|
| Specifies the initial delay, in minutes, before PolicySync retrieves access audits from Databricks SQL. |