Skip to content

Commit cd8bf2a

Browse files
authored
GHAS unbundling: review and update non-UI instances of "code security" (#54699)
1 parent 5863c11 commit cd8bf2a

25 files changed

Lines changed: 57 additions & 56 deletions

File tree

content/actions/security-for-github-actions/security-guides/using-githubs-security-features-to-secure-your-use-of-github-actions.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -80,7 +80,7 @@ For information on how to configure {% data variables.product.prodname_dependabo
8080

8181
## Protecting actions you've created
8282

83-
{% data variables.product.prodname_dotcom %} enables collaboration between people who publish and maintain actions and vulnerability reporters in order to promote code security. {% data reusables.security-advisory.security-advisory-overview %}
83+
{% data variables.product.prodname_dotcom %} enables collaboration between people who publish and maintain actions and vulnerability reporters in order to promote secure coding. {% data reusables.security-advisory.security-advisory-overview %}
8484

8585
If you are someone who maintains an action that is used in other projects, you can use the following {% data variables.product.prodname_dotcom %} features to enhance the security of the actions you've published.
8686

content/admin/enforcing-policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-code-security-and-analysis-for-your-enterprise.md

Lines changed: 7 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,8 @@
11
---
2-
title: Enforcing policies for code security and analysis for your enterprise
3-
intro: 'You can enforce policies to manage the use of code security and analysis features within your enterprise''s organizations.'
4-
permissions: 'Enterprise owners can define and enforce policies to control use of code security and analysis features in an enterprise.'
2+
title: Enforcing policies for security features in your enterprise
3+
intro: 'You can enforce policies to manage the use of security features for codebases within your enterprise''s organizations.'
4+
allowTitleToDifferFromFilename: true
5+
permissions: 'Enterprise owners'
56
product: '{% data reusables.gated-features.ghas %}'
67
versions:
78
ghec: '*'
@@ -26,12 +27,12 @@ redirect_from:
2627
- /github/setting-up-and-managing-your-enterprise/enforcing-a-policy-on-dependency-insights-in-your-enterprise-account
2728
- /github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account/enforcing-a-policy-on-dependency-insights-in-your-enterprise-account
2829
- /admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-code-security-and-analysis-for-your-enterprise
29-
shortTitle: Code security & analysis
30+
shortTitle: Security & analysis
3031
---
3132

32-
## About policies for code security and analysis in your enterprise
33+
## About policies for using security features in your enterprise
3334

34-
You can enforce policies to manage the use of code security and analysis features within organizations owned by your enterprise. You can allow or disallow people with admin access to a repository to enable or disable the security and analysis features.
35+
You can enforce policies to manage the use of security features within organizations owned by your enterprise. You can allow or disallow people with admin access to a repository to enable or disable the security and analysis features.
3536

3637
Additionally, you can enforce policies for the use of {% data variables.product.prodname_GHAS %}{% ifversion ghas-products %} products{% endif %} in your enterprise's organizations and repositories.
3738

content/admin/managing-code-security/index.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
2-
title: Managing code security for your enterprise
2+
title: Managing a secure coding environment for your enterprise
33
allowTitleToDifferFromFilename: true
4-
shortTitle: Code security
4+
shortTitle: Secure coding
55
intro: 'You can build security into your developers'' workflow with features that keep secrets and vulnerabilities out of your codebase, and that maintain your software supply chain.'
66
versions:
77
ghec: '*'

content/billing/managing-billing-for-your-products/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -92,7 +92,7 @@ For other billing-related questions, contact {% data variables.contact.github_su
9292

9393
{% elsif ghes %}
9494

95-
You can make extra features for code security available to users by buying and uploading a license for {% data variables.product.prodname_GH_advanced_security %}. For more information about {% data variables.product.prodname_GH_advanced_security %}, see [AUTOTITLE](/get-started/learning-about-github/about-github-advanced-security).
95+
You can make extra features available to users by buying and uploading a license for {% data variables.product.prodname_GH_advanced_security %}. For more information about {% data variables.product.prodname_GH_advanced_security %}, see [AUTOTITLE](/get-started/learning-about-github/about-github-advanced-security).
9696

9797
{% data reusables.advanced-security.ghas-products-tip %}
9898

content/code-security/code-scanning/enabling-code-scanning/configuring-default-setup-for-code-scanning.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -64,7 +64,7 @@ You can use default setup for all {% data variables.product.prodname_codeql %}-s
6464

6565
### Customizing default setup
6666

67-
We recommend that you start using {% data variables.product.prodname_code_scanning %} with default setup. After you've initially configured default setup, you can evaluate {% data variables.product.prodname_code_scanning %} to see how it's working for you. If you find that something isn't working as you expect, you can customize default setup to better meet your code security needs. For more information, see [AUTOTITLE](/code-security/code-scanning/enabling-code-scanning/evaluating-default-setup-for-code-scanning).
67+
We recommend that you start using {% data variables.product.prodname_code_scanning %} with default setup. After you've initially configured default setup, you can evaluate {% data variables.product.prodname_code_scanning %} to see how it's working for you. If you find that something isn't working as you expect, you can customize default setup to better meet your needs. For more information, see [AUTOTITLE](/code-security/code-scanning/enabling-code-scanning/evaluating-default-setup-for-code-scanning).
6868

6969
### About adding non-compiled and compiled languages to your default setup
7070

content/code-security/code-scanning/enabling-code-scanning/evaluating-default-setup-for-code-scanning.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Evaluating default setup for code scanning
33
shortTitle: Evaluate code scanning
4-
intro: 'Learn how to assess how code scanning is working for you, and how you can customize your setup to best meet your code security needs.'
4+
intro: 'Learn how to assess how code scanning is working for you, and how you can customize your setup to best meet your needs.'
55
permissions: '{% data reusables.permissions.security-repo-enable %}'
66
type: how_to
77
topics:

content/code-security/code-scanning/managing-code-scanning-alerts/fixing-alerts-in-security-campaign.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -69,7 +69,7 @@ If you want to see the code that triggered the security alert and the suggested
6969

7070
If you have access to {% data variables.product.prodname_copilot_chat_short %} then you can ask the AI questions about the vulnerability, the suggested fix, and how to test that the fix is comprehensive.
7171

72-
To get the most out of {% data variables.product.prodname_copilot_chat_short %} when you're working on code security, you should explicitly ask {% data variables.product.prodname_copilot_chat_short %} to use the {% data variables.product.prodname_GH_advanced_security %} skill to answer your questions.
72+
To get the most out of {% data variables.product.prodname_copilot_chat_short %} when you're working with alerts, you should explicitly ask {% data variables.product.prodname_copilot_chat_short %} to use the {% data variables.product.prodname_GH_advanced_security %} skill to answer your questions.
7373

7474
For example: "Use the {% data variables.product.prodname_GH_advanced_security %} skill to explain how this alert introduces a vulnerability into the code."
7575

content/code-security/code-scanning/managing-code-scanning-alerts/responsible-use-autofix-code-scanning.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -30,7 +30,7 @@ In an organization's security overview dashboard, you can view the total number
3030

3131
## Developer experience
3232

33-
{% data variables.product.prodname_code_scanning_caps %} users can already see security alerts to analyze their pull requests. However, developers often have little training in code security so fixing these alerts requires substantial effort. They must first read and understand the alert location and description, and then use that understanding to edit the source code to fix the vulnerability.
33+
{% data variables.product.prodname_code_scanning_caps %} users can already see security alerts to analyze their pull requests. However, developers often have little training in secure coding so fixing these alerts requires substantial effort. They must first read and understand the alert location and description, and then use that understanding to edit the source code to fix the vulnerability.
3434

3535
{% data variables.product.prodname_copilot_autofix_short %} lowers the barrier of entry to developers by combining information on best practices with details of the codebase and alert to suggest a potential fix to the developer. Instead of starting with a search for information about the vulnerability, the developer starts with a code suggestion that demonstrates a potential solution for their codebase. The developer evaluates the potential fix to determine whether it is the best solution for their codebase and to ensure that it maintains the intended behavior.
3636

content/code-security/code-scanning/managing-your-code-scanning-configuration/editing-your-configuration-of-default-setup.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Editing your configuration of default setup
33
shortTitle: Edit default setup
4-
intro: 'You can edit your existing configuration of default setup for {% data variables.product.prodname_code_scanning %} to better meet your code security needs.'
4+
intro: 'You can edit your existing configuration of default setup for {% data variables.product.prodname_code_scanning %} to better meet your needs.'
55
permissions: '{% data reusables.permissions.security-org-enable %}'
66
versions:
77
fpt: '*'
@@ -15,7 +15,7 @@ topics:
1515

1616
## About editing your configuration of default setup
1717

18-
After running an initial analysis of your code with default setup, you may need to make changes to your configuration to better meet your code security needs. For existing configurations of default setup, you can edit:
18+
After running an initial analysis of your code with default setup, you may need to make changes to your configuration to better meet your needs. For existing configurations of default setup, you can edit:
1919
* Which languages default setup will analyze.
2020
* The query suite run during analysis. For more information on the available query suites, see [AUTOTITLE](/code-security/code-scanning/managing-your-code-scanning-configuration/codeql-query-suites).{% ifversion codeql-threat-models %}
2121
* The threat models ({% data variables.release-phases.public_preview %}) to use for analysis. Your choice of threat model determines which sources of tainted data are treated as a risk to your application. During the {% data variables.release-phases.public_preview %}, threat models are supported only for analysis of {% data variables.code-scanning.code_scanning_threat_model_support %}. For more information about threat models, see [Including local sources of tainted data in default setup](#including-local-sources-of-tainted-data-in-default-setup).

content/code-security/getting-started/index.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,8 @@
11
---
2-
title: Getting started with code security
2+
title: Getting started with secure coding
33
shortTitle: Getting started
44
allowTitleToDifferFromFilename: true
5-
intro: 'Introduction to code security with {% data variables.product.github %}.'
5+
intro: 'Introduction to secure coding with {% data variables.product.github %}.'
66
versions:
77
fpt: '*'
88
ghes: '*'

0 commit comments

Comments
 (0)