jprdonnelly/docs
1
0
Fork 0
mirror of synced 2025-12-19 18:10:59 -05:00
Code Issues Projects Releases Wiki Activity

The secret risk assessment is generally available [GA] (#57186)

Browse Source
This commit is contained in:
Sophie
2025-08-27 11:23:43 +02:00
committed by GitHub
parent 88e3945d45
commit 66598ebe84
4 changed files with 6 additions and 14 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
content/code-security/securing-your-organization/understanding-your-organizations-exposure-to-leaked-secrets/about-secret-risk-assessment.md
View File

@@ -33,8 +33,6 @@ Regularly assessing your exposure to leaked secrets is good practice to help ide
## About {% data variables.product.prodname_secret_risk_assessment %}
{% data reusables.secret-risk-assessment.public-preview-note %}
{% ifversion fpt %}
>[!TIP] This report is only available if you are on the {% data variables.product.prodname_team %} plan. For information about the plan and how to upgrade, see [{% data variables.product.prodname_team %}](/get-started/learning-about-github/githubs-plans#github-team) and [Upgrading your organization's plan](/billing/managing-the-plan-for-your-github-account/upgrading-your-accounts-plan#upgrading-your-organizations-plan).
@@ -45,12 +43,12 @@ Regularly assessing your exposure to leaked secrets is good practice to help ide
The {% data variables.product.prodname_secret_risk_assessment %} report provides the following insights:
* **Total secrets**—Aggregate count of exposed secrets detected within the organization.
* **Public leaks**—Distinct secrets found in your organization's public repositories.
* **Preventable leaks**—Secrets that could have been protected, using {% data variables.product.prodname_GH_secret_protection %} features such as {% data variables.product.prodname_secret_scanning %} and push protection.
* **Secret locations**—Locations that are scanned for the report. {% data reusables.secret-risk-assessment.what-is-scanned %}
* **Secret categories**—Distribution of the types of secrets that are leaked. Secrets can be partner secrets, which are strings that match secrets issued by service providers in our partner program, or generic secrets, which are non-provider patterns such as SSH keys, database connection strings, and JSON web tokens.
* **Repositories with leaks**—Repositories where leaked secrets were detected, out of all the repositories scanned.
* **Total secrets**—Aggregate count of exposed secrets detected within the organization.
* **Public leaks**—Distinct secrets found in your organization's public repositories.
* **Preventable leaks**—Secrets that could have been protected, using {% data variables.product.prodname_GH_secret_protection %} features such as {% data variables.product.prodname_secret_scanning %} and push protection.
* **Secret locations**—Locations that are scanned for the report. {% data reusables.secret-risk-assessment.what-is-scanned %}
* **Secret categories**—Distribution of the types of secrets that are leaked. Secrets can be partner secrets, which are strings that match secrets issued by service providers in our partner program, or generic secrets, which are non-provider patterns such as SSH keys, database connection strings, and JSON web tokens.
* **Repositories with leaks**—Repositories where leaked secrets were detected, out of all the repositories scanned.
{% data reusables.security-overview.secret-risk-assessment-report-generation-cadence %}

2
content/code-security/securing-your-organization/understanding-your-organizations-exposure-to-leaked-secrets/choosing-github-secret-protection.md
View File

@@ -69,8 +69,6 @@ In addition, repository administrators can enable security features at the repos
## Enabling {% data variables.product.prodname_secret_protection %} from the {% data variables.product.prodname_secret_risk_assessment %}
{% data reusables.secret-risk-assessment.public-preview-note %}
{% data reusables.organizations.navigate-to-org %}
{% data reusables.organizations.security-overview %}
{% data reusables.security-overview.open-assessments-view %}

2
content/code-security/securing-your-organization/understanding-your-organizations-exposure-to-leaked-secrets/interpreting-secret-risk-assessment-results.md
View File

@@ -16,8 +16,6 @@ topics:
The {% data variables.product.prodname_secret_risk_assessment %} dashboard displays point-in-time insights into the secrets detected in your organization. {% data reusables.secret-risk-assessment.link-conceptual-information %}
{% data reusables.secret-risk-assessment.public-preview-note %}
## Prerequisites
You need to generate a {% data variables.product.prodname_secret_risk_assessment %} report and wait for the scan to complete before being able to view and export the results. See [AUTOTITLE](/code-security/securing-your-organization/understanding-your-organizations-exposure-to-leaked-secrets/viewing-the-secret-risk-assessment-report-for-your-organization#generating-an-initial-secret-risk-assessment) and [Exporting the {% data variables.product.prodname_secret_risk_assessment %} to CSV](/code-security/securing-your-organization/understanding-your-organizations-exposure-to-leaked-secrets/viewing-the-secret-risk-assessment-report-for-your-organization#exporting-the-secret-risk-assessment-to-csv).

2
content/code-security/securing-your-organization/understanding-your-organizations-exposure-to-leaked-secrets/viewing-the-secret-risk-assessment-report-for-your-organization.md
View File

@@ -20,8 +20,6 @@ topics:
You can generate the {% data variables.product.prodname_secret_risk_assessment %} report for your organization, review it, and export the results to CSV.
{% data reusables.secret-risk-assessment.public-preview-note %}
## Generating an initial {% data variables.product.prodname_secret_risk_assessment %}
{% data reusables.organizations.navigate-to-org %}