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).
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.
Static analysis client support
Supported operating systems and the types projects that can be scanned by ASoC when you perform static analysis.
Client tool interoperability

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.
  - Static analysis language support
    The types of files that can be scanned by ASoC when you perform static analysis.
  - Static analysis client support
    Supported operating systems and the types projects that can be scanned by ASoC when you perform static analysis.
    - Client tool interoperability
  - United States government regulation compliance
    Compliance with United States government security and information technology regulations help to remove sales impediments and roadblocks. It also provides a proof point to prospects worldwide that HCL is working to make their products the most secure in the industry. The Static Analyzer Command Line Utility supports the standards and guidelines that are outlined in this topic. To learn how to configure the utility for compliance, contact your HCL Support Representative.
- Scanning for security vulnerabilities
  To scan source code for security vulnerabilities, follow the steps in these topics.
- 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.

Client tool interoperability

AppScan on Cloud analyzes code in complex development environments; installed components may vary according to the system where artifacts are being tested. Depending on availability of certain tools, scan results may differ.

When Visual Studio, Maven, or Gradle type projects are found, but the respective tool is unavailable to load the project during scanning, ASoC alerts you. If you encounter the message

<filetype> found but <tool> not detected, which may affect scan results. Refer to the following article for details <link>

ASoC could not locate one of these tools on the current system. When an expected tool is not present, ASoC makes a best effort to discover files by crawling specified directories.

The following table details scan behavior when an expected tool cannot be located during scanning.


Language	Missing tool	Scan type	Behavior
.NET	Visual Studio	Data flow	If a solution file exists, ASoC requires Visual Studio to be installed to be able to load the solution and project files. If Visual Studio is installed, ASoC loads the solution and project files and scans the files associated with the project (exe, assemblies). If Visual Studio is not installed, ASoC attempts to load the solution file and the IRGen exits with nothing found. ASoC does not attempt to scan source code.
.NET	Visual Studio	Source code	If a solution file exists, ASoC requires Visual Studio to be installed to be able to load the solution and project files. If Visual Studio is installed ASoC loads the solution and project files and discovers the source files associated with the project. If ASoC is unable to load the solution file because Visual Studio is not installed, ASoC crawls the directory to find source code, and results may include source files that were not a part of the .NET project.
Java	Gradle	Data flow	If build.gradle exists, ASoC checks for Gradle. If Gradle is detected, ASoC attempts to use Gradle to build the Gradle project and collect the build artifacts. If Gradle is not installed, ASoC crawls the entire directory.
Java	Maven	Data flow	If pom.xml exists, ASoC checks for Maven. If Maven is detected, ASoC tries to use mvn to build the Maven project and collect the output files (war, jar, and so on). If Maven is not detected, ASoC crawls the entire directory.