Research Academy
My account Customers About Blog Careers Legal Contact Resellers

DAST

Connecting Burp Suite DAST to GitHub

  • Last updated: November 5, 2026

  • Read time: 3 Minutes

To create and link GitHub issues from Burp Suite DAST, connect it to GitHub.

Before you start, create a personal access token in GitHub. For instructions, see Preparing GitHub for Burp Suite DAST.

Choosing a GitHub deployment

Select the deployment that hosts your repositories. Burp Suite DAST connects to the address of that deployment. All deployments use a personal access token.

  • If you use GitHub.com, select GitHub.com. This is the default, and you do not need to enter a URL.
  • If you use GitHub Enterprise Cloud with data residency, select GitHub Enterprise Cloud with data residency. In Enterprise Cloud URL, enter the URL of your enterprise, such as https://mydomain.ghe.com.
  • If you use GitHub Enterprise Server, select GitHub Enterprise Server. In Enterprise Server URL, enter the URL of your instance, such as https://github.example.com. This option works on Self-hosted deployments only.

Adding a GitHub connection

  1. Log in to Burp Suite DAST as a user with the Modify settings permission.
  2. Click the settings icon in the top-right corner, then click Integrations.
  3. Click Configure for GitHub.
  4. Enter a Connection name. Use a name that no other connection uses. Burp Suite DAST ignores case when it compares names.
  5. Select a Deployment. For GitHub Enterprise Cloud or GitHub Enterprise Server, also enter its URL. Click Next.
  6. Enter your Personal access token and click Next. Burp Suite DAST checks the connection. If the check fails, see Checking the GitHub connection.
  7. (Optional) Select a default Assignee. For details, see Setting a default GitHub assignee.
  8. Save the connection.

Each connection has its own deployment and token. To add another connection:

  1. Click Edit for GitHub.
  2. Click Add connection.
  3. Repeat steps 4 to 8 above.

Setting a default GitHub assignee

To assign every GitHub issue to the same user, select a default Assignee. The user must be able to receive GitHub issues in each repository that you use. You can override the default in an action.

To assign a GitHub user other than the owner of your token, enter their full login.

When you save an action that uses the default, Burp Suite DAST checks that the user can receive GitHub issues in the repository of the action. If the user cannot, then Burp Suite DAST shows a <login> can't be assigned issues in this repository. Choose another assignee. error. To fix this, select a different assignee in the action, or change the default.

Network access for GitHub

On Cloud, you need no network change for GitHub.com or GitHub Enterprise Cloud with data residency. Cloud instances of Burp Suite DAST connect only to hosts on an allow-list, and api.github.com and api.*.ghe.com are on it. Cloud instances accept only public https URLs. If you enter anything else, Burp Suite DAST shows a This URL can't be used. Enter a public https URL. error.

Cloud deployments cannot connect to GitHub Enterprise Server. You host your own server, so PortSwigger cannot add it to the allow-list. Use a Self-hosted deployment instead.

Self-hosted instances can connect to any GitHub deployment that your network can reach. This includes GitHub Enterprise Server.

To check, edit or remove a connection, see Managing GitHub connections.