Home
Scanning and monitoring
Learn how to run scans and IAST monitoring sessions on your apps, and import issues from 3rd party scanners.
Static (SAST) scanning
Use static analysis to scan applications for security vulnerabilities. To accomplish this, either use AppScan Go! or download a small client utility and use its command line interface (CLI) perform security analysis on on either source code or binary files for all supported languages. Static analysis plug-ins for Eclipse, IntelliJ IDEA, and Visual Studio are available through their respective marketplaces. Once plugins are installed, you can scan Java projects in Eclipse and IntelliJ IDEA, or .NET (C#, ASP.NET, VB.NET) projects in Visual Studio. Additional information on plugins and integrations is listed here.
System requirements for static analysis
This section describes the supported operating systems and the types of files, locations, and projects that can be scanned by ASoC when you perform static analysis.

Scanning and monitoring
Learn how to run scans and IAST monitoring sessions on your apps, and import issues from 3rd party scanners.
- Sample apps and scripts
  Use these sample applications to practice scanning with ASoC.
- Dynamic (DAST) scanning
  ASoC can perform dynamic analysis of an application that runs in a browser. Use the configuration options available in ASoC, or upload an AppScan Standard configuration.
- Static (SAST) scanning
  Use static analysis to scan applications for security vulnerabilities. To accomplish this, either use AppScan Go! or download a small client utility and use its command line interface (CLI) perform security analysis on on either source code or binary files for all supported languages. Static analysis plug-ins for Eclipse, IntelliJ IDEA, and Visual Studio are available through their respective marketplaces. Once plugins are installed, you can scan Java projects in Eclipse and IntelliJ IDEA, or .NET (C#, ASP.NET, VB.NET) projects in Visual Studio. Additional information on plugins and integrations is listed here.
  - Setting up the Static Analyzer Command Line Utility
    For static analysis, you 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.
  - System requirements for static analysis
    This section describes the 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
      This topic describes the supported types of files that can be scanned by ASoC when you perform static analysis.
    - Static analysis client support
      This topics describes the supported operating systems and the types projects that can be scanned by ASoC when you perform static analysis.
  - 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.
- Open source testing
  Open source testing locates and analyzes open source packages in your code. Our Software Composition Analysis (SCA) aggregates information from a variety of sources, constantly monitoring for new vulnerabilities in an automated process that keeps our information up-to-date daily. Sources include the most popular security vulnerability databases (NVD, Github advisory, Microsoft MSRC), and a wide range of lesser-known security advisories and open source project issue trackers.
- Interactive (IAST) monitoring
  ASoC can monitor normal application runtime behavior, to detect vulnerabilities.
- Scan status
- Personal scans
  A personal scan is a way of evaluating the relative security of an application in development without affecting overall application scan data, or compliance.
- Private sites
  An AppScan Presence on your server enables you to scan sites not accessible from the Internet.

System requirements for static analysis

This section describes the supported operating systems and the types of files, locations, and projects that can be scanned by ASoC when you perform static analysis.

The Static Analyzer Command Line Utility (SAClientUtil) is updated regularly for a variety of reasons, including:

New language support
Updated language support (new files types associated with supported languages, for example)
New features
Fixes

When a Static Analyzer Command Line Utility update impacts system requirements and/or language support, the updated information is reflected in this section in addition to being listed in Recent updates.