Burp Suite Enterprise Edition Power Tools: Unleashing the power to the command line, Python, and more

tl;dr

We have released BSEEPT - Burp Suite Enterprise Edition Power Tools which:

• Is a command line tool to drive all aspects of the BSEE GraphQL API.
• Is a Python client library to allow you to easily utilise the BSEE GraphQL API in your own code be it command line tooling, lambdas, or integration layers.
• Returns BSEE's JSON allowing you to parse on the command line with jq and similar.

Backstory

In January I joined PortSwigger in a more involved capacity as Non-Executive Director++ (the ++ being I can still code whilst sitting in the boardroom). In my first month I spent time coming up to speed on the products, their features, roadmaps, and most importantly their APIs for extensibility and similar.

These first months saw me produce two extension prototypes using the Montoya API. These used the Google Safe Browsing API to identify known malicious sites in sitemaps and a YAML-powered regular expression engine to identify sensitive information presence / leakage. I then had the fortune of working with Hannah and Alex on the TOTP Authenticate extension to support multi-factor authentication in Burp Suite Enterprise Edition.

I then turned my attention to the Burp Suite Enterprise Edition GraphQL API. It struck me that we had this amazing GraphQL API, which we both use in the product, but also expose to customers. But for DevOps teams and others in the security function to really utilize this required a bit of investment.

So an objective was born ... write the power tools that teams who work with Burp Suite Enterprise Edition would find valuable.

Que A-Team building music, over 80 commits, lots of learning (I learnt to use a Mac at the same time) and out popped BSEEPT.

BSEEPT allows you to use every aspect of the GraphQL API from the command line or in your own Python code.

Quick Demo

I have written an extensive readme on the GitHub project but I will give an example of how one might use it.

In this example we will run through several steps:

1. Query the run scans.
2. Then pass through jq to just extract the issue titles.
3. Then pass through jq to build a CSV of issue titles, site, and path they were found in.

All without writing any new code - just using command line tools!

So we first get the scan details:

Second, extract the issues for the successful scan with the scan ID of 123:

Third, we use jq to parse the JSON and print the issue titles from scan 123:

Fourth, we build a CSV-like output of issue names, their origin site and path:

That's it. As mentioned there is an extensive help document with examples of both the command line and code.

Issues and feedback

Please raise any bugs / feature requests as issues so they can be resolved.

Email with any questions / feedback to ollie.whitehouse at portswigger [.] net.

Getting it

Scoot on over to the BSEEPT - BSEEPT - Burp Suite Enterprise Edition Power Tools GitHub project.

Burp Suite Enterprise Edition

Ollie Whitehouse

@ollieatnowhere