A DAST tool is truly on-premise when the console, the scan engine and the findings database all run inside your network and the product can be licensed and updated without internet access. Products that meet that bar include Burp Suite DAST, Invicti, OpenText Fortify DAST, HCL AppScan, Offensive360 and the open-source ZAP. Several other products place only the scan engine in your network and keep results in the vendor cloud.
That difference matters for internal applications, regulated data and disconnected networks, and it is easy to miss in a product sheet. This guide explains what to check and compares the main options.
Three deployment models
- Cloud scanner. The engine runs in the vendor cloud and reaches your application over the internet. Suitable for public applications only.
- Cloud console with a local engine or tunnel. An agent or engine inside your network scans internal targets. Requests originate locally, but findings, including request and response evidence, are stored in the vendor cloud.
- Self-hosted platform. Console, engine and database run in your environment. This is the model that works for disconnected networks and strict data-location rules.
Comparison at a glance
| Product | Console location | Engine location | Disconnected networks | Notes |
|---|---|---|---|---|
| Burp Suite DAST | Self-hosted or cloud | Self-hosted | Yes, self-hosted edition | Uses your own database; Kubernetes or standard install |
| Invicti | Cloud or self-hosted | Cloud or self-hosted | Self-hosted edition | Known for automatic confirmation of findings |
| OpenText Fortify DAST | Self-hosted | Self-hosted | Yes | WebInspect, with ScanCentral for scale |
| HCL AppScan | Self-hosted or cloud | Self-hosted or cloud | Yes | AppScan Standard desktop and AppScan 360 platform |
| Rapid7 InsightAppSec | Cloud | Cloud or local engine | Not for the console | Local engine reports to the cloud console |
| ZAP | None built in | Wherever you run it | Yes | Open source; scripting needed for complex applications |
| Offensive360 | Self-hosted or cloud | Same appliance | Yes | SAST and mobile testing in the same appliance |
What to check before you buy
Licensing and activation
Ask whether activation needs a call to a vendor server, and how the licence is renewed in a network without internet access.
Updates
Detection content ages quickly. Ask for the offline update package format, how often it is released, and how you verify its integrity before import.
Out-of-band checks
Some detection techniques confirm an issue by observing a callback to an external server. In a closed network the callback listener has to run inside it. Ask whether the product ships one and which checks are unavailable offline.
Authenticated scanning
Most business logic sits behind a login. Confirm support for your sign-in method: form login, single sign-on, multi-factor steps, API tokens, and session handling for single-page applications.
API coverage
Confirm import of OpenAPI and GraphQL schemas and Postman collections, so APIs without a crawlable front end are tested.
Where evidence is stored
Request and response evidence can contain personal data and secrets. Confirm that it stays in your database and how long it is retained.
The options in more detail
Burp Suite DAST
The enterprise scanner from PortSwigger, built on the Burp scanning engine many testers already use. The self-hosted edition installs on your own servers or Kubernetes cluster with your own database.
Invicti
An enterprise DAST product that can be deployed in the cloud or self-hosted. Its automatic confirmation of many findings reduces manual verification.
OpenText Fortify DAST
Formerly WebInspect, a long-established installed scanner, often used with Fortify SAST in government environments.
HCL AppScan
AppScan Standard is a desktop scanner for testers, and AppScan 360 is the self-hosted platform. IAST is available next to DAST.
ZAP
The widely used open-source scanner. A good choice for CI checks and for teams with scripting skills. Plan your own reporting and scheduling around it.
Offensive360
DAST is delivered in the same OVA or Azure VHD appliance as SAST and mobile application testing, so one installation covers static and dynamic testing in a closed network. It tests web applications, REST and GraphQL APIs and single-page applications with authenticated scanning, and reports request and response evidence. The licence is quoted annually per scope. See the DAST product page and deployment options.
When a self-hosted platform is not needed
If you only scan public websites and your policies allow evidence to be stored with a vendor, a cloud DAST service is simpler to run. If you scan a few internal applications and accept cloud-stored results, a cloud console with a local engine is a reasonable middle path.
Evaluation steps
- Install each finalist on a machine with no internet route and run a licensed scan.
- Scan one authenticated application and one API with each product.
- Import an offline update and check that detection content changed.
- Review where findings and evidence are stored, and export a report.
Related reading: best DAST tools, benchmark a DAST scanner with a practice application and SAST for air-gapped environments.
Vendor details were checked against public vendor documentation in November 2026. Confirm current packaging with each vendor.
Frequently asked questions
Which DAST tools can run fully on-premise?
Burp Suite DAST, Invicti, OpenText Fortify DAST (WebInspect), HCL AppScan, Offensive360 and the open-source ZAP can all be installed inside your own network. Some other products install only a scan engine locally and keep the console in the vendor cloud.
What is the difference between an on-premise scan engine and an on-premise DAST platform?
With an on-premise engine, traffic to your application originates inside your network, but findings, schedules and reports are stored in the vendor cloud. With an on-premise platform, the console, database and engine all run in your environment, so no scan data is stored outside it.
Can DAST work in an air-gapped network?
Yes, if the product can be licensed, run and updated without internet access. Checks that rely on external callback servers need a callback listener hosted inside the network, so ask how the product handles them offline.
Is there a free self-hosted DAST scanner?
Yes. ZAP is open source and runs locally or in CI. It needs tuning and scripting for authenticated and single-page applications, and it has no central management console of its own.