Skip to content

Commit 9708c4c

Browse files
authored
Secret scanning sends detections in secret gists to partners (#56885)
1 parent 7353948 commit 9708c4c

File tree

4 files changed

+13
-5
lines changed

4 files changed

+13
-5
lines changed

content/code-security/secret-scanning/introduction/about-secret-scanning-for-partners.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -18,6 +18,10 @@ shortTitle: Secret scanning for partners
1818

1919
> [!NOTE]You cannot change the configuration of {% data variables.product.prodname_secret_scanning %} for partner patterns on public repositories.
2020
21+
{% data variables.secret-scanning.partner_alerts_caps %} scans:
22+
23+
{% data reusables.secret-scanning.what-is-scanned %}
24+
2125
The reason partner alerts are directly sent to the secret providers whenever a leak is detected for one of their secrets is that this enables the provider to take immediate action to protect you and protect their resources. The notification process for regular alerts is different. Regular alerts are displayed on the repository's **Security** tab on {% data variables.product.prodname_dotcom %} for you to resolve.
2226

2327
{% data reusables.secret-scanning.secret-scanning-pattern-pair-matches %}

content/code-security/secret-scanning/introduction/about-secret-scanning.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -29,8 +29,14 @@ shortTitle: Secret scanning
2929

3030
{% data variables.product.prodname_secret_scanning_caps %} scans your entire Git history on all branches present in your {% data variables.product.prodname_dotcom %} repository for secrets, even if the repository is archived. {% data variables.product.prodname_dotcom %} will also periodically run a full Git history scan for new secret types in existing content in {% ifversion fpt or ghec %}public repositories{% else %}repositories with {% data variables.product.prodname_GH_secret_protection %} enabled{% endif %} where {% data variables.product.prodname_secret_scanning %} is enabled when new supported secret types are added.
3131

32+
Additionally, {% data variables.product.prodname_secret_scanning %} scans:
33+
3234
{% data reusables.secret-scanning.what-is-scanned %}
3335

36+
{% ifversion fpt or ghec %}
37+
This additional scanning is free for public repositories.
38+
{% endif %}
39+
3440
{% ifversion ghas-products %}{% ifversion secret-risk-assessment %}
3541
> [!TIP]
3642
> 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.

content/get-started/writing-on-github/editing-and-sharing-content-with-gists/creating-gists.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -22,6 +22,8 @@ Gists can be public or secret. Public gists show up in {% data variables.gists.d
2222

2323
Secret gists don't show up in {% data variables.gists.discover_url %} and are not searchable unless you are logged in and are the author of the secret gist. Secret gists aren't private. If you send the URL of a secret gist to a friend, they'll be able to see it. However, if someone you don't know discovers the URL, they'll also be able to see your gist. If you need to keep your code away from prying eyes, you may want to [create a private repository](/repositories/creating-and-managing-repositories/creating-a-new-repository) instead.
2424

25+
For {% data variables.product.prodname_dotcom_the_website %} and {% data variables.product.prodname_ghe_cloud %}, {% data variables.product.github %} automatically scans _secret gists_ for partner secrets and informs the relevant partner whenever one of their secrets is leaked.{% ifversion fpt or ghec %} See [AUTOTITLE](/code-security/secret-scanning/introduction/about-secret-scanning-for-partners).{% endif %}
26+
2527
{% data reusables.gist.cannot-convert-public-gists-to-secret %} However, a secret gist can be made public by editing the gist and updating the visibility to public.
2628

2729
{% ifversion ghes %}
Lines changed: 1 addition & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,12 +1,8 @@
1-
Additionally, {% data variables.product.prodname_secret_scanning %} scans:
21
* Descriptions and comments in issues
32
* Titles, descriptions, and comments, in open and closed _historical_ issues{% ifversion fpt or ghec %}. A notification is sent to the relevant partner when a historical partner pattern is detected.{% endif %}
43
* Titles, descriptions, and comments in pull requests
54
* Titles, descriptions, and comments in {% data variables.product.prodname_discussions %}{% ifversion secret-scanning-enhancements-wikis %}
65
* Wikis{% endif %}
7-
8-
{% ifversion fpt or ghec %}
9-
This additional scanning is free for public repositories.
10-
{% endif %}
6+
* Secret gists. A notification is sent to the relevant partner when a partner pattern is detected in a secret gist.
117

128
{% data reusables.secret-scanning.beta-prs-discussions-wikis-scanned %}

0 commit comments

Comments
 (0)