Affichage et filtrage des alertes à partir de l’analyse des secrets

Découvrez comment rechercher et filtrer analyse des secrets les alertes pour votre référentiel.

Qui peut utiliser cette fonctionnalité ?

Propriétaires de référentiels, propriétaire d’organisations, gestionnaires de sécurité et utilisateurs avec le rôle d’administrateur

Dans cet article

About the secret scanning alerts page

When you enable secret scanning for a repository or push commits to a repository with secret scanning enabled, GitHub scans the contents for secrets that match patterns defined by service providers and any custom patterns defined in your enterprise, organization, or repository.

When secret scanning detects a secret, GitHub generates an alert. GitHub displays an alert in the Security tab of the repository.

To help you triage alerts more effectively, GitHub separates alerts into two lists:

  • High confidence alerts.
  • Other alerts.

Screenshot of the secret scanning alert view. The button to toggle between "High confidence" and "Other" alerts is highlighted with an orange outline.

High confidence alerts list

The "High confidence" alerts list displays alerts that relate to supported patterns and specified custom patterns. This list is always the default view for the alerts page.

Other alerts list

The "Other" alerts list displays alerts that relate to non-provider patterns (such as private keys). These types of alerts have a higher rate of false positives.

In addition, alerts that fall into this category:

  • Are limited in quantity to 5000 alerts per repository (this includes open and closed alerts).
  • Are not shown in the summary views for security overview, only in the "Secret scanning" view.
  • Only have the first five detected locations shown on GitHub for non-provider patterns.

For GitHub to scan for non-provider patterns, you must first enable the feature for your repository or organization. For more information, see Enabling secret scanning for non-provider patterns.

Viewing alerts

Alerts for secret scanning are displayed under the Security tab of the repository.

  1. On GitHub, navigate to the main page of the repository.
  2. Under the repository name, click Security. If you cannot see the "Security" tab, select the dropdown menu, and then click Security.
    Screenshot of a repository header showing the tabs. The "Security" tab is highlighted by a dark orange outline.
  3. In the left sidebar, under "Vulnerability alerts", click Secret scanning.
  4. Optionally, toggle to "Other" to see alerts for non-provider patterns.
  5. Under "Secret scanning", click the alert you want to view.

Filtering alerts

You can apply various filters to the alerts list to help you find the alerts you're interested in. You can use the dropdown menus above the alerts list, or input the qualifiers listed in the table into the search bar.

QualifierDescription
is:openDisplays open alerts.
is:closedDisplays closed alerts.
validity:activeDisplays alerts for secrets that are known to be active. For more information about validity statuses, see Evaluating alerts from secret scanning.
validity:inactiveDisplays alerts for secrets that are no longer active.
validity:unknownDisplays alerts for secrets where the validity status of the secret is unknown.
secret-type:SECRET-NAMEDisplays alerts for a specific secret type, for example, secret-type:github_personal_access_token. For a list of supported secret types, see Supported secret scanning patterns.
provider:PROVIDER-NAMEDisplays alerts for a specific provider, for example, provider:github. For a list of supported partners, see Supported secret scanning patterns.
confidence:highDisplays alerts for high-confidence secrets, which relate to supported secrets and custom patterns. For a list of supported patterns, see Supported secret scanning patterns.
confidence:otherDisplays alerts for non-provider patterns, such as private keys. For a list of supported non-provider patterns, see Supported secret scanning patterns.

Next steps