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 where GitHub Advanced Security is enabled. For more information, see "About GitHub Advanced Security."

In this article

Note: Secret scanning was in beta in GitHub Enterprise Server 3.0. For the generally available release of secret scanning, upgrade to the latest release of GitHub Enterprise Server.

Managing secret scanning alerts

  1. On GitHub Enterprise Server, 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, use 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 Enterprise Server is valid. If so, create a new secret, update any services that use the old secret, and then delete the old secret.

Did this doc help you?Privacy policy

Help us make these docs great!

All GitHub docs are open source. See something that's wrong or unclear? Submit a pull request.

Make a contribution

Or, learn how to contribute.