Home
Administering
Learn how to administer the product.
Administering AppScan® Source
This section explains user management, permissions, application and project registration, and port configuration.
Using AppScan® Source for Analysis in standalone mode
You can use AppScan® Source for Analysis while not connected to an AppScan Enterprise or the AppScan Database Service. However, you will be unable to share scans or assessments with other AppScan Source clients.

Administering
Learn how to administer the product.
- Administering AppScan® Source
  This section explains user management, permissions, application and project registration, and port configuration.
  - User accounts and permissions
    Before AppScan® Source users can begin to scan or triage results, an administrator must create user accounts and assign permissions to the accounts.
  - Using AppScan® Source for Analysis in standalone mode
    You can use AppScan® Source for Analysis while not connected to an AppScan Enterprise or the AppScan Database Service. However, you will be unable to share scans or assessments with other AppScan Source clients.
  - Creating AppScan® Source users
    Typically, administrators will have users log in to AppScan® Source products with their AppScan Enterprise Server credentials. However, if there is cause for having AppScan Source users that do not exist in the AppScan Enterprise Server, administrators can create local AppScan Source users, according to the instructions in this topic.
- Auditing user activity
  AppScan® Source offers a convenient location for auditing user activity. The Audit view logs events such as authentication to the AppScan Enterprise Server, the creation of new users, and the creation of new rules in the database.
- Logging in to AppScan® Enterprise Server from AppScan® Source products
  Most AppScan® Source products and components require a connection to an AppScan Enterprise Server. The server provides centralized user management capabilities and a mechanism for sharing assessments. All user management occurs in AppScan Enterprise.
- LDAP integration
  To add an AppScan® Source user that will be authenticated via LDAP, you must have configured the AppScan Enterprise Server user repository to use an LDAP repository.
- Registering applications and projects for publishing to AppScan® Source
- 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.
- Port configuration

Using AppScan® Source for Analysis in standalone mode

You can use AppScan® Source for Analysis while not connected to an AppScan® Enterprise or the AppScan® Database Service. However, you will be unable to share scans or assessments with other AppScan® Source clients.

Standalone functionality

Choose Standalone Mode for AppScan® Source for Analysis at installation.

When you choose standalone mode at installation, login to AppScan® Enterprise is not required as there is no database authentication. However, a valid AppScan® Source license is required.

Using AppScan® Source for Analysis in standalone mode is much like using it in connected mode for performing scans and managing assessments, with the following distinctions:

Scan configurations can be saved locally and shared when connected.
Filters can be saved locally and shared when connected.
Assessments can be saved locally and published when connected. Publishing results is allowed as long as AppScan Enterprise server is configured.
Pattern rules can be saved locally but cannot be shared when connected.
Custom rules can be saved locally but cannot be share when connected.
Scan configurations, filters, assessments, pattern rules, and custom rules created by other AppScan Source users cannot be shared with you.

Switching between connected and disconnected mode

CAUTION: Choose your connection mode at installation carefully. We do not recommend switching between connected and standalone mode. If you must change from standalone mode to connected mode, reinstalling AppScan® Source for Analysis is the preferred method to do so.

You can switch between disconnected and connected mode by editing the connect_mode paramater in the ounce.ozsetting file:

Setting connect_mode to true indicates AppScan® Source for Analysis will start in connected mode, requiring a connection and login to AppScan Enterprise. True is the default.
Setting connecct_mode to false indicates AppScan® Source will start in disconnected mode. A connection and login to AppScan Enterprise is not required.

After editing this setting, you must restart AppScan® Source for Analysis.