Skip to main content

엔터프라이즈용 GitHub Advanced Security 기능 관리

엔터프라이즈가 소유한 모든 조직에서 코드를 보호하고 분석하는 GitHub Advanced Security 기능을 제어할 수 있습니다.

누가 이 기능을 사용할 수 있는 있나요?

Enterprise owners can manage Advanced Security features for organizations in an enterprise.

About management of Advanced Security features

You can use Advanced Security features to harden security for the organizations in your enterprise. You can quickly enable security features at scale with the GitHub-recommended security configuration, a collection of security enablement settings you can apply to repositories in an organization. You can then further customize GitHub Advanced Security features at the organization level with global settings. See "About enabling security features at scale."

Security configurations and global settings are in beta and subject to change.

To manage individual GitHub Advanced Security features, you can enable or disable each feature for all existing and/or new repositories within the organizations owned by your enterprise.

You can also enable or disable Advanced Security features via the API. For more information, see "REST API endpoints for secret scanning" in the REST API documentation.

For information about buying a license for GitHub Advanced Security, see "About billing for GitHub Advanced Security."

If you have disallowed GitHub Advanced Security for an organization, that organization will not be affected by enabling a feature for all existing repositories or for all new repositories. For more information about disallowing GitHub Advanced Security for an organization, see "Enforcing policies for code security and analysis for your enterprise."

When you enable one or more security and analysis features for existing repositories, you will see any results displayed on GitHub within minutes.

Managing Advanced Security features

Note: If you enable GitHub Advanced Security, active committers to these repositories will use GitHub Advanced Security licenses. This option is deactivated if you have exceeded your license capacity.

  1. In the top-right corner of GitHub Enterprise Server, click your profile photo, then click Enterprise settings.

    Screenshot of the drop-down menu that appears when you click the profile photo on GitHub Enterprise Server. The "Enterprise settings" option is highlighted in a dark orange outline.

  2. On the left side of the page, in the enterprise account sidebar, click Settings.

  3. In the left sidebar, click Code security & analysis.

  4. Optionally, enable or disable a feature for all existing repositories.

    • To the right of the feature, click Disable all or Enable all. If the control for "GitHub Advanced Security" is disabled, you have no available licenses for GitHub Advanced Security.

      Screenshot of the "Configure security and analysis features" section of the enterprise settings. To the right of each setting are "Enable all" and "Disable all" buttons, which are outlined in dark orange.

    • To confirm the change, click the Enable/Disable all or Enable/Disable for eligible repositories button in the dialog that is displayed.

  5. Optionally, to enable or disable a feature automatically when new private and internal repositories, user namespace repositories , or public repositories and repositories with GitHub Advanced Security enabled are created, select the checkbox below the feature.

  6. Optionally, to include a resource link in the message that members will see when they attempt to push a secret, select Add a resource link in the CLI and web UI when a commit is blocked, then type a URL, and click Save link.

    Note: When a custom link is configured for an organization, the organization-level value overrides the custom link set for the enterprise. For more information, see "Push protection for repositories and organizations."

    Screenshot of the "Push protection" section of the settings for security and analysis features. The checkbox and the text field used for enabling a custom link are outlined in dark orange.