- 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
- PolicySync
- Snowflake
- Redshift
- Redshift Spectrum
- PostgreSQL
- Microsoft SQL Server
- Databricks SQL
- RocksDB
- Google BigQuery
- Power BI
- UserSync
- Privacera Plugin
- Databricks
- Spark standalone
- Spark on EKS
- Trino Open Source
- Dremio
- AWS EMR
- AWS EMR with Native Apache Ranger
- GCP Dataproc
- Starburst Enterprise
- Privacera services (Data Assets)
- Audit Fluentd
- Grafana
- Access Request Manager (ARM)
- 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
- CLI actions
- Debugging and logging
- Advanced service configuration
- Increase Privacera portal timeout for large requests
- Order of precedence in PolicySync filter
- Configure system properties
- PolicySync
- Databricks
- Table properties
- Upgrade Privacera Manager
- Troubleshooting
- 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
-
- Possible Errors and Solutions in Privacera Manager
- 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
- Example Workflow Usage
- Discovery health check
- Reports
- Built-in Reports
- Saved reports
- Offline reports
- Reports with the query builder
- How-to
- Privacera Encryption Guide
- Essential Privacera Encryption terminology
- Install Privacera Encryption
- Encryption Key Management
- Schemes
- Scheme Policies
- Encryption Schemes
- Presentation Schemes
- Masking schemes
- Encryption formats, algorithms, and scopes
- Deprecated encryption formats, algorithms, and scopes
- Encryption with PEG REST API
- PEG REST API on Privacera Platform
- PEG API Endpoint
- Encryption Endpoint Summary for Privacera Platform
- Authentication Methods on Privacera Platform
- Anatomy of the /protect API Endpoint on Privacera Platform
- About Constructing the datalist for protect
- About Deconstructing the datalist for unprotect
- Example of Data Transformation with /unprotect and Presentation Scheme
- Example PEG API endpoints
- /unprotect with masking scheme
- REST API Response Partial Success on Bulk Operations
- Audit Details for PEG REST API Accesses
- REST API Reference
- Make calls on behalf of another user
- Troubleshoot REST API Issues on Privacera Platform
- PEG REST API on Privacera Platform
- Encryption with Databricks, Hive, Streamsets, Trino
- Databricks UDFs for encryption and masking
- Hive UDFs
- Streamsets
- Trino UDFs
- 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
- Request Access
- Approve access requests
- Service Explorer
- User/Groups/Roles
- Permissions
- Reports
- Audit
- Security Zone
- Access Control using APIs
- AWS User Guide
- Overview of Privacera on AWS
- Set 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
- S3 browser
- Getting started with Minio
- Plugins
- How to Get Support
- Coordinated Vulnerability Disclosure (CVD) Program of Privacera
- Shared Security Model
- Privacera documentation changelog
How to Get Support
Contact Technical Support if you need assistance with a Privacera product.
Privacera support is available as follows:
Use the Privacera Support Portal to log a ticket (registration required).
Call 1-888-768-9054 (toll free) or 1-510-751-1852 (international).
Log on to Zendesk site.
Use the Privacera Support Portal (account required)
Set up a Privacera Support Portal Account
Request an account by calling Privacera or by emailing support@privacera.com.
You will receive an email invitation from Zendesk.
Follow the instructions in the email to create your account.
Note your login credentials and bookmark the login page.
Create Tickets
From the Privacera Support portal home page, click Submit a request.
The Submit a request page displays.
Enter the ticket information. Fields are required unless otherwise noted.
Privacera Deployment Platform - Select your environment from the list.
Privacera Version - The software version running on your system.
Ticket Severity - Describes the impact of the issue.
Severity 1 (Urgent) - Critical application or service functionality is no longer operational. No workaround identified. (Applies to Production installations only.)
Severity 2 (High) - Critical application or service functionality semi-operational but impact is business-critical. May or may not have a workaround.
Severity 3 (Normal) - Other problems including user interface assistance, configuration assistance, deployment assistance, and application upgrades.
Severity 4 (Low) - Low-risk issues or requests for information. Doesn't impact the business.
Click Submit.
The system sends a status update by email when you create a ticket and when Privacera Support updates it.
View Your Tickets
On the portal home page, click your user name and select My activities form the list.
In addition to the fields used to create the ticket, you will see:
Id - The system-generated ticket number.
Status - The state that the ticket is in.
Support Assignee: The support engineer assigned to work on your ticket.
Priority: Mapped to ticket severity as follows:
Urgent: S1.
High: S2.
Normal: S3.
Low: S3.
Support Ticket Lifecycle
A ticket moves through these phases:
New: Initial state when you create a ticket.
Open: A support agent is assigned to the ticket.
awaiting your reply: The agent is waiting for more information from you.
Solved: The agent has resolved the issue.
Closed: Seven days after a ticket is set to Solved, the user can no longer update or post new comments but there will be a link to create a followup ticket if needed.
PrivaceraCloud Support
PrivaceraCloud Support is available for registered customers in a number of ways, via email, phone, and permitted remote access.
Permitted Remote Access
This feature enables Privacera Support to provide support by accessing your account as an authorized user. Remote support will have the same role as the authorizing user.
Unless otherwise requested, Privacera Support will not view or access information in individual accounts and does not have rights or access to log on to PrivaceraCloud account.
In some cases, however, its useful to allow access by Privacera Support in order to assist with configuration changes or to access and assist with policy definitions. For those purposes, PrivaceraCloud account administrators may request and enable time-limited remote access by Privacera Support. Authorization is token based and the token is limited to 24 hours and can be revoked by the authorizing user at any point prior to the 24 hour limit.
The access functions as an impersonation, so that the PrivaceraCloud Support login sees exactly what the authorizing user sees.
Setting this up is a multi-step process. To initiate this support, contact Privacera Support. You will be providing with a time-limited token, so coordinate with them in advance.
Steps:
Open the username menu (upper right navigation bar).
Under "Need Help?", click on "Contact Privacera Support".
That will open the Contact Privacera Support dialog, with a large GENERATE TOKEN FOR PRIVACERA SUPPORT button. Click this button.
The dialog will update and display a six digit support token. Provide this value to Privacera Support by secure methods (phone or encrypted text message).
The username menu will update to reflect that a support token is active, along with two new options: "Terminate" and Show Token List. (Show Token List will be added to this menu after the first use of Contact Privacera Support).
You may use Terminate at any point while the support token is active, to revoke its use.
You may also open Show Token List at any point. It will display a list of active and inactive tokens. You may also revoke any active tokens from this list.