Skip to main content

Managing alerts from secret scanning

You can view and close alerts for secrets checked in to your repository.

Secret scanning is available for organization-owned repositories in GitHub AE. This is a GitHub Advanced Security feature (free during the beta release).

Managing secret scanning alerts

  1. On your enterprise, navigate to the main page of the repository.

  2. Under your repository name, click Security. Security tab

  3. In the left sidebar, click Secret scanning alerts.

    "Secret scanning alerts" tab

  4. Under "Secret scanning" click the alert you want to view.

    List of alerts from secret scanning

  5. Optionally, select the "Mark as" drop-down menu and click a reason for resolving an alert.

    Drop-down menu for resolving an alert from secret scanning

Securing compromised secrets

Once a secret has been committed to a repository, you should consider the secret compromised. GitHub recommends the following actions for compromised secrets:

  • For a compromised GitHub personal access token, delete the compromised token, create a new token, and update any services that use the old token. For more information, see "Creating a personal access token for the command line."
  • For all other secrets, first verify that the secret committed to GitHub AE is valid. If so, create a new secret, update any services that use the old secret, and then delete the old secret.