Overview
OWASP ZAP (Zed Attack Proxy) is the free, community flagship for web application testing. Like Burp it proxies your browser traffic for manual inspection, and unlike Burp Community it ships a full active scanner, spider, fuzzer and a powerful REST API for CI pipelines — free forever, maintained by OWASP contributors and sponsors.
Teams wire ZAP into deployment pipelines so every release of their own app gets an automated baseline scan: spider the app, run the active scan against staging, fail the build on high-severity alerts. Beginners start with the automated scan button; professionals drive everything through the API.
Key features
- Intercepting proxy plus full active vulnerability scanner
- Traditional and AJAX spiders for coverage
- Fuzzer, forced browse and custom scan policies
- REST API and automation framework for CI pipelines
- Add-on marketplace with community scan rules
- Free and open source forever (OWASP flagship)
Install & first run
No install needed for first look — download ZAP below for your OS.
- Launch ZAP and run the Automated Scan against your local test app (OWASP Juice Shop on localhost).
- Read the Alerts tree: red and orange items first.
- Open one alert, read its description and solution, and verify it manually in the proxied browser.
- Re-scan after fixing to confirm the alert clears.
Real-world example
Your team ships a new customer portal every sprint. Add a ZAP baseline scan to the staging pipeline: spider, active scan, export the alert report. When the sprint adds a forgotten debug endpoint, ZAP flags it before release — the fix lands the same day instead of becoming an incident.
Common questions
Is ZAP really free?
Yes — every feature, including the active scanner and API, is free and open source.
Is ZAP a replacement for Burp?
It is a credible free alternative: proxy, spider, passive and active scanning, plus automation via the packaged scans in the API. Burp wins on extensions and manual workflow.
How do I scan an authenticated app?
Record a login in the AJAX spider with a context, then reuse that context for the active scan. Unauthenticated scans miss most of the app.
Can it run in CI?
Yes - zap-baseline.py and zap-full-scan.py in Docker are the standard approach, and the Automation Framework is the current recommended route.
Related tools
Burp Suite
The standard web app testing proxy: intercept, inspect and modify traffic for apps you are authorized to test. Freemium.
ffuf
High-speed web fuzzer for directories, parameters, virtual hosts and headers. Free, open source, one binary that runs on any OS.
SQLMap
Automatic SQL injection detection and exploitation testing for your own apps and labs. Free, open source.
Related reading: OWASP Amass vs Subfinder: Subdomain Recon Comparison · Burp Suite vs OWASP ZAP: Web Security Proxy Guide
Keep exploring: browse every assessment phase in the Pentest Hub.
Authorized testing only — only ever test systems you own or have explicit written permission to assess.
