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.
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.
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.
Specifying global options with APPSCAN_OPTS
Set the APPSCAN_OPTS environment variable to specify global options before running a scan. Global options can be specified before scanning when using AppScan Go!, Static Analyzer Command Line Utility, IDEs, and plugins.

Getting started
Welcome to the documentation for HCL AppScan on Cloud, where you can find information about how to install, maintain, and use this service.
Navigation
This section describes the items on the main AppScan on Cloud menu bar, with links to more detailed information.
Administration
Define users, applications, policies, and configure DevOps integrations.
Dynamic analysis
AppScan on Cloud performs security scans for web-applications for production, staging and development environments. For development environments it is aided by Private Site Scanning technology to scan applications not accessible to the open Internet.
Interactive monitoring
Using an agent installed on your application, ASoC 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).
- About static analysis (SAST)
- System requirements for static analysis
  Supported operating systems and the types of files, locations, and projects that can be scanned by ASoC 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 on Cloud
    Configure a static analysis scan.
  - Configuring a scan using AppScan Go!
    AppScan Go! steps you through configuring and running a static scan. You run the scan in the cloud or use a plugin to automate scanning.
  - 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.
    - 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.
    - 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.
      - Specifying global options with APPSCAN_OPTS
        Set the APPSCAN_OPTS environment variable to specify global options before running a scan. Global options can be specified before scanning when using AppScan Go!, Static Analyzer Command Line Utility, IDEs, and plugins.
      - Using a configuration file with a plugin to automate scanning
        When using plugins, you can make use of appscan-config.xml to automate scanning.
    - 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.
  - Generating in IRX file using a plugin or IDE
  - Configuring a scan using an archive file
  - About Software Composition Analysis
    Software Composition Analysis (SCA) locates and analyzes open source and third-party packages used by your code.
  - Static analysis integrations
  - Submitting HCL AppScan Source assessments to the Cloud for analysis
    If you have a subscription to HCL AppScan on Cloud, you can submit AppScan Source assessments for analysis there. Assessments from AppScan Source Versions 9.0 or higher are supported. The number of scans you can submit depends on your ASoC subscription.
  - Best practices for Java scanning
  - Static analysis scan results
    Features available in static analysis scan results.
- Sample apps and scripts
  Use these sample applications to practice scanning with ASoC.
- 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 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.
Troubleshooting
If you experience problems with this service, you can perform these troubleshooting tasks to determine the corrective action to take.
FAQ & Reference
Frequently asked questions, information about integrating ASoC into the product lifecycle (SDLC), and ASoC API documentation.

Specifying global options with `APPSCAN_OPTS`

Set the APPSCAN_OPTS environment variable to specify global options before running a scan. Global options can be specified before scanning when using AppScan Go!, Static Analyzer Command Line Utility, IDEs, and plugins.

When using APPSCAN_OPTS, the option name must be preceded by -D. In addition, on Linux systems, you must surround the value with double-quotes:

Windows
```
set APPSCAN_OPTS=<option>[=<value>]
```

Linux

export APPSCAN_OPTS="<option>[=<value>]"

For example, to use the option ENABLE_SECRETS:

Windows
```
set APPSCAN_OPTS=-DENABLE_SECRETS
```
Linux
```
export APPSCAN_OPTS="-DENABLE_SECRETS"
```

Available options for use with APPSCAN_OPTS are:


Option	Description	Values	Default
Java parallel processing options
`USE_SLICER`	Enable Java parallel processing	True/False	True
`DISABLE_CACHE`	Prevents use of the cache, thus forcing a re-run of the IR generation process on each class file even if there is a cache entry.
`IRX_MINOR_CACHE_HOME`	Specifies the location of the file cache.	Windows mapped and UNC drives, Linux mounts, or a local target.	`<user home directory>/.appscan/irx_cache`
Options for configuring analysis
`ENABLE_SECRETS`	Enable scanning for secrets in source files.
`SECRETS_ONLY`	Scan for secrets in source code files only
`OPENSOURCE_ONLY`	Gather open source (SCA) information during IRX generation only.
`SOURCECODE_ONLY`	Scan source code files, ignoring other supported file types (`.dll`, `.exe`, `.jar`, `.sln`, and so on) only.
`STATIC_ANALYSIS_ONLY`	Prepare for static analysis during IRX generation only.
`thirdParty`	Enable static analysis of third-party code.
`scan_speed`	Set the scan speed to `<value>`.	Simple Balanced Thorough Deep	Deep
Miscellaneous
`DEBUG`	Enable debug logging.
`NO_ENCRYPT`	Do not encrypt the generated `.irx` file.