cyoung144894 (Community Member) asked a question.

October 25, 2023 at 12:42 PM
How to Reduce and Optimize Veracode Scan Time

Veracode pipeline-scan is used. Github Marketplace https://github.com/marketplace/actions/veracode-pipeline-scan

 

The Veracode scan took approximately 9-10 minutes. We want to optimize the veracode scan time and get it down to roughly 3-5 minutes. The artifact jar file is approximately 100-150 MB in size.

 

Is there any chance of implementing:

 

  • Is it possible to skip files that have previously been scanned in a previous scan and have had no modifications made to them?

 

  • 1 answer
  • 1.31K views
lucas.ferreira likes this.

  • lucas.ferreira (M3Corp)

    hello @cyoung144894 (Community Member)​ 

     

    Pipeline scan tend to be faster than policy or sandbox scans, but, 90 seconds it's a reasonable time in general. Scans by pipeline scanner can take more than that depending of the size of application and complexity.

     

    • If your application have more than 1 module required to scan (.wars; .jars; js files, etc) you can put the paramater flag "include" and only the modules that you can scan as a value.
    • For compare differences between past results scans, pipeline scan have the baseline that you can configure into your action. image
    • In this link, we have some examples using baseline file scan: https://github.com/marketplace/actions/veracode-pipeline-scan
    Expand Post

Topics (5)

No articles found
Loading

Ask the Community

Get answers, share a use case, discuss your favorite features, or get input from the community.