FAQ

What is the difference between PrivaceraCloud and Privacera Self-Managed?¶

PrivaceraCloud is a fully managed service that is hosted and managed by Privacera. Privacera Self-Managed is a software that you can install on your own infrastructure. You can read more about the deployment options here.

What does Rolling Release mean?¶

Privacera does rolling releases, which means that new features and bug fixes are released continuously. This allows Privacera to provide new features and fixes to customers as soon as they are ready. In this model, there are all hot fixes and patches are released as soon as they are ready and tested to all the customers. Since these releases are minor, they do not require any downtime and cause minimal disruption to the customers. Another advantage of this model is that CVEs are addressed as soon as they are discovered without waiting for the next major release.

Why are the versions of PrivaceraCloud and Self Managed different?¶

Traditionally PrivaceraCloud gets the latest features and bug fixes first. Once the features are tested and stable, they are backported to the Self Managed version. This is why the versions of PrivaceraCloud and Self Managed are different. With the new rolling release model, the gap between the versions is expected to be reduced and eventually the versions will be in sync.

What are breaking changes?

What are breaking changes¶

Breaking changes are changes that are introduced in a new version of the software that are not backward compatible with previous versions or it requires additional configuration changes or steps to upgrade to the new version. These changes can include changes to the API, configuration, or behavior of the software.

Before upgrading to a newer version, please check any breaking changes () were introduced in prior versions after your current version. If there are breaking changes, you must follow the specific upgrade instructions detailed in the release notes for those versions before upgrading to the latest version.

Example Scenario: If you are currently on version 9.0.1.1 and want to upgrade to 9.0.5.1, and there are breaking changes introduced in 9.0.3.1, you should first upgrade to 9.0.3.1. Ensure all breaking changes are resolved before proceeding to version 9.0.5.1.

graph TD
Start["Current Version (e.g., 9.0.1.1)"] --> Backup["Take Backup of DB & Configs"]
Backup --> |Check for Changes| Check{"Breaking Changes?"}
Check -->|Yes| IntermediateVersion["Upgrade to Intermediate Version (e.g., 9.0.3.1)"]
IntermediateVersion --> Resolve["Resolve Breaking Changes"]
Resolve --> Proceed["Proceed to Latest Version (e.g., 9.0.5.1)"]
Check -->|No| Proceed
Proceed --> Verify["Verify Upgrade"]
Verify --> End["Upgrade Complete"]

How do I upgrade Privacera?¶

Upgrade applies to only Privacera Self-Managed and the Data Plane components of PrivaceraCloud. All the components in PrivaceraCloud are managed by Privacera and are upgraded automatically.

To upgrade Privacera Self-Managed, follow the steps in the Privacera Upgrade Instructions.

What should I do if I forget my password?¶

If you forget your password, you can reset it by clicking the Forgot Password link on the login page. You will receive an email with instructions on how to reset your password. If you do not receive the email, check your spam folder or contact your administrator. You can also contact Privacera support for further assistance.

Who is the owner of the PrivaceraCloud account?¶

The owner of the PrivaceraCloud account is the person who signed up for the account. The owner has full control over the account and can manage users, roles, and policies. If you are the owner of the account and want to change the owner, contact Privacera support for assistance.

How do I change the owner of the PrivaceraCloud account?¶

To change the owner of the PrivaceraCloud account, contact Privacera support for assistance.

Can I switch from Pull Mode to Push Mode in AWS Lake Formation connector?¶

Yes, you can switch from Pull Mode to Push Mode in the AWS Lake Formation connector. You can refer to the documentation for more information.

Why are there different connectors for Databricks?¶

Databricks has multiple products and each behaves differently. You can refer here to the different Databricks Compute Types. Some of the compute are governed by individual workspaces and same could be managed centrally using Unity Catalog. Also Classic SQL warehouses supported limited access control. So for each of these scenarios, Privacera has a different connectors and their behavior is different also. Reference to individual connector documentation for more details.