2e7adc3bd4
Co-authored-by: Anne-Marie <102995847+am-stead@users.noreply.github.com> Co-authored-by: Pallavi <96553709+pallsama@users.noreply.github.com> Co-authored-by: Isaac Brown <101839405+isaacmbrown@users.noreply.github.com> Co-authored-by: isaacmbrown <isaacmbrown@github.com> Co-authored-by: mchammer01 <42146119+mchammer01@users.noreply.github.com> Co-authored-by: Jules <19994093+jules-p@users.noreply.github.com> Co-authored-by: Rachael Rose Renk <91027132+rachaelrenk@users.noreply.github.com> Co-authored-by: Felicity Chapman <felicitymay@github.com> Co-authored-by: docs-bot <77750099+docs-bot@users.noreply.github.com> Co-authored-by: Hector Alfaro <hectorsector@github.com> Co-authored-by: Kevin Heis <heiskr@users.noreply.github.com>
3.2 KiB
title, shortTitle, intro, permissions, versions, topics
| title | shortTitle | intro | permissions | versions | topics | |||||
|---|---|---|---|---|---|---|---|---|---|---|
| Choosing a security configuration for your repositories | Choose security configuration | Find out which type of {% data variables.product.prodname_security_configuration %} will meet the security needs of the repositories in your organization. | {% data reusables.permissions.security-org-enable %} |
|
|
About choosing a {% data variables.product.prodname_security_configuration %}
{% data reusables.security-configurations.define-security-configurations %} {% data variables.product.company_short %} offers two types of {% data variables.product.prodname_security_configurations %}:
- The {% data variables.product.prodname_github_security_configuration %}
- {% data variables.product.prodname_custom_security_configurations_caps %}
We recommend that organizations initially apply the {% data variables.product.prodname_github_security_configuration %}. After you have applied the {% data variables.product.prodname_github_security_configuration %} to repositories in your organization, you can evaluate the security findings for each repository and determine if you instead want to create and apply a {% data variables.product.prodname_custom_security_configuration %}.
Choosing the {% data variables.product.prodname_github_security_configuration %}
The {% data variables.product.prodname_github_security_configuration %} offers a number of benefits:
- It is created and managed by {% data variables.product.company_short %}'s subject matter experts.
- It is the quickest {% data variables.product.prodname_security_configuration %} to apply to all repositories in your organization.
- It is designed to effectively secure both low- and high-impact repositories.
To start securing repositories in your organization with the {% data variables.product.prodname_github_security_configuration %}, see "AUTOTITLE."
Choosing a {% data variables.product.prodname_custom_security_configuration %}
If you are familiar with {% data variables.product.company_short %}'s security products, and you have specific security needs that the {% data variables.product.prodname_github_security_configuration %} can't meet, you can create and apply {% data variables.product.prodname_custom_security_configurations %}. With {% data variables.product.prodname_custom_security_configurations %}, you can:
- Edit the enablement settings for different security features
- Create several configurations for repositories with different security needs
- Manage your {% data variables.product.prodname_GH_advanced_security %} licensing by including or excluding {% data variables.product.prodname_GH_advanced_security %} features for a particular configuration
To start securing repositories in your organization with {% data variables.product.prodname_custom_security_configurations %}, see "AUTOTITLE."