Welcome
Welcome to the HCL AppScan Enterprise 10.5.0 documentation, where you can find information about how to install, maintain, and use HCL AppScan Enterprise.
Accessibility features for AppScan® Enterprise
Accessibility features assist users who have a disability, such as restricted mobility or limited vision, to use information technology content successfully.
Overview
Learn general information about the product.
Installing
Learn how to install the product.
Upgrading and migrating
Learn how to upgrade the product.
- Product changes when you upgrade from a previous version
  Learn about changes that might affect your scans or report data when you upgrade from a previous version. Make sure that you read all the topics so that you understand the upgrade process.
- Fix pack installation
  Fix packs are available for download from FNO.
- Replacing Jazz™ Team Server with WebSphere® Liberty - Frequently asked questions
  Beginning with v9.0.1, AppScan® Enterprise includes an architecture redesign to reduce the installation footprint and to remove Rational® Jazz™ Team Server (Jazz Team Server) as the user authentication component.
- Migrating Jazz Team Server users to Liberty in AppScan Enterprise
  To migrate Jazz Team users to use the Liberty authentication method, export a .csv file of users by using a command before you begin upgrading to v9.0.1 and higher. Then, you can follow one of the following two methods and register the same users in Liberty so that they can access AppScan Enterprise v9.0.1 and higher.
- Upgrading to the latest version of AppScan Enterprise
  For a successful upgrade to the latest version of AppScan Enterprise, read this topic carefully.
- Configuring the SQL Server database for AppScan® Enterprise
  The AppScan® Enterprise Server configuration needs information about SQL Server. Configure the SQL Server first to save time during the AppScan configuration. If you upgrade SQL Server to a newer version, follow these instructions as well.
- Configuring a basic user registry for the Liberty profile
- Using a certificate in your certificate store with Liberty
  This procedure describes how to use Liberty certificates to secure IIS.
- Upgrading the AppScan® Source LDAP connection with an Oracle database
  If you are changing LDAP settings (such as the server name or alias name) or if you are moving the AppScan® Enterprise Server to another computer, you must update the asc.properties file to reflect those changes.
- Enabling FIPS 140-2 or NIST SP800-131a on WebSphere Liberty Profile
  Use one of these procedures to enable FIPS 140-2 or NIST SP800-131a on WebSphere Liberty Profile.
- OWASP report visibility in AppScan Enterprise updates
Integrating
Learn how to integrate the product with other solutions.
DevOps
Learn how to extend the product with REST APIs and plugins.
Best practices
Learn best practices for using the product.
Configuring
Learn how to configure the product.
Administering
Learn how to administer the product.
Managing application risk
Follow this workflow to manage application security risks in your organization.
Troubleshooting and support
To help you understand, isolate, and resolve problems with your HCL® software, the troubleshooting and support information contains instructions for using the problem-determination resources that are provided with your HCL products.
Reference
Review reference information for the product.
Glossary

OWASP report visibility in AppScan Enterprise updates

Update Behavior

When a user updates AppScan Enterprise to a newer version, AppScan Enterprise will retain access to previously available OWASP reports alongside the latest version. For example, updating from v10.4.0 to v10.5.0 will provide access to both the OWASP API Security Top 10 report 2023 (included with v10.5.0) and the OWASP API Security Top 10 report from previous versions (e.g., 2019).

Reasoning

This behavior is due to the design of the OWASP regulation file. The file name incorporates the year of its release (e.g., "owasp_API_top_10_2023.asreg"). During the update process, the existing regulation file(s) are not overwritten, ensuring continued access to historical OWASP reports.