
JOliver168889 (Community Member) asked a question.
We've been trying to figure out why our static scans have gone from a 100% to 76% in the last two days when the code(assemblies) are exactly the same. We have tried experiments where the .zip file pushed and receiving a score of 100% is now getting a 76%. We ran this experiment because we are trying to figure out if newer scans contain different assemblies and are causing the wildly different results. Apparently the same .zip file that received a score of 100% as recently as 1/13/2020 is now getting a 76% even though the package that is statically scanned are identical. We also noticed that the scans which received a score of 100% took ~5 minutes to execute from start to finish but the newer, lower score, scans are now taking anywhere from 11 - 16 minutes. The question I have is whether the static scanner technology has gone through a major revision since 1/13? If not we're hard pressed to explain why the results are so drastically different.
.png)
Hi @JOliver168889 (Community Member)
You can find the release notes for our products in the Veracode Help Center: https://help.veracode.com/reader/0152lUHzdfrlpRBBmxjSSQ/NEvIVi3r1obdkD8PMRxzaA . The latest release for Veracode Static Analysis was done on the 19th of December.
When investigating a difference in results from Veracode Static Analysis we typically recommend the following:
If you have any questions on this please feel free to contact the Veracode Application Security Consulting service either through Veracode Support or through scheduling a consultation: https://help.veracode.com/reader/_xqy2rBkFBfaxzuiNu~wsg/kAO0UeevRvOPnidK6_e5IA .
Thank you,
Boy Baukema