AnsweredAssumed Answered

Assessment Time too long

Question asked by Mike R on Dec 4, 2017
Latest reply on Dec 22, 2017 by Dave Ferguson

Like • Show 0 Likes0
Comment • 3

Hello,

I have weekly scheduled WAS scans on Wordpress apps that are now reaching their time limit. None of them are authenticated scans. I noticed this in the scan reports:

Scan on 1st app

Crawling Time 00:47:05	Assessment Time 23:07:34	Operating System F5 Networks Big-IP
Links Collected 1559	Links Crawled 923	Requests Performed 282083	Avg. Response Time 0.8106 seconds

Scan on 2nd app

Crawling Time 00:37:40	Assessment Time 23:18:58	Operating System Linux 2.6 ...
Links Collected 1313	Links Crawled 672	Requests Performed 35229	Avg. Response Time 6.917509 seconds

Obviously the assessment time is going on way too long. Can anyone shed some light as to why this might be happening and how to fix it?

Thanks

No one else has this question

Outcomes

Dave Ferguson

Dec 4, 2017 3:22 PM

The second web app is taking on average almost 7 seconds to respond to a request. That's extremely slow. I consider anything over 1 second to be slow. The scan time is obviously going to go up when the scanner has to wait so long for a response. Try to find out from the app owners why the web app has such slow performance.

1 person found this helpful

Actions

Mike R @ Dave Ferguson on Dec 5, 2017 6:14 AM

I'll look into the second app's response time with the app owner. But my biggest concern is the 23 hours it takes to do the assessment. What is it really doing? Is there anyway to debug this or see what's going on? Does the assessment still make queries to the webapp or is that processing done without it?

Actions

Dave Ferguson

@ Mike R on Dec 22, 2017 12:43 PM

The scanner is making HTTP requests to the server and analyzing the responses. The web server logs would allow you to see what's going on in terms of the requests that were sent. An assessment/scan cannot be done without making queries to the web app.

1 person found this helpful

Actions

3 Replies

Dave Ferguson Dec 4, 2017 3:22 PM
Mark Correct
Correct Answer
The second web app is taking on average almost 7 seconds to respond to a request. That's extremely slow. I consider anything over 1 second to be slow. The scan time is obviously going to go up when the scanner has to wait so long for a response. Try to find out from the app owners why the web app has such slow performance.
1 person found this helpful
Like • Show 0 Likes0
Actions
- Mike R @ Dave Ferguson on Dec 5, 2017 6:14 AM
  Mark Correct
  Correct Answer
  I'll look into the second app's response time with the app owner. But my biggest concern is the 23 hours it takes to do the assessment. What is it really doing? Is there anyway to debug this or see what's going on? Does the assessment still make queries to the webapp or is that processing done without it?
  Like • Show 0 Likes0
  Actions
  - Dave Ferguson @ Mike R on Dec 22, 2017 12:43 PM
    Mark Correct
    Correct Answer
    The scanner is making HTTP requests to the server and analyzing the responses. The web server logs would allow you to see what's going on in terms of the requests that were sent. An assessment/scan cannot be done without making queries to the web app.
    1 person found this helpful
    Like • Show 0 Likes0
    Actions

Assessment Time too long

Outcomes

Related Content

Recommended Content