Configuring Scan Policies

Field

Description

Name

This is the name for the Scan Policy.

Description

This is a description that helps explain the policy's features to anyone else who may also use it.

Shared

Select to enable others to have access to the policy.

Item

Description

Generate Proof

Select Yes to enable the generation of proof for the current security check group (default: True).

Proof Sharing

Enable or disable sharing the same proof across vulnerabilities (default: True).

Only Run on the Start Path (RoR)

Select Yes to restrict attacking to the Start Path only. Otherwise, every directory will be attacked).

Resource Finder Limit

During the scan, Acunetix 360 tries to reveal some common directories that might not be publicly viewable. To do this, Acunetix 360 has a list of common directories. Enter a number to set the maximum number of hidden resources and folders to look for in each folder (default: 125).

Include/Exclude

This option is related to cookie-based checks. You can control which cookies will be included in cookie related security controls, such as checking cookie attributes:

• Select Include to include the specified cookie names in the security check
• Select Default to include all cookies

Cookie Names

Enter the cookie names that will be managed during the scan.

Check All Pages

Select True to conduct CORS checks on all pages. Otherwise only unique directories will be checked (default: True).

Prepend Original Value

Prepend the original value to the Cross Site Scripting payloads. This can make the scan more accurate.(default: False).

Attack Referer

You can use this option to opt out of attacking the Referer header. If the Referer value is required by the target application, you can disable it by selecting False (default: True).

Possible Admin Interface

This option controls whether Netsparker can detect possible administration pages in the scope HTML Content check group (default: Enabled).

Maximum Path Count

Enter a number to set the maximum number of paths to check against HTTP methods.

Database Type

Select which databases your application uses in order to tailor the SQL injection payloads to the specific database type.

Upload Folders

Acunetix 360 will search the uploaded files in these website directories. You can add more directories in a comma separated format.

Search Upload Folders

This determines whether the upload folders should be visited to locate the uploaded file (default: True).

Field

Description

Crawling Page Limit

Enter a number to set the maximum number of pages to crawl. Once this number is reached, Acunetix 360 ends the crawling phase (default: 7.500).

Maximum Signature

Enter a number to set the maximum number of samples to collect from pages with similar URL signatures (default: 9). The URL signature consists of path, HTTP method and parameter name. For instance /?name=one, /?name=two.

Maximum Page Visits

Enter a number to set the maximum number of times the crawler visits a page (e.g. /index.php or /page.php). If this number is exceeded, Acunetix 360 will stop crawling that page, even if there are new parameters that have not yet been crawled  (default: 40).

For further information, see Scanning Parameter-Based Navigation Websites.

Wait Resource Finder

Enable to ensure Acunetix 360 waits for the Resource Finder to finish before ending the crawling phase. Depending on the website, this search for hidden folders and resources can take a significant amount of time, perhaps longer than the crawling phase (default: Disabled).

Text Parser

Enable to ensure the static HTML/Text Parser can search for links in HTML comments and similar locations. The Text Parser cannot parse JavaScript  (default: Enabled).

Text Parser Extensions

The Text Parser parses files for links. If you want the Text Parser to find links in files with an extension that is not listed in the default extension list below, specify their extension in this setting. Separate extensions with a comma, whitespace, or semicolon.

Default extensions include:.asa, .asax, .ascx, .ashx, .asmx, .asp, .aspx, .cfc, .cfm, .cgi, .config, .dll, .htm, .html, .inc, .include, .js, .jsp, .php, .php3, .php5, .phtm, .phtml, .shtm, .shtml, .xhtm and .xhtml.

Parse SOAP Web Services

Check to enable SOAP Web Service discovery by parsing WSDL files (default: Enabled).

Parse REST Web Services

Check to enable REST Web Service discovery by parsing OpenAPI (Formerly Swagger) and WADL files (default: Enabled).

Parse URI Fragments

Check to enable parsing URI fragments to discover parameters in the fragment. For example: http://example.com/#page=foo.php (Default: Enabled)

Fallback to GET

Acunetix 360 uses HEAD requests to find hidden resources. Check to enable Acunetix 360 to fall back to GET requests when HEAD requests don't work. This might increase scan time  (default: Disabled).

Add Related Links

Check to specify whether all related links should be crawled when a new link is found (default: Enabled).

Enable Parameter-Based Navigation

Check to enable Parameter-Based Navigation if the target website uses parameter based navigation instead of pages to serve different content, for example e.g. /?page=home, /?page=contact instead of /home.php or /contact.php (default: Disabled).

Enable Query-Based Navigation

Check to enable that only query-string parameters will be recognized as navigation parameters. Navigational Parameter RegEx won’t match POST or other parameter types.

Navigational Parameter RegEx

Enter a regular expression. If a parameter name matches the regular expression, it will be considered as a navigational parameter.

For further information, see Scanning Parameter-Based Navigation Websites.

Maximum Page Visits

Enter a maximum number for visits to a page containing navigational parameters. This value must be between 1 and 1000.

Field

Description

Analyze JavaScript/AJAX

Check to enable Acunetix 360 to analyze JavaScript and AJAX to find relevant links and pages in the target application. This option is CPU-intensive. Please disable it if you experience performance issues (default: Enabled).

Select / Load  a Pre-defined Preset

Acunetix 360 can scan different kinds of JavaScript applications ranging from occasional JavaScript-generated content to large Single Page Applications.

The options are:

• Default
• SPA (Single Page Application)
• Large SPA

DOM Load Timeout

Enter a number to set the amount of time (milliseconds) to wait for the page to load, including the downloading and browser rendering time, before Acunetix 360 begins to analyze the JavaScript DOM simulation  (default: 30000 milliseconds).

DOM Simulation Timeout

Enter a number to set the amount of time (milliseconds) to wait before JavaScript ends DOM simulation. This is the timeout for the whole simulation operation of a single page. In case of a large application, it might not be feasible to scan all of the application since the parameters are typically identified until the timeout is reached. The value of this timeout can have an impact on the scan duration (default: 45000 milliseconds).

Interevent Timeout

Enter a number to set the amount of time (milliseconds) to wait after triggering a JavaScript event, before the next event is triggered. During this time, no other DOM/JS events will be triggered by the scanner. Increase this number if the target website has high latency AJAX calls that modify the DOM (default: 100 milliseconds).

Max Simulated Elements

Enter a number to set the maximum number of DOM elements the parser will simulate before terminating the simulation for this page  (default: 500).

Skip Threshold

Enter a number to set the number of elements to simulate before skipping elements. Enter '0' to disable sampling (default: 300).

Elements to Skip

Enter a number to set the number of elements to skip simulation after the Skip Threshold has been exceeded (default: 10).

This setting and Skip Threshold are used to specify how many elements should be parsed before the parser starts skipping (Elements to Skip) some elements. For example, if the Skip Threshold is set to 1000 and Elements to Skip is set to 10, after simulating 1000 elements, the parser will not simulate elements 1001 to 1009. Element 1010 will be simulated. The idea behind these settings is to diversify the simulation.

Max Modified Element Depth

Enter a number to limit the simulation to a set number of nested elements. The value must be between 0 and 100.

This setting specifies the maximum number of levels the DOM parser should follow when a DOM modification is triggered due to another simulation or modification. This can be used as a sort of infinite loop protection.

For example, imagine a case where a button is clicked and another button is created. When this new button is clicked it will create another one, and so on. This depth setting allows you to control the maximum depth that the simulation will go in such cases (default: 4).

Pre-simulation Wait

Enter a number to set the amount of time (milliseconds) the scanner should wait before starting the simulation, after the page has loaded (default: 0). This can be used to configure the scanner to wait for custom page loading logic of dynamic pages.

Exclude by CSS Selector

Exclude HTML elements such as logout buttons from event simulation by CSS selectors. All matched elements will be excluded with their children. To test, try your selector in the Developer Toolbar's Console Tab in the browser you use (press F12 to open it). After opening the Developer Toolbar’s Console Tab using the document.querySelectorAll JavaScript function, you can list the CSS selectors that you want to exclude. Please note that if the selector is not very specific i.e. many items match the selector at any time, it will affect scan performance (and possibly coverage) negatively.

Maximum Option Elements

Enter a number to set the maximum number of option elements, per select element, to simulate. The value must be between 1 and 1000. The suggested maximum is 20 (default: 10).

Persistent JavaScript Cookies

Enter the names of cookies (separated by semicolons) that are set in JavaScript via document.cookie and not from HTTP Headers, that should persist across authentication and DOM simulation.

Open Redirect Conf. Timeout

Enter a number to set the time (milliseconds) to wait before ending JavaScript DOM simulation for Open Redirection confirmation. The value must be between 1 and 21600000. (Default: 45000)

XSS Confirmation Timeout

Enter a number to set the time (milliseconds) to wait before ending JavaScript DOM simulation for XSS confirmation. The value must be between 1 and 21600000 (default: 45000).

Exclude by Javascript Events

Enter a JavaScript event that DOM excludes from the simulation. To enter multiple events, you can separate them via a comma.

Filter Document Events

Check to filter events that are attached to a document by name to a constant set (e.g. mousedown, keyup), to reduce triggered event counting during the simulation (default: Disabled).

Ignore document events

Check to ignore the triggering events that are attached to the document object (default: Disabled).

Filter Colon Events

Check to filter events that contain a colon (:) in their name, to reduce triggered event counting during the simulation. They are usually used by frameworks and would be triggered by other events (default: Disabled).

Extract Static Resources

Check to extract static resources from DOM elements (default: Enabled).

Allow Out-of-Scope XML HTTP Requests During Simulation

Check if the target website fails to load when some requests cannot be loaded because of the scan profile's out-of-scope settings (default: Enabled).

Generate Debug Info

Check to enable the debugger to generate debug information during the scan.

When this option is enabled, the DOM parser will write the diagnostics information to a log file in the scan folder, including data about the coverage. When this option is enabled, the scan may be slowed down and will use some additional disk space (default: None).

Block navigation on SPAs

Check to enable Invicti to block extra navigation on single-page applications.

Field                                

Description

Maximum Number of Parameters to Attack on a Single Page

Enter a number to set the maximum parameters Acunetix 360 should attack on a single page (default: 24).

Once the maximum is reached, Acunetix 360 will stop attacking that page.

Enable Proof Generation

Check to generate a Proof of Exploit after a vulnerability is confirmed  (default: Enabled).

Attack Parameter Names

Enable to generate extra attacks which place attack payloads into the name of a request parameter (default: Enabled).

Attack Referer Header

Enable to generate extra attacks which place attack payloads into the Referer header (default: Disabled).

Attack User-Agent Header

Enable to generate extra attacks which place attack payloads into the User-Agent header (default: Disabled).

Attack Cookies

Enable to generate extra attacks which place payloads on cookie name and values (default: Disabled).

Optimize Header Attacks

Enable to issue header attacks on each unique link path (otherwise, all links will be attacked) (default: Enabled).

Override Version Vulnerability Severities

Acunetix 360 overrides the severity of out of date library findings according to the highest known issue in the outdated library. For example, if an out-of-date Javascript library has a XSS vulnerability, Acunetix 360 increases the severity of the issue to High as is in XSS. (Default: Enabled)

Optimize Attacks to Recurring Parameters

Enable to detect recurring parameters in different URLs (e.g. search widgets, newsletter subscription forms). It will attack the number of links that are allowed in the Recurring Parameters Attack Limit field. (default: Disabled).

Recurring Parameters Attack Limit

Enter a number to set the maximum number of pages to attack for recurring parameters. Once the maximum is reached, Acunetix 360 will stop attacking recurring parameters on remaining pages (default: 10).

Anti-CSRF Token Field Names (Comma Separated)

Anti-CSRF token is a prevention mechanism that uses a unique, unpredictable value for CSRF attacks. These form field values should be kept as they are, so forms that are sent are not rejected by target applications.

This option can be used to instruct Acunetix 360 not to attack these fields. Enter the Anti-CSRF Token Field Names

*token*, *csrf*, ViewStateUserKey, __RequestVerificationToken, protect_from_forgery, *xsrf*, nonce.

Enable Random Parameter Attacks in Cross-site Scripting Engine

Enable to attempt to add extra parameters to pages to detect Cross-site Scripting vulnerabilities (default: Enabled).

Field

Description

Auto Custom 404

Check to select an automatic 404 Error page.

Manual Custom 404

Check to select a manual 404 Error page.

Disabled

Check to disable the 404 Error page.

Maximum 404 Signatures

Enter a number to set the maximum number of 404 Error page samples to collect (default: 1000). The maximum value is 2500.

Maximum 404 Pages to Attack

Enter a number to set the maximum number of 404 samples to crawl and attack (default: 10).

Field

Description

Case Sensitive

Acunetix 360 does not differentiate between case sensitive and insensitive URLs. In other words, by default, Acunetix 360 does not differentiate between uppercase and lowercase URLs. Both these URLs are treated as the same URL:

• http://example.com/dir/index.php
• http://example.com/DiR/IndEX.php

Enable the Case Sensitive checkbox if you want to change this behaviour because your target uses case sensitive URLs. When enabled and (for example) there is an SQL Injection in both index.php and IndEX.php, they will be reported as separate issues.

Default: Disabled

Bypass Scope for Static checks

When enabled, Acunetix 360 will make requests to resources which are out of scope. This means Acunetix 360 will check for static vulnerabilities (e.g. Crossdomain.xml, Robots.txt), even when the Scan Scope does not cover the root.

For example, if your target URL is http://example.com/test and your Scope is set to Entered Path and Below, Acunetix 360 will still send requests to the root domain, (e.g. http://example.com/Crossdomain.xml).

Static checks do not include invasive requests. So, in many cases, it is advised to enable this option. However, it is disabled by default, to avoid potential legal issues in tests conducted with strict scan scopes.

Default: Disabled

Enable Content -Type Checks

By default, Acunetix 360 excludes a number of files from the scan, based on their content type. For example, fields such as PDF and compressed files do not need to be scanned during a web vulnerability scanning. Acunetix 360 checks the Content-type HTTP response header of the file and if it matches a header listed in this list it will ignore it.

You can also exclude a file or page from a scan based on its content-type header or remove any excluded content type from the exclusion from the Ignore these Content Types option in the Scope section when configuring a Scan Policy.

Enable to analyze pages that have a listed content-type header.

Default: Disabled

Block Ad Networks

During a scan, Acunetix 360 loads the crawled pages into an internal browser to simulate specific DOM events (e.g, click, mouse over, form submit) to find more attack surfaces. If a page loads resources from advertising networks continuously, this will affect the loading time and might even result in a timeout.

Enable to stop sending requests to known ad networks.

Default: Enabled

Field

Description

Name

This is a friendly name for your reference/the parameter (e.g. 'ASP Session ID (COOKIE)').

Pattern

This is the actual name of the parameter to be excluded from the scan (e.g. ASPSESSIONID*).

Pattern matching is case sensitive, so use the correct capitalization.

You can also use any of these pattern options (wildcards) to match the patterns in the parameter name:

• ? - any single character
• * - zero or more characters
• # - any single digit (0-9)
• [charlist] - any single character in charlist
• [!charlist] - any single character not in charlist

The parameters will be ignored only during the attack phase.

For further information, see Pattern Options.

Type

This is the parameter type (e.g. COOKIE).

The dropdown options are:

• POST
• GET
• COOKIE
• ALL

If you want to ignore GET and POST parameters with this name or match, create two entries, one with POST and one with GET.

If you want to ignore GET, POST and COOKIE parameters, create one entry with ALL.

Field

Description

Name

This is a friendly name for your reference.

Type

This is the form input type.

The options are:

• hidden
• text
• textarea
• submit
• reset
• button
• image
• file
• radio
• select
• checkbox
• password
• color
• date
• datetime
• datetime-local
• email
• month
• number
• range
• search
• tel
• time
• url
• week
• output

The type should be a valid input type.

Pattern

This is the value that the HTML attribute value will be matched against based on the selected Match.

Pattern should be a valid regular expression if the Match dropdown is set to RegEx.

Target

This is the match target.

The options are:

• Select All
• Name
• Label
• Placeholder
• Id

It is possible to select one or more options.

Match

This is the match type for the Pattern field.

The options are:

• RegEx
• Exact
• Contains
• Starts
• Ends

Value

This is the value Acunetix 360 will submit to the input parameter when the match is successful.

Force

When this option is enabled Acunetix 360 will submit the provided value even when the parameter is already populated with some other value.

Field

Description

Authentication Brute Force (Basic, NTLM, Digest)

Check to enable Authentication Brute Force.

Maximum Username/Password Combinations to Test

Enter a number to set the maximum number of Username/Password combinations to test.

By default, this is set to 10.

Field

Description

Input Name

Enter a value to be matched with the input name to detect whether autocomplete is enabled for the input.

The Input Name can contain any valid wildcard characters, such as ? * #.

Acunetix 360 will only issue an alert if Autocomplete is enabled on a text input that matches one of these values.

Field

Description

Email Pattern

Enter any email addressed you'd like the scan to ignore.

Email Pattern can contain any valid wildcard characters (? * #).

Acunetix 360 will ignore any Email Disclosure vulnerability if it matches one of these patterns.

Field

Description

Checkbox

Select if you want to enable CSRF checks for authenticated scans only.

User Name Inputs

Enter a list of strings to indicate a username that includes one of these.

Login Form Values

Enter a list of strings to indicate a login form that includes one of these.

Non-CSRF Form Values

Enter a list of strings to indicate non-CSRF form values whose name or action includes one of these.

Non-CSRF Input Values

Enter a list of strings to indicate non-CSRF input values whose name or value includes one of these.

Captcha Indicators

Enter a list of forms which contain Captcha against CSRF.

Field

Description

Type

This is the type of which Web Storage mechanism will be used.

From the dropdown, select an item.

The options are:

• Local
• Session

Key

This is the name of the key you want to create.

Value

This is the value you want to give the key you are creating.

Origin

Enter storage data for a specific origin. (Otherwise leave it empty to allow the DOM parser to pass it for any origin.)

Field

Description

Extension

This is a list of file types to which the specified Crawling and Attacking activity will be applied.

For further information, see Crawl and Attack Options.

Crawl

Select the required Crawling activity for the file type (Extension).

The options are:

• Do Not Crawl
• Crawl
• Crawl Only Parameter (default)

Attack

Select the required Attacking activity for the file type (Extension).

The options are:

• Do Not Attack
• Attack Parameters (default)
• Attack Parameters and Query String

Field

Description

(Pre-defined) User Agent(s)

Select or Enter the User Agent string to be used in all HTTP requests during scans.

Force this value

Enable to force Acunetix 360 to use the User Agent.

Request

Enter a number to set the interval (seconds) to wait for a response from the target before it is considered to have timed-out. Depending on the configuration, if a request times out, Acunetix 360 will try to send it again or cancel it.

• Connection Timeout (sec) - This is the number of seconds to wait before the HTTP Request times out.
• Request Timeout (sec): This is the interval in seconds that Invicti Enterprise should wait for a response from the target before the request is considered to have timed out. Depending on the configuration, in case of a connection timeout, Invicti Enterprise will try to send the request again, or cancel it.
• Concurrent Connections (sec): Enter the maximum number of simultaneous connections Acunetix 360 should open when scanning the target system. Depending on the target application, a high number of simultaneous connections may cause connectivity or Denial of Service issues.

Requests per second

Move the slider left or right to set the maximum [number] of requests initiated per second. Depending on the target application, setting this figure too high might cause connectivity or Denial of Service issues. The recommendation is 30.

HTTP Keep Alive

Enable to improve the server's performance and decrease the load.

Support Gzip/Deflate

Enable to complete the scan in less time, if the target web server supports Gzip or Deflate.

Support Cookies

Enable to support HTTP cookies.

Capture HTTP Requests

Enable to save HTTP requests during scans using the Fiddler session file format.

Field

Description

Enabled

Enable so that the custom header is added to all HTTP requests.

Name

The Name field in the HTTP Header should only contain ASCII characters. As the HTTP headers construct name and value pairs, this field is for the name part.

Value

A header value to be used in attacks with the corresponding header.

Attack Mode

The options are:

• None (default)
• Optimized
• Full

Field

Description

Security Protocol

Select the security protocol(s) that is supported by the website to be scanned.

The options are:

• SSLv3: This is disabled by default.
• TLS 1.0: This is enabled by default.
• TLS 1.1: This is enabled by default.
• TLS 1.2: This is enabled by default.
• TLS 1.3: This is disabled by default.

Untrusted Certificates

This indicates the action taken when an attacker is encountered with an untrusted certificate at Target & Additional Websites or External Websites.

The options are:

• Accept untrusted certificate
• Reject untrusted certificate

Field

Description

Use Application (Global) Proxy

Enable to use the Application Proxy.

The Applications Proxy can be defined at the Proxy tab in the Options dialog.

Use System (Internet Explorer) Proxy

Enable to use the System Proxy. This is the default.

The System Proxy is the system-wide proxy which is used by every program by default.

Use Custom Proxy

Enable to use and configure a Custom Proxy.

The Custom Proxy should be configured explicitly to be used unlike System Proxy. It is scan policy specific and valid in the scope of the policy.

Don't use proxy server for local (intranet) addresses

Enable so that no proxy will be used.

Use this proxy server for the requests other than the target website(s)

Enable so that this proxy is used instead of the proxy server in the agent configuration.

Field

Description

Enable Knowledge Base

Enable to switch on the Knowledge Base checks.

Note that disabling this option means that some issues may not be reported.

Sensitive Keyword Pattern

This is a pattern that is accessible from a website that may contain sensitive data in comments. The Sensitive Keyword Pattern should be a valid regular expression. Acunetix 360 uses these patterns to find sensitive keywords in the code’s comments.

Field

Description

Browser Settings

• Default Browser Parameters: These are the default browser parameters that Acunetix 360 uses when it launches a Chromium instance to scan your website. You can deselect any parameters to disable it. Or, you can add a new parameter.

• Headful Browser Parameters: These are the headful browser parameters that Acunetix 360 uses when it launches a Chromium instance to authenticate with your website. You can deselect any parameters to disable it. Or, you can add a new parameter.

Policy

Description

Default

Unless you configure them as Shared, these can only be used by you.

Share

These are policies that others can use.

Private

There are policies that only you can use.

Mine

These are policies you created.

Information

Note that the user who has the Account Administrator role can see the private policies of the team members.