Review reference information for HCL® AppScan® Source, including using utilities, plug-ins, and APIs.
The CLI is an interface to core AppScan® Source functionality.
login_local (local)
Welcome to the documentation for HCL® 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.
Learn how to install, upgrade, and activate HCL® AppScan® Source.
Learn how to configure applications and projects, and set attributes and properties in HCL® AppScan® Source.
Learn how to administer user accounts and permissions, audit user activity, and manage integrations in HCL® AppScan® Source.
This section explains how to scan your source code and manage assessments in HCL® AppScan® Source.
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.
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.
Learn how to extend the product to meet specific development requirements.
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.
makefile
makefiles
Many CLI commands require that you have the appropriate AppScan® Source permissions.
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.
about (a)
clearcache (cc)
delete (del)
deleteassess (da)
deleteuser (du)
delvar (dv)
details (det)
echo
export (expt)
getaseinfo (gase)
help (?)
import (im)
info (i)
list (ls, dir)
listassess (la)
listgroups (lgrp)
listusers (lu)
log
login (in)
login_file
logout (out)
moduser (mu)
newuser (nu)
openapplication (oa)
openassessmentfile (oaf)
openfolder (of)
password (passwd)
printuser (pu)
publishassess (pa)
publishassessase (pase)
quit
record (rc)
refresh (rf)
register (reg)
removeassess (da)
report (rpt)
scan (sc)
script (scr)
setaseinfo (sase)
If your AppScan® Enterprise Server has been installed with the AppScan Enterprise Console option, you can publish assessments to it. The Enterprise Console offers a variety of tools for working with your assessments - such as reporting features, issue management, trend analysis, and dashboards.
setcurrentobject (set, cd)
setvar (sv)
unregister (unreg)
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.
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.
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.
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.
Learn common product terminology.
Self-help information, resources, and tools to help you troubleshoot issues while using HCL® AppScan® Source.
Deprecated in AppScan® Source Version 6. Use login (in).