Welcome
Installation
Learn about AppScan 360° architecture and how to install the product.
Prerequisites Setup Guide
Resource Requirements

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
  - Resource Requirements
- 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).

Resource Requirements

This section outlines the storage and computing requirements for deploying and running HCL AppScan 360°. Proper resource allocation is crucial for optimal performance and scalability.

Storage Requirements

AppScan 360° requires MSSQL database and file storage. Estimated storage needs based on scan executions are:


Scan Executions	MSSQL Server Storage	File Storage
1,000	1GB	10GB
100.000	5GB	100GB
1,000,000	20GB	1000GB

Recommendation: Allocate a minimum of 200 GB for both MSSQL server storage and file storage to accommodate temporary logs. Storage must be:

Encrypted
Redundant
Sharable between pods
Supporting ReadWriteMany (RWX) access mode

Old scans can be manually deleted to save space.

Computing Requirements

AppScan 360° Platform


Component	Memory (Min/Max)	CPU (vCore, Min/Max)
ASCP	42GB / 48GB	10/12

Scanning Resources


Scenario	Memory (Min/Rec)	CPU (vCore, Min/Rec)
Dynamic analysis scanning: single scan	3GB/4GB	2/3
Dynamic analysis scanning: five concurrent scans	15GB/20GB	10/15
Dynamic analysis scanning: ten concurrent scans	30GB/40GB	20/30
Static analysis scanning: single scan	16GB/28GB	2/4
Static analysis scanning: five concurrent scans	80GB/140GB	10/20
Static analysis scanning: ten concurrent scans	160GB/280GB	20/40
Software Composition Analysis (SCA) scanning: single scan	1GB/2GB	2/5
Software Composition Analysis (SCA) scanning: five concurrent scans	2GB/4GB	7/10
Software Composition Analysis (SCA) scanning: ten concurrent scans	4GB/6GB	10/12

Note: Resources scale with concurrent scans.

Nodes require at least 28 GB RAM and 4 cores for static scans
Nodes require at least 4 GB RAM, 3 cores, and 200 GB disk space for dynamic scans
Ensure sufficient AppScan 360° licenses and Kubernetes resource availability
Do not exceed 25 concurrent scans