topic Re: compute vulnerability results not updating in Prisma Cloud Discussions

compute vulnerability results not updating

Retired Member — Mon, 07 Feb 2022 23:23:27 GMT

Based upon the vulnerabilities reported by Compute in my Lambda function, I updated the urllib3 library in my Python3.7 function to the latest version (1.25.8), but rescanning my function still shows the old library (1.25.7). Does anyone know how I can resolve this? the function should now no longer show any vulnerabilities for urllib3, and should definitely no longer in it's inventory state it uses urllib3 v1.25.7...

Re: compute vulnerability results not updating

PBowden — Tue, 28 Apr 2020 18:11:49 GMT

Hi Johan,

Please review the following hyperlink for directions pertaining to performing a manual scan of your function using twistcli. In my experience this will update your results as expected in the console.

"You can also use the twistcli command line utility to scan your serverless functions. First download your serverless function as a ZIP file, then run: Scan reports can viewed in Prisma Cloud Console, but only when you pass the --ci and the --publish flag to twistcli.
These flags are designed to minimize clutter in the Console UI, since many people might be using`twistcli` for scanning, but everyone will need to share it with the larger team in Console. To view scan reports in Console, go to Monitor > Vulnerabilities > Functions > CI or Monitor > Compliance > Functions > CI.
$ twistcli serverless scan <SERVERLESS_FUNCTION.ZIP>"

https://docs.paloaltonetworks.com/prisma/prisma-cloud/prisma-cloud-admin-compute/vulnerability_management/serverless_functions.html

Thanks

Patrick

Re: compute vulnerability results not updating

Retired Member — Wed, 29 Apr 2020 11:24:58 GMT

Thanks for the suggestion, though I am still wondering why a "scan now" button doesn't automatically update the results...

Re: compute vulnerability results not updating

PBowden — Wed, 29 Apr 2020 19:44:35 GMT

Hi Johan,

Have you recently upgraded? Any changes to note? As explained to me, twistcli scans are different from what takes place when the "scan now" button is used. Specifically, I've seen this before, after an upgrade. Glad to be of assistance.

Patrick