You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 09438af
Browse filesBrowse the repository at this point in the historyBrowse files
For {% data variables.product.prodname_code_scanning %} alerts from {% data variables.product.prodname_codeql %} analysis, you can use security overview to see how {% data variables.product.prodname_codeql %} is performing in pull requests in repositories across your organization, and to identify repositories where you may need to take action. For more information, see [AUTOTITLE](/code-security/security-overview/viewing-metrics-for-pull-request-alerts).
43
+
For {% data variables.product.prodname_code_scanning %} alerts from {% data variables.product.prodname_codeql %} analysis, you can use security overview to see how {% data variables.product.prodname_codeql %} is performing in pull requests in repositories across your organization, and to identify repositories where you may need to take action. For more information, see [AUTOTITLE](/code-security/concepts/code-scanning/pull-request-alert-metrics).
intro: Understand {% data variables.product.prodname_codeql %}'s performance in pull requests across your organizations.
5
+
permissions: '{% data reusables.permissions.security-overview %}'
6
+
product: '{% data reusables.gated-features.security-overview-fpt-cs-only %}'
7
+
topics:
8
+
- Security overview
9
+
- Code Security
10
+
- Code scanning
11
+
- CodeQL
12
+
- Organizations
13
+
- Teams
14
+
contentType: concepts
15
+
versions:
16
+
feature: security-overview-org-codeql-pr-alerts
17
+
---
18
+
19
+
## Overview
20
+
21
+
The metrics overview for {% data variables.product.prodname_codeql %} pull request alerts on security overview helps you understand how well {% data variables.product.prodname_codeql %} is preventing vulnerabilities in pull requests in your organization or across organizations in your enterprise. You can view the entire dataset or filter for specific criteria, making it easy to identify repositories where you may need to take action to find and reduce security risks.
22
+
23
+
## Available metrics
24
+
25
+
The overview shows you a summary of how many vulnerabilities prevented by {% data variables.product.prodname_codeql %} have been caught in pull requests. The metrics are only tracked for pull requests that have been merged into the default branches of repositories in your organizations.
26
+
27
+
You can also find more granular metrics, such as how many alerts were fixed{% ifversion code-scanning-autofix %} with and without {% data variables.copilot.copilot_autofix_short %} suggestions{% endif %}, how many were unresolved and merged, and how many were dismissed as false positive or risk accepted.
28
+
29
+
You can also view:
30
+
31
+
* The rules that are causing the most alerts, and how many alerts each rule is associated with.
32
+
33
+
* The number of alerts that were merged into the default branch without resolution, and the number of alerts dismissed as an acceptable risk.
34
+
35
+
{% ifversion code-scanning-autofix %}
36
+
* The number of alerts that were fixed with an accepted {% data variables.copilot.copilot_autofix_short %} suggestion, displayed as a fraction of how many total {% data variables.copilot.copilot_autofix_short %} suggestions were available.
37
+
38
+
* Remediation rates, in a graph showing the percentage of alerts that were remediated with an available {% data variables.copilot.copilot_autofix_short %} suggestion, and the percentage of alerts that were remediated without a {% data variables.copilot.copilot_autofix_short %} suggestion.
39
+
40
+
* Mean time to remediate, in a graph showing the average age of closed alerts that were remediated with an available {% data variables.copilot.copilot_autofix_short %} suggestion, and the average age of closed alerts that were remediated without a {% data variables.copilot.copilot_autofix_short %} suggestion.
41
+
{% endif %}
42
+
43
+
{% ifversion code-scanning-autofix %}
44
+
> [!NOTE] Metrics for {% data variables.copilot.copilot_autofix_short %} will be shown only for repositories where {% data variables.copilot.copilot_autofix_short %} is enabled.
45
+
{% else %}
46
+
> [!NOTE] Metrics for {% data variables.copilot.copilot_autofix_short %} are omitted because {% data variables.copilot.copilot_autofix_short %} is available only on {% data variables.product.github %} cloud platforms.
47
+
{% endif %}
48
+
49
+
## Visibility
50
+
51
+
You can see {% data variables.product.prodname_code_scanning %} metrics for a repository if you have:
52
+
53
+
* The `admin` role for the repository
54
+
* A custom repository role with the "View {% data variables.product.prodname_code_scanning %} alerts" fine-grained permissions for the repository
55
+
* Access to alerts for the repository
56
+
57
+
## Next steps
58
+
59
+
To find your pull request alert metrics, see [AUTOTITLE](/code-security/how-tos/view-and-interpret-data/analyze-organization-data/viewing-metrics-for-pull-request-alerts).
intro: 'Understand push protection''s performance across your organizations.'
5
+
permissions: '{% data reusables.permissions.security-overview %}'
6
+
product: '{% data reusables.gated-features.security-overview-fpt-sp-only %}'
7
+
versions:
8
+
fpt: '*'
9
+
ghes: '*'
10
+
ghec: '*'
11
+
topics:
12
+
- Security overview
13
+
- Secret Protection
14
+
- Secret scanning
15
+
- Organizations
16
+
- Teams
17
+
contentType: concepts
18
+
---
19
+
20
+
## Overview
21
+
22
+
The metrics overview for {% data variables.product.prodname_secret_scanning %} push protection on security overview helps you understand how well you are preventing secret leaks in your organization or across organizations in your enterprise. You can view the entire dataset or filter for specific criteria, making it easy to identify repositories where you may need to take action to prevent future leaks.
23
+
24
+
## Available metrics
25
+
26
+
The overview shows you a summary of how many pushes containing secrets have been successfully blocked by push protection, as well as how many times push protection was bypassed.
27
+
28
+
You can also find more granular metrics, such as:
29
+
* The secret types that have been blocked or bypassed the most
30
+
* The repositories that have had the most pushes blocked
31
+
* The repositories that are bypassing push protection the most
32
+
* The percentage distribution of reasons that users give when they bypass the protection
33
+
34
+
## Visibility
35
+
36
+
You can see {% data variables.product.prodname_secret_scanning %} metrics for a repository if you have:
37
+
38
+
* The `admin` role for the repository
39
+
* A custom repository role with the "View {% data variables.product.prodname_secret_scanning %} alerts" fine-grained permissions for the repository
40
+
* Access to alerts for the repository
41
+
42
+
## Next steps
43
+
44
+
To find your push protection metrics, see [AUTOTITLE](/code-security/how-tos/view-and-interpret-data/analyze-organization-data/viewing-metrics-for-secret-scanning-push-protection).
Copy file name to clipboardExpand all lines: content/code-security/how-tos/manage-security-alerts/manage-code-scanning-alerts/assessing-code-scanning-alerts-for-your-repository.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -58,7 +58,7 @@ With a {% data variables.copilot.copilot_enterprise %} license, you can ask {% d
58
58
59
59
## Viewing metrics for {% data variables.product.prodname_codeql %} pull request alerts for an organization
60
60
61
-
For {% data variables.product.prodname_code_scanning %} alerts from {% data variables.product.prodname_codeql %} analysis, you can use security overview to see how {% data variables.product.prodname_codeql %} is performing in pull requests in repositories where you have write access across your organization, and to identify repositories where you may need to take action. For more information, see [AUTOTITLE](/code-security/security-overview/viewing-metrics-for-pull-request-alerts).
61
+
For {% data variables.product.prodname_code_scanning %} alerts from {% data variables.product.prodname_codeql %} analysis, you can use security overview to see how {% data variables.product.prodname_codeql %} is performing in pull requests in repositories where you have write access across your organization, and to identify repositories where you may need to take action. For more information, see [AUTOTITLE](/code-security/concepts/code-scanning/pull-request-alert-metrics).
Copy file name to clipboardExpand all lines: content/code-security/how-tos/view-and-interpret-data/analyze-organization-data/viewing-metrics-for-pull-request-alerts.md
+1-31Lines changed: 1 addition & 31 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
title: Viewing metrics for pull request alerts
3
3
shortTitle: View PR alert metrics
4
4
allowTitleToDifferFromFilename: true
5
-
intro: You can use security overview to see how {% data variables.product.prodname_codeql %} is performing in pull requests for repositories across your organizations, and to identify repositories where you may need to take action.
5
+
intro: Monitor {% data variables.product.prodname_codeql %}'s performance in pull requests across your organizations to identify repositories where you may need to take action.
6
6
permissions: '{% data reusables.permissions.security-overview %}'
7
7
product: '{% data reusables.gated-features.security-overview-fpt-cs-only %}'
## About {% data variables.product.prodname_codeql %} pull request alerts metrics
23
-
24
-
The metrics overview for {% data variables.product.prodname_codeql %} pull request alerts helps you to understand how well {% data variables.product.prodname_codeql %} is preventing vulnerabilities in your organizations. You can use the metrics to assess how {% data variables.product.prodname_codeql %} is performing in pull requests, and to easily identify the repositories where you may need to take action in order to identify and reduce security risks.
25
-
26
-
The overview shows you a summary of how many vulnerabilities prevented by {% data variables.product.prodname_codeql %} have been caught in pull requests. The metrics are only tracked for pull requests that have been merged into the default branches of repositories in your organizations.
27
-
28
-
You can also find more granular metrics, such as how many alerts were fixed{% ifversion code-scanning-autofix %} with and without {% data variables.copilot.copilot_autofix_short %} suggestions{% endif %}, how many were unresolved and merged, and how many were dismissed as false positive or as risk accepted.
29
-
30
-
You can also view:
31
-
32
-
* The rules that are causing the most alerts, and how many alerts each rule is associated with.
33
-
34
-
* The number of alerts that were merged into the default branch without resolution, and the number of alerts dismissed as an acceptable risk.
35
-
36
-
{% ifversion code-scanning-autofix %}
37
-
* The number of alerts that were fixed with an accepted {% data variables.copilot.copilot_autofix_short %} suggestion, displayed as a fraction of how many total {% data variables.copilot.copilot_autofix_short %} suggestions were available.
38
-
39
-
* Remediation rates, in a graph showing the percentage of alerts that were remediated with an available {% data variables.copilot.copilot_autofix_short %} suggestion, and the percentage of alerts that were remediated without a {% data variables.copilot.copilot_autofix_short %} suggestion.
40
-
41
-
* Mean time to remediate, in a graph showing the average age of closed alerts that were remediated with an available {% data variables.copilot.copilot_autofix_short %} suggestion, and the average age of closed alerts that were remediated without a {% data variables.copilot.copilot_autofix_short %} suggestion.
42
-
{% endif %}
43
-
44
-
You can apply filters to the data. The metrics are based on activity from the default period or your selected period.
45
-
46
-
{% ifversion code-scanning-autofix %}
47
-
> [!NOTE] Metrics for {% data variables.copilot.copilot_autofix_short %} will be shown only for repositories where {% data variables.copilot.copilot_autofix_short %} is enabled.
48
-
{% else %}
49
-
> [!NOTE] Metrics for {% data variables.copilot.copilot_autofix_short %} are omitted because {% data variables.copilot.copilot_autofix_short %} is available only on {% data variables.product.github %} cloud platforms.
50
-
{% endif %}
51
-
52
22
## Viewing {% data variables.product.prodname_codeql %} pull request alerts metrics for an organization
53
23
54
24
{% data reusables.organizations.navigate-to-org %}
Copy file name to clipboardExpand all lines: content/code-security/how-tos/view-and-interpret-data/analyze-organization-data/viewing-metrics-for-secret-scanning-push-protection.md
+2-28Lines changed: 2 additions & 28 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
title: Viewing metrics for secret scanning push protection
3
3
shortTitle: View secret scanning metrics
4
4
allowTitleToDifferFromFilename: true
5
-
intro: You can use security overview to see how {% data variables.product.prodname_secret_scanning %} push protection is performing in repositories across your organization{% ifversion security-overview-enterprise-secret-scanning-metrics %} or enterprise{% endif %}, and to identify repositories where you may need to take action.
5
+
intro: Monitor push protection's performance across your organization{% ifversion security-overview-enterprise-secret-scanning-metrics %} or enterprise{% endif %} to identify repositories where you may need to take action.
6
6
permissions: '{% data reusables.permissions.security-overview %}'
7
7
product: '{% data reusables.gated-features.security-overview-fpt-sp-only %}'
8
8
contentType: how-tos
@@ -23,28 +23,6 @@ versions:
23
23
24
24
{% data reusables.secret-scanning.push-protection-org-metrics-beta %}
25
25
26
-
## About metrics for {% data variables.product.prodname_secret_scanning %} push protection
27
-
28
-
The metrics overview for {% data variables.product.prodname_secret_scanning %} push protection helps you to understand how well you are preventing security leaks in your organization{% ifversion security-overview-enterprise-secret-scanning-metrics %} or across organizations in your enterprise{% endif %}. You can use the metrics to assess how push protection is performing, and to easily identify the repositories where you may need to take action in order to prevent leaks of sensitive information.
29
-
30
-
The overview shows you a summary of how many pushes containing secrets have been successfully blocked by push protection, as well as how many times push protection was bypassed.
31
-
32
-
You can also find more granular metrics, such as:
33
-
* The secret types that have been blocked or bypassed the most
34
-
* The repositories that have had the most pushes blocked
35
-
* The repositories that are bypassing push protection the most
36
-
* The percentage distribution of reasons that users give when they bypass the protection
37
-
38
-
Use the date picker to set the time range that you want to view alert activity and metrics for, and click in the search box to add further filters on the alerts and metrics displayed. For more information, see [AUTOTITLE](/code-security/security-overview/filtering-alerts-in-security-overview#additional-filters-for-secret-scanning-alert-views).
39
-
40
-
You can see {% data variables.product.prodname_secret_scanning %} metrics if you have:
41
-
42
-
* The `admin` role for the repository.
43
-
* A custom repository role with the "View {% data variables.product.prodname_secret_scanning %} results" fine-grained permissions for the repository. For more information, see [AUTOTITLE](/organizations/managing-user-access-to-your-organizations-repositories/managing-repository-roles/about-custom-repository-roles#security).
44
-
* Access to alerts for the repository. For more information, see [AUTOTITLE](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts).
45
-
46
-
The metrics are based on activity from the default period or your selected period.
47
-
48
26
## Viewing metrics for {% data variables.product.prodname_secret_scanning %} push protection for an organization
49
27
50
28
{% data reusables.organizations.navigate-to-org %}
@@ -53,18 +31,14 @@ The metrics are based on activity from the default period or your selected perio
53
31
1. Click on an individual secret type or repository to see the associated {% data variables.secret-scanning.alerts %} for your organization.
54
32
{% data reusables.security-overview.filter-secret-scanning-metrics %}
## Viewing metrics for {% data variables.product.prodname_secret_scanning %} push protection for an enterprise
59
35
60
36
You can view metrics for {% data variables.product.prodname_secret_scanning %} push protection across organizations in an enterprise. {% data reusables.security-overview.information-varies-GHAS %}
61
37
62
-
{% ifversion ghes %}{% data reusables.enterprise-accounts.access-enterprise-ghes %}{% else %}{% data reusables.enterprise-accounts.access-enterprise-on-dotcom %}{% endif %}
38
+
{% data reusables.enterprise-accounts.access-enterprise %}
63
39
{% data reusables.code-scanning.click-code-security-enterprise %}
64
40
1. In the sidebar, click **{% data variables.product.prodname_secret_scanning_caps %} metrics**.
65
41
1. Click on an individual secret type or repository to see the associated {% data variables.secret-scanning.alerts %} for your enterprise.
66
42
{% data reusables.security-overview.filter-secret-scanning-metrics %}
67
43
68
44
{% data reusables.security-overview.enterprise-filters-tip %}
Copy file name to clipboardExpand all lines: content/code-security/tutorials/adopting-github-advanced-security-at-scale/phase-3-pilot-programs.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -86,7 +86,7 @@ Next, enable push protection for each pilot project.
86
86
87
87
If you plan to configure a link to a resource in the message that's displayed when a developer attempts to push a blocked secret, now would be a good time to test and start to refine the guidance that you plan to make available.
88
88
89
-
Start to review activity using the push protection metrics page in security overview. For more information, see [AUTOTITLE](/code-security/security-overview/viewing-metrics-for-secret-scanning-push-protection).
89
+
Start to review activity using the push protection metrics page in security overview. For more information, see [AUTOTITLE](/code-security/concepts/secret-security/push-protection-metrics).
90
90
91
91
If you have collated any custom patterns specific to your enterprise, especially any related to the projects piloting {% data variables.product.prodname_secret_scanning %}, you can configure those. For more information, see [AUTOTITLE](/code-security/secret-scanning/using-advanced-secret-scanning-and-push-protection-features/custom-patterns/defining-custom-patterns-for-secret-scanning).
Copy file name to clipboardExpand all lines: content/code-security/tutorials/adopting-github-advanced-security-at-scale/phase-5-rollout-and-scale-code-scanning.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -40,7 +40,7 @@ You'll also need SMEs if you need to use advanced setup for {% data variables.pr
For {% data variables.product.prodname_code_scanning %} alerts from {% data variables.product.prodname_codeql %} analysis, you can use security overview to see how {% data variables.product.prodname_codeql %} is performing in pull requests in repositories across your organization, and to identify repositories where you may need to take action. For more information, see [AUTOTITLE](/code-security/security-overview/viewing-metrics-for-pull-request-alerts).
43
+
For {% data variables.product.prodname_code_scanning %} alerts from {% data variables.product.prodname_codeql %} analysis, you can use security overview to see how {% data variables.product.prodname_codeql %} is performing in pull requests in repositories across your organization, and to identify repositories where you may need to take action. For more information, see [AUTOTITLE](/code-security/concepts/code-scanning/pull-request-alert-metrics).
0 commit comments