Skip to main content
ドキュメントには� �繁に更新が� えられ、その都度公開されています。本ページの翻訳はま� 未完成な部分があることをご了承く� さい。最新の情� �については、英語のドキュメンテーションをご参照く� さい。本ページの翻訳に問題がある� �合はこちらまでご連絡く� さい。
Enterprise Server 3.1
日本語
� 
Code security
Enterprise Server 3.1
日本語

� 

このバージョンの GitHub Enterprise はこの日付をもって終了となりました: 2022-06-03. 重大なセキュリティの問題に対してであっても、パッチリリースは作成されません。 パフォーマンスの向上、セキュリティの改善、新機能のためには、最新バージョンのGitHub Enterpriseにアップグレードしてく� さい。 アップグレードに関する支援については、GitHub Enterprise supportに連絡してく� さい。

Securing your repository

ここには以下の内容があります:

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

Repository administrators and organization owners can configure repository security settings.

Introduction

This guide shows you how to configure security features for a repository. You must be a repository administrator or organization owner to configure security settings for a repository.

Your security needs are unique to your repository, so you may not need to enable every feature for your repository. For more information, see "GitHub security features."

Some features are available for all repositories. Additional features are available to enterprises that use GitHub Advanced Security. 詳しい情� �については、「GitHub Advanced Security について」を参照してく� さい。

Managing access to your repository

The first step to securing a repository is to set up who can see and modify your code. For more information, see "Managing repository settings."

From the main page of your repository, click Settings, then scroll down to the "Danger Zone."

Setting a security policy

  1. From the main page of your repository, click Security.
  2. Click Security policy.
  3. Click Start setup.
  4. Add information about supported versions of your project and how to report vulnerabilities.

For more information, see "Adding a security policy to your repository."

Managing the dependency graph

Enterprise owners can configure the dependency graph and Dependabotアラート for an enterprise. 詳しい情� �については「Enterpriseでの依存関係グラフの有効化」及び「EnterpriseでのDependabotの有効化」を参照してく� さい。

For more information, see "Exploring the dependencies of a repository."

Managing Dependabotアラート

Dependabotアラート are generated when GitHub identifies a dependency in the dependency graph with a vulnerability.

Enterprise owners can configure the dependency graph and Dependabotアラート for an enterprise. 詳しい情� �については「Enterpriseでの依存関係グラフの有効化」及び「EnterpriseでのDependabotの有効化」を参照してく� さい。

For more information, see "About Dependabotアラート."

Configuring code scanning

You can set up code scanning to automatically identify vulnerabilities and errors in the code stored in your repository by using a CodeQL分析ワークフロー or third-party tool. For more information, see "Setting up code scanning for a repository."

Code scanning is available for organization-owned repositories if your enterprise uses GitHub Advanced Security.

Configuring secret scanning

Secret scanning is available for organization-owned repositories if your enterprise uses GitHub Advanced Security. Secret scanning may already be enabled for your repository, depending upon your organization's settings.

  1. From the main page of your repository, click Settings.
  2. Click Security & analysis.
  3. If GitHub Advanced Security is not already enabled, click Enable.
  4. Next to Secret scanning, click Enable.

Next steps

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