The Qualys WAS Burp extension provides two useful features for Qualys Web Application Scanning (WAS) customers.
First is the ability to import a WAS finding into Burp Repeater for manual validation of a WAS-discovered vulnerability. This feature works with both Burp Professional and Burp Community editions. Note that if a transient token is part of the imported request, such as a cookie for an authenticated session, you will need to update it manually.
Second is an option to send Burp scanner issues to Qualys WAS. This allows you to view and report Burp issues together with WAS findings for a more complete picture of your web application's security posture. Burp Suite Professional is required to use this feature.
To learn more about Qualys WAS, its integration with Burp, and the additional security and compliance solutions available on the Qualys Cloud Platform, please visit https://qualys.com/was-burp.
Burp Suite Professional or Burp Suite Community edition as noted above
Qualys WAS subscription, including API
Import a Qualys WAS finding into Burp Repeater via context menu to manually validate it
Send selected Burp scanner issues to Qualys WAS via context menu on Target tab
Upstream proxy server settings in Burp are honored automatically
All Qualys shared platforms and private cloud platforms are supported
Written in Java
Add the extension to your instance of Burp Suite Professional by installing directly from the "BApp Store" tab within Burp or by loading the jar file from the Extensions tab.
In the "Qualys WAS" tab, select the appropriate Qualys platform for your subscription and enter your Qualys username & password.
Click "Validate Credentials" to ensure successful connectivity to the Qualys platform.
Review the "Logs" section on the Qualys WAS tab to see API success/failure messages.
To validate a WAS finding:
Go to Burp Repeater and right-click in the empty Request area.
Select "Import Qualys WAS Finding".
Choose "Enter Finding ID" if you know the WAS finding ID, otherwise choose "Select from a Web App's Open Findings".
If you choose
"Enter Finding ID", enter the finding ID in the text box (the longer UUID of the finding is preferred, although the numeric finding ID should work as well). Click "Fetch".
"Select from a Web App's Open Findings", you will see a list of web apps from WAS. Select a web app. The open vulnerabilities will be loaded into the Findings list. Note that only vulnerabilities are loaded, not "informational" QIDs. Select the finding you want to validate. If multiple payloads are present, you will also need to choose one of the payloads.
Click "Import Request". (Note: If the WAS finding was detected prior to WAS Engine 7.0, some request headers may be missing or the format may need to be tweaked manually).
If required, manually update the session cookie or other authentication token in the request.
Click "Send" and inspect the response to validate the finding.
To send Burp issues to WAS:
Perform passive and/or active scans in Burp.
Go to: Target > Site map > Issues.
Right-click the desired scanner issue(s) and click "Send to Qualys WAS".
Select the web application from WAS for which the issues apply. If you don't see the correct web app in the list, the web app may not have been created within WAS yet or the Qualys user account entered may not have permission to the correct web app.
Select the "purge" or "close" checkbox as desired.
Click the "Send to Qualys WAS" button.
22 October 2019
You can install BApps directly within Burp, via the BApp Store feature in the Burp Extender tool. You can also download them from here, for offline installation into Burp.
You can view the source code for this BApp by visiting our GitHub page.
Follow @BApp_Store on Twitter to receive notifications of all BApp releases and updates.