Skip to content

Commit c81c40e

Browse files
Merge branch 'main' into codex/document-merge-group-branch-filters
2 parents b9c0dca + dec52ec commit c81c40e

143 files changed

Lines changed: 79508 additions & 36932 deletions

File tree

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

Dockerfile

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@
1010
# ---------------------------------------------------------------
1111
# To update the sha:
1212
# https://github.com/github/gh-base-image/pkgs/container/gh-base-image%2Fgh-base-noble
13-
FROM ghcr.io/github/gh-base-image/gh-base-noble:20260625-083609-gedf42de01@sha256:bf0a2f43957531d73dcb2abceabf2228560f1f67d14e23f5bb0c0ccbabd77dee AS base
13+
FROM ghcr.io/github/gh-base-image/gh-base-noble:20260630-205522-g4a33dc6bb@sha256:2b8edd7da1718e2e9c25b98fd31dae58e57e756ef19842eac212255765cf4ada AS base
1414

1515
# Install curl for Node install and determining the early access branch
1616
# Install git for cloning docs-early-access & translations repos
3 Bytes
Loading
6 Bytes
Loading
2.25 KB
Loading
2 KB
Loading
16.9 KB
Loading

content/code-security/concepts/secret-security/index.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -10,6 +10,7 @@ contentType: concepts
1010
children:
1111
- /secret-leakage-risks
1212
- /secret-scanning
13+
- /public-monitoring
1314
- /push-protection
1415
- /secret-security-with-github
1516
- /about-alerts
Lines changed: 41 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,41 @@
1+
---
2+
title: Public monitoring for secret scanning
3+
shortTitle: Public monitoring
4+
allowTitleToDifferFromFilename: true
5+
intro: 'Public monitoring detects credentials leaked by your enterprise members in public repositories across {% data variables.product.github %}, giving you visibility into secret exposure beyond your enterprise''s boundaries.'
6+
versions:
7+
feature: secret-scanning-public-monitoring
8+
product: 'Public monitoring is available for enterprises on {% data variables.product.prodname_ghe_cloud %} with {% data variables.product.prodname_GH_advanced_security %} or {% data variables.product.prodname_GH_secret_protection %} enabled. Public monitoring is **not available for {% data variables.enterprise.data_residency %}**.'
9+
contentType: concepts
10+
category:
11+
- Protect your secrets
12+
---
13+
14+
{% data reusables.secret-scanning.public-monitoring-public-preview %}
15+
16+
## About public monitoring
17+
18+
{% data variables.product.github %} monitors for secrets leaked across {% data variables.product.github %} in real time. Public monitoring attributes publicly exposed secrets back to your enterprise, based on where your people commit.
19+
20+
{% data variables.product.prodname_secret_scanning_caps %} detects secrets in repositories that your enterprise owns. Public monitoring extends this detection to secrets found in arbitrary public repos across {% data variables.product.github %}.com, regardless of whether or not your enterprise owns the repository where it was leaked.
21+
22+
This gives enterprise security administrators visibility into credential exposure they wouldn't otherwise be aware of, helping identify potential risks and leaked secrets which could be exploited by bad actors.
23+
24+
## How public monitoring works
25+
26+
Public monitoring scans public repositories, including non-code content like issue and pull request comments across {% data variables.product.github %} for secrets associated with your enterprise. When a secret is detected, an alert is surfaced in the enterprise-level security overview.
27+
28+
### Attribution methods
29+
30+
Public monitoring uses two methods to associate detected secrets with your enterprise:
31+
32+
* **Enterprise membership:** Secrets leaked by users who are members of your enterprise
33+
* **Verified domain matching:** Secrets leaked by users whose email address matches a verified domain of your enterprise, even if they are not direct enterprise members
34+
35+
Both attribution methods are active when public monitoring is enabled.
36+
37+
## Requirements
38+
39+
To use public monitoring, your enterprise must:
40+
41+
* Have {% data variables.product.prodname_GH_advanced_security %} or {% data variables.product.prodname_GH_secret_protection %} enabled

content/code-security/concepts/secret-security/secret-scanning.md

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -77,3 +77,11 @@ Validity checks are separate from {% data variables.product.prodname_secret_scan
7777
## How can I access this feature?
7878

7979
{% data reusables.gated-features.secret-scanning %}
80+
81+
{% ifversion secret-scanning-public-monitoring %}
82+
83+
## Public monitoring
84+
85+
In addition to scanning repositories your enterprise owns, you can enable public monitoring to detect secrets leaked by your enterprise members in public repositories across {% data variables.product.github %}. This extends {% data variables.product.prodname_secret_scanning %} beyond the repositories your enterprise owns to follow your members' activity across the platform. See [AUTOTITLE](/code-security/concepts/secret-security/public-monitoring).
86+
87+
{% endif %}
Lines changed: 27 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,27 @@
1+
---
2+
title: Enabling public monitoring for your enterprise
3+
shortTitle: Enable public monitoring
4+
intro: 'Start detecting secrets your enterprise members leak in public repositories outside your enterprise''s boundaries.'
5+
versions:
6+
feature: secret-scanning-public-monitoring
7+
permissions: Enterprise owners can enable public monitoring for their enterprise.
8+
contentType: how-tos
9+
category:
10+
- Secure at scale
11+
---
12+
13+
{% data reusables.secret-scanning.public-monitoring-public-preview %}
14+
15+
## Prerequisites
16+
17+
Before enabling public monitoring, ensure your enterprise has:
18+
19+
* {% data variables.product.prodname_GH_advanced_security %} or {% data variables.product.prodname_GH_secret_protection %} enabled
20+
* While not necessary, we recommend having at one verified domain configured (see [AUTOTITLE](/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise)) in order to get the full value for the feature.
21+
22+
## Enabling public monitoring
23+
24+
{% data reusables.enterprise-accounts.access-enterprise %}
25+
{% data reusables.enterprise-accounts.settings-tab %}
26+
{% data reusables.enterprise-accounts.advanced-security-tab %}
27+
1. Under "Additional Settings," toggle **Public monitoring**.

0 commit comments

Comments
 (0)