When you visit any website, it may store or retrieve information on your browser, mostly in the form of cookies. This information might be about you, your preferences or your device and is mostly used to make the site work as you expect it to. The information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies. Click on the different category headings to find out more and change our default settings. However, blocking some types of cookies may impact your experience of the site and the services we are able to offer.
More information
Hello user, I would recommend you contact our technical support team. Here's how you can log a case:
1. Navigate to the upper right corner of any page in the Community, and click on your user avatar.
2. Select Contact Support from the drop-down menu.Please open a support case and provide a detailed explanation of your query to facilitate better assistance from our engineers.
Regards,
Veracode support
Correct, no actions for previous scans if you have a new scan. New scans = current snapshot of the code. Old scan could mean previous version of the code. If someone uses a previous version of the code and doesn't know that the patches weren't already applied to their version but to a later one they would have no idea they are vulnerable, so it is GOOD that you aren't able to 'edit' previous version scans.