aleks_jk (Community Member) asked a question.

When the Veracode sandbox expires why all earlier scan results are wiped out and then the next new scan is stuck at Module Selection in Veracode?

We have an Azure pipeline setup to run on monthly basis, but when the Veracode sandbox expires (90 days after it is created) all earlier scan results are wiped out, Veracode automatically creates a new empty sandbox, but the next new scan is stuck at Module Selection phase in Veracode.

So, first issue is why the earlier scan results are wiped out? We have monthly scans for our app, which means at least one scan result should always be there and should not be a problem for pipelines to run on a monthly basis.

The second issue is why it is stuck at Module Selection phase? We need our pipelines to have no manual intervention. Is there an option to set module required option from automation?


  • Hello @aleks_jk (Community Member)​ ,

     

    There are 2 Sandbox data retention modes.

     

    Time-To-Live Mode:

    In this mode, Veracode automatically sets an expiration date for development sandboxes when you create them. By default, Veracode sets the expiration date to 90 days after the sandbox creation date. (From what you described this is what you are currently using for a Sandbox.)

     

    Or

     

    Rolling-Histories Mode:

    This mode preserves the last 15 scans you have prepared, on a rolling basis. The first scan in the sequence is the first scan to retire from your results after 15 scans have run. The sandbox itself never expires.

     

    For more information in selecting the Sandbox that works for you, I would suggest reviewing the link from the Help Center on Sandbox selections:

    https://docs.veracode.com/r/About_Sandbox_Data_Retention

     

    After reviewing what Sandbox option that works for you, you can work with your Administrator of selections and or setup.

     

    The second question:  why it is stuck at the Module Selection phase? We need our pipelines to have no manual intervention. Is there an option to set the module required option from automation?

     

    For module selection:

    After pre-scan is completed you have the option to select the modules for scanning, or you can select and enable the Auto-Scan option to skip this step. This step is outlined in the link below.

     

    https://docs.veracode.com/r/Request_the_Static_Scan_and_Configure_Scan_Options

     

    Kind regards,

    Steven

    Veracode Support Engineer

     

     

     

    Expand Post

Topics (3)

No articles found
Loading

Ask the Community

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