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).
Static analysis troubleshooting
If you experience problems with static analysis, you can perform these troubleshooting tasks to determine the corrective action to take.
.NET scan results show the assembly file instead of the source file

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.
- 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.
  - Eclipse Photon plug-in crashes with _cairo_operator_bounded_by_source: Assertion: 'NOT REACHED' failed.
    On Red Hat Linux, after installing the Eclipse plug-in for Eclipse Photon, clicking on the Location in the report (or any action that triggers opening the editor to the line of source code) causes Eclipse to crash.
  - Errors or warnings occur when generating a static analysis IRX file
  - .NET scan results 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
  - Unable to connect to AppScan on Cloud from AppScan Go!
  - IRX file is too large to analyze
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.

.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.

Symptom

The analysis results of a .NET scan show the .dll or .exe file instead of the source file (.cs or .vb).

Cause

This occurs when the .pdb file associated with the .dll or .exe being scanned is missing or in the wrong format. Projects created in Visual Studio 2017 use the "portable" pdb format, by default. AppScan on Cloud does not support the "portable" pdb format.

Resolution

Ensure that each dll/exe being scanned has a corresponding .pdb file located in the same directory as the dll/exe and that the format of the pdb is "Full". If the .pdb file is missing or you are not sure of the format, do the following:

In the Visual Studio project's properties, change the "Debugging Information" property to "Full" and rebuild the project prior to scanning:

In Visual Studio, right-click the project and choose Properties.
Click the Build tab.
Click the Advanced button.
Se the Debugging Information setting to Full.
Save the change and rebuild the project.

Note: Be sure to select the desired build configuration (for example, Debug|x64) in Visual Studio prior to making these changes. Each build configuration can specify a different .pdb format.