- 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
StreamSets Data Collector (SDC) and Privacera Encryption on Privacera Platform
This topic provides instruction on how to install and configure the Privacera StreamSets plugin for Ranger and Privacera Encryption.
Enable Encryption for SDC
To enable Privacera Encryption for the StreamSets Data Collector (SDC), do the following:
Run the following command:
cd ~/privacera/privacera-manager/config cp sample-vars/vars.crypto.streamset.yml custom-vars/vars.crypto.streamset.yml
Update Privacera Manager:
cd ~/privacera/privacera-manager/ ./privacera-manager.sh update
Configure Encryption for SDC
Copy the StreamSets Privacera package.
If you have StreamSets and Privacera Manager running on different systems, copy the following two files from
~/privacera/privacera-manager/output/streamset/
on the Privacera Manager host machine:privacera-streamset.tar.gz
crypto-config
If you have JCEKS enabled, copy the following file from the location,
~/privacera/privacera-manager/config/keystores/
of the Privacera Manager host machine:cryptoprop.jceks
If you have StreamSets and Privacera Manager running on same system, do the following:
cp ~/privacera/privacera-manager/output/streamset/privacera-streamset.tar.gz ~/privacera/downloads cp -r ~/privacera/privacera-manager/output/streamset/crypto-config ~/privacera/downloads/crypto-config
If you have JCEKS enabled, do the following:
cp ~/privacera/privacera-manager/config/keystores/cryptoprop.jceks ~/privacera/downloads/crypto-config/
Extract the StreamSets Privacera package.
cd ~/privacera/downloads mkdir streamsets tar xfz ~/privacera/downloads/privacera-streamset.tar.gz -C streamsets
Access the StreamSets installation directory as root user.
sudo su
Set the StreamSets installation directory.
export STREAMSET_HOME=/opt/streamset/streamsets-datacollector-3.13.0
Copy the Privacera library into the StreamSets data collector
user-libs
directory:cp -r streamsets/privacera-streamset/ $<STREAMSET_HOME>/user-libs/
Copy the configuration files.
cp -r crypto-config $<STREAMSET_HOME>/../crypto-config
Define a security policy.
cat << EOF >> $<STREAMSET_HOME>/etc/sdc-security.policy grant < permission java.io.FilePermission "/opt/privacera/-", "read"; permission java.io.FilePermission "/opt/streamset/-", "read,write"; permission java.net.SocketPermission "*", "connect,accept,listen,resolve"; >; EOF
Stop StreamSets.
kill -9 $(ps aux | grep 'sdc'| awk '<print $2>')
Restart StreamSets.
ulimit -n 32768 nohup $<STREAMSET_HOME>/bin/streamsets dc &
Verify the logs to make sure that StreamSets is running.
tail -f $<STREAMSET_HOME>/log/sdc.log
Verify StreamSets setup
To verify that Privacera Encryption is now working with the StreamSets Data Collector (SDC), follow these steps:
Configure a sample pipeline to encrypt a local file. You can use the following sample. Import this sample pipeline into StreamSets. For more information, see Sample pipeline.
Access the StreamSets installation directory as root user.
sudo su
Create data directories.
DATA_DIR=/opt/streamset/ cd $<DATA_DIR> mkdir -p customer_data/input mkdir -p customer_data/output mkdir -p customer_data/input_error mkdir -p customer_data/output/encrypted_error
Create a sample data file:
cat << EOF > customer_data/input/customer_data_with_header.csv id,name,ssn,email_address,amount 1,Tamara,898453744,aphillips@vang.info,162454.67 2,Richard,65511350,vreynolds@gmail.com,602.89 3,Tanya,634090950,harringtonwilliam@diaz-king.com,48712.67 4,Richard,829439881,martinvalerie@yahoo.com,5122.02 5,Raymond,227804351,sarachavez@yahoo.com,97963.857 6,Melissa,553465892,kevinwillis@gmail.com,36654.806 7,Deborah,782539839,brittney24@yahoo.com,19.231 8,Rodney,515337130,jenniferkelly@davis-bond.biz,65083.651 9,Katherine,137057143,jperkins@gmail.com,4822.343 10,David,432941241,wmccann@hotmail.com,4069.34 EOF
Create a metadata file to map the input dataset columns to Privacera Encryption schema columns:
cat << EOF > customer_data/customer_data.meta COLUMN_NAME|SCHEME_NAME id| name|SYSTEM_PERSON_NAME ssn|SYSTEM_SSN email_address|SYSTEM_EMAIL amount| EOF
To run the sample pipeline, make sure you have the Privacera user created in your Ranger and it has permissions on the KMS keys starting with pmsk*.
Add permission for keys in Ranger
Log in to the Ranger UI as an administrator and create the Privacera user. You can grant permissions to the Privacera user on keys.
Log in to Ranger with keyadmin credentials and click on
privacera_kms
.Create or update policy for Privacera user.
Run the StreamSets pipeline preview and verify the encrypted value on the right side of the table.