GitHub Destination

Configuring Github as an alert destination in your Panther Console


Destinations are integrations that receive alerts from rules, policies, system health notifications, and rule errors. Panther supports configuring Github as the destination where you will receive alerts.
The GitHub Destination requires a Repository name and an API Token.
When an alert is forwarded to a GitHub Destination, it creates an Issue in the repository. The repository must have Issues enabled.
The integration is most useful when infrastructure is defined in code such as with AWS CloudFormation or with Terraform.

How to set up Github alert destinations in Panther


We recommend creating a dedicated Panther Alerts service account in Github.

Generating an API Token in Github

Follow GitHub's documentation on generating a Personal Access Token.
  1. 1.
    Log in to your Github account using your service account (or any developer service account that has access to the repo)
  2. 2.
    Navigate to Settings > Developer settings:
    The image shows the Github "Developer Settings" page. In the upper right corner, a dropdown menu is expanded and the "Settings" option is highlighted.
  3. 3.
    On the Developer Settings page, Click Personal access tokens on the left. Click Generate new token.
    On the Developer Settings page in Github, the Personal Access Tokens tab is selected. There is a token named "Panther Alerts."
  4. 4.
    Fill out the form to configure your token. Select the repo permissions checkbox.
  5. 5.
    Click Generate Token. Copy the token and store it in a secure location, as you will need it in the next steps.
    • Note: GitHub does not allow you to view the token again. If you lose access to this token, you will need to generate a new one.
      In the Github page for Personal Access Tokens, the token appears in a green tile. A black rectangle covers the actual token value in this screen shot.

Configure the Github Destination in Panther

  1. 1.
    Log in to the Panther Console.
  2. 2.
    In the left sidebar, click Configure > Alert Destinations.
  3. 3.
    Click +Add your first Destination.
    • If you have already created Destinations, click Create New in the upper right side of the page to add a new Destination.
  4. 4.
    Click Github.
  5. 5.
    Fill out the form to configure the Destination:
    • Display Name: Enter a descriptive name.
    • Repository Name: Enter the Github repository name. This will be in the format owner/repo_name.
    • Token: Enter the token you generated in Github during the previous steps of this documentation.
    • Severity: Select the severity level of alerts to send to this Destination.
    • Alert Types: Select the alert types to send to this Destination.
    • Log Type: By default, we will send alerts from all log types. Specify log types here if you want to only send alerts from specific log types.
      In the Panther Console, the "Configure your Github Destination" page is displayed. It contains fields for Display Name, Repository Name, Token, Severity, Alert Types, and Log Types.
  6. 6.
    Click Add Destination.
  7. 7.
    On the final page, optionally click Send Test Alert to test the integration. When you are finished, click Finish Setup.

Additional Information on Destinations

For more information on alert routing order, modifying or deleting destinations, and workflow automation, please see the Panther docs: Destinations.