The HUD is new interface that provides the functionality of ZAP directly in the browser.

Learn more:

• Blog: Hacking with a Heads Up Display
• Video: The OWASP ZAP HUD - Usable Security Tooling
• Wiki: Inside the HUD

You can download ZAP enabled with the HUD from:

1. Download and run the latest ZAP Weekly Release
2. Run it from this repo using:

   git clone https://github.com/zaproxy/zap-hud.git
   ./gradlew runZap
   

3. Those of you building ZAP directly from the source code will also be able to install it from the ZAP Marketplace. You will need Java 8+ installed.

You'll see the HUD Radar icon in the tool bar. When the icon is selected the HUD will be added to your browser.

1. Quick Start: Select either Firefox or Chrome on the Quick Start tab and click on the Launch Browser button.

2. Manually: You can also configure Firefox or Chrome to proxy via ZAP manually, but you will need to import the ZAP Root CA Certificate.

The first time the HUD is launched you'll be prompted with the HUD Tutorial. We recommend that you follow the tutorial even if you have read the above blog post and watched the video.

ZAP is a community project and so we are always very keen to hear from anyone who'd like to contribute, just post to the ZAP Dev Group

This is definitely still Alpha quality and there are some known issues and limitations with the current release. Development on the HUD is very active and we recommend you check in often for new features and improvements. :)

You should NOT use it on sites you do not trust! However it is in scope for the ZAP bug bounty on BugCrowd

Limitations while running:

• It's early days, so only a limited amount of ZAP functionality is available
• Firefox has been tested more than Chrome, but both should work (JxBrowser, doesn't currently work)
• The code to support the HUD in multiple browser tabs is very new so might be buggy
  • In particular don't close the first tab on Firefox or the HUD will stop working (weird, we know. See #199 for details)
• Using the HUD with browser dev tools open can significantly affect performance
• Behaviour using the browser back button is currently undefined

Issues and todos in code:

• We're using Vue.js in dev mode, which prevents us from using a suitably strong CSP
• JavaScript code still needs to be formatted and linted
• Documentation could, of course, be better
• Async functions are handled as via Promises as opposed to using 'await' pattern

These lists aren't exhaustive, but do highlight some of the larger restrictions.