Advanced features for continuous security testing

This article explains the advanced functionalities of the Crashtest Security Suite and how to earn the sweet fruits of automated pentesting in agile development processes.

In the project preferences, you can configure in-depth settings for further fine-tuning your security scan. Especially the automation part is where you can use our software to the fullest extent and get started on your continuous security testing journey (also referred to as "DevSevOps"). 


If your system is protected by authentication, you can specify the needed authentication to access the system.


Screenshot 2020-04-02 at 16.09.59


System authentication: If HTTP basic authentication (.htaccess protection) is enabled, configure the credentials here.

Application authentication: If your application has a login form, you may add credentials here. This only works for Multi-Page Applications.


Screenshot 2020-04-02 at 14.55.27

Parameter authentication: This setting allows you to configure HTTP headers, GET parameters, or (session) cookies for authentication. Please check out this wiki article if you want more guidance on setting up an API for scans.

Our advanced authentication article describes more advanced authentication flows such as SAML or OAuth2.


This setting is where you reap the benefits of automated pentesting - starting a security scan automatically by time or event.


Screenshot 2020-04-02 at 15.47.17


Scheduled Scan: Configure a daily or weekly schedule so that your scans are started automatically at a particular time, day or week. Just follow the steps shown in the video below:



Webhook: Create a webhook so your build system can start a security scan automatically based on your needs. Following these steps, you can easily integrate it into your CI/CD pipeline.


Screenshot 2020-04-02 at 15.47.48


Enter a Slack webhook so that we notify you every time a scan has finished. More information on the creation of Slack webhooks can be found here.


Screenshot 2020-04-02 at 14.58.53

Crawler Mode & Throttling


Screenshot 2020-04-02 at 15.44.57-1


Crawling method
Adjust the crawler mode to define whether the smart crawling should try to detect forms that appear on multiple sites and only scan them once to reduce the scan duration.
You can choose between the following crawling methods:

  • The Smart Crawling mode tries to detect forms that appear on multiple sites (e.g., a search form) and only scans them once to reduce the scan duration. Depending on the implementation of your web application, this might reduce the scan coverage if an identical form appears on multiple sites but is processed differently. Please choose the exhaustive crawling if this is the case.
  • The Exhaustive Crawling mode scans each detected form for vulnerabilities. Therefore forms appearing on multiple sites are scanned each time individually. This might significantly increase the scan duration but can increase the detection rate.

Adjust the throttling threshold to limit the maximum number of requests per second sent to scan your server. Please consider that the threshold influences the scan duration and that certain scanners require a minimum threshold.