After the scan is started, it may take a long time to scan or the scan may not be completed.
Please check the following possible causes.
■ Cause 1.
The time required for scanning depends on the scanning speed and the type of target site.
Please check the following to see if the scanning time is longer than expected.
How long does it take to scan?
■ Cause 2.
When scanning, a scan is performed for each parameter of the request.
Therefore, the inspection time increases in proportion to the number of parameters.
The number of parameters for each page can be checked by following the procedure below.
[Procedure]
1. Click Scan List > Hamburger Menu > Report Download.
2. Download "Crawl Results List" or "Crawl Results List with Scan Progress" from Report Download.
3. Check the parameters for each page from the "Request body column (J column)" in the file.
Please be aware that pages with many parameters take longer to scan, and please check the causes of the following.
■ Cause 3.
When performing an automatic crawl, similar pages are automatically excluded.
However, depending on the site design, similar pages may be acquired and determined to be scanned.
In such cases, similar pages are scanned, resulting in a larger number of pages and longer scanning time.
If the same page is the target of multiple scans, you can reduce scanning time by excluding these pages from the scanner.
If there are pages that have the same URL and parameter contents, set one of them to be excluded from the scan, and then perform the scan.
To exclude a page from being scanned, click "Page Settings (Scan Target, Memo)" on each page of the screen transition diagram, and change the scan target to OFF.
If many similar pages appear in the screen transition diagram, AeyeScan will automatically exclude similar pages by setting "Scan Basic Options>Exclude Similar Pages" to "Strong" before scanning.
See below for details.
What is the "Exclude Similar Pages"?
■ Cause 4:
In the case of manual crawling, if access to the screen to be scanned fails during scanning, access is performed from the first screen recorded in the manual crawl result and scanning continues.
Therefore, if many screens are recorded in one manual crawl result, the scanning process will take longer.
(e.g., when multiple functions are being operated with one manual crawl result).
If possible, it is recommended to reduce the number of screen transitions by recording the manual crawl result for each function.
■ Cause 5.
Response time from the site being scanned may be longer than the scanning load.
If the response time from the top URL of the target site exceeds 10 seconds, a notification (bell mark in the upper left corner of the screen) The following notification will appear.
The scan for ID:1 is slow due to a slow response from the site.
When accessing the top URL for ID:1, it took more than 10 seconds to respond. Please consider reducing the "Scan Speed" in the "Basic Information" or increasing the specification of your web server. This notification is sent at most once per hour.
If the above is displayed, please consider changing the scan speed or increasing the server specs.
■ Cause 6.
It is possible that the response time is longer for a specific request rather than the entire site.
In this case, please check the scan log to see which specific request is taking longer to respond.
How to obtain the scan log
Go to Scan List > Hamburger Menu > Report Download, and select "Others > Access Log" to obtain the access log.
Note that this method is available only if the "Save Scan Log" checkbox is checked when the scan is created.