Docs for new Secret risk assessment, GHAS SKU unbundling, and expansion to Team plan - ships 1st April (UK morning) (#54748)
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> Co-authored-by: Isaac Brown <101839405+isaacmbrown@users.noreply.github.com> Co-authored-by: mchammer01 <42146119+mchammer01@users.noreply.github.com> Co-authored-by: Anne-Marie <102995847+am-stead@users.noreply.github.com> Co-authored-by: Hector Alfaro <hectorsector@github.com> Co-authored-by: Vanessa <vgrl@github.com> Co-authored-by: Erin Havens <erinhav@github.com> Co-authored-by: Aaron Waggener <73763104+aaronwaggener@users.noreply.github.com> Co-authored-by: Sam Browning <106113886+sabrowning1@users.noreply.github.com> Co-authored-by: Sarah Schneider <sarahs@users.noreply.github.com> Co-authored-by: Sarita Iyer <66540150+saritai@users.noreply.github.com> Co-authored-by: Sarah Schneider <sarahs@github.com>
This commit is contained in:
@@ -1,7 +1,7 @@
|
||||
---
|
||||
title: About security overview
|
||||
intro: 'You can gain insights into the overall security landscape of your organization or enterprise and identify repositories that require intervention using security overview.'
|
||||
product: '{% data reusables.gated-features.security-overview %}'
|
||||
product: '{% data reusables.gated-features.security-overview-general %}'
|
||||
redirect_from:
|
||||
- /code-security/security-overview/exploring-security-alerts
|
||||
- /code-security/security-overview/about-the-security-overview
|
||||
@@ -21,22 +21,31 @@ topics:
|
||||
- Secret scanning
|
||||
- Teams
|
||||
---
|
||||
<!-- expires 2025-04-01 -->
|
||||
|
||||
<!-- The whole article will be suitable for GitHub Team users -->
|
||||
{% ifversion fpt %}
|
||||
|
||||
{% ifversion fpt %}{% data reusables.security-overview.about-security-overview %} For more information, see [the {% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/code-security/security-overview/about-security-overview).{% endif %}
|
||||
Security overview provides insights into the security of code stored in repositories in your organization.
|
||||
|
||||
{% ifversion ghec or ghes %}
|
||||
* **All organizations** on {% data variables.product.prodname_team %} can use the free **{% data variables.product.prodname_secret_risk_assessment %}** to evaluate the exposure of their organization to leaked secrets, see [AUTOTITLE](/code-security/securing-your-organization/understanding-your-organizations-exposure-to-leaked-secrets/viewing-the-secret-risk-assessment-report-for-your-organization).
|
||||
* {% data variables.product.prodname_team %} accounts that purchase **{% data variables.product.prodname_GH_cs_or_sp %}** have access to views with additional insights.
|
||||
|
||||
<!-- end expires 2025-04-01 -->
|
||||
The information below describes the views available to organizations with {% data variables.product.prodname_GH_cs_or_sp %} that you can use to identify trends in detection, remediation, and prevention of security alerts and dig deep into the current state of your repositories.
|
||||
|
||||
{% elsif ghec or ghes %}
|
||||
|
||||
Security overview contains focused views where you can explore trends in detection, remediation, and prevention of security alerts and dig deep into the current state of your codebases.
|
||||
|
||||
* Information about {% data variables.product.prodname_dependabot %} features and alerts is shown for all repositories.
|
||||
* Information for {% data variables.product.prodname_AS %} features, such as {% data variables.product.prodname_code_scanning %} and {% data variables.product.prodname_secret_scanning %}, is shown for organizations and enterprises that use {% data variables.product.prodname_GHAS_cs_or_sp %}{% ifversion fpt or ghec %} and for public repositories{% endif %}.
|
||||
{% ifversion ghec %}
|
||||
All organizations on {% data variables.product.prodname_enterprise %} can use:
|
||||
* **{% data variables.product.prodname_secret_risk_assessment_caps %}** to evaluate the exposure of their organization to leaked secrets, see [AUTOTITLE](/code-security/securing-your-organization/understanding-your-organizations-exposure-to-leaked-secrets/viewing-the-secret-risk-assessment-report-for-your-organization).
|
||||
* **{% data variables.product.prodname_dependabot %}** data to evaluate the security of their supply chain in all repositories.
|
||||
{% else %}
|
||||
All organizations on {% data variables.product.prodname_enterprise %} can use {% data variables.product.prodname_dependabot %} data to evaluate the security of their supply chain in all repositories.
|
||||
{% endif %}
|
||||
|
||||
For more information, see [AUTOTITLE](/code-security/dependabot/dependabot-alerts/about-dependabot-alerts#dependabot-alerts-for-vulnerable-dependencies) and [AUTOTITLE](/get-started/learning-about-github/about-github-advanced-security).
|
||||
In addition, data for **{% data variables.product.prodname_AS %}** features, such as {% data variables.product.prodname_code_scanning %} and {% data variables.product.prodname_secret_scanning %}, is shown for organizations and enterprises that use {% data variables.product.prodname_GHAS_cs_or_sp %}{% ifversion ghec %}, and for public repositories{% endif %}, see [AUTOTITLE](/code-security/dependabot/dependabot-alerts/about-dependabot-alerts#dependabot-alerts-for-vulnerable-dependencies) and [AUTOTITLE](/get-started/learning-about-github/about-github-advanced-security).
|
||||
|
||||
{% endif %}
|
||||
|
||||
## About the views
|
||||
|
||||
@@ -65,10 +74,11 @@ Security overview has multiple views that provide different ways to explore enab
|
||||
{% ifversion security-overview-dashboard %}
|
||||
* **Overview:** visualize trends in **Detection**, **Remediation**, and **Prevention** of security alerts, see [AUTOTITLE](/code-security/security-overview/viewing-security-insights).{% endif %}
|
||||
* **Risk and Alert views:** explore the risk from security alerts of all types or focus on a single alert type and identify your risk from specific vulnerable dependencies, code weaknesses, or leaked secrets, see [AUTOTITLE](/code-security/security-overview/assessing-code-security-risk).
|
||||
* **Coverage:** assess the adoption of security features across repositories in the organization, see [AUTOTITLE](/code-security/security-overview/assessing-adoption-code-security).{% ifversion security-overview-tool-adoption %}
|
||||
* **Coverage:** assess the adoption of security features across repositories in the organization, see [AUTOTITLE](/code-security/security-overview/assessing-adoption-code-security).{% ifversion ghas-products %}{% ifversion secret-risk-assessment %}
|
||||
* **Assessments:** regardless of the enablement status of {% data variables.product.prodname_AS %} features, organizations on {% data variables.product.prodname_team %} and {% data variables.product.prodname_enterprise %} can run a free report to scan the code in the organization for leaked secrets, see [AUTOTITLE](/code-security/securing-your-organization/understanding-your-organizations-exposure-to-leaked-secrets/about-secret-risk-assessment).{% endif %}{% endif %}{% ifversion security-overview-tool-adoption %}
|
||||
* **Enablement trends:** see how quickly different teams are adopting security features.{% endif %}{% ifversion security-overview-org-codeql-pr-alerts %}
|
||||
* **CodeQL pull request alerts:** assess the impact of running CodeQL on pull requests and how development teams are resolving code scanning alerts, see [AUTOTITLE](/code-security/security-overview/viewing-metrics-for-pull-request-alerts).{% endif %}{% ifversion security-overview-push-protection-metrics-page %}
|
||||
* **Secret scanning:** find out which types of secret are blocked by push protection{% ifversion security-overview-delegated-bypass-requests %} and which teams are bypassing push protection{% endif %}, see [AUTOTITLE](/code-security/security-overview/viewing-metrics-for-secret-scanning-push-protection){% ifversion security-overview-delegated-bypass-requests %} and [AUTOTITLE](/code-security/security-overview/reviewing-requests-to-bypass-push-protection){% endif %}.{% endif %}
|
||||
* **CodeQL pull request alerts:** assess the impact of running CodeQL on pull requests and how development teams are resolving code scanning alerts, see [AUTOTITLE](/code-security/security-overview/viewing-metrics-for-pull-request-alerts).{% endif %}
|
||||
* **Secret scanning:** find out which types of secret are blocked by push protection{% ifversion security-overview-delegated-bypass-requests %} and which teams are bypassing push protection{% endif %}, see [AUTOTITLE](/code-security/security-overview/viewing-metrics-for-secret-scanning-push-protection){% ifversion security-overview-delegated-bypass-requests %} and [AUTOTITLE](/code-security/security-overview/reviewing-requests-to-bypass-push-protection){% endif %}.
|
||||
|
||||
{% ifversion security-campaigns %}
|
||||
You also create and manage security campaigns to remediate alerts from security overview, see [AUTOTITLE](/code-security/securing-your-organization/fixing-security-alerts-at-scale/creating-tracking-security-campaigns) and [AUTOTITLE](/code-security/securing-your-organization/fixing-security-alerts-at-scale/best-practice-fix-alerts-at-scale).
|
||||
@@ -76,7 +86,7 @@ You also create and manage security campaigns to remediate alerts from security
|
||||
|
||||
## About security overview for enterprises
|
||||
|
||||
You can find security overview on the **Code Security** tab for your enterprise. Each page displays aggregated and repository-specific security information for your enterprise.
|
||||
You can find security overview on the **Security** tab for your enterprise. Each page displays aggregated and repository-specific security information for your enterprise.
|
||||
|
||||
As with security overview for organizations, security overview for enterprises has multiple views that provide different ways to explore data.
|
||||
|
||||
@@ -138,4 +148,3 @@ If you're an owner of an {% data variables.enterprise.prodname_emu_enterprise %}
|
||||
* [AUTOTITLE](/code-security/securing-your-organization){% else %}
|
||||
* [AUTOTITLE](/code-security/getting-started/quickstart-for-securing-your-organization){% endif %}
|
||||
* [AUTOTITLE](/code-security/adopting-github-advanced-security-at-scale/introduction-to-adopting-github-advanced-security-at-scale)
|
||||
{% endif %}
|
||||
|
||||
@@ -4,6 +4,7 @@ shortTitle: Assess adoption of features
|
||||
allowTitleToDifferFromFilename: true
|
||||
intro: 'You can use security overview to see which teams and repositories have already enabled features for secure coding, and identify any that are not yet protected.'
|
||||
permissions: '{% data reusables.permissions.security-overview %}'
|
||||
product: '{% data reusables.gated-features.security-overview-fpt-both %}'
|
||||
type: how_to
|
||||
topics:
|
||||
- Security overview
|
||||
@@ -13,18 +14,22 @@ topics:
|
||||
- Organizations
|
||||
- Teams
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghec: '*'
|
||||
---
|
||||
|
||||
|
||||
|
||||
## About adoption of features for secure coding
|
||||
|
||||
You can use security overview to see which repositories and teams have already enabled each security feature, and where people need more encouragement to adopt these features. The "Security coverage" view shows a summary and detailed information on feature enablement for an organization. You can filter the view to show a subset of repositories using the "enabled" and "not enabled" links, the "Teams" dropdown menu, and a search field in the page header.
|
||||
|
||||
{% ifversion security-configurations %}
|
||||

|
||||
|
||||
{% else %}
|
||||

|
||||
{% endif %}
|
||||
|
||||
>[!NOTE] "Pull request alerts" are reported as enabled only when {% data variables.product.prodname_code_scanning %} has analyzed at least one pull request since alerts were enabled for the repository.
|
||||
|
||||
{% ifversion security-overview-export-data %}
|
||||
@@ -46,8 +51,6 @@ You can view data to assess the enablement of features for secure coding across
|
||||
1. To display the "Security coverage" view, in the sidebar, click **{% octicon "meter" aria-hidden="true" %} Coverage**.
|
||||
{% data reusables.code-scanning.using-security-overview-coverage %}
|
||||
|
||||

|
||||
|
||||
{% ifversion pre-security-configurations %}
|
||||
1. Optionally, click **{% octicon "gear" aria-hidden="true" %} Security settings** to enable security features for a repository and click **Save security settings** to confirm the changes. If a feature is not shown, it has more complex configuration requirements and you need to use the repository settings dialog. For more information, see [AUTOTITLE](/code-security/getting-started/securing-your-repository).
|
||||
1. Optionally, select some or all of the repositories that match your current search and click **Security settings** in the table header to display a side panel where you can enable security features for the selected repositories. When you've finished, click **Apply changes** to confirm the changes. For more information, see [AUTOTITLE](/code-security/security-overview/enabling-security-features-for-multiple-repositories).
|
||||
@@ -73,9 +76,7 @@ In the enterprise-level view, you can view data about the enablement of features
|
||||
1. To display the "Security coverage" view, in the sidebar, click **Coverage**.
|
||||
{% data reusables.code-scanning.using-security-overview-coverage %}
|
||||
|
||||

|
||||
|
||||
{% data reusables.security-overview.enterprise-filters-tip %}
|
||||
{% data reusables.security-overview.enterprise-filters-tip %}
|
||||
|
||||
{% ifversion security-overview-tool-adoption %}
|
||||
|
||||
@@ -129,6 +130,6 @@ You can view data to assess the enablement status and enablement status trends o
|
||||
|
||||
Some security features can and should be enabled on all repositories. For example, {% data variables.secret-scanning.alerts %} and push protection reduce the risk of a security leak no matter what information is stored in the repository. If you see repositories that don't already use these features, you should either enable them or discuss an enablement plan with the team who owns the repository. For information on enabling features for a whole organization, see {% ifversion security-configurations %}[AUTOTITLE](/code-security/securing-your-organization/enabling-security-features-in-your-organization){% else %}[AUTOTITLE](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization){% endif %}.
|
||||
|
||||
Other features are not available for use in all repositories. For example, there would be no point in enabling {% data variables.product.prodname_dependabot %}{% ifversion default-setup-pre-enablement %}{% else %} or {% data variables.product.prodname_code_scanning %}{% endif %} for repositories that only use ecosystems or languages that are unsupported. As such, it's normal to have some repositories where these features are not enabled.
|
||||
Other features are not suitable for use in all repositories. For example, there would be no point in enabling {% data variables.product.prodname_dependabot %}{% ifversion default-setup-pre-enablement %}{% else %} or {% data variables.product.prodname_code_scanning %}{% endif %} for repositories that only use ecosystems or languages that are unsupported. As such, it's normal to have some repositories where these features are not enabled.
|
||||
|
||||
Your enterprise may also have configured policies to limit the use of some security features. For more information, see [AUTOTITLE](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-code-security-and-analysis-for-your-enterprise).
|
||||
|
||||
@@ -4,6 +4,7 @@ shortTitle: Assess security risk of code
|
||||
allowTitleToDifferFromFilename: true
|
||||
intro: 'You can use security overview to see which teams and repositories are affected by security alerts, and identify repositories for urgent remedial action.'
|
||||
permissions: '{% data reusables.permissions.security-overview %}'
|
||||
product: '{% data reusables.gated-features.security-overview-fpt-both %}'
|
||||
type: how_to
|
||||
topics:
|
||||
- Security overview
|
||||
@@ -13,14 +14,13 @@ topics:
|
||||
- Organizations
|
||||
- Teams
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghec: '*'
|
||||
redirect_from:
|
||||
- /code-security/security-overview/viewing-the-security-overview
|
||||
---
|
||||
|
||||
|
||||
|
||||
## Exploring the security risks in your code
|
||||
|
||||
You can use the different views on your **Security** tab to explore the security risks in your code.
|
||||
|
||||
@@ -5,7 +5,7 @@ intro: You can use security overview to select a subset of repositories and enab
|
||||
permissions: '{% data reusables.permissions.security-org-enable %}'
|
||||
allowTitleToDifferFromFilename: true
|
||||
versions:
|
||||
feature: security-configurations-beta-and-pre-beta
|
||||
feature: security-configurations-beta-and-pre-beta # Display article for old GHES versions only
|
||||
type: how_to
|
||||
topics:
|
||||
- Security overview
|
||||
|
||||
@@ -3,6 +3,7 @@ title: Exporting data from security overview
|
||||
shortTitle: Export data
|
||||
intro: From security overview, you can export CSV files of the data used for your organization or enterprise's overview, risk, coverage, and {% data variables.product.prodname_codeql %} pull request alerts pages.
|
||||
permissions: '{% data reusables.permissions.security-overview %}'
|
||||
product: '{% data reusables.gated-features.security-overview-fpt-both %}'
|
||||
versions:
|
||||
feature: security-overview-export-data
|
||||
type: how_to
|
||||
@@ -38,12 +39,8 @@ The CSV file you download will contain data corresponding to the filters you hav
|
||||
|
||||
It may take a moment for {% data variables.product.github %} to generate the CSV file of your data. Once the CSV file generates, the file will automatically start downloading, and a banner will appear confirming your report is ready. If you are downloading the CSV from the overview page, you will also receive an email when your report is ready, containing a link to download the CSV.
|
||||
|
||||
{% ifversion secret-scanning-non-provider-patterns %}
|
||||
|
||||
> [!NOTE]
|
||||
> The summary views ({% ifversion security-overview-dashboard %}"Overview", {% endif %}"Coverage" and "Risk") show data only for {% ifversion secret-scanning-alert-experimental-list %}default{% else %}high confidence{% endif %} alerts. {% data variables.product.prodname_code_scanning_caps %} alerts from third-party tools, and {% data variables.product.prodname_secret_scanning %} alerts for non-provider patterns or for ignored directories are all omitted from these views. Consequently, files exported from the summary views do not contain data for these types of alert.
|
||||
|
||||
{% endif %}
|
||||
> The summary views ("Overview", "Coverage" and "Risk") show data only for default alerts. {% data variables.product.prodname_code_scanning_caps %} alerts from third-party tools, and {% data variables.product.prodname_secret_scanning %} alerts for non-provider patterns or for ignored directories are all omitted from these views. Consequently, files exported from the summary views do not contain data for these types of alert.
|
||||
|
||||
## Exporting overview, coverage, and risk data from your enterprise's security overview
|
||||
|
||||
|
||||
@@ -2,8 +2,10 @@
|
||||
title: Filtering alerts in security overview
|
||||
intro: Use filters to view specific categories of alerts
|
||||
permissions: '{% data reusables.permissions.security-overview %}'
|
||||
product: '{% data reusables.gated-features.security-overview-fpt-both %}'
|
||||
allowTitleToDifferFromFilename: true
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghec: '*'
|
||||
type: how_to
|
||||
@@ -119,7 +121,7 @@ In the "Risk" and "Coverage" views, you can show data only for repositories wher
|
||||
|
||||
| Qualifier | Description |
|
||||
| -------- | -------- |
|
||||
| `advanced-security` | Display data for repositories where {% data variables.product.prodname_AS %} is{% ifversion ghas-products-cloud %} products are{% endif %} enabled or not enabled. |
|
||||
| `advanced-security` | Display data for repositories where {% data variables.product.prodname_GHAS %} is enabled or not enabled. |
|
||||
| `code-scanning-default-setup`| Display data for repositories where {% data variables.product.prodname_code_scanning %} is enabled or not enabled using {% data variables.product.prodname_codeql %} default setup. |
|
||||
| `code-scanning-pull-request-alerts`| Display data for repositories where {% data variables.product.prodname_code_scanning %} is enabled or not enabled to run on pull requests. |
|
||||
| `dependabot-security-updates` | Display data for repositories where {% data variables.product.prodname_dependabot_security_updates %} is enabled or not enabled. |
|
||||
|
||||
@@ -2,8 +2,8 @@
|
||||
title: Viewing security information for your organization or enterprise
|
||||
shortTitle: Security overview
|
||||
allowTitleToDifferFromFilename: true
|
||||
intro: 'View, sort, and filter security alerts and coverage information from across your organization or enterprise, and enable security features for their repositories.'
|
||||
product: '{% data reusables.gated-features.security-overview %}'
|
||||
intro: 'Visualize adoption rates for {% data variables.product.prodname_GHAS %} features, alert discovery, and remediation for your organization or enterprise.'
|
||||
product: '{% data reusables.gated-features.security-overview-general %}'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
|
||||
@@ -3,6 +3,7 @@ title: Reviewing requests to bypass push protection
|
||||
shortTitle: Review bypass requests
|
||||
intro: 'You can use security overview to review requests to bypass push protection from contributors pushing to repositories across your organization.'
|
||||
permissions: '{% data reusables.permissions.security-overview %}'
|
||||
product: '{% data reusables.gated-features.security-overview-fpt-sp-only %}'
|
||||
type: how_to
|
||||
topics:
|
||||
- Security overview
|
||||
@@ -19,7 +20,7 @@ versions:
|
||||
|
||||
If your organization has configured delegated bypass for push protection, a designated team of reviewers controls which organization members can push secrets to repositories in your organization, and which members must first make a "bypass request" in order to push the secret.
|
||||
|
||||
On the "Bypass requests" page in security overview, reviewers can find, review (approve or deny) and manage these requests.
|
||||
On the "Push protection bypass" page in security overview, reviewers can find, review (approve or deny) and manage these requests.
|
||||
|
||||
For more information, see [AUTOTITLE](/code-security/secret-scanning/using-advanced-secret-scanning-and-push-protection-features/delegated-bypass-for-push-protection/managing-requests-to-bypass-push-protection).
|
||||
|
||||
|
||||
@@ -4,6 +4,7 @@ shortTitle: View PR alert metrics
|
||||
allowTitleToDifferFromFilename: true
|
||||
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.'
|
||||
permissions: '{% data reusables.permissions.security-overview %}'
|
||||
product: '{% data reusables.gated-features.security-overview-fpt-cs-only %}'
|
||||
type: how_to
|
||||
topics:
|
||||
- Security overview
|
||||
@@ -58,16 +59,12 @@ You can apply filters to the data. The metrics are based on activity from the de
|
||||
* Optionally, to remove a filter from your search, click **{% octicon "filter" aria-hidden="true" %} Filter**. In the row of the filter you want to remove, click {% octicon "x" aria-label="Delete FILTER-NUMBER: FILTER-PROPERTIES" %}, then click **Apply**.{% ifversion security-overview-export-data %}
|
||||
1. You can use the **{% octicon "download" aria-hidden="true" %} Export CSV** button to download a CSV file of the data currently displayed on the page for security research and in-depth data analysis. For more information, see [AUTOTITLE](/code-security/security-overview/exporting-data-from-security-overview). {% endif %}
|
||||
|
||||
{% ifversion security-overview-enterprise-codeql-pr-alerts %}
|
||||
|
||||
## Viewing {% data variables.product.prodname_codeql %} pull request alerts metrics for your enterprise
|
||||
|
||||
You can also view metrics for {% data variables.product.prodname_codeql %} alerts in pull requests across organizations in your enterprise.
|
||||
|
||||
{% data reusables.security-overview.enterprise-filters-tip %}
|
||||
|
||||
{% data reusables.enterprise-accounts.access-enterprise-on-dotcom %}
|
||||
{% data reusables.code-scanning.click-code-security-enterprise %}
|
||||
1. In the sidebar, under "Metrics", click **{% octicon "graph" aria-hidden="true" %} {% data variables.product.prodname_codeql %} pull request alerts**.
|
||||
|
||||
{% endif %}
|
||||
{% data reusables.security-overview.enterprise-filters-tip %}
|
||||
|
||||
@@ -4,6 +4,7 @@ shortTitle: View secret scanning metrics
|
||||
allowTitleToDifferFromFilename: true
|
||||
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.'
|
||||
permissions: '{% data reusables.permissions.security-overview %}'
|
||||
product: '{% data reusables.gated-features.security-overview-fpt-sp-only %}'
|
||||
type: how_to
|
||||
redirect_from:
|
||||
- /code-security/security-overview/viewing-metrics-for-secret-scanning-push-protection-in-your-organization
|
||||
@@ -14,7 +15,9 @@ topics:
|
||||
- Organizations
|
||||
- Teams
|
||||
versions:
|
||||
feature: security-overview-push-protection-metrics-page
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
ghes: '*'
|
||||
---
|
||||
|
||||
{% data reusables.secret-scanning.push-protection-org-metrics-beta %}
|
||||
@@ -61,12 +64,12 @@ The metrics are based on activity from the default period or your selected perio
|
||||
|
||||
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 %}
|
||||
|
||||
{% data reusables.security-overview.enterprise-filters-tip %}
|
||||
|
||||
{% ifversion ghes %}{% data reusables.enterprise-accounts.access-enterprise-ghes %}{% else %}{% data reusables.enterprise-accounts.access-enterprise-on-dotcom %}{% endif %}
|
||||
{% data reusables.code-scanning.click-code-security-enterprise %}
|
||||
1. In the sidebar, click **{% data variables.product.prodname_secret_scanning_caps %} metrics**.
|
||||
1. Click on an individual secret type or repository to see the associated {% data variables.secret-scanning.alerts %} for your enterprise.
|
||||
{% data reusables.security-overview.filter-secret-scanning-metrics %}
|
||||
|
||||
{% data reusables.security-overview.enterprise-filters-tip %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
@@ -3,6 +3,7 @@ title: Viewing security insights
|
||||
shortTitle: View security insights
|
||||
intro: 'You can use the overview dashboard in security overview to monitor the security landscape of the repositories in your organization{% ifversion security-overview-dashboard-enterprise %} or enterprise{% endif %}.'
|
||||
permissions: '{% data reusables.permissions.security-overview %}'
|
||||
product: '{% data reusables.gated-features.security-overview-fpt-both %}'
|
||||
versions:
|
||||
feature: security-overview-dashboard
|
||||
type: how_to
|
||||
@@ -88,7 +89,7 @@ Keep in mind that the overview page tracks changes over time for security alert
|
||||
## Understanding the overview dashboard
|
||||
|
||||
{% ifversion security-overview-3-tab-dashboard %}
|
||||
<!--Content for GHEC and GHES 3.16+ see next HTML comment for GHES =< 3.15-->
|
||||
<!--Content for FPT, GHEC, and GHES 3.16+ see next HTML comment for GHES =< 3.15-->
|
||||
|
||||
* [Detection tab](#detection-tab)
|
||||
* [Remediation tab](#remediation-tab)
|
||||
|
||||
Reference in New Issue
Block a user