Configuration
You configure a scan by choosing settings that best describe your application, and the kind of testing you want.
- Scan Configuration Wizards
  You can quickly configure basic scans using the wizards.
- Scan Configuration Dialog Box
  - URL and Servers view
    Configure the Starting URL for the svcan, and any additional servers and domains to be included.
  - Login Management view
    Show AppScan® how to log in to your application.
  - One-Time Password (OTP) view
    If required by your application, configure AppScan® to use OTP when logging in.
  - Environment Definition view
    Environment definition is not essential, but enables AppScan® to safely refrain from sending non-relevant tests during the scan, resulting in a faster and more accurate scan.
  - Exclude Paths and Files view
    You can configure AppScan to ignore certain paths in the application, or specific types of file.
  - Explore Options view
    Define scan limits, link extraction methods and the general Explore method.
  - Parameters and Cookies view
    Identify session IDs and list parameters to exclude from the scan.
  - Automatic Form Fill view
    Provide AppScan® with valid parameter values for filling forms in your application during the scan.
  - Error Pages view
    Add strings, regular expressions and URLs to identify your application's custom error pages.
  - Multi-Step Operations view
    Record and manage multi-step operations that are required to reach specifica parts of the application that could otherwise be missed.
  - Content-Based Results view
    Define a logical structure for the application tree, if AppScan® will not be able to do this based on URL structure.
  - Communication and Proxy view
    Configure communication timeout and proxy server settings.
  - HTTP Authentication view
    Add server-level authentication and client-side certificates, if required by the application.
  - 3rd Party Authentication view
    3rd Party Authentication view of the Configuration dialog box lets you configure AWS settings.
  - Test Policy view
    Define and edit the collection of tests that will be sent to the application during testing; the test policy.
  - Test Optimization view
    Apply optimization for faster scans at times in the product lifecycle when speed is more important to you than scan depth.
  - Test Options view
    Additional test options.
  - Privilege Escalation view
    Refer AppScan to scans run using different user privileges, to discover privileged resources that may be accessible to users with insufficient privileges.
  - Advanced Configuration view
    This view gives you access to many advanced registry settings and it should only be used by experienced AppScan users, or when instructed to do so by the support team to troubleshoot a problem.
- Scan using a Postman Collection
  If you have a Postman Collection of requests to your web API, you can import it and use it as the basis for a scan.
- Scan file structure
  Explains the basic structure of an AppScan Standard SCAN file.
- Scan templates
  A scan template is simply a scan configuration that has been saved so that you can use it again.
- Changing the configuration during a scan

One-Time Password (OTP) view

If required by your application, configure AppScan® to use OTP when logging in.

If your application uses OTP, select one of the two options, otherwise leave the default setting: None.

When you record the login procedure, AppScan will extract the relevant parameters from the traffic and add them to the OTP HTTP-parameters list. They will also be added to the OTP entry in Automatic Form Fill view. If AppScan fails to identify the parameters, you must add them yourself, either in this view or in Automatic Form Fill view.

Limitations:

Only one OTP type (TOTP or URL-generated) is supported per scan.
For TOTP only numerical values are supported.
OTP is supported only when the Chromium browser is used to record the Login. It is not supported if Internet Explorer is used.

To see our short video demo, click the icon below:


Option	Description
TOTP	For time-based one-time passwords, you must provide AppScan with: Secret key OTP length (number of digits) Hash algorithm used (select from the dropdown) Time step (in seconds) Tip: The times on the AppScan machine and the tested server must both be accurate.
URL-generated OTP	If the OTP is accessible from a designated URL, you can configure AppScan to extract it from the URL’s response. You must provide AppScan with: URL Regular expression that will identify the OTP in the URL response.
None	OTP is not used by the site, or scanning those pages that use OTP is not required.
Details
OTP HTTP-parameters	If you have selected one of the OTP types, then when you validate the login procedure, AppScan will identify the required parameters needed from the traffic, and add them to the Automatic Form Fill list. They will also be shown here. If AppScan® fails to identify the parameters, you must add them yourself. Parameters must be comma separated.