steps I've tried:
I can repeat this with the same result always. If I make a code change so that the CVE is either introduced or removed, the only way I can get prisma cloud to detect it is if I remove the Azure account scope and add it back again. I make no changes in Azure itself (other than re-publishing the code). I've also tried waiting the 24h default scan interval according to docs, but the result is the same.
So what am I missing? Something fundamental about how vulnerability scanning works? Currently I have the sense that there is some bug in the way Prisma Cloud determines that a change has happened in an Azure function, or there is some caching going on which isn't cleared properly when a new scan starts, or there is something about the logic of scans which I don't understand...
ps. we're using an pay-as-you-go license bought through AWS for our testing atm., not sure if that might affect something...
I hope that this note finds you well! I know that it has been a while since you had posted this question but I wanted to see if you still potentially needed any help. Thank you for your time and I hope that you have a good remainder of your day.
J. Avery King
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!