How to Use Scan Scope

You can use scan scope to decide which URLs are attacked or crawled. You can set the app level URLs within the app or set the scan config URLs from within the scan config.

Set app-level scan scope

You create the app-level scan scope when you add an app. Go to Apps and click Add App > Target Domains.

InsightAppSec Add New App

The URLs specified for the app are added in Target Domains. These URLs make up the seed URLs for a scan. Any scans on an app will use the app-level URLs as seed URLs.

App scan scope behavior

When you add an app-level URL, default crawling and attack restrictions are added. A wildcard is added after the domain URL.

The wildcard is added to the top level domain.




Set scan config scan scope

You can establish additional scan URLs for each app. Go to **Scan Scope **and click Scan URLs.

InsightAppSec Scan Scope URLs


  • App URLs - The URLs that were set when the app was created. Any scans run from the App will use the App URLs as the seed or base URL.
  • Scan Config URLs - Add more seed URLs that only apply to this config. You can choose a protocol (HTTP or HTTPS), subdomain (such as www or api), and sub-pages. You can add one URL at a time or type in a list of URLs.

Scan scope inheritance

The way you set up your scan determines how seed URLs are inherited.

Example 1

The scan config level will override the app level URL.

Example 2

The scan will ignore http://domain.com/login.php

Scan scope configuration example

In this section, we cover different app-level and scan-level configurations along with the expected behavior for each configuration.

Crawl 2 pages

Use this configuration if you only need to crawl 2 pages in your app.

For example:

  1. Create your app with your URL.

InsightAppSec Add New App

  1. Go to Scan Scope > Scan URLs and add your target URLs.

InsightAppSec Scan Scope Configure URLs

  1. Go to the Crawling Restrictions tab and exclude all site URLs using a wildcard, then add each page your want to scan.

For example:

InsightAppSec Scan Scope Crawling Restrictions

The scan will only include the pages specified.

Scan 2 directories

Use this configuration if you need to scan 2 directories in your app, but you only want to attack the pages in 1 directory.

For example:

  1. Create your app with your URL.

InsighAppSec Add New Image

  1. Go to Scan Scope > Scan URLs and add the subdirectories that you want to target.

For example:

InsighAppSec Scan Scope URLs

  1. Click the Crawl Restrictions tab and add your 3 restrictions. One should exclude the site with a wildcard, while 2 should include the subdirectories to scan with a wildcard.

For example:

InsightAppSec Scan Scope Crawling

  1. Click the Attack Restrictions tab and add 3 new constraints. This is where you will only attack the pages in one directory. One will include the subdirectory to attack, the other 2 will exclude the site and other subdirectory.

For example:

Insight AppSec Scan Scope Attack

  1. Run your scan.

Only the pages included in the Attack Restrictions will be attacked, but both subdirectories will be crawled.

Scan you app and restrict 1 directory from attacks

Use this configuration if you need to scan your app, but want to restrict a directory from attacks.

  1. Create your app with your URL.

For example:

InsightAppSec Add New App

  1. Go to Scan Scope > Scan URLs and add the subdirectories that you want to target.

InsightAppSec Scan Scope Scan URLs

  1. Click the Attack Restrictions tab and one new constraint that excludes your directory with a wildcard and includes the app URL as a wildcard.

For example:

InsightAppSec Scan Scope Attack CORS

  1. Run your scan.

The whole site will be crawled, but pages within the CORS directory will not be attacked.