Welcome
Welcome to the documentation for HCL AppScan Standard version 10.5.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.
    - Form fields
      In the Configuration under Automatic Form Fill, the General Form Fill view lists the values that AppScan will utilize to automatically fill in forms.
      - Exporting Form Fields
        You can save form field data for future use, by exporting your Form fields table as an XML file and importing it later.
      - Importing a saved ASFF file
  - Error pages
    Enhance your application's error page identification by adding strings or regular expressions that enable AppScan® to recognize your error pages witihin the response content, path or both. This ensures that AppScan can effectively recognize and handle your error pages, contributing to the overall accuracy of your security scans.
  - 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 provides access to numerous advanced registry settings and 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

Form fields

In the Configuration under Automatic Form Fill, the General Form Fill view lists the values that AppScan will utilize to automatically fill in forms.

About this task

You can add to or edit the Form fields that AppScan® uses to automatically fill forms during scanning.

Procedure

To add a new definition, click + Add.

The Add form field dialog box appears.


Column	Description
Description	A name that describes the parameter.
Parameters	The name, or part of the name, that is used to define this parameter in the HTML. When AppScan finds a field with this parameter name it fills in the value supplied. To enter multiple parameter names in one row, use a comma without a space. Example: Description: Zip Code \| Parameters: zip,postal
Value	The user input that AppScan will send for this parameter.
Match Type	Defines how AppScan will search for the parameter defined here, and how it relates to field-filling options supplied by the site. Options are "Partial" or "Complete." Complete: The value will be input only for parameters that exactly match one of the text strings in the Parameters field. (For example, the parameter defined as `addr`, will not be used for a field named `address`.) Furthermore, if the field offers a drill-down list of options, this value will be used only if it exactly matches one of the options. Partial: This value will be input for parameters that match or partially match one of the parameter strings listed here. (For example, if the parameter is defined as `addr`, it will also be used for a fields named `address`, or `ADDR`.) Furthermore, if the field offers a drill-down list of options, and none of the options exactly match the value entered here, a close match will be used instead.
URL	If this field is left empty, this value will be used for this parameter regardless of URL. If a specific URL is given, this value will be used for only for parameters that occur in this URL. (You can therefore define a parameter one way for one URL and differently for another.) However, if there is no other row with the same parameters and an empty URL, the value of this row is default for all other URLs too.

Example

Exporting Form Fields

Importing a saved ASFF file