Frecuentemente publicamos actualizaciones de nuestra documentación. Es posible que la traducción de esta página esté en curso. Para conocer la información más actual, visita la documentación en inglés. Si existe un problema con las traducciones en esta página, por favor infórmanos.

Managing alerts from secret scanning

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

Escaneo de secretos is available for all public repositories, and for private repositories owned by organizations where GitHub Advanced Security is enabled. For more information, see "About GitHub Advanced Security."

En este artículo

Nota: Las Escaneo de secretos para los repositorios privados se encuentran actualmente en beta y están sujetas a cambios. Para solicitar acceso al beta,, únete a la lista de espera.

Managing escaneo de secretos alerts

  1. En GitHub, visita la página principal del repositorio.

  2. Debajo de tu nombre de repositorio, da clic en Seguridad. Pestaña de seguridad

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

Configuring notifications for escaneo de secretos alerts

When a new secret is detected, GitHub 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 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."

¿Te ayudó este documento?

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

O, learn how to contribute.