Learn how to administer the product.
Learn how to create scan templates in AppScan Enterprise.
Learn how to manage user groups and access permission.
Administrators can configure the settings for log files for the Enterprise Console and AppScan Server and download them when they need to troubleshoot issues. This function eliminates the need to search the file system of the computer where the Enterprise Console or AppScan Server is installed.
Create an Activity Log report to determine who is using AppScan Enterprise and what they are doing with it. The report lists the users that made changes and when the changes were made. Because the log is always recording activity, all you must do is create the report. Only Administrators can create the Activity Log report; however, any user can be given access to it as part of a report pack's properties. If you do not want other users to see the Activity Log report, change `All Other Users' to No Access on the Users and Groups page for the report pack.
Product Administrators are responsible for managing each server to its optimal performance.
See the status of scan jobs currently running or waiting to run so that you can prioritize the order in which your key scan jobs run. For example, you might have scan jobs that are part of a time-sensitive deliverable, like a holiday shopping special. You can move them to the top of the queue to make sure that they are prioritized first in the schedule.
Make sure that you must have the latest version of AppScan® Enterprise (including Fixpacks and iFixes) before you update to the latest security rules. You can verify the version and release date of the security rules by looking in the About link in the AppScan Enterprise main menu.
AppScan® Standard provides a database of thousands of tests. However, if your web application has issues that are specific to it, or if you want to write your own advisories for fixing issues, you can create your own tests. These tests are saved and included in your AppScan database of tests. You can also export them as a *.udt file to import into AppScan Enterprise.
SQL Server database maintenance includes upgrading SQL servers, SQL database backup, log file configuration, and database usage.
Learn how to prepare for security testing in AppScan Enterprise.
The security team (whose members have Administrator privileges) creates templates by using scan configuration that they author in AppScan Standard. The scan template file is then available for use in AppScan Enterprise. Developers (with QuickScan user privileges) pick up the template when they create a scan, and use a wizard in the new AppScan Dynamic Analysis Client to finish the scan creation. They use the same Client when they need to amend the scan configuration.
Starting in v9.0.2, the security team can create a scan template based on scan configuration options in AppScan Standard. Developers modify these templates in the AppScan Dynamic Analysis Client to create scans. The AppScan Dynamic Analysis Client uses the same scan configuration options that are used in AppScan Standard, including action-based login and manual explore.