Home
Managing application risk
Follow this workflow to manage application security risks in your organization.
Step 2: Testing applications for vulnerabilities
Learn how to test vulnerabilities identified in an application.
Scenarios for creating scans
These scenarios are targeted at developers and the security team. Choose the user role that most closely matches your situation.
Security Team
Using scan configuration authored in AppScan standard, the security team creates templates.
Editing a developer's scan
As a security analyst, you might have to help a developer to edit a basic scan they created. In the AppScan Dynamic Analysis Client, you can see scan configuration options that a developer cannot see.

Managing application risk
Follow this workflow to manage application security risks in your organization.
- Step 1: Creating an application inventory
  Learn how to create an application inventory.
- Step 2: Testing applications for vulnerabilities
  Learn how to test vulnerabilities identified in an application.
  - Importing issues from third-party scanners
    Learn how to import issues from 3rd-party scanners.
  - Scenarios for creating scans
    These scenarios are targeted at developers and the security team. Choose the user role that most closely matches your situation.
    - Overview of scan configuration differences in v9.0.2 and higher and in previous versions
      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.
    - Developers
      The developer team creates scan templates using different methods and user interfaces in AppScan.
    - Security Team
      Using scan configuration authored in AppScan standard, the security team creates templates.
      - Creating scan templates
        This topic helps security team to learn creating scan templates.
      - Creating a scan
        Learn how to create a scan.
      - Editing a developer's scan
        As a security analyst, you might have to help a developer to edit a basic scan they created. In the AppScan Dynamic Analysis Client, you can see scan configuration options that a developer cannot see.
      - Filtering similar pages based on structure (DOM)
        Page Structure (DOM) Filtering can greatly reduce scan time by identifying pages that are similar enough to pages already scanned, that they can safely be ignored. AppScan compares new pages with those pages already scanned for structural (DOM) similarity, which indicates the new page contains no new links or contains content that requires more testing. For example, on a commercial site there might be a catalog with individual pages for a thousand different items that are identical in all other ways. There is usually no need to scan all of those pages. Filtering based on DOM similarity can greatly reduce scan time.
    - Converting scan configurations from AppScan® Standard in the AppScan® Dynamic Analysis Client
      If you have an existing content scan that is based on a scan template (*.scant) from AppScan® Standard, you can convert the scan configuration so that you can edit it directly in the AppScan Dynamic Analysis Client. However, after you convert the scan configuration, you cannot open it again in AppScan Standard.
  - Running and scheduling jobs
    Learn how to run and schedule a job in AppScan Enterprise.
  - Copying a scan between two Enterprise Consoles
    Export scan properties and creating a new scan based on those properties. This is the method you use to copy a scan between two Enterprise Console instances.
  - Stopping a job and then resuming it
    There are three methods you can use to stop a job while it is running. Each method is used for a different reason, which largely depends on whether you want to keep the data or you want to continue running the job from the point where it left off. You can resume a suspended job to continue the scan from where it stopped. A resumed job is handled by the next free agent on any available agent server.
- Step 3: Determining risks and prioritizing vulnerabilities
  Learn how to determine risks and prioritize vulnerabilities identified in an application.
- Step 4: Remediating risks
  Learn how to remediate risks identified in an application.
- Step 5: Measuring progress and demonstrating compliance
  Learn how to measure progress and demonstrate compliance.

Editing a developer's scan

As a security analyst, you might have to help a developer to edit a basic scan they created. In the AppScan Dynamic Analysis Client, you can see scan configuration options that a developer cannot see.

About this task

Procedure

Go to the Scans view.
In the relevant folder, click Edit for the scan you want to edit.
On the Setup tab of the scan, click Edit.
On the Start page of the AppScan Dynamic Analysis Client, select Update Existing Job, go to the applicable folder and select the scan.
Make your modifications and click Update Job.