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.
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
- General FAQ
  This topic addresses general application questions.
- Troubleshooting tools
- Digital signature troubleshooting
- External traffic recorder not recording
  If your external device is configured correctly, AppScan's external login recorder and external traffic recorder will show the traffic sent from the device as you send it. This section offers suggestions if it does not.
- Insufficient disk space
- License troubleshooting
- Login troubleshooting
  Tips for troubleshooting session detection problems in Scan Configuration > Login Management view.
- Low virtual memory
- Multi-step operation troubleshooting
  Some suggestions for troubleshooting action-based multi-step operations.
- No URLs found
- Out-of-session troubleshooting
  Some suggestions for troubleshooting out-of-session issues.
- Postman Collection scan
  Some suggestions for troubleshooting a Postman Collection scan.
- Server not responding
  Some suggestions for troubleshooting if the server is not responding.
- Replacing unsigned extensions
  If you want to use an unsigned extension that you used with a previous version of AppScan, you can either elect to trust it, or see if a signed version is available to replace it with.
- Extended Support Mode
  Extended Support Mode logs all AppScan activity, for packing and sending to your support provider to help troubleshooting a problematic procedure.
- Changing the default browser
  You can configure AppScan to use a browser other than its built-in browser.
- Reporting false positive results
- Logs
  This section includes explanations of Scan Log messages (View > Scan Log).
CLI
This section describes the syntax and options available using the Command line interface.
References
Menus and toolbar summaries, and glossary

Multi-step operation troubleshooting

Some suggestions for troubleshooting action-based multi-step operations.

If AppScan fails to scan your action-based multi-step recording, try the following troubleshooting steps:

In Configuration > Multi-step Operations, select the sequence and click Validate. The browser opens and replays the sequence. Verify that the browser performs all the expected steps. If the recorded actions do not match the current version of the site, re-record the sequence.
When the browser closes, verify that a green check mark appears next to each action in the sequence. If one of more of the actions has a red X, verify that the action is needed to perform the next step in the sequence (such as clicking on a pop-up that doesn't appear in the play-back). If it is not needed, delete it by selecting the action and clicking .
After each step in the sequence, AppScan inserts a WAIT action of duration 0 seconds. Try increasing the duration of the WAIT action before a failed action.
Check that the Redundancy Tuning and Tracking Options for all parameters and cookies in the test request are correct. If they are not, either correct them, or delete them from the list in Configuration > Parameters and Cookies > main tab.
Increase the no-interaction timeout in Configuration > Advanced Configuration > Action-based: Multi-step no-interaction timeout.