Beta: the full scanner is free while it is in beta. Sign in and scan a site

ScanBastion Start Free Beta Scan

Comparison

Self-hosted ZAP vs ScanBastion: run your own scanner, or use a hosted one?

ZAP (Zed Attack Proxy, formerly OWASP ZAP) is the most widely used open-source web application scanner. It is free under the Apache-2.0 licence, and since leaving OWASP in September 2023 it describes itself as an independent open-source project controlled by the ZAP Core Team and supported by Checkmarx, hence “ZAP by Checkmarx”. You can run it yourself, on a laptop, on a server or in Docker. ScanBastion is a hosted website scanner for agencies and consultants: nothing to install, a bounded scan of each client site, and a report the client can read. It is not hosted ZAP, and this page is clear about what that means.

At a glance

ZAP, self-hostedScanBastion
What it isFree, open-source scanner you install and run: desktop app, daemon or Docker imageHosted website scanner with a report per site, for agencies and consultants
CostFree; you supply the machine, the hosting and the time to run and maintain itPublished plans per target: free, $19, $59, $149 a month
SetupJava 17 or higher on Windows and Linux (bundled on macOS), or Docker images (stable, weekly, nightly, bare) from GHCR and Docker HubNothing to install: sign in, add the site, confirm you are authorized
Passive scanning✓ Yes: the baseline scan spiders the target (one minute by default) and reports passive results without any attacksBuilt-in passive analysis of a bounded crawl, in every profile; headers, TLS, DNS and email checks alongside
Active scanning✓ Yes: full scan (spider with no default time limit, then a full active scan) and API scan for OpenAPI and GraphQLVerified targets only Deep adds Nuclei DAST injection testing of GET parameters and paths; no POST forms, no out-of-band callbacks, no time-based payloads
Authenticated scans✓ Yes: contexts, authentication methods, verification strategies and users, applied to the spiders and active scanner— No
Scripting and automation✓ Yes: scripts in any JSR 223 language (JavaScript, Zest, Groovy, Python, Ruby), including scan-rule and authentication scripts; Automation Framework driven by one YAML file— No: three fixed profiles, Quick, Standard and Deep
Scheduled and CI scansYou build them; the baseline scan is designed to suit CI/CD— No
Traffic limitsWhatever you configureFixed per profile: Quick 150 requests at 1 per second, Standard 600 at 2 per second, Deep 3,000 at 4 per second; stop button on every scan
Authorization before scanningYour responsibilityConfirmed under your account for every target; a proof of control (file, meta tag or DNS record) can be added for client sites, and is required for Deep
ReportsHTML, JSON (including SARIF), XML, Markdown and PDF templates, with themes and custom templates8-page client assessment report on every plan, including Starter; co-branded “Assessed by” cover line on Agency and Studio; see the sample
StatusCurrent release ZAP 2.17.0● Free beta

ZAP details from zaproxy.org, zaproxy.org/docs/zap-ownership, zaproxy.org/download, zaproxy.org/docs/docker/about, zaproxy.org/docs/docker/baseline-scan, zaproxy.org/docs/docker/full-scan, zaproxy.org/docs/desktop/start/features/authentication, zaproxy.org/docs/desktop/addons/script-console, zaproxy.org/docs/desktop/addons/report-generation, zaproxy.org/blog/2023-08-01-zap-is-joining-the-software-security-project and github.com/zaproxy/zaproxy as of 16 November 2026. ZAP is a trademark of its owner and is not affiliated with ScanBastion.

When self-hosted ZAP is the better choice

  • You need depth, not convenience. ZAP's full scan runs a complete active scan, and its API scan tests OpenAPI and GraphQL definitions. ScanBastion's Deep profile is deliberately narrower: GET parameters and paths only, on verified sites.
  • You need to test behind a log-in. ZAP handles a wide range of authentication mechanisms for its spiders and active scanner. ScanBastion does not log in.
  • You want to script it. Custom scan rules, authentication scripts and an Automation Framework plan in YAML make ZAP a toolkit you can shape to each engagement. ScanBastion has three fixed profiles.
  • You want it in your pipeline and on your own infrastructure. The Docker images and the baseline scan are built for CI/CD, scans can run on a schedule you set, and scan data stays on machines you control.
  • Your budget is zero and your time is not. ZAP is free. If someone on the team is comfortable with Java or Docker, tuning scan policies and reading raw alerts, it costs nothing but that time.

When ScanBastion fits better

  • You do not want to run scanning infrastructure. No Java, Docker images, add-on updates or a server to keep alive between client jobs: sign in, add the site and start a scan.
  • You need scans that are safe on a client's production site. Quick and Standard read ordinary responses and send specific, non-destructive detection requests, under fixed request budgets and rates, so a scan does not depend on someone choosing the right scan policy first. See passive vs active scanning.
  • Authorisation is on the record. Every target carries your signed-in confirmation that you are authorized, and a proof of control (a file, a meta tag or a DNS record) puts the client's acknowledgement on the report too. Active testing runs only on sites that have one. See the Responsible Scanning Policy.
  • The report is the deliverable. Instead of formatting scanner alerts for a client, you get an 8-page report written for them: limitations on page 1, a recommended order of work, evidence and a specific fix per finding, and severity, confidence and verification shown separately. See how to read a scanner finding.
  • You look after many client sites. Every site sits in one account with its own scan history, and verification decisions carry forward between scans. Fifteen sites cost $59 a month on Agency once paid plans open; it is free during the beta.

Does ScanBastion run ZAP?

No. The ScanBastion engine has a ZAP integration that can run ZAP's passive scan rules only (one spider thread, bounded by depth, page count and time, no forms submitted, the active scanner never started), but it is not enabled on scanbastion.com: ZAP is not installed on the scanning host, so no scan run here includes a ZAP stage. What every scan runs instead is ScanBastion's own built-in passive analysis of the pages its crawl fetched, which looks for some of the same weaknesses ZAP's passive rules do but is not ZAP's rule set. The changelog records when the site stopped saying otherwise.

Frequently asked

Is ZAP still an OWASP project?

No. The ZAP team took ZAP out of OWASP in September 2023 to obtain enough funding to keep maintaining it. It had announced in August 2023 that it was joining the Software Security Project, a Linux Foundation initiative; ZAP's site now says it is supported by Checkmarx and is not part of any foundation. It remains free and open source under the Apache-2.0 licence, and is often still called OWASP ZAP.

Is ScanBastion a hosted version of ZAP?

No. ScanBastion does not currently run ZAP. Its scans use its own built-in passive analysis, header, TLS, DNS and email checks, a curated, non-intrusive Nuclei template set in Standard, and in Deep active injection testing with Nuclei's DAST templates on verified sites only. If you specifically need ZAP's rules, run ZAP.

Can I use both?

Yes, and some consultants will: ScanBastion for routine, production-safe assessments of every client site and the report the client reads; self-hosted ZAP for authenticated or full active testing of a site whose owner has agreed to it, under a separate authorisation.

Can I try ScanBastion now?

The free headers and TLS checker runs today against any site. The full scan runs once you sign in, free during the beta.