Home
Configuring
Learn how to configure applications and projects, and set attributes and properties in HCL® AppScan® Source.
Configuring applications and projects
Before you scan, you must configure applications and projects. This section explains the Application Discovery Assistant, New Application Wizard, and the New Project Wizard. You will learn how to configure attributes for AppScan® Source for Analysis. In addition, this section teaches you how to add existing applications and projects for scanning - and how to add files to projects.
Configuring your development environment for Eclipse projects
Before you import an Eclipse project, you must properly configure the development environment. Although Eclipse is the basis for each project type, AppScan® Source distinguishes between the different versions.
Eclipse workspace importers: Eclipse preference configuration
The AppScan® Source for Analysis installation provides a default Eclipse importer. This importer identifies the location of Eclipse and the JRE. If the default Eclipse importer is unable to import your workspace, it may be necessary to create a new Eclipse importer.

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 and projects, and set attributes and properties in HCL® AppScan® Source.
- Configuring applications and projects
  Before you scan, you must configure applications and projects. This section explains the Application Discovery Assistant, New Application Wizard, and the New Project Wizard. You will learn how to configure attributes for AppScan® Source for Analysis. In addition, this section teaches you how to add existing applications and projects for scanning - and how to add files to projects.
  - AppScan® Source application and project files
    AppScan® Source applications and projects have corresponding files that maintain configuration information required for scanning, as well as triage customization. It is recommended that these files reside in the same directory as the source code, since configuration information (dependencies, compiler options, and so forth) required to build the projects is very similar to that required for AppScan Source to scan them successfully. Best practice includes managing these files with your source control system.
  - Configuring applications
    You can use the New Application Wizard or the Application Discovery Assistant to create applications. The Application Discovery Assistant automates application setup for you, whereas the New Application Wizard allows you to add applications, guiding you through the configuration process. The wizard helps you manually create a project or add existing projects to an application. This section describes these two methods for adding application and basic configuration tasks.
  - Configuring your development environment for Eclipse projects
    Before you import an Eclipse project, you must properly configure the development environment. Although Eclipse is the basis for each project type, AppScan® Source distinguishes between the different versions.
    - Eclipse or Application Developer updates
      For Eclipse or Application Developer environments external to AppScan® Source, you must make sure that you have the appropriate software updates installed. These instructions explain how to obtain and install the updates. The procedure may vary for different versions.
    - Eclipse workspace importers: Eclipse preference configuration
      The AppScan® Source for Analysis installation provides a default Eclipse importer. This importer identifies the location of Eclipse and the JRE. If the default Eclipse importer is unable to import your workspace, it may be necessary to create a new Eclipse importer.
  - Creating a new project for an application
    After you add an application, you add projects to it.
  - Copying projects
    AppScan® Source for Analysis allows you to copy all project types except .NET projects. Modifications to the project do not affect the duplicated project; after you copy a project, there is no connection between the original project and the copied project. When you copy an imported project, you create an AppScan Source project file (.ppf) with all configuration information.
  - Modifying application and project properties
    When you select an application or project in the Explorer view, the current properties appear in the Properties view, where you can make modifications.
  - Global attributes
    Global attributes must be defined before they can be associated with individual applications. Global attributes are defined in the Properties view by selecting All Applications in the Explorer view.
  - Application attributes
    Application attributes apply to the currently-selected application and depend on previously created global attributes.
  - Removing applications and projects
    You can remove applications and projects from AppScan® Source for Analysis if they are not registered.
  - Explorer view
    The Explorer view contains a Quick Start section at the top - and an explorer section at the bottom which contains one node, All Applications. The Quick Start section contains several useful links that launch common actions. The explorer section consists of a tree pane that provides a hierarchical view of your resources: applications, projects, directories, and project files, with All Applications as its root. You navigate these resources much like a file browser. As you navigate the view, the selection state of the tree determines the available tabs in the Properties view.
- Preferences
  Preferences are personal choices about the appearance and operation of AppScan® Source for Analysis.
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.
Troubleshooting and support
Self-help information, resources, and tools to help you troubleshoot issues while using HCL® AppScan® Source.

Eclipse workspace importers: Eclipse preference configuration

The AppScan® Source for Analysis installation provides a default Eclipse importer. This importer identifies the location of Eclipse and the JRE. If the default Eclipse importer is unable to import your workspace, it may be necessary to create a new Eclipse importer.

Before you begin

Each importer configuration represents an installation of Eclipse. To use these configurations to import existing workspaces and projects to AppScan® Source for Analysis, you may also need to install the AppScan® Source for Development plug-ins into the Eclipse environment.

Before adding a workspace, you must create a configuration for the workspace type.

Procedure

In AppScan® Source for Analysis, select Edit > Preferences from the main workbench menu.
Select Eclipse Workspace Importers.
Click Create a new configuration and then complete the New Import Configuration dialog box to create a new configuration:
- Product: Select the appropriate product
  Note: If the product that was used to create the workspace is not available for selection, ensure that you have completed the configuration steps outlined in Eclipse or Application Developer updates before attempting to create the workspace importer.
- Name: Importer name
- Location: Path to the base directory of the Eclipse installation
- JRE Location: Path to the root directory of the Java™ Runtime Environment (JRE). Use a JDK in <install_dir>\JDKS (where <install_dir> is the location of your AppScan® Source installation) or any other preferred JDK.
Click OK.
To identify the importer as default, select it and click Make the selected configuration the default. This causes an icon to display in the importer's Default column.