Welcome
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).
Static analysis troubleshooting
If you experience problems with static analysis, you can perform these troubleshooting tasks to determine the corrective action to take.
Security scan fails with Application with id x does not exist error

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.
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).
- System requirements for static analysis
  Supported operating systems and the types of files, locations, and projects that can be scanned by AppScan 360° when you perform static analysis.
- Scanning for security vulnerabilities
  To scan source code for security vulnerabilities, follow the steps in these topics.
- Static analysis troubleshooting
  If you experience problems with static analysis, you can perform these troubleshooting tasks to determine the corrective action to take.
  - Automatic update of AppScan Go! fails
  - Troubleshooting static analysis scans
  - Errors or warnings occur when generating a static analysis IRX file
  - .NET scan results show the assembly file instead of the source file
    When the .pdb file is in the wrong format, .NET scan results can show the assembly file instead of the source file.
  - Static analysis of ASP.NET site fails due to problems with precompilation
  - Static analysis Failed to create application 'Default' error
  - Security scan fails with Application with id x does not exist error
  - Unable to connect to AppScan 360° from AppScan Go!
  - IRX file is too large to analyze
  - IRX upload fails due to mismatched encryption
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.
Reference
Some frequently asked questions, and information about integrating AppScan 360° into the product lifecycle (SDLC).

Security scan fails with `Application with id x does not exist` error

Symptom

Running a scan that uses the Jenkins or IDE plugin or command line interface (CLI) fails with this error:

Application with id x does not exist

Failed to run the security scan: Problems occurred submitting the IRX file to the
analysis service.

Cause

Previously, AppScan 360° associated applications based on the app_id. A recent update changed this association from app_id to guid. For the most part, the AppScan 360° service will prompt you to reassociate applications based on this update. For the Jenkins and IDE plugins and CLI, you must take additional steps.

Resolution

For the Jenkins plugin, re-save your Jenkins plugin configuration according to the instructions at Adding security analysis to your Jenkins automation server and try the scan again.

For the IDE plugin, when prompted, re-select the same application to scan and click OK.

For CLI, the new guid replaces app_id. The guid is a unique 32-character identifier. For example, 33c3281a-6d7c-e711-b334-002590731623. Using the appscan list_apps command, determine the guid for each app and replace the app_id with it in the queue_analysis command in scripts or on the command line.