Skip to content

Instantly share code, notes, and snippets.

@mccabe615
Created September 15, 2018 15:52
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save mccabe615/81ad7c905df5f619c5fa0014812c87c8 to your computer and use it in GitHub Desktop.
Save mccabe615/81ad7c905df5f619c5fa0014812c87c8 to your computer and use it in GitHub Desktop.
Required ports for Burp enterprise

Users and API clients need to access the web server on a port that you can select (by default, 8080). The Enterprise server needs to access portswigger.net on port 443, to carry out license activation and software updates. Note that this access is needed for ongoing usage of the software, not only during initial installation. You can configure a network proxy if this is needed to reach the public web. If you install agents on any external machines, these need to access the Enterprise server machine on port 8072. If you use the bundled database, then any external agent machines will need to access the Enterprise server machine on port 9092. If you use an external database, then the Enterprise server and any external agents will need to access the database service on the configured host and port. Agents will need to access the sites that are to be scanned (on ports 80, 443, etc. as required). To gain the full benefit of Burp Suite’s out-of-band vulnerability detection technology, agents will need to access burpcollaborator.net on port 443.

  • API (ent in): 8080
  • Agent access (ent in): 8072
  • Portswigger (ent out): 443
  • Database (ent out/agent out): 3306
  • Collab (end out): 443
  • Agent (agent out): 80/443
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment