Skip to main content

このバージョンの GitHub Enterprise はこの日付をもって終了となります: 2022-10-12. 重大なセキュリティの問題に対してであっても、パッチリリースは作成されません。 パフォーマンスの向上、セキュリティの向上、新機能の向上を図るために、最新バージョンの GitHub Enterprise にアップグレードします。 アップグレードに関するヘルプについては、GitHub Enterprise サポートにお問い合わせください

Managing alerts from secret scanning

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

Secret scanning is available for organization-owned repositories in GitHub Enterprise Server if your enterprise has a license for GitHub Advanced Security. 詳細については、「GitHub Advanced Security について」を参照してください。

Managing secret scanning alerts

  1. your GitHub Enterprise Server instance で、リポジトリのメイン ページへ移動します。

  2. リポジトリ名の下にある [Security](セキュリティ) をクリックします。 [セキュリティ] タブ

  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. To dismiss an alert, select the "Mark as" dropdown menu and click a reason for resolving an alert.

    Screenshot of the dropdown 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 Enterprise Server 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 secret scanning alerts

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