Skip to content


Simon Bennetts edited this page Nov 28, 2017 · 4 revisions

Options Active Scan Input Vectors screen

This screen allows you to configure the active scan input vectors. These are the elements that the active scanner will attack. Scanning all of the elements supported will take longer, but not scanning some elements may cause some vulnerabilities to be missed.

Injectable Targets

The request elements that the active scanner will target:

URL Query String & Data Driven Nodes

Key value pairs in the request URL query, ie after the ?. If there are no query parameters then an arbitrary one will be tested. If Data Driven Nodes are defined within a Context they will be tested.


Key value pairs in the request POST data.

URL Path

Path elements in the request URL, ie the elements separated by /.

HTTP Headers

Request HTTP Headers.

All Requests

Allows to scan the HTTP Headers of all requests. Not just requests that send parameters, through the query or request body.

Cookie Data

Request cookies.

Build-in Input Vector Handlers

The data formats that the active scanner will target:

     Multipart Form Data
     XML tag/attribute
     Google Web Toolkit
     OData id/filter

Enable Script Input Vectors

If this option is selected then the active scanner will use any enabled script input vectors. Script input vectors are scripts which you have written or imported into ZAP and allow you to target elements which are not supported by default.

This screen also allows you to configure the parameters which will be ignored by the active scanner.

See also

     UI Overview for an overview of the user interface
     Options dialogs for details of the other Options dialog screens
     Active Scan Input Vectors
Clone this wiki locally
You can’t perform that action at this time.