What input does the system need?

The first information needed by hyperscan is the initial URL where the crawling should commence, plus the authentication details for accessing your Web application.

You also need to specify:

• which vulnerabilities your Web application should be scanned for (scan policy)
• which standard should be used to structure the reports which will be generated, and to whom they should be sent
• the times when the scans will be running

In the next step, hyperscan itself determines the directory and file structure of your Web application (crawling). 

You can check the results and, if necessary, add something to them. In doing so, you can use a recorder function and simply access the missing pages in a Web browser.

hyperscan draws the signatures for the scan process from a signature database that is regularly updated. You can also create your own signatures if you wish.

What output do you get?

• To all responsible persons a personalised report will be sent in PDF format
• You can monitor the chronological development of your Web application's susceptibility to attacks on the dashboard
• You get executive summaries and statistics plus detailed information about every vulnerability found
• You have the option of sending the found vulnerabilities to the hyperguard Web application firewall so that hyperguard automatically protects your Web application from the vulnerabilities found