Advanced Security의 유료 사용 관리하기

조직에서 GitHub Advanced Security 비용을 제어하십시오.

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

관리자 역할이 있는 조직 소유자, 보안 관리자 및 조직 구성원

이 문서의 내용

Prerequisites

Before you can effectively manage your paid use of Advanced Security, you should understand how Advanced Security is billed. See GitHub Advanced Security license billing.

Understanding your license usage

  1. In the upper-right corner of GitHub, click your profile picture, then click Organizations.

  2. Under your organization name, click Settings. If you cannot see the "Settings" tab, select the dropdown menu, then click Settings.

    Screenshot of the tabs in an organization's profile. The "Settings" tab is outlined in dark orange.

  3. In the "Security" section of the sidebar, select the Code security dropdown menu, then click Configurations.

  4. In the "Apply configurations" section, your current license usage will be displayed. NUMBER-USED out of NUMBER-PURCHASED available GitHub Advanced Security licenses in use by YOUR-ENTERPRISE.

    Screenshot of the "Apply configurations" section. The current license use for the enterprise is outlined in dark orange.

  5. Optionally, to find specific repositories in your organization, filter the repository table. To learn more, see Filtering repositories in your organization using the repository table.

  6. To quickly identify the number of licenses needed to enable GitHub Advanced Security on a specific repository, in that repository's row of the repository table, read "NUMBER licenses required".

  7. To view license usage for multiple repositories in your organization, select the repositories from the repository table. In the "Apply configurations" section, you will see the number of licenses required to apply GitHub Advanced Security to the repositories, as well as the number of licenses made available if you disable GitHub Advanced Security on those repositories.

    Screenshot of the "Apply configurations" section. The potential changes to GHAS license usage for the enterprise are outlined in dark orange.

Turning off Advanced Security

The simplest way to turn off all Advanced Security features for one or more repositories is to create a security configuration where the product is disabled at the top level. You can apply this custom configuration to repositories where you want to turn off paid features.

팁

Ensure that you give your custom configuration a very clear name, for example: "No Code Security" or "Secret Protection and Supply chain only" to avoid confusion.

For more information, see Creating a custom security configuration and Applying a custom security configuration.

To prevent future enablement of security features, we recommend you ask your enterprise administrator to set the enterprise account's Advanced Security policies so that: