Home
Reference
Review reference information for HCL® AppScan® Source, including using utilities, plug-ins, and APIs.
AppScan® Source Data Access API
The Data Access API provides access to AppScan® Source-generated assessment results, including findings and finding details. It also provides access to assessment metrics such as analysis date and time, lines of code, V-density, and number of findings.

Welcome
Welcome to the documentation for HCL® AppScan® Source.
What's New
Explore these new features that have been added to AppScan® Source - and note any features and capabilities that have been deprecated in this release.
Installing
Learn how to install, upgrade, and activate HCL® AppScan® Source.
Configuring
Learn how to configure applications, folders, and projects, and set attributes and properties in HCL® AppScan® Source.
Administering
Learn how to administer user accounts and permissions, audit user activity, and manage integrations in HCL® AppScan® Source.
Scanning
This section explains how to scan your source code and manage assessments in HCL® AppScan® Source.
Triage and analysis
Grouping similar findings allows security analysts or IT auditors to segment and triage source code problems. This section explains how to triage AppScan® Source assessments and analyze results.
Reporting
Security analysts and risk managers can access reports of select findings or a series of audit reports that measure compliance with software security best practices and regulatory requirements. This section explains how to create reports of aggregate finding data.
Extending product function
Learn how to extend the product to meet specific development requirements.
Reference
Review reference information for HCL® AppScan® Source, including using utilities, plug-ins, and APIs.
- The Ounce/Make build utility
  Ounce/Make is a tool that automates the importing of configuration information into AppScan® Source from build environments that use makefile. Ounce/Make eliminates the need to import configuration information from makefiles manually; this the recommended method of configuring these projects.
- AppScan® Source command line interface (CLI)
  The CLI is an interface to core AppScan® Source functionality.
- The Ounce/Ant build tool
  This section describes how to use Ounce/Ant, an AppScan® Source build utility that integrates AppScan Source and Apache Ant. Integrating Ounce/Ant with your Ant environment helps you automate builds and code assessments.
- AppScan® Source Data Access API
  The Data Access API provides access to AppScan® Source-generated assessment results, including findings and finding details. It also provides access to assessment metrics such as analysis date and time, lines of code, V-density, and number of findings.
  - Data Access API object model
  - Using the Data Access API
    You can find complete examples for a number of Data Access API scenarios in the SamplePublished.java and SampleSdk.java files included in <install_dir>\sdk\sample\com\ouncelabs\sdk\sample (where <install_dir> is the location of your AppScan® Source installation).
  - Data Access API classes and methods
  - Ounce/Maven plug-in
    This section describes the Ounce/Maven plug-in, which uses Maven, an Apache build tool, to integrate AppScan® Source into the Maven workflow.
  - AppScan® Source for Automation
    The Automation Server (ounceautod) allows you to automate key aspects of the AppScan® Source workflow and integrate security with build environments during the software development life cycle (SDLC). The Automation Server allows you to queue requests to scan and publish assessments, and generate reports on the security of application code.
  - Framework for Frameworks handling APIs
    AppScan® Source provides a set of Java™ APIs that allow you to add support for frameworks that are used in your applications. The classes and methods offered in these APIs allow you to account for frameworks for which built-in support is not provided.
  - AppScan® Source client component error messages
  - AppScan® Source for Analysis samples
    AppScan® Source for Analysis includes a sample applicationsample applications that you can use to familiarize yourself with the product.
  - The AppScan® Source for Analysis work environment
    To get the most out of AppScan® Source, you should understand the basic concepts behind the AppScan Source for Analysis working environment and how to use the options that best fit your workflow.
  - Views and windows
    AppScan® Source for Development views and windows provide alternative presentations of findings, support code editing, and allow you to navigate the information in your workbench. A view might appear by itself, or stacked with other views in a tabbed notebook. You can change the layout of a perspective or window layout by opening and closing views and by docking them in different positions in the Workbench window.
  - CWE support
    The Common Weakness Enumeration (CWE) is an industry standard list that provides common names for publicly known software weaknesses. This topic lists the CWE IDs that are supported in the current version of AppScan® Source.
- Glossary
  Learn common product terminology.
Troubleshooting and support
Self-help information, resources, and tools to help you troubleshoot issues while using HCL® AppScan® Source.

AppScan® Source Data Access API

The Data Access API provides access to AppScan® Source-generated assessment results, including findings and finding details. It also provides access to assessment metrics such as analysis date and time, lines of code, V-density, and number of findings.

The Data Access API is included with the installation of these AppScan® Source components:

AppScan® Source for Analysis
AppScan® Source command line interface (CLI)

The Data Access API is installed as <install_dir>\sdk\ouncesdk.jar on Windows and <install_dir>/sdk/ouncesdk.jar on Linux (where <install_dir> is the location of your AppScan® Source installation).

The Data Access API requires JDK 11 or later.

On Windows: When running a program that uses the SDK, specify these Java™ Virtual Machine (JVM) arguments on the command line:

java -classpath 
<install_dir>\lib\avalon-framework-4.1.5.jar;
<install_dir>\lib\commons-lang3-3.3.2.jar;
<install_dir>\lib\icu4j-52_1.jar;
<install_dir>\lib\jacorb.jar;
<install_dir>\lib\log4j-api-2.17.1.jar;
<install_dir>\lib\log4j-core-2.17.1.jar;
<install_dir>\lib\logkit-1.2.jar;
<install_dir>\sdk\ouncesdk.jar;
<install_dir>\lib\xml-apis.jar;
<install_dir>\lib\saxon9.jar
<install_dir>\lib\j11_lib*
<install_dir>\lib\jackson-core-2.15.0.jar
<install_dir>\lib\jackson-databind-2.15.0.jar:
<install_dir>\lib\jackson-annotations-2.15.0.jar
... com.company.product.ClassName

On Linux: When running a program that uses the SDK, specify these Java™ Virtual Machine (JVM) arguments on the command line:

java -classpath 
<install_dir>/lib/avalon-framework-4.1.5.jar:
<install_dir>/lib/commons-lang3-3.3.2.jar:
<install_dir>/lib/icu4j-52_1.jar:
<install_dir>/lib/jacorb.jar:
<install_dir>/lib/log4j-api-2.17.1.jar;
<install_dir>/lib/log4j-core-2.17.1.jar;
<install_dir>/lib/logkit-1.2.jar:
<install_dir>/sdk/ouncesdk.jar:
<install_dir>/lib/xml-apis.jar:
<install_dir>/lib/saxon9.jar
<install_dir>/lib/j11_lib/*
<install_dir>/lib/jackson-core-2.15.0.jar
<install_dir>/lib/jackson-databind-2.15.0.jar:
<install_dir>/lib/jackson-annotations-2.15.0.jar
... com.company.product.ClassName