PRISMA-* IDs

PRISMA-* ID Syntax

Investigating PRISMA-* Vulnerabilities

Supported Packages and Languages

Package
- supported Operating Systems packages, such as an RPM (Red Hat and derived distributions), dpkg/deb (Debian and derived distributions), or apk (Alpine Linux). RedHat non-RPM artifacts which are layered, containerized products such as OpenShift.
Jar
- the Java Archive format, which is a zip file with a standard structure. The war file format, or web app archive, is also supported.
Python
- a Python library.
Nodejs
- a Node.js library.
Gem
- a Ruby gem library.
Go
- a GoLang library.
App
- a binary associated with a well-known application, such as Nginx or PostgreSQL.

Prisma ID FAQs

Why use PRISMA-IDs?
We are committed to ensuring that the Prisma Cloud Intelligence Stream provides the most accurate and up-to-date vulnerability information.
Through the Intelligence Stream, Prisma Cloud should be able to alert on any relevant vulnerabilities that exist in scanned environments, regardless of having a CVE or not. Our researchers monitor open-source code repositories continuously to detect publicly discussed but undisclosed vulnerabilities that are not tracked under a CVE record. Upon finding such a vulnerability, the researchers complete a full analysis of the vulnerability including assessing its severity and describing its impact, and finally assign a PRISMA ID. The Intelligence Stream is shortly thereafter updated with the new entry, and users immediately benefit from the detection of the vulnerability by Prisma Cloud.
This process allows Prisma Cloud users to be better informed and secure from vulnerabilities that are otherwise not detected by regular vulnerability management tools.
Why not wait for a CVE-ID?
Although most vulnerabilities in open-source are assigned CVEs quickly after being discovered, some vulnerabilities are not assigned a CVE for various reasons. In some cases, maintainers are unaware of the process to assign CVEs, ignorant of the importance of having a CVE, or may even refuse to have CVE IDs assigned to their projects.
Prisma Cloud researchers actively encourage all maintainers to assign CVE IDs to security vulnerabilities in their projects. We partner with NVD and MITRE to ensure that information regarding known vulnerabilities is public and available to everyone in the industry. PRISMA IDs are not meant to be a replacement for CVEs – PRISMA IDs are assigned to ensure our users are protected from any known threat regardless of whether a CVE was assigned to it or not.
Palo Alto Networks is a CVE Numbering Authorities (CNA); we assign CVE IDs to any zero-day vulnerability we discover. The purpose of PRISMA IDs is to track vulnerabilities that were already in public knowledge at the time we identified them, but were not tracked under a CVE ID.
Why not all PRISMA-IDs get assigned with a CVE ID?
As mentioned above, although we do encourage all maintainers to assign CVEs to the vulnerabilities found in their projects, we keep seeing a lot of undisclosed vulnerabilities that are publicly discussed. We would be happy to see all PRISMA IDs be replaced with a CVE ID, however, we do have limited resources - and simply cannot assign a CVE for each vulnerability. For zero-day vulnerabilities found by our research team, we follow the responsible disclosure process and ask the vendor to assign a CVE or offer the assistance of Palo Alto Networks as a CNA.
Can PRISMA-IDs be found on NVD or MITRE?
Public vulnerabilities identified by our researchers, before a CVE is associated with them, are assigned a PRISMA-* identifier. You may access the reference link to get more information about the source through which our researchers discovered the vulnerability.
Do you have a way to correlate PRISMA-ID to CVE when it is assigned a CVE?
Through an ongoing maintenance process, PRISMA-IDs are replaced with a corresponding CVE ID when it is created.
PRISMA-XXXX disappeared, what happened?
When a vulnerability with a Prisma ID is assigned a CVE ID, the PRISMA ID is replaced with the new CVE. Findings will display the official CVE ID instead.
What is the "Published Date" in Console?
The Published date is the date that the CVE was published by the feed source or by NVD. This information is taken from the relevant feed - either the vendor feed or NVD.
The date a CVE is published in NVD is not the date it was analyzed. The CVE can be published in NVD and only later updated with the analysis.
Why do I see a newly added CVE with an old published/fixed date?
The Published Date of the CVE is the date when the vendor published it first. The CVE may have been added to the IS after the published date because the feed is constantly updated.
When a PRISMA ID or a Pre-Filled CVE is replaced with a CVE entry from NVD or a vendor’s feed, the
Published Date
of the CVE will reflect what was published in the official CVE.
I have set a grace period and my builds were passing. Now “all of a sudden” they fail on a CVE/PRISMA ID that wasn’t there before. What happened?
See the answer above.
The severity assigned to a vulnerability is different between the IS and NVD, how is that possible?
For known vulnerabilities with a CVE, we rely on the most authoritative source. For OS packages (packages that are maintained by the OS vendor, marked as type "package" in Compute), the CVE details are from the specific vendor feed. For other CVEs, the information is from official sources like NVD and vendor-specific security advisories. If the affected package is maintained by an OS vendor, the severity as indicated by the vendor is used and not the severity determined by NVD. Furthermore, for new vulnerabilities missing analysis, or undocumented vulnerabilities (such as PRISMA-IDs), we rely on severity determined by our researchers.
How do I check if my Intelligence Stream is up to date?
Navigate to
Manage > System > Intelligence
.
Verify that the Status is
Connected
.
Check the
Last streams update
.
How can I know which OS releases are supported?
Prisma Cloud can protect containers built on nearly any base layer operating system. We update our feed with the vendor’s data only for supported versions. CVE information is provided for the base layers detailed in the system requirements for all versions except EOL versions. While our feed could still contain vulnerability data for EOL versions, it is not complete and is potentially inaccurate because of missing details on the vulnerability. If there are no vulnerabilities in our feed for a specific distro release, the version will be tagged with the following message:
OS not supported and may be missing vulnerability data. Please use a supported version of the OS.
Does the Intelligence Stream include CVE information for EOL versions?
See the answer above.
I have seen an open CVE/PRISMA vulnerability that I believe has a fix. What should I do?
The IS uses the automated maintenance process for any updates to existing vulnerabilities. If you believe new information regarding a vulnerability is missing from our feed, please report it through the support channels.
Where can I find more information on troubleshooting?
See the Troubleshooting section.