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
Administration
Define users, applications, policies, and configure DevOps integrations.
Navigation
This section describes the items on the main AppScan 360° menu bar, with links to more detailed information.
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.
- Sample applications and scripts
- Static analysis troubleshooting
  If you experience problems with static analysis, you can perform these troubleshooting tasks to determine the corrective action to take.
  - 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
  - Issues with per user installation of AppScan Go! on Windows 7
  - Unable to connect to AppScan 360° from AppScan Go!
  - IRX file is too large to analyze
Results
The Scan History tab of your application displays your scan results (including scan statistics) and rescan options.
Reference
Some frequently asked questions, and information about integrating AppScan 360° into the product lifecycle (SDLC).

IRX file is too large to analyze

Symptom

AppScan 360° is unable to scan a generated IRX file due to size.

Cause

The most common reason an IRX file is particularly large is the inclusion of third-party libraries and/or code in a scan. Third-party dependencies should be available for the scan, but we do not recommend analyzing them directly.

Resolution

When you generate an IRX file in AppScan 360°, AppScan 360° also creates an archive of logs named <scan name>_logs.zip. Review the scan.manifest file within that archive to see what files are being scanned. If there are numerous third-party files listed in non-Open Source language sections of the scan.manifest file, and thus being scanned, use an appscan-config.xml file to limit the scope of the scan to just your files and code. See Configuring IRX file generation with the CLI for details about creating an appscan-config.xml file.

Note: Third-party libraries listed under the Open Source language are normal and do not affect the size of the IRX.

If your scan does not contain third-party artifacts, contact HCL Customer Support for additional assistance.