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
Hi @SJain212272 (Community Member) ,
In general, to reduce the time that Veracode Static Analysis takes to analyze an application it's best to ensure that you reduce as much as possible that which you provide for analysis. Here are some common things for consideration:
If you are introducing Veracode Static Analysis in the CI/CD pipeline I would also highly recommend looking into Pipeline Scans, you can find more information here: https://help.veracode.com/reader/tS9CaFwL4_lbIEWWomsJoA/ovfZGgu96UINQxIuTqRDwg .
It may not always be possible to reduce scan time and preserve a meaningful result. You may need to consider changing your scanning strategy to scan nightly scan if this is not possible.
I would recommend you schedule a consultation call to discuss any questions on this.
You can check out this knowledge article (https://community.veracode.com/s/article/How-to-schedule-a-consultation-call) on how to schedule a consultation call with us.
Thank you,
Boy Baukema