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.
Configure a scan in AppScan 360°
Scan mode
Scan mode describes whether AppScan 360° scans build outputs (.dll, .jar, and so on) or source code files in projects for specific languages.

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°
    - Scan mode
      Scan mode describes whether AppScan 360° scans build outputs (.dll, .jar, and so on) or source code files in projects for specific languages.
    - Static analysis scan status
  - 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.
  - 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).

Scan mode

Scan mode describes whether AppScan 360° scans build outputs (.dll, .jar, and so on) or source code files in projects for specific languages.

Specify scan mode in AppScan Go! or by using the source code-only option in command line utility (CLI). By default, Static Analyzer does not analyze the source code for compiled languages (Java, .NET, and C/C++). For these languages, users have the option of specifying scan mode. For all other languages, scanning is of source code-only.

Understanding the different methods of scanning is critical to the success of your project. Each has specific uses, requirements, and results differ.

Source code-only scanning

Early in the software development lifecycle, source code-only scanning of uncompiled code can be a helpful tool to head off issues and confirm programmatic approach before the project is too far along.

Generally performed by developers, and requiring access to source files, source code-only scans are fast but not necessarily as accurate as scans of compiled code. Results of source code-only scans pinpoint vulnerabilities in specific lines of code; they do not show trace data.

You can specify source code-only scanning for certain languages.

Bytecode/compiled (build output scanning)

When accuracy is preferred over speed of a scan, scanning build outputs can help you understand not just where in an application a vulnerability exists, but also the impact of that vulnerability. Scanning build outputs is sometimes referred to as "dataflow" scanning.

Build output scans require access to the fully built application. Scan results display "traces" showing the flow of tainted data through the application, from the point it enters the application to the point at which the data is used (called the "sink"). The trace shows the line of code and the tainted variable at each point in the trace; its appearance is similar to an exception stack trace.

Build output scanning may have additional requirements, depending on the project type:

Application dependencies should be available for the most complete and accurate results.
For Java and .NET bytecode is required, so the application needs to be built before running the scan.
For C/C++, a Visual Studio solution is required.