Configuration
You configure a scan by choosing settings that best describe your application, and the kind of testing you want.
- Scan Configuration Wizards
  You can quickly configure basic scans using the wizards.
- Scan Configuration Dialog Box
  - URL and Servers view
    Configure the Starting URL for the svcan, and any additional servers and domains to be included.
  - Login Management view
    Show AppScan® how to log in to your application.
  - One-Time Password (OTP) view
    Configure AppScan® to use OTP (a kind of multi-factor authentication, or MFA) when logging in.
  - Environment Definition view
    Environment definition is not essential, but enables AppScan® to safely refrain from sending non-relevant tests during the scan, resulting in a faster and more accurate scan.
  - Exclude Paths and Files view
    You can configure AppScan to ignore certain paths in the application, or specific types of file.
  - Explore Options view
    Define scan limits, link extraction methods and the general Explore method.
  - Parameters and Cookies view
    Identify session IDs and list parameters to exclude from the scan.
  - Automatic Form Filler view
    Provide AppScan® with valid parameter values for filling forms in your application during the scan.
  - Error Pages view
    Add strings, regular expressions and URLs to identify your application's custom error pages.
  - Multi-Step Operations view
    Record and manage multi-step operations that are required to reach specifica parts of the application that could otherwise be missed.
  - Content-Based Results view
    Define a logical structure for the application tree, if AppScan® will not be able to do this based on URL structure.
  - Communication and Proxy view
    Configure communication timeout and proxy server settings.
  - HTTP Authentication view
    Add server-level authentication and client-side certificates, if required by the application.
  - 3rd Party Authentication view
    3rd Party Authentication view of the Configuration dialog box lets you configure AWS settings.
  - Test Policy view
    Define and edit the collection of tests that will be sent to the application during testing; the test policy.
  - Test Optimization view
    Apply optimization for faster scans at times in the product lifecycle when speed is more important to you than scan depth.
  - Test Options view
    Additional test options.
  - Privilege Escalation view
    Refer AppScan to scans run using different user privileges, to discover privileged resources that may be accessible to users with insufficient privileges.
  - Advanced Configuration view
    This view gives you access to many advanced registry settings and it should only be used by experienced AppScan users, or when instructed to do so by the support team to troubleshoot a problem.
- Scan using a Postman Collection
  If you have a Postman Collection of requests to your web API, you can import it and use it as the basis for a scan.
- Scan file structure
  Explains the basic structure of an AppScan Standard SCAN file.
- Scan templates
  A scan template is simply a scan configuration that has been saved so that you can use it again.
- Changing the configuration during a scan

3rd Party Authentication view

3rd Party Authentication view of the Configuration dialog box lets you configure AWS settings.

Most requests to AWS must be signed with an AWS Signature Version 4 access key, which consists of an access key ID and secret access key. You must provide these to AppScan so it its requests will not be denied.

If requests to your AWS application require AWS Signature Version 4, AppScan must be able add this to its requests. The following information is required for this:

Default:
- Access key
- Secret key
- Region (the region that houses the service, for example: us-east-2)
- Service (the service code, for example: s3, see below for more details)
Cognito:
- Identity pool ID
- Region (the region that houses the service, for example: us-east-2)
- Service (the service code, for example: s3, see below for more details)

The keys and ID are encrypted and not readable in the saved scan template file (SCANT).

What is my service code?

The code for your AWS endpoint service is the segment that precedes amazonaws.com or the region code in the AWS host name. For example, s3 is the endpoint service for both https://<account-id>.s3-control.eu-north-1.amazonaws.com and https://s3.us-east-2.amazonaws.com host names. For more information, see Service endpoints and quotas in AWS.

Restricting AWS to specific parts of the site

By default, the AWS settings are used for the entire site. If AWS is used for only parts of the site,you can define them in the lower pane. You can define URLs, paths and/or folders.

To restrict AWS to part of the site:

Click
In the Add path dialog, enter a single URL, path, or folder, and click OK.
Repeat to define all parts of the site that use AWS.