AI Info Guide
AI news for everyone

GitHub makes public secret monitoring generally available for enterprises

October 28, 2026 · Central Time

GitHub announced general availability of public monitoring for enterprises on October 28. The feature alerts an enterprise when secrets associated with it appear in public GitHub content, including outside repositories it owns. The announcement describes coverage on github.com, not a search of the entire internet.

Examples include public git content, pull-request comments and user-created gists. GitHub says monitoring runs in real time and does not scan other parties' private repositories. Separate enterprise secret scanning remains available for repositories an organization owns, including private and internal repositories.

Findings are attributed using enterprise membership or verified-domain matching. The former checks whether the committer belongs to the enterprise; the latter matches an email to a verified enterprise or organization domain. GitHub calls these attribution heuristics, so an alert should be investigated rather than treated as proof of who intentionally disclosed a credential.

For Enterprise Cloud customers with data residency, attribution uses verified-domain matching only. GitHub says enterprise membership rosters do not cross the tenant boundary and that alerts are encrypted and delivered to the enterprise dashboard. This is a product description, not an independent audit of residency controls.

Enterprise owners and enterprise security managers can enable public monitoring from the Security tab. GitHub says recently leaked secrets will appear and future matching exposures will be monitored. No-setup wording does not mean the feature is already enabled for every enterprise or that a leaked credential has been automatically revoked.

The announcement lists Enterprise Cloud with Secret Protection or Advanced Security as eligible, including data-residency support, at no additional cost under those licenses. It does not announce free universal access for all GitHub accounts. Detecting public exposure and revoking or rotating a secret are separate steps.

Original sources

↑ Back to top