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
When the .pdb file is in the wrong format, .NET scan results can show the assembly file instead of the source file.

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
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.
- 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.
  - Errors or warnings occur when generating a static analysis IRX file
  - .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.
  - 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
  - Issues with per user installation of AppScan Go! on Windows 7
  - Unable to connect to AppScan 360° from AppScan Go!
  - IRX file is too large to analyze
Results
The Scan History tab of your application displays your scan results (including scan statistics) and rescan options.
Reference
Some frequently asked questions, and information about integrating AppScan 360° into the product lifecycle (SDLC).

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