Code security configurations available at the enterprise level - GHES 3.16+ (#54414)

Co-authored-by: Kevin Heis <heiskr@users.noreply.github.com>

content/admin/managing-code-security/managing-github-advanced-security-for-your-enterprise/index.md

@@ -1,7 +1,8 @@
 ---
 title: '{% ifversion ghes %}Setting up GitHub Advanced Security features on your appliance{% else %}Configuring infrastructure for GitHub Advanced Security features{% endif %}'
 shortTitle: '{% ifversion ghes %}Set up{% else %}Configure{% endif %} GitHub Advanced Security'
-intro: 'You can {% ifversion ghes %}set up{% else %}configure{% endif %} {% data variables.product.prodname_advanced_security %} to suit your organization''s needs.'
+intro: 'You can {% ifversion ghes %}set up{% else %}configure{% endif %} {% data variables.product.prodname_advanced_security %} to suit your enterprise''s needs.'
+allowTitleToDifferFromFilename: true
 product: '{% data reusables.gated-features.ghas %}'
 redirect_from:
   - /enterprise/admin/configuration/configuring-advanced-security-features

content/admin/managing-code-security/securing-your-enterprise/creating-a-custom-security-configuration-for-your-enterprise.md

@@ -88,9 +88,6 @@ When creating a security configuration, keep in mind that:
     * Alerts. To learn about {% data variables.secret-scanning.alerts %}, see [AUTOTITLE](/code-security/secret-scanning/introduction/about-secret-scanning).{% ifversion org-npp-enablement-security-configurations %}
     * Non-provider patterns. To learn more about scanning for non-provider patterns, see [AUTOTITLE](/code-security/secret-scanning/introduction/supported-secret-scanning-patterns#non-provider-patterns) and [AUTOTITLE](/code-security/secret-scanning/managing-alerts-from-secret-scanning/viewing-alerts).{% endif %}
     * Push protection. To learn about push protection, see [AUTOTITLE](/code-security/secret-scanning/introduction/about-push-protection).
-{% ifversion push-protection-delegated-bypass-configurations %}
-1. Optionally, under "Push protection", choose whether you want to assign bypass privileges to selected actors in your organization. By assigning bypass privileges, selected organization members can bypass push protection, and there is a review and approval process for all other contributors. For further guidance on how to configure this setting, see [AUTOTITLE](/code-security/secret-scanning/using-advanced-secret-scanning-and-push-protection-features/delegated-bypass-for-push-protection/enabling-delegated-bypass-for-push-protection#configuring-delegated-bypass-for-an-organization).
-{% endif %}
 1. Optionally, in the "Policy" section, you can choose to automatically apply the {% data variables.product.prodname_security_configuration %} to newly created repositories depending on their visibility. Select the **None** {% octicon "triangle-down" aria-hidden="true" %} dropdown menu, then click **Public**, or **Private and internal**, or **All repositories**.
 
 1. Optionally, in the "Policy" section, you can enforce the configuration and block repository owners from changing features that are enabled or disabled by the configuration (features that are not set aren't enforced). Next to "Enforce configuration", select **Enforce** from the dropdown menu.

content/admin/managing-code-security/securing-your-enterprise/deleting-a-custom-security-configuration.md

@@ -24,5 +24,5 @@ If you no longer need a {% data variables.product.prodname_custom_security_confi
 {% data reusables.enterprise-accounts.settings-tab %}
 1. In the left sidebar, click **Code security**.
 1. In the configurations table, click the name of the {% data variables.product.prodname_custom_security_configuration %} you want to delete.
-1. In the "Edit configuration" page, scroll to the bottom of the "Security settings" section, then click **Delete configuration**.
+1. In the "Edit configuration" page, scroll to the bottom of the "Policy" section, then click **Delete configuration**.
 1. Ensure you read the warning in the "Delete this configuration?" dialog, to confirm you are comfortable deleting the {% data variables.product.prodname_custom_security_configuration %}, then click **Delete configuration**.

data/reusables/security-configurations/security-features-use-actions.md

@@ -1 +1,5 @@
+{% ifversion ghec %}
+
 >[!NOTE] Some features enabled in {% data variables.product.prodname_security_configurations %} may require Actions minutes to work. {% data variables.product.prodname_dotcom %} will let you know if that's the case when you apply the configuration to a repository. For more information about billing for {% data variables.product.prodname_actions %}, see [AUTOTITLE](/billing/managing-billing-for-github-actions/about-billing-for-github-actions).
+
+{% endif %}