Skip to main content
ドキュメントへの更新が頻繁に発行されており、このページの翻訳はまだ行われている場合があります。最新情報については、英語版のドキュメントをご覧ください。
現在、GitHub AE は限定的リリースです。
 

 

Securing your organization

この記事では、次の項目が扱われます。

You can use a number of GitHub features to help keep your organization secure.

Who can use this feature

Organization owners can configure organization security settings.

Introduction

This guide shows you how to configure security features for an organization. Your organization's security needs are unique and you may not need to enable every security feature. For more information, see "GitHub security features."

一部の機能は、すべてのリポジトリに使用できます。 その他の機能は、GitHub Advanced Security を使うエンタープライズに使用できます。 詳細については、「GitHub Advanced Security について」を参照してください。

Managing access to your organization

You can use roles to control what actions people can take in your organization. For example, you can assign the security manager role to a team to give them the ability to manage security settings across your organization, as well as read access to all repositories. For more information, see "Roles in an organization."

Managing Dependabot alerts and the dependency graph

注: 現在、Dependabot alerts はベータ版であり、変更される可能性があります。

Enterprise の所有者は、Dependabot alerts を構成できます。 詳細については、「[エンタープライズの Dependabot の有効化](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)」を参照してください。

For more information, see "About Dependabot alerts," "Exploring the dependencies of a repository," and "Managing security and analysis settings for your organization."

Managing dependency review

Dependency review is an Advanced Security feature that lets you visualize dependency changes in pull requests before they are merged into your repositories. For more information, see "About dependency review."

Dependency review is available when dependency graph is enabled for your enterprise and you enable Advanced Security for the organization (see below).

Managing GitHub Advanced Security

You can enable or disable Advanced Security features.

  1. Click your profile photo, then click Organizations.
  2. Click Settings next to your organization.
  3. Click Security & analysis.
  4. Click Enable all or Disable all next to GitHub Advanced Security.
  5. Optionally, select Automatically enable for new private repositories.

For more information, see "About GitHub Advanced Security" and "Managing security and analysis settings for your organization."

Configuring secret scanning

Secret scanning is an Advanced Security feature that scans repositories for secrets that are insecurely stored.

Secret scanning is available if your enterprise uses Advanced Security.

You can enable or disable secret scanning for all repositories across your organization that have Advanced Security enabled.

  1. Click your profile photo, then click Organizations.
  2. Click Settings next to your organization.
  3. Click Security & analysis.
  4. Click Enable all or Disable all next to Secret scanning (GitHub Advanced Security repositories only).
  5. Optionally, select Automatically enable for private repositories added to Advanced Security.

For more information, see "Managing security and analysis settings for your organization."

Configuring code scanning

Code scanning is an Advanced Security feature that scans code for security vulnerabilities and errors

Code scanning is available if your enterprise uses Advanced Security.

Code scanning is configured at the repository level. For more information, see "Setting up code scanning for a repository."

Next steps

You can view and manage alerts from security features to address dependencies and vulnerabilities in your code. For more information, see "Managing code scanning for your repository," and "Managing alerts from secret scanning."

You can view, filter, and sort security alerts for repositories owned by your organization in the security overview. For more information, see "About the security overview."