# GitHub Issues

The GitHub Issues integration lets you turn ZeroThreat scan findings into real, trackable work right inside the repositories your team uses. Connect once, pick the repository, and directly create issues from inside ZeroThreat scans with all the vulnerability details attached. Comments stay in sync between GitHub and ZeroThreat, reducing back-and-forth and keeping everyone aligned. You also get better planning and prioritization with labels, assignees, and status sync for clear visibility into progress. Whether you're running periodic scans or have a fully automated CI/CD pipeline, this integration ensures that vulnerabilities gets visibility and focus within your GitHub repository.

### Prerequisites

Before you begin, ensure the following:

* Your target application is verified on ZeroThreat.
* You have a GitHub account with permission to create issues in the intended repository.
* You are logged into the correct GitHub account in your browser.
* Your target is associated with a professional plan (or any plan that supports Issue Tracking integrations) in ZeroThreat.

#### Step 1: Connect ZeroThreat to GitHub

1. Navigate to the **Targets** (<img src="https://help.zerothreat.ai/Images/image%20(44).png" alt="" data-size="line">) section in ZeroThreat.
2. Click the **Continuous Integration** (<img src="https://help.zerothreat.ai/Images/image%20(207).png" alt="" data-size="line">) button for your desired target.
3. In the configuration drawer, click the **Issue Tracking** (<img src="https://help.zerothreat.ai/Images/image%20(208).png" alt="" data-size="line">) section.
4. Locate **GitHub** and click **Authorize**.

<figure><img src="https://1825008717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fs6Y7hKb1RwZWFZo4EnUm%2Fuploads%2FqhkazywxLuv9K65y3nZ1%2Fimage.png?alt=media&#x26;token=d76eb59f-c1f0-4095-8037-4e4b922ba2b4" alt=""><figcaption></figcaption></figure>

5. A new browser tab will open for GitHub authorization. Here you will see all the access rights required. Once ready click on **Authorize zerothreatai.**

<figure><img src="https://1825008717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fs6Y7hKb1RwZWFZo4EnUm%2Fuploads%2FGaoakh6aAodXmZh9WGj1%2FMicrosoftTeams-image%20(63).png?alt=media&#x26;token=844818d4-397a-4d14-962a-a98050cc4c64" alt="" width="563"><figcaption></figcaption></figure>

Here, you might be asked to complete your Multi-Factor Authentication that you set with GitHub. Complete the required Authentication.

<figure><img src="https://1825008717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fs6Y7hKb1RwZWFZo4EnUm%2Fuploads%2FpLwXShPQgdlolltLw4Td%2FMicrosoftTeams-image%20(61).png?alt=media&#x26;token=45308177-c72d-4931-b074-4f1bdd2e78de" alt=""><figcaption></figcaption></figure>

Once authorized, you’ll be redirected back to your ZeroThreat dashboard.

<figure><img src="https://1825008717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fs6Y7hKb1RwZWFZo4EnUm%2Fuploads%2Fhdipi8B1OZS36Vuc63QX%2FMicrosoftTeams-image%20(62).png?alt=media&#x26;token=d50c7eea-2ae8-4739-bf40-b85fa70a3587" alt=""><figcaption></figcaption></figure>

#### Step 2: Create GitHub Issues from a Scan Report

Once GitHub is connected:

1. Go to the **Scans** (<img src="https://help.zerothreat.ai/Images/image%20(210).png" alt="" data-size="line">) section in ZeroThreat.
2. Open any completed scan report.
3. Click the **GitHub Issues** button at the top of the report.

A GitHub integration popup will appear with configuration options.

#### Step 3: Configure GitHub Issue Settings

In the **GitHub Issue** popup:

* **Repository**: Select the GitHub repository where you want to track vulnerabilities.
* **Include Organization Resources (optional)**: Toggle this if you installed the app at the org level and want to browse org-wide repositories and Projects.
* **Projects (optional)**: Choose a GitHub Project to add issues to for planning and tracking.
  * Supports organization or repository Projects (subject to your GitHub permissions).

Click **Submit** to save your selections.

<figure><img src="https://1825008717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fs6Y7hKb1RwZWFZo4EnUm%2Fuploads%2F4CSzeSsSfauO3lMwEq4y%2FMicrosoftTeams-image%20(64).png?alt=media&#x26;token=e1b002dd-bb32-4690-aaba-6fa8c70ece10" alt="" width="563"><figcaption></figcaption></figure>

#### Step 4: Create Issues for Vulnerabilities

1. In the scan report, select the vulnerability you want to create a GitHub Issue for.
2. Click on **Create Issue** (<img src="https://1825008717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fs6Y7hKb1RwZWFZo4EnUm%2Fuploads%2F2XX3I4mBIWiTpOfucrPE%2FMicrosoftTeams-image%20(65).png?alt=media&#x26;token=a97718b8-3cf1-4a08-b4c9-bac202668338" alt="" data-size="line">) once done.

ZeroThreat will generate individual GitHub issues for each finding under that vulnerability.

<figure><img src="https://1825008717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fs6Y7hKb1RwZWFZo4EnUm%2Fuploads%2F0rPxoW4cIL1NhsAckwVk%2FMicrosoftTeams-image%20(66).png?alt=media&#x26;token=2da25774-2192-4e83-b09a-271da532f097" alt="" width="563"><figcaption></figcaption></figure>

All findings are immediately pushed to GitHub and can be tracked from either platform (ZeroThreat and GitHub).

{% hint style="info" %}
You can only create Issue for one vulnerability at a time, this is done to avoid cluttering your Repository. We recommend creating Issues only for the vulnerabilities that have impact, and are confirmed and verified.
{% endhint %}

#### Step 5: View and Manage Issues in GitHub

* Go to **Created Issues** in ZeroThreat to see all GitHub issues created for that scan.

<figure><img src="https://1825008717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fs6Y7hKb1RwZWFZo4EnUm%2Fuploads%2FG0goMHGYMG8ZBksgzjvG%2FMicrosoftTeams-image%20(67).png?alt=media&#x26;token=ec169aa4-7a44-4180-9f1a-686b7a9679ec" alt=""><figcaption></figcaption></figure>

* Click any issue to open it directly in GitHub. Each GitHub issue includes:
  * A detailed description of the vulnerability
  * HTTP request and response headers
  * Evidence (such as vulnerable parameters, payloads, or proof of concept)
  * A link back to the full scan report in ZeroThreat

<figure><img src="https://1825008717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fs6Y7hKb1RwZWFZo4EnUm%2Fuploads%2Fl1voEwHvjyveDCjxXEbZ%2FMicrosoftTeams-image%20(68).png?alt=media&#x26;token=ff06a01e-5f25-4e0a-8b44-e2a4f89d1285" alt="" width="563"><figcaption></figcaption></figure>

{% hint style="danger" %}
It is important that you don't remove the two labels **ZeroThreatAI** and **ZT-ME0Y8OX39319** (ZT-id). These two labels are used to enable bi-directional sync between ZeroThreat Portal and GitHub, removing this will stop the sync.
{% endhint %}

#### Step 6: Bi-directional Comment Sync

Collaborate without switching platforms:

* Leave comments on the GitHub issue—these will automatically appear in the corresponding vulnerability in ZeroThreat.
* Add comments from within ZeroThreat—they will be synced back to GitHub Issue.

<figure><img src="https://1825008717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fs6Y7hKb1RwZWFZo4EnUm%2Fuploads%2FlONAFDksXcHUjhChlvM3%2FMicrosoftTeams-image%20(69).png?alt=media&#x26;token=0e756223-5914-4a2b-8623-cc4e0e43f309" alt="" width="563"><figcaption></figcaption></figure>

This ensures both security and engineering teams stay aligned on context and progress.

#### Step 7: Monitor Issue Status in ZeroThreat

To view the current status of the issues you created:

1. Open the same scan report where you initially generated the GitHub issues.
2. Click the **GitHub Issue** button again and select the same repository (and Project, if used).

You’ll see the latest details for each issue, including assignees, and current status—such as **OPEN** or **CLOSED**—mirroring what you see in GitHub.

<figure><img src="https://1825008717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fs6Y7hKb1RwZWFZo4EnUm%2Fuploads%2F4WM2fhuvH8UfEGnAzNuu%2FMicrosoftTeams-image%20(70).png?alt=media&#x26;token=53bc32b5-52c6-486f-9822-509a73247e7e" alt="" width="563"><figcaption></figcaption></figure>

This provides a central, security-focused view of your development team’s progress on remediation.

### Best Practices

* Create GitHub issues only for validated, high-priority vulnerabilities to avoid noise.
* Align scan schedules with sprint cycles or release timeleines for smoother remediation planning.

You’re all set with GitHub Issues.\
Head over to our guide on Reviewing [**Scan Reports**](https://zerothreat.gitbook.io/docs-zerothreat/manage-scans/scan-report) to learn and analyze different sections of the scan report.
