Sometimes, users can not use file upload and API Endpoints as verification methods — this is why we also offer manual scan target verification on some occasions.
This article shows Crashtest Security Suite’s Advanced Scan Configuration. Crashtest Security Suite’s crawlers have various intelligent algorithms that aim to reduce the number of pages crawled automatically. These algorithms are necessary and beneficial because, in web applications, there are often views on data for which scanning one example representative view covers the other views.
Insecure network services can be exposed if ports are open on a webserver which is not absolutely necessary. Find out, how you can fix the problem.
This article helps you find the answers to the technical terminology behind our solution.
This article summarises questions users have when first start using Crashtest Security Suite and answers them.
This article collects questions you might ask yourself when using the Crashtest Security Suite and points you in the right direction.
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:
How to get the most out of the Crashtest Security Scan Results?
Our software provides three views to give you the most relevant information on your projects.
For our invasive scanners, you need to confirm that you can access the application – by uploading a text file to the root directory of the URL.
Marking findings in the Crashtest Security suite.
You can find the functionality to mark a detected finding as a False Positive on the last scan page of each scan target. Here you have three options, you can mark your finding as false positive, won’t fix or accept risk.