Skip to main content

Эта версия GitHub Enterprise Server была прекращена 2025-04-03. Исправления выпускаться не будут даже при критических проблемах безопасности. Для повышения производительности, повышения безопасности и новых функций выполните обновление до последней версии GitHub Enterprise Server. Чтобы получить справку по обновлению, обратитесь в службу поддержки GitHub Enterprise.

Применение политик безопасности кода и анализа для вашего предприятия

Вы можете применять политики для управления использованием функций безопасности и анализа кода в организациях предприятия.

Кто может использовать эту функцию?

Enterprise owners

GitHub Advanced Security доступен для корпоративных учетных записей в GitHub Enterprise Cloud и GitHub Enterprise Server.

Дополнительные сведения см. в разделе Планы GitHub.

Сведения о GitHub Advanced Security for Azure DevOpsсм. в разделе "Настройка GitHub Advanced Security for Azure DevOps в Microsoft Learn.

About policies for using security features in your enterprise

You can enforce policies to manage the use of security features within organizations owned by your enterprise. You can allow or disallow people with admin access to a repository to enable or disable the security and analysis features.

Additionally, you can enforce policies for the use of GitHub Advanced Security in your enterprise's organizations and repositories.

Enforcing a policy for the availability of Advanced Security in your enterprise's organizations

GitHub bills for Advanced Security products on a per-committer basis. See About billing for GitHub Advanced Security.

You can enforce a policy that controls whether repository administrators are allowed to enable features for Advanced Security in an organization's repositories. You can configure a policy for all organizations owned by your enterprise account, or for individual organizations that you choose.

Disallowing GitHub Advanced Security for an organization prevents repository administrators from enabling GitHub Advanced Security features for additional repositories, but does not disable the features for repositories where the features are already enabled.

Note

This policy only impacts repository administrators, specifically. Organization owners and security managers can always enable security features, regardless of how you set this policy. For more information, see Roles in an organization.

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

    Screenshot of the dropdown menu shown when you click the profile photo on GitHub Enterprise Server. The "Enterprise settings" option is outlined.

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

  3. Under "Policies", click Code security and analysis.

  4. Under "Advanced Security availability", select the dropdown menu, then click a policy for the organizations owned by your enterprise.

  5. Optionally, if you chose Allow for selected organizations, to the right of an organization, select the dropdown menu to define which Advanced Security products are available to the organization.

    Screenshot of the dropdown menu to choose a Advanced Security policy for selected organizations in the enterprise. The dropdown is outlined.

Enforcing a policy to manage the use of Dependabot alerts in your enterprise

Across all organizations owned by your enterprise, you can allow members with admin permissions for repositories to enable or disable Dependabot alerts and change Dependabot alerts settings.

Note

This policy only impacts repository administrators, specifically. Organization owners and security managers can always enable security features, regardless of how you set this policy. For more information, see Roles in an organization.

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

    Screenshot of the dropdown menu shown when you click the profile photo on GitHub Enterprise Server. The "Enterprise settings" option is outlined.

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

  3. Under "Policies", click Code security and analysis.

  4. In the "Policies" section, under "Enable or disable Dependabot alerts by repository admins", use the dropdown menu to choose a policy.

Enforcing a policy to manage the use of Advanced Security features in your enterprise's repositories

Across all of your enterprise's organizations, you can allow or disallow people with admin access to repositories to manage the use of Advanced Security features in the repositories.

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

    Screenshot of the dropdown menu shown when you click the profile photo on GitHub Enterprise Server. The "Enterprise settings" option is outlined.

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

  3. Under "Policies", click Code security and analysis.

  4. In the "GitHub Advanced Security policies" section, under "Enable or disable GitHub Advanced Security by repository admins", select the dropdown menu and click a policy.

Enforcing a policy to manage the use of secret scanning in your enterprise's repositories

Across all of your enterprise's organizations, you can allow or disallow people with admin access to repositories to manage and configure secret scanning for the repositories. GitHub Advanced Security must be enabled for the organization for this policy to take effect.

Note

This policy only impacts repository administrators, specifically. Organization owners and security managers can always enable security features, regardless of how you set this policy. For more information, see Roles in an organization.

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

    Screenshot of the dropdown menu shown when you click the profile photo on GitHub Enterprise Server. The "Enterprise settings" option is outlined.

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

  3. Under "Policies", click Code security and analysis.

  4. In the "Policies" section, under "Enable or disable secret scanning by repository admins", select the dropdown menu and click a policy.