Redundancy tuning

Careful redundancy tuning can significantly reduce scan time.

AppScan® tries to avoid sending more than one request when it is clear that no new information will be revealed. In many cases a difference in the value of a particular parameter is insignificant, and it is not necessary to send more than one request when all other parameters are the same and only that value is different.

Consider the following two requests:

.../doAction.pl?action=buy&timestamp=14:00&n=1

.../doAction.pl?action=buy&timestamp=15:30&n=1

The only difference between them is their Timestamp value.

In most cases it would be sufficient to send a single request using either of the configurations, and unnecessary to send them both. It is unlikely that the response to one of the requests would reveal any weakness that would not also be revealed by the other. You should therefore configure the Redundancy Tuning settings for the Timestamp parameter so that in cases like this only one of the requests will be sent.

See also:

Redundancy tuning options

Redundancy tuning defaults

Changing redundancy tuning defaults

Changing redundancy tuning for a specific parameter