Prisma™ Cloud Known Issues
Review the list of known issues and deprecation notice on Prisma Cloud.
The following table lists the known issues on Prisma Cloud. For deprecation notices or upcoming changes, see Look Ahead - Planned Updates.
Dashboard widgets don't load for a large data set where the time window is also large.
aws-emr-describe-clusterAPIs now run once every 24 hours to generate alerts. If you have cloud accounts with a significant amount of ECS/EMR resources, the resource status is updated once a day.
Fixed in 21.6.1
Due to the GCP Terraform v0.15.3 upgrade an error occurred after the creation of a resource. The error stated that you cannot print sensitive data like service account to the console.
With this fix, credentials are now saved to a JSON file instead of displaying in a console.
On occasion, when you edit a GCP cloud account to include or exclude projects for monitoring, the changes to your cloud account are not saved because the API flow control limit is reached.
Ingestion Enabled. After an hour, edit the account and enable ingestion (toggle
Due to performance challenges with Azure Resource Groups, the auto completion using RQL on the
Investigatepage, is temporarily paused until we address the issue.When you use
azure.resource.groupas an attribute in your query, for example,
config from cloud.resource where azure.resource.group =, you will only see the option to enter a string.
The RQL continues to work as expected and any existing policy or saved search that uses the
azure.resource.groupattribute is not affected.
Alerts generated for policies that reference the
azure-disk-listAPI are resolved and reopened intermittently.
Applies to Prisma Cloud Data Security onlyMalware report is not available in PDF format.
Applies to Prisma Cloud Data Security onlyThe Dashboard displays an error when you select an account group that does not contain any accounts.
When you add a GCP Organization that includes folders on Prisma Cloud, the error
Load more folders in nested-2displays when you have an empty folder that does not include projects.
The Business Unit Report does not support multi-byte characters used in languages such as Japanese.
The Business Unit Report csv file lists all enabled policies even when there are no open alerts, because there are no resources to scan.
When you enable Dataflow compression for a cloud account, the subnetwork creation status may display a failure message on the onboarding status page. This error displays because the time threshold to create the subnetwork and report completion exceeds the response time threshold on Prisma Cloud.
Workaround—Click to the previous page and click next to load the status page again.
If you have the maximum number of VPCs (5) already created in the project and then you enable flowlog compression, the onboarding fails because Prisma Cloud is unable to add the network needed to enable Dataflow compression. When this happens the remediation steps in the message that displays is incorrect.
The integration status check for Jira displays as yellow instead of red even if the integration is misconfigured.
Recommended For You
Recommended videos not found.