Note: Alerts are created only for repositories with secret scanning for advanced security enabled. Secrets found in public repositories using the free secret scanning for partner patterns service are reported directly to the partner, without creating an alert.
On GitHub.com, 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 "Close 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 Cloud is valid. If so, create a new secret, update any services that use the old secret, and then delete the old secret.
Note: If a secret is detected in a public repository on GitHub.com and the secret also matches a partner pattern, an alert is generated and the potential secret is reported to the service provider. For details of partner patterns, see "Supported secrets for partner patterns."
When a new secret is detected, GitHub Enterprise Cloud notifies all users with access to security alerts for the repository according to their notification preferences. You will receive an email notification if you are watching the repository, have enabled notifications for security alerts or for all the activity on the repository, or 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."