- Platform Release 6.5
- Privacera Platform Release 6.5
- Enhancements and updates in Privacera Access Management 6.5 release
- Enhancements and updates in Privacera Discovery 6.5 release
- Enhancements and updates in Privacera Encryption 6.5 release
- Deprecation of older version of PolicySync
- Upgrade Prerequisites
- Supported versions of third-party systems
- Documentation changelog
- Known Issues 6.5
- Platform - Supported Versions of Third-Party Systems
- Platform Support Policy and End-of-Support Dates
- Privacera Platform Release 6.5
- Privacera Platform Installation
- About Privacera Manager (PM)
- Install overview
- Prerequisites
- Installation
- Default services configuration
- Component services configurations
- Access Management
- Data Server
- UserSync
- Privacera Plugin
- Databricks
- Spark standalone
- Spark on EKS
- Portal SSO with PingFederate
- Trino Open Source
- Dremio
- AWS EMR
- AWS EMR with Native Apache Ranger
- GCP Dataproc
- Starburst Enterprise
- Privacera services (Data Assets)
- Audit Fluentd
- Grafana
- Ranger Tagsync
- Discovery
- Encryption & Masking
- Privacera Encryption Gateway (PEG) and Cryptography with Ranger KMS
- AWS S3 bucket encryption
- Ranger KMS
- AuthZ / AuthN
- Security
- Access Management
- Reference - Custom Properties
- Validation
- Additional Privacera Manager configurations
- Upgrade Privacera Manager
- Troubleshooting
- How to validate installation
- Possible Errors and Solutions in Privacera Manager
- Unable to Connect to Docker
- Terminate Installation
- 6.5 Platform Installation fails with invalid apiVersion
- Ansible Kubernetes Module does not load
- Unable to connect to Kubernetes Cluster
- Common Errors/Warnings in YAML Config Files
- Delete old unused Privacera Docker images
- Unable to debug error for an Ansible task
- Unable to upgrade from 4.x to 5.x or 6.x due to Zookeeper snapshot issue
- Storage issue in Privacera UserSync & PolicySync
- Permission Denied Errors in PM Docker Installation
- Unable to initialize the Discovery Kubernetes pod
- Portal service
- Grafana service
- Audit server
- Audit Fluentd
- Privacera Plugin
- How-to
- Appendix
- AWS topics
- AWS CLI
- AWS IAM
- Configure S3 for real-time scanning
- Install Docker and Docker compose (AWS-Linux-RHEL)
- AWS S3 MinIO quick setup
- Cross account IAM role for Databricks
- Integrate Privacera services in separate VPC
- Securely access S3 buckets ssing IAM roles
- Multiple AWS account support in Dataserver using Databricks
- Multiple AWS S3 IAM role support in Dataserver
- Azure topics
- GCP topics
- Kubernetes
- Microsoft SQL topics
- Snowflake configuration for PolicySync
- Create Azure resources
- Databricks
- Spark Plug-in
- Azure key vault
- Add custom properties
- Migrate Ranger KMS master key
- IAM policy for AWS controller
- Customize topic and table names
- Configure SSL for Privacera
- Configure Real-time scan across projects in GCP
- Upload custom SSL certificates
- Deployment size
- Service-level system properties
- PrestoSQL standalone installation
- AWS topics
- Privacera Platform User Guide
- Introduction to Privacera Platform
- Settings
- Data inventory
- Token generator
- System configuration
- Diagnostics
- Notifications
- How-to
- Privacera Discovery User Guide
- What is Discovery?
- Discovery Dashboard
- Scan Techniques
- Processing order of scan techniques
- Add and scan resources in a data source
- Start or cancel a scan
- Tags
- Dictionaries
- Patterns
- Scan status
- Data zone movement
- Models
- Disallowed Tags policy
- Rules
- Types of rules
- Example rules and classifications
- Create a structured rule
- Create an unstructured rule
- Create a rule mapping
- Export rules and mappings
- Import rules and mappings
- Post-processing in real-time and offline scans
- Enable post-processing
- Example of post-processing rules on tags
- List of structured rules
- Supported scan file formats
- Data Source Scanning
- Data Inventory
- TagSync using Apache Ranger
- Compliance Workflow
- Data zones and workflow policies
- Workflow Policies
- Alerts Dashboard
- Data Zone Dashboard
- Data zone movement
- Workflow policy use case example
- Discovery Health Check
- Reports
- How-to
- Privacera Encryption Guide
- Overview of Privacera Encryption
- Install Privacera Encryption
- Encryption Key Management
- Schemes
- Encryption with PEG REST API
- Privacera Encryption REST API
- PEG API endpoint
- PEG REST API encryption endpoints
- PEG REST API authentication methods on Privacera Platform
- 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
- /authenticate
- /protect with encryption scheme
- /protect with masking scheme
- /protect with both encryption and masking schemes
- /unprotect without presentation scheme
- /unprotect with presentation scheme
- /unprotect with masking scheme
- REST API response partial success on bulk operations
- Audit details for PEG REST API accesses
- Make encryption API calls on behalf of another user
- Troubleshoot REST API Issues on Privacera Platform
- Privacera Encryption REST API
- Encryption with Databricks, Hive, Streamsets, Trino
- Databricks UDFs for encryption and masking on PrivaceraPlatform
- Hive UDFs for encryption on Privacera Platform
- StreamSets Data Collector (SDC) and Privacera Encryption on Privacera Platform
- Trino UDFs for encryption and masking on Privacera Platform
- Privacera Access Management User Guide
- Privacera Access Management
- How Polices are evaluated
- Resource policies
- Policies overview
- Creating Resource Based Policies
- Configure Policy with Attribute-Based Access Control
- Configuring Policy with Conditional Masking
- Tag Policies
- Entitlement
- Service Explorer
- Users, groups, and roles
- Permissions
- Reports
- Audit
- Security Zone
- Access Control using APIs
- AWS User Guide
- Overview of Privacera on AWS
- Configure policies for AWS services
- Using Athena with data access server
- Using DynamoDB with data access server
- Databricks access manager policy
- Accessing Kinesis with data access server
- Accessing Firehose with Data Access Server
- EMR user guide
- AWS S3 bucket encryption
- Getting started with Minio
- Plugins
- How to Get Support
- Coordinated Vulnerability Disclosure (CVD) Program of Privacera
- Shared Security Model
- Privacera Platform documentation changelog
Connect JDBC-based systems for Privacera Discovery
The following systems can be connected to Privacera Discovery as data sources via Java Database Connectivity (JDBC):
Amazon Aurora
Microsoft SQL Server
MySQL
Oracle
Postgres
PrestoSQL
Note
Starburst PrestoSQL versions are supported through version 350-e.
Redshift
Snowflake
Spark SQL
Synapse
Trino
Starburst
The general process is as follows:
Create or identify a service user in the target system with read/write privileges.
Determine the JDBC connection string to the data and database name in that target.
Define these details as properties in the Privacera Platform.
Prerequisites
Have the following details ready to enter into the data source definition in Privacera:
A username and password in the target system that has read/write permission.
The name of the JDBC driver you need.
A JDBC connection string to communicate with the target data source.
Required properties in Privacera
Values for the following properties are described in Required Name of JDBC Driver per Target System, Username and Password, and Required JDBC Connection String.
Note
The format of the jdbc.url
value varies by target system. Not all systems require databaseName
.
jdbc.driver.class=<jdbc_driver_name> jdbc.username=<user_with_readwrite_permission> jdbc.password=<login_credentials_of_identified_user> jdbc.url=jdbc:<protocol>://<hostname>:<port>;databaseName=<database_name>
Required name of JDBC Driver per target system
Depending on the target system, for the jdbc.driver.class
definition you enter in the Privacera properties, use one of the JDBC drivers shown below.
Amazon Aurora:
org.mariadb.jdbc.Driver
Microsoft SQL Server:
com.microsoft.sqlserver.jdbc.SQLServerDriver
MySQL:
com.mysql.jdbc.Driver
Oracle:
oracle.jdbc.driver.OracleDriver
Postgres:
org.postgresql.Driver
PrestoSQL:
org.apache.hive.jdbc.HiveDriver
Redshift:
com.amazon.redshift.jdbc.Driver
Snowflake:
net.snowflake.client.jdbc.SnowflakeDriver
Spark SQL (Databricks):
org.apache.hive.jdbc.HiveDriver
Synapse:
com.microsoft.sqlserver.jdbc.SQLServerDriver
Trino:
io.trino.jdbc.TrinoDriver
Starburst:
io.trino.jdbc.TrinoDriver
Username and password
Identify the name of a user who must have read/write permission in your data source and the login credentials for that user. These values are needed for jdbc.username
and jdbc.password
properties in Privacera.
Required JDBC connection string
The jdbc.url
value you enter in the Privacera properties must be one of the following, where <domainName>, <port>
, and other variables are for your specific environment:
Amazon Aurora:
jdbc:mysql://<domainName>:<port>/<dbname>
Microsoft SQL Server:
jdbc:sqlserver://<domainName>:<port>;databaseName=<db_name>
MySQL:
jdbc:mysql://<domainName>:<port>/<dbname>
Oracle:
jdbc:oracle:thin:@//<domainName>:<port>/<dbname>.localdomain
Postgres:
jdbc:postgresql://<domainName>:<port>/<dbname>
PrestoSQL:
jdbc:presto://<domainName>:<port>/<catalog_name>
Redshift:
jdbc:redshift://<domainName>:<port>/<dbname>
Snowflake:
jdbc:snowflake://<domainName>:<port>/?warehouse=<name_of_policysync_warehouse>
Spark SQL (Databricks):
jdbc:hive2://<domainName>:<port>/default;transportMode=http;ssl=true;httpPath=sql/protocolv1/o/0/xxxx-xxxxxx-xxxxxxxx;AuthMech=3;
Synapse:
jdbc:sqlserver://<domainName>:<port>;databaseName=<dbname>
Trino:
jdbc:trino://<host>:<port>/<catalog>
Starburst:
jdbc:trino://<host>:<port>/<catalog>
Note
The following three databases can be added as catalog on Trino and Starburst server: MySQL, Oracle, PostgreSQL
Add JDBC-Based data source in Privacera
These are the setup and steps to add a JDBC-based data source.
Setup
Have the details listed in the planning sections above ready to enter into the data source definition in Privacera
Steps
To add a JDBC-based data source in Privacera Platform:
Navigate to: Settings > Data Source Registration.
Optionally click Add System or modify an existing data source.
Enter a useful name for this data source and a useful description.
Click Save.
Locate the new data source system name and from the wrench icon on the right, select Add Data Source.
In the Add Data Source dialog, on the Choose tab, select JDBC APPLICATION.
On the Configure tab:
Enter a required Application Name of your choice.
Enter a required Application Code of your choice. This is an identifier for your own use.
If you have prepared a properties file in JSON format, click Import Properties and load the file.
Scroll to find the following properties and enter the values you prepared:
jdbc.username
jdbc.password
jdbc.driver.class
jdbc.url
Accept the default values for all other properties or modify them if needed.
At the bottom left, to verify the properties, click Test Connection.
At the bottom right, click Next to save the data source or Back to return to the Choose tab.