Troubleshoot vulnerability detection
Prisma Cloud offers a comprehensive Intelligence Stream for vulnerability management that draws on threat intelligence from commercial providers, the open source community, as well as distinctive vulnerability intelligence curated by Prisma Cloud vulnerability researchers.
Use this troubleshooting section to verify the accuracy of Prisma Cloud scan results, understand the logic behind scan reports, and provide the details requested in the template when you submit a support request for further analysis.
The information in this section will help answer the most common questions related to CVE scan reports –
- Whether a CVE reported by Prisma Cloud is suspected to be a false positive (meaning there is an assumption that the CVE doesn’t exist on a package / image but it displays on the Prisma Cloud Console)
- Whether a CVE in Prisma Cloud is suspected to be a false negative (meaning there is an assumption that a CVE does exist on package / image but it does not display on Prisma Cloud Console)
Before you start with the troubleshooting workflow, check the following prerequisites for accurate scan results.
- Connection to Intelligence Stream is up to date.
- Navigate toManage > System > Intelligence.
- Verify that thestatusisConnected.
After you complete the prerequisite checks, continue to troubleshoot further. The commands below are for Linux distributions but you can use the same process for Windows distributions.
Step 1: Running the image in a container
Whether troubleshooting for a false positive or a false negative scenario, the image should be searched for signs of the given package or file that has been associated with the CVE. Running the image in a container is a good way to proceed. As a best security practice, always run these experiments in a sandbox environment instead of production.
Download the image or load it from a tar on a host protected by a container Defender environment:
docker pull <imagename> OR docker load -i <image.tar>
Instantiate a container from the image:
docker run –rm –detach –name vuln_testing <imagename>
If the image exits immediately, the entrypoint or CMD associated with it most likely doesn’t spawn a long running process. In that case, the docker run command given above can have a command and arguments appended to it overriding the built in directives and ensuring that the container remains up while it is being investigated. For example:
$ docker run –rm –detach –name vuln_testing <imagename> sleep infinity
Step 2: Investigate the Container
Get the ID of the running container then exec into it:
$ docker ps | grep vuln_testing $ docker exec -ti <containerID> /bin/bash
If the bash shell isn’t installed in the image, try alternate shells such as /bin/sh or /bin/ash.
Step 3: Find the Linux distribution of the image
Match the detected OS type in the Console against the listed OS inside running container to ensure that it was correctly identified.
$ cat /etc/os-release
Tip: If the os-release file is not found, look for /etc/redhat-release, /etc/lsb-release, or other files matching /etc/*-release.
Step 4: Locate the package associated with the CVE
Locate the package or file that is associated with the CVE that was listed, or that was not detected despite the expectations. Additionally, confirm the version of the package detected inside the container with the one shown in Prisma Cloud Console or, in case of false negative, which is shown in the other source confirming the CVE.
An easy command to do this is to use find the package in the whole filesystem is:
$ find / -name <package_name>
abc@3f61f8497e23:/# find / -name console /dev/console /sys/devices/virtual/tty/console /sys/class/tty/console
Run the package binary with --version tag if available. You can also search for the version in Console. Go to
Monitor > Vulnerabilities, then click on an image, and select the
abc@3f61f8497e23:/# /usr/bin/wget --version GNU Wget 1.20.3 built on linux-gnu.
Some other ways to find the package, depending on the type of package are -
Get the version from the jar name.
If investigating false positives, find the package path from image details in Console. Select
Monitor > Vulnerabilities > Images, click on the image, and select the
For OS packages, use the OS package manager to find the installed package and version.
For example, you can use the following for RHEL/CentOS/SUSE packages (here searching for the curl package):
Another example for Debian/Ubuntu:
For python packages, you can run the following command in the package path (if already known)
(OR) in the .dist-info directory.
The above steps should help answer whether the vulnerable package exists in the image or not and answer if a CVE is truly false positive. If you found the package and the vulnerable version in image but have questions on the report’s accuracy, you can search the vendor’s official feeds to confirm the source of the CVE report.
1. "I found the package but I’m not sure if it’s truly vulnerable."
Monitor > Vulnerabilities > CVE Viewer, type the CVE ID and verify the source matching OS of your image, or look for the reference with empty Distro and Release if it’s a specific language library.
You can then directly search vendor feeds to confirm CVE’s authenticity. For OS packages, the relevant vendor site should be consulted. For specific language libraries, the site of that project should be visited. The National Vulnerability Database (NVD) should be used for locating CVE information that is not available on official vendor feeds.
Vendor vulnerability data may differ between feeds and NVD analysis. For example, in severity, description or affected versions. Prisma Cloud gives more weight to specific vendor analysis to provide accurate vulnerability data.
Example 1: A vulnerability was determined to be high severity per NVD analysis, but Red Hat Linux analysis determined the vulnerability to be of high severity on RHEL releases. Prisma Cloud should display high severity in this case.
Example 2: A vulnerability was discovered in an open-source package and was fixed in the latest release. NVD analysis mentioned the vulnerability affects all releases earlier than the latest release. At the same time, the vulnerability could be fixed on earlier releases on RHEL, with maintainers having backported the patch to earlier releases of the package for RHEL.
2. "I found the vulnerable package but Prisma Cloud doesn’t show it’s CVE."
When looking into a false negative, it is important to confirm the type of the vulnerability (that is anticipated to be ‘missing’ from scan results), where type equals one of the supported formats that Compute currently detects when interrogating an image.
- package - an OS package, such as an RPM (Red Hat and derived distributions), dpkg/deb (Debian and derived distributions), or apk (Alpine Linux).
- 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, sometimes consisting of zip archives with varying structures and names (eggs, wheels) or plain text files on disk with supporting metadata text files.
- nodejs - a NodeJS library, primarily consisting of text files on disk with supporting metadata text files.
- gem - a Ruby library, consisting of text files on disk with supporting metadata text files.
- go - a Golang binary, which typically contains dependencies that are statically compiled into it. Where most C programs make use of dynamically linked libraries/shared-objects that are present on the host and pulled in at run time, Golang binaries usually have their dependencies embedded within them at compile time.
- app - a binary associated with a well known application, such as Nginx or PostgreSQL.
If it is one of the above supported types yet missing in Prisma Cloud Compute’s scan report, then open a support case and provide the following information so our teams can investigate further.
Submit a Support Request
When submitting a technical support request with Palo Alto Networks, provide the following information to help our teams identify the root cause more quickly. This information is required to review escalations.
- Debug logs: Provide full debug logs throughManage > System > View Logs > Upload / Download Debug logs. You can also use twistcli to upload logs:$ ./linux/twistcli support upload --help
Image details: If the issue is in a container image, provide the affected container image (image.tar). You may also check if the image can be downloaded from Docker Hub and share a link to pull the image. Always validate the Image ID SHA to ensure it’s the same image. If you are unable to share the image, please provide an image where the issue reproduces that we can analyse.Scan discrepancy report sheet: Ensure you have a spreadsheet with following columns info filled out from your prior analysis.CVE IDPackage TypePackage NamePackage VersionPath where package is found in imageCVE Reported in Console? Yes/NoCVE Reported by any other vendor/source?Your explanation/commentsExample: CVE-2021-38297OSgnutls283.6.7-4+deb10u5/usr/bin/gnutlsYes. Suspect it to be a false positiveI don’t believe this CVE should be reported for this version of package because I don’t see version in NVD.
- The debug log option is only available on self-hosted Consoles. In the event that you have a SaaS Console, gather the console.log (fromManage > System > View Logs) and the defender.log (under /var/lib/twistlock/log directory on host) from the host where the image was first scanned.
Frequently Asked Questions
I see a CVE in the scan, but it does not appear on NVD or is still under analysis. What is the information I’m seeing?
When a CVE is assigned to a vulnerability, usually NVD analysis takes place, and it may take multiple days for the NVD site to update with description and the affected releases range. Instead of waiting for the official analysis to complete, our researchers manually review the details of the CVE and add it as a pre-filled CVE to our Intelligence Stream, so you can know you are vulnerable and mitigate the vulnerability before the official analysis is done. See the Prisma Cloud vulnerability feed doc for more information.
What are PRISMA-* vulnerabilities?
Our researchers assign a PRISMA-* identifier for vulnerabilities that lack a CVE ID. Many vulnerabilities are publicly discussed or patched without a CVE ever being assigned to them. Our researchers find those vulnerabilities, analyse them and assign a PRISMA ID whenever applicable, so you can know what you need to be aware of. See the Prisma Cloud vulnerability feed doc for more information.
I see CVEs with Fix status “affected”. What are these? Are they false positives?
CVEs with the status “affected” are CVEs that don’t have a fix yet, and the vendor marked them as affecting the current OS release. Some other vulnerability scanners don’t show them, but these are not false positives. You can also decide not to show vulnerabilities with no fix - go to Defend > Vulnerabilities > edit your desired rule > Advanced settings > turn on the toggle “Apply rule when vendor fixes are available”.
I see a lot of low severity CVEs. What are these? Are they false positives?
You can decide if you want to see vulnerabilities that have negligible severity or “will not fix” status. These CVEs have already been reviewed by the vendor and are not going to be fixed. Although they are not truly false positives, Prisma Cloud Compute doesn’t show these CVEs by default, since the vendor decided a fix is not necessary. You can change this configuration - go to
Manage > System > Scan > Unactionable vulnerabilities.
Where do you take CVE information such as severity and fixed version from?
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 taken from the specific vendor feed. For other CVEs, the information is taken from official sources like NVD and vendor specific Security Advisories. For new vulnerabilities missing analysis or undocumented vulnerabilities (such as PRISMA-IDs), we rely on severity determined by our researchers.
I see on the Red Hat security page that a CVE affects my OS release, but it doesn’t show up in Prisma’s scan. What happened?
Our Intelligence stream is drawing CVE information from Red Hat API - using OVAL v2 streams. While the HTML CVE page is already updated, there could be a delay in the API update.
Why does Prisma Cloud show more vulnerabilities than what I see in the Red Hat catalog?
The Red Hat Container Health Index analysis is based on RPM packages signed and created by Red Hat, and does not grade other software that may be included in a container image. Thus, non-OS vulnerabilities like jar, python, etc., will not be listed on Red Hat Catalog. Furthermore, the Red Hat catalog only shows CVEs that have a fix, meaning there is a security advisory with the fix. “Affected” CVEs (see above) don’t have a fix, and they won’t appear in the Red Hat catalog.
What is the “Published Date” in Console?
Published date is the date that the CVE was published by the vendor / project or by NVD. This information is taken from the relevant feed - either the vendor feed or NVD. Please note that 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.
What is the “Fix Date” in Console?
Fix date is the date the vulnerability data was fixed by the vendor. When we can’t find the relevant fix date in the official feeds, the published date in NVD is considered as the fix date.
A new vulnerability is affecting Compute - what should I do?
If the vulnerability affects Compute that has not yet been addressed, please report it through support channels or to PSIRT.
A CVE exists in NVD but I don’t see it in the CVE viewer, what should I do?
If you believe a CVE that was fully analysed by NVD is missing from our feeds, please report it through the support channels.