Skip to main content
We publish frequent updates to our documentation, and translation of this page may still be in progress. For the most current information, please visit the English documentation.

비밀 검사에서 경고 관리

리포지토리에 체크 인된 비밀에 대한 경고를 보고 닫을 수 있습니다.

Who can use this feature

People with admin access to a repository can view and dismiss secret scanning alerts for the repository.

Secret scanning alerts for partners는 모든 공용 리포지토리에서 자동으로 실행됩니다. GitHub Advanced Security에 대한 라이선스가 있는 경우 조직이 소유한 모든 리포지토리에 대해 secret scanning alerts for users를 사용하도록 설정하고 구성할 수 있습니다. 자세한 내용은 "secret scanning alerts for users정보" 및 "GitHub Advanced Security 정보"를 참조하세요.

Managing secret scanning alerts

Note: Alerts are created only for repositories with secret scanning alerts for users enabled. Secrets found in public repositories using the free secret scanning alerts for partners service are reported directly to the partner, without creating an alert. For more information, see "Supported secrets for partner alerts."

  1. On, navigate to the main page of the repository.

  2. Under the repository name, click Security. Security tab

  3. In the left sidebar, click Secret scanning alerts.

    Screenshot of the "Secret scanning alerts" tab

  4. Under "Secret scanning" click the alert you want to view.

    Screenshot of the list of alerts from secret scanning

  5. Check the validity of the secret and follow the remediation steps.

    Screenshot of the validity check for a GitHub token

    Note: Validity check for GitHub tokens is currently in public beta and subject to change.

    GitHub provides information about the validity of the secret, for GitHub tokens only.

    Active secretGitHub confirmed this secret is active
    Active secretGitHub checked with this secret's provider and found that the secret is active
    Possibly active secretGitHub does not support validation checks for this token type yet
    Possibly active secretGitHub could not verify this secret
    Secret appears inactiveYou should make sure no unauthorized access has already occurred
  6. To dismiss an alert, select the "Close as" dropdown menu and click a reason for resolving an alert.

    Screenshot of the dropdown menu for dismissing an alert from secret scanning showing link to partner documentation

  7. Optionally, add a dismissal comment. The dismissal comment will be added to the alert timeline and can be used as justification during auditing and reporting. You can view the history of all dismissed alerts and dismissal comments in the alert timeline. You can also retrieve or set a comment by using the Secret scanning API. The comment is contained in the resolution_comment field. For more information, see "Secret scanning" in the REST API documentation.

    Screenshot showing how to dismiss an alert via the "Dismiss alert" dropdown, with the option to add a dismissal comment

  8. Click Close alert.

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 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 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 alerts."

Configuring notifications for secret scanning alerts

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."