Getting started
Welcome to the documentation for HCL AppScan 360°, where you can find information about how to install, maintain, and use this service.
Installation
Learn about AppScan 360° architecture and how to install the product.
- Installation file locations
- Prerequisites Setup Guide
- AppScan 360° Setup Assistant
- Single VM installation of AppScan 360°
- Distributed installation of AppScan 360°
- Configuring user authentication
  Authenticate users for AppScan 360° using either single sign-on (SSO) or LDAP authentication.
- Updating the Software Composition Analysis (SCA) vulnerability database
  The Software Composition Analysis (SCA) vulnerability database includes the most popular security vulnerability databases (NVD, Github advisory, Microsoft MSRC), and a wide range of lesser-known security advisories and open source project issue trackers. AppScan 360° users can enable automatic updating of the SCA vulneratility database at installation or configure manual updating.
- Managing AppScan 360° deployments in My HCLSoftware
  AppScan 360° licenses are managed through the My HCL Software (MHS) portal. Create a license deployment in MHS, specify license entitlements, and download a license file from MHS, then upload that file to AppScan 360°.
- Opening AppScan 360° for the first time
- Upgrade Guide for AppScan 360°
- Uninstalling AppScan 360°
- Troubleshooting Guide
Navigation
This section describes the items on the main AppScan 360° menu bar, with links to more detailed information.
Administration
Define users, applications, policies, and configure DevOps integrations.
Dynamic analysis
HCL AppScan 360° performs security scans for web-applications for production, staging and development environments.
Interactive monitoring
Using an agent installed on your application, AppScan 360° identifies security vulnerabilities in your application during runtime by monitoring all interactions, both legitimate and malicious. The process is "passive," in the sense that IAST does not send its own tests, and can therefore run indefinitely.
Software Composition Analysis
Use Software Composition Analysis (SCA) to scan for security vulnerabilities in open source and third-party packages used by your code. SCA includes Intelligent Finding Analytics (IFA) and Intelligent Code Analytics (ICA).
Static analysis
Use static analysis (SAST) to scan for security vulnerabilities in web and desktop applications. Static analysis includes Intelligent Finding Analytics (IFA) and Intelligent Code Analytics (ICA).
Results
The Scans and Sessions page lists the scans under the categories DAST, SAST, SCA, and IAST, where you can view your scan results, including scan statistics. To view, rescan, or download reports, select a scan.The Scans and Sessions page lists scans under the categories where you can view your scan results, including scan statistics. To view, rescan, or download reports, select a scan.
AppScan Model Context Protocol (MCP) server
The AppScan MCP server integrates HCL AppScan 360° directly with AI-powered development environments and agents. By implementing the Model Context Protocol (MCP), this server allows LLMs (such as Claude or models running in VS Code) to securely access your security data—including SAST, DAST, SCA, and IAST results—to help you triage issues, analyze findings, and automate workflows using natural language.
Reference
Some frequently asked questions, and information about integrating AppScan 360° into the product lifecycle (SDLC).

Helm Based Installation Upgrade Instructions

Introduction

This section provides instructions for upgrading AppScan 360° in the Helm based installation method. This guide is applicable for upgrading from version 2.0.0/2.0.1 to 2.1.0.

Upgrade Steps

Ensure Pre-Upgrade Checklist is completed.
Prepare cluster for upgrade - Install and configure Gateway controller
Prepare configuration file for helm installation.
- Find and copy singular-singular.clusterKit.yaml file from previous installation to current kits location.
- This will ensure the same config is supplied for upgrade.
- Add new properties required for v2.1.0. Refer Preparing the configuration file
Follow instructions in the Helm installation guide to run the installation with new helm charts for v2.1.0.

Note: If the Helm version is upgraded to 4, the Helmfile binary must also be updated to the latest version.