Prisma detecting CVEs when pulled but not during scan job in CI

cancel
Showing results for 
Search instead for 
Did you mean: 

Prisma detecting CVEs when pulled but not during scan job in CI

L0 Member

So, I'm basically pulling the base images of the certain OS,  and hardening them to reload onto another registry. When I pull the image and harden and push, under CI Scans of (Gitlab) of my pipeline. I don't get any CVEs. But when I pull the same image which I pushed to the last registry and run the ci scan with only a docker file which contains only 

`FROM (hardened-image)` I'm getting vulnerabilities, I do not understand what is happening and why it is happening, can someone help me?

 

1 REPLY 1

L0 Member

Could you be running into a tagging issue? Are you pushing hardened-image:$build-id and then pulling latest? Curious to know what you found out or how you resolved this!

Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

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!