- 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
Azure
Azure ADLS Data Server
This topic covers integration of Azure Data Lake Storage (ADLS) with the Privacera Platform using Privacera Data Access Server.
Prerequisites
Ensure that the following prerequisites are met:
You have access to an Azure Storage account along with required credentials.
For more information on how to set up an Azure storage account, refer to Azure Storage Account Creation.
Get the values for the following Azure properties: Application (client) ID, Client secrets
CLI Configuration
Go to the privacera-manager folder in your virtual machine. Open the config folder, copy the sample vars.dataserver.azure.yml file to the custom-vars/ folder, and edit it.
cd ~/privacera/privacera-manager cp config/sample-vars/vars.dataserver.azure.yml config/custom-vars/ vi custom-vars/vars.dataserver.azure.yml
Edit the Azure-related information. For property details and description, click here.
If you want to use Azure CLI, use the following properties:
ENABLE_AZURE_CLI: "true" AZURE_GEN2_SHARED_KEY_AUTH: "true" AZURE_ACCOUNT_NAME: "<PLEASE_CHANGE>" AZURE_SHARED_KEY: "<PLEASE_CHANGE>"
If you want to access multiple Azure storage accounts with shared key authentication, use the following properties:
AZURE_GEN2_SHARED_KEY_AUTH: "true" AZURE_ACCT_SHARED_KEY_PAIRS: "<PLEASE_CHANGE>"
Note
Configuring
AZURE_GEN2_SHARED_KEY_AUTH
property allows you to access the resources in the Azure accounts only through the File Explorer in Privacera Portal.If you want to access multiple azure storage accounts with OAuth application based authentication, use the following property:
AZURE_GEN2_SHARED_KEY_AUTH: "false" AZURE_TENANTID: "<PLEASE_CHANGE>" AZURE_SUBSCRIPTION_ID: "<PLEASE_CHANGE>" AZURE_RESOURCE_GROUP: "<PLEASE_CHANGE>" DATASERVER_AZURE_APP_CLIENT_CONFIG_LIST: - index: 0 clientId: "<PLEASE_CHANGE>" clientSecret: "<PLEASE_CHANGE>" storageAccName: "<PLEASE_CHANGE>"
Note
Configuring
AZURE_GEN2_SHARED_KEY_AUTH
property allows you to access the resources in the Azure accounts only through the File Explorer in Privacera Portal.Note
You can also add custom properties that are not included by default. See Dataserver.
Run the following command.
cd ~/privacera/privacera-manager ./privacera-manager.sh update
Configuration Properties
Property Name | Description | Example |
---|---|---|
ENABLE_AZURE_CLI | Uncomment to use Azure CLI. The | true |
AZURE_GEN2_SHARED_KEY_AUTH | For To use multiple Azure storage accounts with shared key authentication, then set this property to To use multiple Azure storage accounts with OAuth authentication, then set this property to | true |
AZURE_ACCOUNT_NAME | Azure ADLS storage account name | company-qa-dept |
AZURE_SHARED_KEY | Azure ADLS storage account shared access key | =0Ty4br:2BIasz>rXm{cqtP8hA;7|TgZZZuTHJTg40z8E5z4UJ':roeJy=d7*/W" |
AZURE_ACCT_SHARED_KEY_PAIRS | Comma-separated multiple storage account names and its shared keys. The format must be ${storage_account_name_1}:${secret_key_1},${storage_account_name_2}:${secret_key_2} | accA:sharedKeyA, accB:sharedKeyB |
AZURE_TENANTID | To get the value for this property, Go to Azure portal > Azure Active Directory > Propertie > Tenant ID | 5a5cxxx-xxxx-xxxx-xxxx-c3172b33xxxx |
AZURE_APP_CLIENT_ID | Get the value by following the Pre-requisites section above. | 8c08xxxx-xxxx-xxxx-xxxx-6w0c95v0xxxx |
AZURE_SUBSCRIPTION_ID | To get the value for this property, Go to Azure portal > Select Subscriptions in the left sidebar > Select whichever subscription is needed > Click on overview > Copy the Subscription ID | 27e8xxxx-xxxx-xxxx-xxxx-c716258wxxxx |
AZURE_RESOURCE_GROUP | To get the value for this property, Go to Azure portal > Storage accounts > Select the storage account you want to configure >Click on Overview > Resource Group | privacera |
DATASERVER_AZURE_APP_CLIENT_CONFIG_LIST: - index: 0 clientId: "<PLEASE_CHANGE>" clientSecret: "<PLEASE_CHANGE>" storageAccName: "<PLEASE_CHANGE>" | Configure multiple OAuth Azure applications and the storage accounts mapped with the configured client id. **Note**: The ‘clientSecret’ property must be in BASE64 format in the YAML file. | DATASERVER_AZURE_APP_CLIENT_CONFIG_LIST: - index: 0 clientId: "8c08xxxx-xxxx-xxxx-xxxx-6w0c95v0xxxx" clientSecret: "WncwSaMpleRZ1ZoLThJYWpZd3YzMkFJNEljZGdVN0FfVAo=" storageAccName: "storageAccA,storageAccB" - index: 1 clientId: "5d37xxxx-xxxx-xxxx-xxxx-7z0cu7e0xxxx" clientSecret: "ZncwSaMpleRZ1ZoLThJYWpZd3YzMkFJNEljZGdVN0FfVAo=" storageAccName: "storageAccC" |
Validation
All-access or attempted access (Allowed and Denied) for Azure ADLS resources will now be recorded to the audit stream. This Audit stream can be reviewed in the Audit page of the Privacera Access Manager. Default access for a data repository is 'Denied' so all data access will be denied.
To verify Privacera Data Management control, perform the following steps:
Login to Privacera Portal, as a portal administrator, open Data Inventory: Data Explorer, and attempt to view the targeted ADLS files or folders. The data will be hidden and a Denied status will be registered in the Audit page.
In Privacera Portal, open Access Management: Resource Policies. Open System 'ADLS' and 'application' (data repository) 'privacera_adls'. Create or modify an access policy to allow access to some or all of your ADLS storage.
Return to Data Inventory: Data Explorer and re-attempt to view the data as allowed by your new policy or policy change. Repeat step 1.
You should be able to view files or folders in the account, and an Allowed status will be registered in the Audit page.
To check the log in the Audit page in Privacera Portal, perform the following steps:
On the Privacera Portal page, expand Access Management and click the Auditfrom the left menu.
The Audit page will be displayed with Ranger Audit details.