Configuring
Learn how to configure the product.
- Configuring your user settings
  There are several settings that you can personalize for your needs.
- Configuring the Enterprise Console
  The Enterprise Console is the main user interface that supports administration, item configuration, and reporting.
  - Identifying the servers and domains in your installation
    Servers and domains are considered global properties. When you add a Starting URL to a content scan job, its domain is automatically added to the Servers and Domains page on the Administration tab. Any job that uses that domain will have the same properties and rules applied to the URLs that it finds.
  - Scheduling blackout periods for a domain
    If you have regularly scheduled site maintenance periods, use a blackout period to suspend the content scan job so your site is not scanned while you are performing maintenance tasks. You can also use a blackout period for those times when your website is subject to heavy visitor traffic. Job and system administrators can schedule and override blackout periods if necessary.
  - Configuring defect tracking integration
    If you use Rational Team Concert™ or Rational® Quality Manager, you can configure defect tracking integration so that issues can be submitted as defects from reports from the Scans view. If you want users to submit issues as defects from an application in the Monitor view, do not configure Rational Team Concert in the Administration view. Instead, configure the integration from the Monitor view.
  - Capturing Traffic and Actions using AppScan Activity Recorder
  - Capturing and Importing Traffic Data
  - Configuring a proxy for the AppScan Dynamic Analysis Client
    Configure the proxy for the AppScan Dynamic Analysis Client and test the connection. This proxy is used to import .scant templates from AppScan Standard. After the .scant template is imported, the security analyst can use it to create a QuickScan template.
  - Capturing Traffic and Actions using AppScan Activity Recorder
  - Test Automation in AppScan® Enterprise using AppScan Traffic Recorder
    The AppScan Traffic Recorder enables you to record traffic to use as Explore data in your AppScan Enterprise (ASE) job. The AppScan Traffic Recorder is a system for managing traffic recorder instances. Traffic recorder instances can be created on demand to record traffic that will later be used for a DAST scan. This document describes how to set up and use the traffic recorder.
  - Updating security rules
    The security rules are updated as a part of your AppScan® Enterprise releases. You can verify the version and release date of the security rules by looking in the About link in the AppScan Enterprise main menu.
- Configuring log retention period property
  The log files generated during a scan run are saved in the server for certain time frame. The time limit until when such log files are retained by the server is referred as log retention period. After this retention period, these log files become outdated while redundantly occupying memory space in the server. You can configure a time limit as a log retention period in the AppScan Enterprise, to automatically delete such log files after this preset period exceeds.

Configuring the Enterprise Console

The Enterprise Console is the main user interface that supports administration, item configuration, and reporting.

Before you begin

The Enterprise Console settings must be configured so users can:

receive alerts for job, report pack or dashboard events
use server-dependant components such as Manual Explore and Recorded Login

Procedure

Log in to the Enterprise Console from your web browser.
Go to the General Settings page of the Administration view, and click Edit in the Enterprise Console Settings section.
Enter an SMTP server name and SMTP server port (typically 25).
Enter the URL of the Enterprise Console instance, for example, https://<ServerName>/<product name>/.
Note: Do not use localhost or 127.0.0.1 as the server name in the instance URL, or Manual Explore and Recorded Login will not work.
(Windows™ authentication): Enter the name of the LDAP server or domain and LDAP group query used to retrieve user group information.
Select the amount of time to keep issue data in the database.
If you manage issues in AppScan Enterprise, leave the Use settings from imported file check box unchecked so that issue attributes, such as the status and severity of existing vulnerabilities, will not be overwritten when you import a file from other AppScan products. Select the check box if you manage the status and severity of the vulnerabilities outside of AppScan Enterprise so that when the file is imported, those settings are taken from the imported file.
(Optional) Enable enhanced security. This option enforces FIPS 140-2 compliance.
Note: If this option is enabled, some functionality that is not FIPS 140-2 compliant will not work as expected or will be disabled, including the Manual Explore plugin.
Click Done.