Additional configuration

Here are some configuration changes to consider if site coverage in the initial Explore stage was insufficient.

About this task

If site coverage in the initial Explore stage was insufficient, or took more than about 30 minutes, consider making some or all of the following possible configuration changes to parameter and cookie definitions.


  1. Click Configuration > Parameters and Cookies view.
  2. Tracking. If your site tracks cookies (such as session identifiers that are updated each time a user logs in), you should make sure they are correctly defined.
    1. Verify that your site's cookies and parameters have been identified and are listed in the main Parameters and Cookies tab, and set as "Tracked".
    2. If necessary, define additional parameters and cookies by clicking the plus icon. For more details see Parameter definition.
  3. Redundancy Tuning. Careful redundancy tuning can significantly reduce scan time without any reduction in scan coverage and accuracy. Review the redundancy tuning to ensure that unnecessary duplicate requests are not sent, but necessary ones are. For more details, see Redundancy tuning.
    1. If the cookie or parameter you want to configure is not listed in click the plus icon and define it.
    2. Verify that settings are appropriate for each cookie or parameter.
  4. Session ID verification. Accurate session ID definition is important to enable AppScan to create legitimate requests during the Explore stage.
    1. Verify that the tracking setting for all session IDs are correctly defined as Login Value.
    2. Verify that all parameters set as Login Value are session IDs.
  5. If you made any changes to the Parameters and Cookies definitions, re-Explore the application. It may also be necessary to re-record the manual Explore and multi-step operations.