Standalone gradle plugin to aid in integrating OWASP ZAP (security analysis tool)
Clone or download
Pull request Compare This branch is 16 commits ahead of PROSPricing:master.
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Type Name Latest commit message Commit time
Failed to load latest commit information.

ZAP Gradle Plugin

Automate web application dynamic security scans using OWASP ZAP.

Nearly all operations of ZAP can be automated using this plugin thanks to the ZAP API. Spidering and Active Scan are provided as tasks.

Originally based off plugin found here:


plugins { 
    id 'com.patdouble.gradle.zap' version '2.0.2'

zapConfig {
    applicationUrl = ""
$ ./gradlew zapSpider zapActiveScan zapReport
$ ls -1 build/reports/zap


The examples directory contains a multi-project Gradle build using several popular vulnerable web applications. The check task in each project starts the application, runs the spider, active scan and produces reports. The reports are in the build/reports/zap directory inside each sub-project.

You need a working Docker install to run the examples.

$ cd examples
$ ./gradlew check
$ ls */build/reports/zap

Getting the Plugin

The plugin is available from the Gradle plugins repository using the usual methods.

plugins {
    id 'com.patdouble.zap' version '2.0.2'


buildscript {
  repositories {
    maven {
      url ""
  dependencies {
    classpath ""

apply plugin: "com.patdouble.zap"

Finding the ZAP Application

By default the plugin will download version 2.7.0 of OWASP ZAP and use it. You can specify a version by including the following in your build.gradle:

zapConfig {
    version = "2.6.0"

If you'd rather use an already installed version, configure the install directory. The directory must include either or zap.bat, the script used to start ZAP.

zapConfig {
    zapInstallDir =  "/path/to/ZAP/install/directory"

Configure Your Application

At a minimum you must configure the URL of your application that ZAP is to scan.

zapConfig {
    applicationUrl = ""

Optional Properties

There are a few optional properties that may be specified within the zapConfig section of the gradle file to further tune your use of ZAP.

zapConfig {
    // The port on which ZAP should run. Defaults to a free port.
    proxyPort = "9999"
    // The format(s) of the output report. Acceptable formats are JSON, HTML, MD and XML. Defaults to all.
    reportFormat = "JSON HTML"
    // The path of the report file to write from the zapReport task, without an extension. This path must be writable, subdirs will be created.
    reportOutputPath = "reports/dynamicscan"
    // The timeout for the active scanner process, in seconds. Defaults to 300 seconds.
    activeScanTimeout = "600" // 10 minutes
    // The API key to use when authenticating to the ZAP API. Defaults to a random value.
    apiKey = "mysecretapikey"
    // Additional command line parameters to use when starting ZAP. Run ` -help` to find available parameters.
    parameters = [ '-addoninstallall', '-addonupdate' ]

Using an Already Running ZAP

It can be useful when debugging your build to use a ZAP instance running in GUI mode. This allows you to see what the ZAP plugin is causing ZAP to do and to experiment with options in the GUI to see how that affects the spidering, active scan, etc.

Start ZAP and fill in the zapConfig options below.

zapConfig {
    // Preferences -> Options -> Local Proxies -> Port
    proxyPort = "9999"
    // Preferences -> Options -> API -> API Key
    apiKey = "mysecretapikey"

The zapStart task will check if ZAP responds on the configured port and if so will use the running process. In this case zapStop will not attempt to stop the process.

Running ZAP with Tests

Instead of (or additional to) spidering, your existing functional tests can be used to populate the list of URLs the active scan attacks. Either run your test task between zapStart and zapActiveScan or configure Gradle task dependencies similarly.

./gradlew zapStart taskThatRunsMyTestsWithALocalProxySetToZAPProxyPort zapActiveScan zapReport zapStop

Updating Tests to Use ZAP

In order for ZAP to see traffic to your app, it must be used as a proxy for those requests. Different testing tools will have different mechanisms for setting up a proxy for a given HTTP request. You can use the zapConfig.proxyPort value to pass the proxy port to your test. By default the port is randomly chosen. The zapStart task will populate the value.

// build.gradle
test.systemProperty 'zap.port', zapConfig.proxyPort
test.environment['ZAP_PORT'] = zapConfig.proxyPort

Python with httplib2:

http_con = httplib2.Http(proxy_info = httplib2.ProxyInfo(httplib2.socks.PROXY_TYPE_HTTP, 'localhost', os.environ['ZAP_PORT']))

Java/Groovy with URLConnection:

URL url = new URL("");
Proxy proxy = new Proxy(Proxy.Type.HTTP, new InetSocketAddress("localhost", Integer.parseInt(System.getProperty("zap.port")));
URLConnection connection = url.openConnection(proxy);


proxy_addr = 'localhost'
proxy_port = ENV['ZAP_PORT'].to_i'', nil, proxy_addr, proxy_port).start { |http|
  # ...

Accessing ZAP API

Nearly everything in ZAP can be accessed via API. The plugin exposes the API using the org.zaproxy:zap-clientapi library. The zapConfig.api DSL gives you access to org.zaproxy.clientapi.core.ClientApi.

task zapSetup {
    doLast {
        zapConfig.api {

Using the API is essential when the application requires authentication. See the examples directory.


Copyright (c) 2018, Patrick Double. All right reserved.

Released under BSD-3 style license.

See and LICENSE file for details.