Enterprise Server 3.16 está disponível no momento como versão release candidate.

Edição de uma configuração de segurança personalizada

Altere as configurações de habilitação em sua custom security configuration para atender melhor às necessidades de segurança dos repositórios.

Quem pode usar esse recurso?

Site administrators

Neste artigo

About editing a custom security configuration

After creating and applying a custom security configuration, you may need to edit the enablement settings for that configuration to better secure your repositories. Any changes you make to the enablement settings of a security configuration will automatically populate to all linked repositories.

Modifying your custom security configuration

  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 Settings.

  3. In the left sidebar, click Code security.

  4. In the "Configurations" section, click the name of the custom security configuration you want to edit.

  5. Edit the name and description of your custom security configuration as desired.

  6. In the "Security settings" section, edit the enablement settings of your custom security configuration as desired.

  7. In the "Policy" section, you can modify the configuration's enforcement status. Enforcing a configuration will block repository owners from changing features that are enabled or disabled by the configuration, but features that are not set aren't enforced. Next to "Enforce configuration", select Enforce or Don't enforce from the dropdown menu.

    Note

    If a user in your enterprise attempts to change the enablement status of a feature in an enforced configuration using the REST API, the API call will appear to succeed, but no enablement statuses will change.

    Some situations can break the enforcement of security configurations for a repository. For example, the enablement of code scanning will not apply to a repository if:

    • GitHub Actions is initially enabled on the repository, but is then disabled in the repository.
    • GitHub Actions required by code scanning configurations are not available in the repository.
    • Self-hosted runners with the label code-scanning are not available.
    • The definition for which languages should not be analyzed using code scanning default setup is changed.

  8. To apply your changes, click Update configuration.