Skip to content

Known Issues in PrivaceraCloud 4.1

PrivaceraCloud Release

Last updated: 2021-12-09

The following are known issues in PrivaceraCloud 4.1 release.

Discovery TagSync does not propagate tags (CLOUD-3838)#

TagSync in the preview feature PrivaceraCloud Discovery does not have the capability to propagate tags for use in access control policies (as Privacera Platform does).

Privacera plans to deliver this functionality as part of our product roadmap.

Restart datasource for deactivated or deleted service (CLOUD-5094)#

When a service in PrivaceraCloud is deactivated or deleted, the associated plugin or datasource application must be restarted because the policies of the deactivated service remain in the dataserver.

Workaround: Restart the datasource of the deleted or deactivated service to refresh the most recent policies from policy cache.

To restart the datasource:

  1. Go to Settings > Datasource.
  2. Click the edit icon next to the datasource.
  3. Select Save.

Scanning large archive files can fail (CLOUD-5055)#

Scanning of large archive files that have a sizable amount of PII might fail if the amount of generated tags is greater than 50KB.

  • CLOUD-5105: A security zone that includes services or tags cannot be deleted.
    Workaround: Before deleting a Security Zone, delete the policy under the tag associated with a Security Zone.

  • CLOUD-3807: Importing of policies works only for active services. If the import JSON file contains policies for deactivated services or services that are not added in Access Manager then the import is not successful.
    Workaround: Fix the import file to remove the definition of the deactivated or non existing services from the JSON file.
    Re-import the corrected import files.

Last update: December 9, 2021