Welcome
Welcome to the documentation for HCL® AppScan® Source.
Introduction to HCL® AppScan® Source
HCL® AppScan® Source delivers maximum value to every user in your organization who plays a role in software security. Whether a security analyst, quality assurance professional, developer, or executive, the AppScan Source products deliver the functionality, flexibility, and power you need - right to your desktop.
What's New in AppScan® Source
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 the product.
Configuring
Learn how to configure the product.
Administering
Learn how to administer the product.
Developing
Learn how to develop by using the product.
Extending product function
Learn how to extend the product.
Reference
Review reference information for the product.
- 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.
  - Objects and context
  - AppScan® Source command line interface (CLI) permissions
    Many CLI commands require that you have the appropriate AppScan® Source permissions.
  - Starting the AppScan® Source command line interface (CLI)
  - Command syntax
    AppScan® Source command line interface (CLI) commands conform to a usage template with required and optional arguments, similar to a command shell. CLI commands are not case sensitive and do not require switches for different arguments.
  - AppScan® Source command line interface (CLI) commands
  - Configuring a scan to run with the CLI
    You can use a configuration file to customize how a scan is run with the command line interface (using the scan command), wherein you can specify individual targets - or include or exclude targets. In addition, you can use the configuration file to specify additional information that would help to generate complete scan results.
  - Running automated assessments
    The AppScan® Source command line interface (CLI) enables you to automatically import an AppScan Source project file (.ppf) and scan your source code. From the command line, you can run a script, such as the following sample, Run_Assessments.txt.
- 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.
- Glossary
  Learn common product terminology.
Troubleshooting and support
There are a number of self-help information resources and tools to help you troubleshoot problems.

Objects and context

The AppScan® Source object tree

The object tree shows the basic structure of AppScan® Source objects. You can scan any object (applications, projects, or source files) within the tree structure.

Active objects and current context

Many AppScan® Source command line interface (CLI) commands act only within the current context; that is, within the current directory or on a specified file. Use the SetCurrentObject (SET, CD) command to move to the object before calling any command that requires a current context.

Additionally, some CLI commands only act on an active object; which may be the currently selected source file, project, or application with an assessment.