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. For more information about upgrading your GitHub Enterprise Server instance, see "About upgrades to new releases" and refer to the Upgrade assistant to find the upgrade path from your current release version.
On your GitHub Enterprise Server instance, navigate to the main page of the repository.
Under your repository name, click Security.
In the left sidebar, click Secret scanning alerts.
Under "Secret scanning" click the alert you want to view.
Optionally, select the "Mark as" drop-down menu and click a reason for resolving an alert.
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.
When a new secret is detected, GitHub Enterprise Server notifies all users with access to security alerts for the repository according to their notification preferences. You will receive alerts if you are watching the repository, have enabled notifications for security alerts or for all the activity on the repository, are the author of the commit that contains the secret and are not ignoring the repository.
For more information, see "Managing security and analysis settings for your repository" and "Configuring notifications."