Burp community forum

How to limit duration of the scan and check it's effectiveness?

Thomas | Last updated: Jul 31, 2019 09:11AM UTC

Hi, is it possible to limit the duration of a scan and to check of the scan was able to connect to the right system? Right now some of our scans were running for weeks, the longest for 82 days. It was not obvious if the scan was really able to connect successfully as there was no reported output which is already a bit strange. So we had to cancel it at a certain point. Is there any configuration option to tell the scanner to stop after e.g. a couple of hours? Is there any option to see wether the scanner was able to really communicate with the right system and did chase it's tail by following some proxy or authentication redirects for days?

Burp User | Last updated: Jul 31, 2019 09:12AM UTC

Sorry I forgot to add, this is about Burp Enterprise

Liam, PortSwigger Agent | Last updated: Jul 31, 2019 10:38AM UTC

Thomas, have you tried using the Scan configuration options in the New Scan console? If possible, we'd like some further information on your installation. Please get back to us with the following: The Burp Suite Enterprise version. The operating system on which you installed Burp Suite Enterprise. The database type and version you are using. Whether the Enterprise Agent installations are on the same machine on which you installed Burp Suite Enterprise, or elsewhere. The log files: By default these are in C:\ProgramData\BurpSuiteEnterpriseEdition on Windows and /var/log/BurpSuiteEnterpriseEdition/ on Linux. There is a separate log file for each day, and the current day's log file doesn't contain a date. If you can, please replicate the issue then send us the latest log files. The agent log files can be found on the agent machine. You can email any details to support@portswigger.net.

You need to Log in to post a reply. Or register here, for free.