Home
Configuration
You configure a scan by choosing settings that best describe your application, and the kind of testing you want.
Views
Multi-Factor Authentication (MFA)
Configure AppScan® to use one-time password or security questions (multi-factor authentication) when logging in.

Welcome
Welcome to the documentation for HCL AppScan Standard version 10.4.0
Getting started
This section provides a short tour of basic product features and procedures, including using the wizard to set up a scan.
Configuration
You configure a scan by choosing settings that best describe your application, and the kind of testing you want.
- Presets
  Presets give you the main configuration views needed for a particular type of scan.
- Views
  - Starting URL and domains
    Configure the Starting URL for the scan, and any additional servers and domains to be included.
  - API
    For scanning web APIs, define the your API type (improves coverage by better configuring custom parameters), explore method, and domains to be tested.
  - Exclude paths and files
    You can configure AppScan to ignore certain paths in the application, or specific types of file.
  - Multi-step operations
    Record and manage multi-step operations that are required to reach specific parts of the application that could otherwise be missed.
  - Login management
    Show AppScan® how to log in to your application.
  - Multi-Factor Authentication (MFA)
    Configure AppScan® to use one-time password or security questions (multi-factor authentication) when logging in.
  - HTTP authentication
    Add server-level authentication and client-side certificates, if required by the application.
  - AWS authorization
    Configure AWS settings.
  - Communication and proxy
    Configure communication timeout and proxy server settings.
  - Parameters, cookies & headers
    Identify session IDs and list parameters to exclude from the scan.
  - Automatic form fill
    Provide AppScan® with valid parameter values for filling forms in your application during the scan.
  - Error pages
    Add strings, regular expressions and URLs to identify your application's custom error pages.
  - Explore options
    Define the explore method (action-based, request-based, or both) that AppScan will use to explore the application, as well as other basic and advanced explore settings.
  - Test policy and optimization
    Define the collection of tests that will be sent to the application during testing (the test policy), and apply optimization for faster scans at times in the product lifecycle when speed is more important to you than scan depth.
  - Environment definition
    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. Customizing CVSS 3.1 environmental scores will improve the accuracy of your scan results.
  - Test options
    Additional test options.
  - Privilege escalation
    Compare scans that used different user privileges, to discover if privileged resources are accessible to non-privileged users.
  - Content-based view
    Lets you define a logical structure for the application tree, for cases where a URL-based tree will just be a long list under one or two URLs. This is not essential, but can make it much easier to navigate results.
  - Advanced configuration
    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
Manual exploring
Manual exploring enables you to explore specific parts of your application, filling in fields and forms as you go. This can be a way of ensuring that particular areas of the site are covered, and that AppScan has the information needed to complete forms correctly.
Scanning
Learn how to start a scan, and what happens during the scan; how to manually manipulate the Explore stage, and how to export the results of a scan.
Data
Data view is populated with information about the structure of the site during the Explore stage of the scan.
Issues
Issues view provides access to the results of a scan. You can view results at a high level or select specific tests or objects and access more details. These details include how to fix, requests/responses, and differences between the test variants that resulted in issues. You can manipulate the severity of issues, resend tests (with or without modifications), and create reports based on Issues.
Reports
This section describes how to generate reports from the scan results.
Tools
This section explains how to use additional tools provided with HCL AppScan Standard.
Integrations
This section describes integrations of other applications with AppScan Standard:
Best practices
This section contains some best practices and use cases for advanced users.
FAQ & Troubleshooting
CLI
This section describes the syntax and options available using the Command line interface.
References
Menus and toolbar summaries, and glossary

Multi-Factor Authentication (MFA)

Configure AppScan® to use one-time password or security questions (multi-factor authentication) when logging in.

One Time Password (OTP)

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.
When OTP is configured, Action-based must be the selected Login playback method in the Login playback. OTP will not work with Request-based login.

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

How to identify the OTP HTTP-parameter

AppScan needs to know the name of the parameter that contains the OTP (in order to be able to log in to the application), and usually identifies it when validating the Recorded Login procedure. If it fails to do so, or if you use Automatic Login, you must add the parameter yourself.

To identify the parameter:

Open a browser and go to your application's login page.
Click F12 to open the developer tools pane of the browser (opens to the right of, or underneath, the main browser pane).
Click on the Elements tab to view the HTML code.
When you select a part of the code, the element is highlighted in the main browser pane.
Locate the element that highlights the OTP field.
Example:
```
<input type="text" name="OTPvalue" value="">
```
The value of the name parameter, without the quotation marks, is the OTP HTTP parameter you need.
Example:
```
OTPvalue
```
If there is more than one OTP HTTP parameter, click Add another to add additional fields as needed.

Security questions

If your application uses security questions, you can add them here.

To add security questions:

Click + Add.
Type in the question and the answer and optionally the parameters if any and click Apply.