Home
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).
Scanning for security vulnerabilities
To scan source code for security vulnerabilities, follow the steps in these topics.
Using the Static Analyzer Command Line Utility
The Static Analyzer Command Line Utility (SAClientUtil) is used to generate an IRX that can be scanned in AppScan on Cloud or AppScan 360°. The appscan prepare command is supported for use with AppScan 360° Static Analysis.
Setting up the Static Analyzer Command Line Utility
For static analysis, download a small Command Line Utility. When you extract the utility to your local disk, you can use its command line interface (CLI) to perform security analysis.
Removing the Static Analyzer Command Line Utility
Remove the Static Analyzer Command Line Utility plug-ins from your integrated development environment (IDE). In addition, instructions for removing the Static Analyzer Command Line Utility are provided. These instructions only need to be followed if you intend on removing Static Analyzer Command Line Utility components from your system. If you are upgrading these components to a new Static Analyzer Command Line Utility version, plug-in installation will remove old components automatically before installing the new version.

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 how to install the AppScan Central Platform and AppScan 360° Static Analysis.
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.
  - Configure a scan in AppScan 360°
  - Configuring a scan using AppScan Go!
    Use AppScan Go! to configure a static scan. You can then run the scan in the cloud or use a plugin to automate scanning.
  - Using the Static Analyzer Command Line Utility
    The Static Analyzer Command Line Utility (SAClientUtil) is used to generate an IRX that can be scanned in AppScan on Cloud or AppScan 360°. The appscan prepare command is supported for use with AppScan 360° Static Analysis.
    - Setting up the Static Analyzer Command Line Utility
      For static analysis, download a small Command Line Utility. When you extract the utility to your local disk, you can use its command line interface (CLI) to perform security analysis.
      - Removing the Static Analyzer Command Line Utility
        Remove the Static Analyzer Command Line Utility plug-ins from your integrated development environment (IDE). In addition, instructions for removing the Static Analyzer Command Line Utility are provided. These instructions only need to be followed if you intend on removing Static Analyzer Command Line Utility components from your system. If you are upgrading these components to a new Static Analyzer Command Line Utility version, plug-in installation will remove old components automatically before installing the new version.
    - Configuring IRX file generation with the CLI
      Use a configuration file for IRX file generation, wherein you can specify individual targets, or include or exclude targets. In addition, you can use the configuration file to specify additional information that would help to generate a complete IRX file.
    - Generating an IRX file using the command-line interface (CLI)
      To initiate an analysis of your files, you must generate an IRX file to submit for scanning. To use the CLI to generate the IRX file, follow these instructions.
    - CLI command reference (Windows)
      Windows-specific commands for performing static analysis using a small client command line interface (CLI) that you download and extract to your local disk.
    - CLI command reference (Linux and macOS)
      Linux-specific commands for performing static analysis using a small client command line interface (CLI) that you download and extract to your local disk.
  - Configuring a scan using an archive file
  - Language-specific features
  - Static analysis scan results
    Features available in static analysis scan results.
- 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.
Results
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).

Removing the Static Analyzer Command Line Utility

Remove the Static Analyzer Command Line Utility plug-ins from your integrated development environment (IDE). In addition, instructions for removing the Static Analyzer Command Line Utility are provided. These instructions only need to be followed if you intend on removing Static Analyzer Command Line Utility components from your system. If you are upgrading these components to a new Static Analyzer Command Line Utility version, plug-in installation will remove old components automatically before installing the new version.

Before you begin

Procedure

Static Analyzer Command Line Utility To remove the Static Analyzer Command Line Utility, delete the extracted SAClientUtil_<version>_<os>.zip contents from your system. If you added the location of the Static Analyzer Command Line Utility \bin directory to your PATH environment variable, remove it.