Co-authored-by: Sarita Iyer <66540150+saritai@users.noreply.github.com> Co-authored-by: Anne-Marie <102995847+am-stead@users.noreply.github.com> Co-authored-by: Felicity Chapman <felicitymay@github.com> Co-authored-by: github-actions <github-actions@github.com> Co-authored-by: Ben Ahmady <32935794+subatoi@users.noreply.github.com> Co-authored-by: Dorothy Mitchell <19343236+dorothymitchell@users.noreply.github.com> Co-authored-by: mc <42146119+mchammer01@users.noreply.github.com>
6.7 KiB
title, intro, permissions, versions, type, topics, shortTitle
| title | intro | permissions | versions | type | topics | shortTitle | |||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Managing GitHub Advanced Security features for your enterprise | You can control {% data variables.product.prodname_GH_advanced_security %} features that secure and analyze code across all organizations owned by your enterprise. | Enterprise owners can manage {% data variables.product.prodname_advanced_security %} features for organizations in an enterprise. |
|
how_to |
|
Manage GitHub Advanced Security |
About management of {% data variables.product.prodname_advanced_security %} features
You can use {% data variables.product.prodname_advanced_security %} features to harden security for the organizations in your enterprise. {% ifversion security-configurations %}{% data reusables.security-configurations.enable-security-features-with-gh-config %}
{% note %}
Note: {% data reusables.security-configurations.security-configurations-beta-note-short %}
{% endnote %}
To manage individual {% data variables.product.prodname_GH_advanced_security %} features, {% else %}To streamline management of {% data variables.product.prodname_advanced_security %}, {% endif %}you can enable or disable each feature for all existing and/or new repositories within the organizations owned by your enterprise.
{% ifversion secret-scanning-enterprise-level-api %}{% data reusables.secret-scanning.secret-scanning-enterprise-level-api %}{% endif %}
{% ifversion ghes %}For information about buying a license for {% data variables.product.prodname_GH_advanced_security %}, see "AUTOTITLE."{% elsif ghec %}For information about buying a license for {% data variables.product.prodname_GH_advanced_security %}, see "AUTOTITLE."{% endif %}
If you have disallowed {% data variables.product.prodname_GH_advanced_security %} for an organization, that organization will not be affected by enabling a feature for all existing repositories or for all new repositories. For more information about disallowing {% data variables.product.prodname_GH_advanced_security %} for an organization, see "AUTOTITLE."
When you enable one or more security and analysis features for existing repositories, you will see any results displayed on {% data variables.product.prodname_dotcom %} within minutes.
{% data reusables.security.security-and-analysis-features-enable-read-only %}
Managing {% data variables.product.prodname_advanced_security %} features
{% data reusables.advanced-security.note-org-enable-uses-seats %}
{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %}
-
In the left sidebar, click Code security & analysis.
-
Optionally, enable or disable a feature for all existing repositories.
-
To the right of the feature, click Disable all or Enable all. {% ifversion ghes or ghec %}If the control for "{% data variables.product.prodname_GH_advanced_security %}" is disabled, you have no available {% ifversion ghas-billing-UI-update %}licenses{% else %}seats{% endif %} for {% data variables.product.prodname_GH_advanced_security %}.{% endif %}
-
To confirm the change, click the Enable/Disable all or Enable/Disable for eligible repositories button in the dialog that is displayed.
-
-
Optionally, to enable or disable a feature automatically when new private and internal repositories{% ifversion secret-scanning-user-owned-repos %}, user namespace repositories {% ifversion ghec %}belonging to {% data variables.product.prodname_emus %}{% endif %}{% endif %}, or public repositories and repositories with {% data variables.product.prodname_GH_advanced_security %} enabled are created, select the checkbox below the feature. {% ifversion secret-scanning-validity-check-partner-patterns %}
-
Optionally, to automatically allow {% data variables.product.prodname_secret_scanning %} to check the validity of a secret by sending it to the relevant partner, select the relevant checkbox under "{% data variables.product.prodname_secret_scanning_caps %}". You can also enable the validity check for a single repository or organization. For more information, see "AUTOTITLE," and "AUTOTITLE."
For information on using the REST API to enable validity checks for partner patterns for your enterprise, see "AUTOTITLE."
{% data reusables.secret-scanning.validity-check-partner-patterns-beta %}
{%- endif %} {% ifversion secret-scanning-custom-link-on-block %}
-
Optionally, to include a resource link in the message that members will see when they attempt to push a secret, select Add a resource link in the CLI and web UI when a commit is blocked, then type a URL, and click Save link.
{% note %}
Note: When a custom link is configured for an organization, the organization-level value overrides the custom link set for the enterprise. For more information, see "AUTOTITLE."
{% endnote %}


