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.
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.
- Options dialog box
  This section describes options you can control, to customize AppScan, from the Options dialog box in Tools > Options.
- Web API Wizard extension
  This extension lets you scan using Open API description files. It is available from Tools > Extensions > Web Services Wizard (Open API), and the extension is enabled by default.
- Scan Scheduler
- User-Defined Tests
  - User-Defined Test wizard
    The User-Defined Test wizard lets you create user-defined tests for AppScan to use when scanning, in addition to the tests it creates automatically.
  - Test Type
    In this step you define the kind of test you are creating. This affects which wizard steps are displayed.
  - Filter
    In this step you define the conditions which must be met to run this test. Only requests that match the conditions will be tested.
  - Modification
    In this step you define the changes that will be made to the original request, to create the test request.
  - Validation
    In this step you define the conditions that indicate the test succeeded.
  - Advisory
    In the Advisory and Advisory Continue steps, you input the text content of the Advisory that will appear in the scan results and reports. All fields are optional.
  - Completing the wizard
    When you have defined the new test, click Finish to add it to the list.
- PowerTools
  AppScan offers access to five utilities (PowerTools), each providing a specific feature to help you manage your application security or to help you use AppScan.
- Customizing the Tools menu
- Extensions
- Logs
  Logs can help you troubleshooting.
- Searching Results
  You can filter the Result List in any of the views, for specific data.
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

Filter

In this step you define the conditions which must be met to run this test. Only requests that match the conditions will be tested.

Defining filters that limit testing to relevant requests only can greatly improve efficiency.

Click Add to add another Single or Group filter.
When adding more than one item, you must specify the logical relation between them: All (And), Any (Or) or None (Not). See example below.

When done, click Next to move to the next step.

Example

In this example three conditions have been added. The new test will be run only on responses that meet either Condition 1 (Request includes my myUserID parameter), or both of Conditions 2 and 3 (Response Status Code is 3xx and Response Body contains specific_text).

As an expression this is:

( 1 | (2 & 3 )