8c62486a96
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> Co-authored-by: Isaac Brown <101839405+isaacmbrown@users.noreply.github.com> Co-authored-by: mchammer01 <42146119+mchammer01@users.noreply.github.com> Co-authored-by: Anne-Marie <102995847+am-stead@users.noreply.github.com> Co-authored-by: Hector Alfaro <hectorsector@github.com> Co-authored-by: Vanessa <vgrl@github.com> Co-authored-by: Erin Havens <erinhav@github.com> Co-authored-by: Aaron Waggener <73763104+aaronwaggener@users.noreply.github.com> Co-authored-by: Sam Browning <106113886+sabrowning1@users.noreply.github.com> Co-authored-by: Sarah Schneider <sarahs@users.noreply.github.com> Co-authored-by: Sarita Iyer <66540150+saritai@users.noreply.github.com> Co-authored-by: Sarah Schneider <sarahs@github.com>
38 lines
2.6 KiB
Markdown
38 lines
2.6 KiB
Markdown
---
|
|
title: Editing a custom security configuration
|
|
shortTitle: Edit custom configuration
|
|
intro: 'Change the enablement settings in your {% data variables.product.prodname_custom_security_configuration %} to better meet the security needs of your repositories.'
|
|
permissions: '{% data reusables.permissions.security-configuration-enterprise-enable %}'
|
|
versions:
|
|
feature: security-configuration-enterprise-level
|
|
topics:
|
|
- Advanced Security
|
|
- Organizations
|
|
- Security
|
|
---
|
|
|
|
## About editing a {% data variables.product.prodname_custom_security_configuration %}
|
|
|
|
After creating and applying a {% data variables.product.prodname_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 {% data variables.product.prodname_security_configuration %} will automatically populate to all linked repositories.
|
|
|
|
{% ifversion security-configurations-cloud %}
|
|
|
|
> [!NOTE]
|
|
> The {% data variables.product.prodname_github_security_configuration %} is managed by {% data variables.product.github %} and cannot be edited. If you would like to customize your security enablement settings, you need to create a {% data variables.product.prodname_custom_security_configuration %}. For more information, see [AUTOTITLE](/admin/managing-code-security/securing-your-enterprise/creating-a-custom-security-configuration-for-your-enterprise).
|
|
|
|
{% endif %}
|
|
|
|
## Modifying your {% data variables.product.prodname_custom_security_configuration %}
|
|
|
|
{% data reusables.enterprise-accounts.access-enterprise %}
|
|
{% data reusables.enterprise-accounts.settings-tab %}
|
|
{% data reusables.enterprise-accounts.advanced-security-tab %}
|
|
1. In the "Configurations" section, click the name of the {% data variables.product.prodname_custom_security_configuration %} you want to edit.
|
|
1. Edit the name and description of your {% data variables.product.prodname_custom_security_configuration %} as desired.
|
|
1. Edit the enablement settings of your {% data variables.product.prodname_custom_security_configuration %} as desired.
|
|
1. 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.
|
|
|
|
{% data reusables.code-scanning.custom-security-configuration-enforcement-edge-cases-enterprise %}
|
|
|
|
1. To apply your changes, click **Update configuration**.
|