3 short steps to get started with automated penetration testing: Login, Scan Target Setup, Scan Start

Watch The Demo

Watch this 10 minutes demo guiding you through the basic features Crashtest Security Suite offers.

How to Setup An Account and Your First Scan Target

This guide explains how to set up the Crashtest Security Suite to get you started with automated penetration tests. Our security scanner is designed for a fast setup, and you should be able to run your first scan within 2 minutes. Let us guide you through the process.

Step 1: Log in

To use the Crashtest Security Suite, log in with your user credentials on https://www.crashtest.cloud. You will be automatically redirected to the Create Scan Target page. If you see an empty dashboard, you can always click the Plus Button or Create New Scan Target to create your first scan target.

Crashtest Security Suite Create Scan Target

Step 2: Create a Scan Target

Next, you need to define some general scan target parameters.

Define the Scan Target type

Crashtest Security Suite Define Scan Target Type

First, you can define the type of project that shall be scanned. You can choose between:

  • Multi-Page Application
    A traditional application is written with a server-side programming language. We will cover a multi-page application project in this quick setup.
  • JavaScript Application
    A web application that heavily uses JavaScript as a client language. These are usually web applications that load data asynchronously using AJAX or Single Page Applications (SPAs).
  • Application Programming Interface (API)
    A REST API. For this type of project, you need a Swagger 2.0 or OpenAPI v3 file, which describes the API for proper scanning. Please go to this link for more information on API scanning. If you need any help with the setup, you can always contact our support for specific guidance on your situation.

Define the scan target details

Crashtest Security Suite Define Scan Target Details

Second, you define the basic information of your scan target:

  • Title
    The name of the scan target, which is shown in the dashboard and PDF report
  • Description
    Optional text to better identify your scan target
  • Protocol
    The protocol which will be used to scan your project (i.e., “HTTP” / “https”)
  • URL
    The domain name or IP address of the scan target. The security scanners will run all tests on this URL.

Define Scan Target Scope

Crashtest Security Suite Define Scan Target Scope

Third, you define the scope for the scan you want to run.

  • “Quick Scan”
    This setting ensures that only non-invasive scanners will be executed.
  • “Full Scan”
    This choice executes all security scanners and should only be performed on easily reproducible staging systems with no live customer data.
    Our scanners may damage the tested system. These damages might include, but are not limited to the following list:


    • Sending arbitrary form requests that may pollute databases with random data
    • Creating workload spikes that might impact the user experience of other users when performing multiple requests at the same time (adjustable via “throttle”-setting)
    • Publishing production data (which might contain privacy-sensitive customer data) through altering SQL database requests

For a complete list of all security scanners and an overview under which setting they are used, please refer to our complete list of scanners.

Step 3: Starting the Scan

…And you are almost done! After creating the scan target, it will appear in the scan target list on your dashboard. Now you are ready to start your first scan. Press the “Start” button.

Crashtest Security Suite starting the scan

Alternatively, you can open the scan target page by clicking on the project name and clicking on “Start Scan.”

Crashtest Security Suite Start Scan

If you have feedback of any sort, positive or negative, please write to us.

Happy automated Pentesting!

We hope you found this user guide useful. The next step in your journey to continuous security is to interpret your scan results.


Identify Security Vulnerabilities in Your Web Apps and APIs