A digital globe sends encrypted user data to a secure access dashboard in a control room.
GitHub has extended secret scanning's public monitoring to GitHub Enterprise Cloud with data residency (GHEC DR). It is now in public preview. When the feature first launched in July, GitHub said support for Enterprise Cloud with data residency was coming soon. The October 22 changelog entry delivers on that promise. It comes with a different attribution model, which matters if you run a data-resident tenant.

A digital globe sends encrypted user data to a secure access dashboard in a control room. What public monitoring does​

Ordinary secret scanning only looks at repositories your enterprise owns. Public monitoring extends detection to secrets found in arbitrary public repos across GitHub.com, whether or not your enterprise owns the repository where the secret leaked. The target is the usual leak: a developer pushes a token to a personal fork, contributes to an open source project, or pastes a key into a public issue. A repository-scoped scanner never sees any of that.

GitHub's announcement says the GHEC DR version monitors public commits across github.com. It attributes exposed credentials back to your enterprise in real time.

The data residency twist: domain matching only​

The GHEC DR version attributes leaks differently from the standard Enterprise Cloud version. In standard Enterprise Cloud, GitHub's own July announcement says it attributes secrets through GitHub's identity layer and verified domains.

Data residency tenants can't use the identity layer, because the two environments are isolated from each other. GitHub says that isolation means enterprise membership rosters are not shared across the boundary. Attribution therefore rests on verified domain matching alone.

In practice:

  • GitHub checks the email address on a public commit author.
  • If that address matches a domain your enterprise has verified, GitHub encrypts the alert and delivers it to your enterprise dashboard.
  • GitHub says the data stays within your designated geography.

Domain verification is the whole attribution mechanism, so your coverage depends on how complete your verified domain list is. If a developer commits with a personal Gmail address, the announced method has nothing to match. Likewise, a company domain you never verified won't produce alerts. The announcement doesn't describe any fallback, exceptions, or handling of ambiguous matches, so don't assume there is one.

Eligibility, enablement and cost​

  • Licensing: you need an active GitHub Advanced Security or GitHub Secret Protection license.
  • Who can turn it on: enterprise admins and enterprise security managers, under enterprise security settings.
  • Cost: GitHub says it is included with either license at no additional cost.
  • Status: public preview, so behavior and settings may change.

The announcement says nothing about detection latency, service-level guarantees, alert retention, or the list of supported secret patterns. It also doesn't say which content types the data-residency preview covers. It names public commits only. Other sources describe the standard feature as also covering pull request comments, issues and discussions. Don't assume the GHEC DR preview does the same until GitHub says so.

A documentation conflict to know about​

At the time of writing, GitHub's public monitoring docs page still says the feature is not available for GitHub Enterprise Cloud with data residency. That contradicts the dated October 22 changelog entry. The likeliest explanation is that the docs haven't caught up yet, but that is my inference and GitHub hasn't said so. If the setting doesn't appear in your enterprise security settings, check your tenant and GitHub's current guidance before concluding you're misconfigured.

Readiness checklist: verify your domains​

Since verified domains drive attribution, verify them before you enable the feature. GitHub's enterprise documentation says enterprise owners do this. The steps below come from that documentation.

  1. You need access to modify DNS records for the domain with your hosting service.
  2. Go to your enterprise, click Settings, then click Verified & approved domains.
  3. Next to "Verified & approved domains for your enterprise account," click Add a domain. Type the domain and click Add domain.
  4. Follow the instructions under "Add a DNS TXT record" to create the TXT record with your DNS provider.
  5. Wait for DNS to update. GitHub says this can take up to 72 hours.
  6. Check the record with dig TXT-RECORD-NAME +nostats +nocomments +nocmd TXT. Replace the placeholder with the name of the TXT record you created.
  7. Also confirm the record resolves directly from your authoritative name servers: dig DOMAIN +nostats +nocomments +nocmd TXT @AUTHORITATIVE-NAMESERVER. GitHub says this avoids problems with CNAME records that point elsewhere.
  8. Return to Verified & approved domains. Next to the pending domain, click the menu, then Continue verifying, then Verify.

GitHub's documentation also notes that once the "Verified" badge shows on your organization profiles, you can optionally delete the TXT entry.

Verification and approval are different things. Verification proves you control the domain. Approval only lets members receive email notifications at a domain you don't own, such as a contractor's. The GHEC DR announcement says attribution is powered exclusively by verified domain matching. I wouldn't count on an approved-only domain triggering alerts.

Also check variants. GitHub's documentation says that if website and email addresses use variants of the same domain, you must verify both. That example concerns organization profile badges rather than public monitoring, but it's a sensible prompt to audit subdomains and alternate corporate domains.

Analysis: who benefits, and what it can't do​

Data residency customers are usually in regulated sectors, or in regions with strict rules on where data lives. Until now they couldn't use this visibility at all. The threat is real for them. The July StepSecurity write-up on the standard feature pointed to supply-chain worms such as Sha1-Hulud, which exfiltrated stolen credentials into over 21,000 new public GitHub repositories in November 2025. A public repository holding stolen secrets is exactly the kind of exposure your internal scanning never sees.

There are caveats:

  • Attribution is a heuristic, not proof of authorship. An email match to a verified domain is a strong signal. It still isn't proof of who made the commit.
  • Coverage depends on commit email hygiene. Developers who commit with personal addresses stay invisible to this method. A policy requiring work addresses for work commits would help, though GitHub's announcement doesn't say anything about enforcing one.
  • It only sees what is already public. GitHub says the feature will never scan private repositories. It surfaces secrets that are already exposed, so you can revoke them. Detection is a prompt to rotate credentials, not a way to undo the exposure.
  • It's a preview. Treat it as an extra signal alongside push protection and your existing secret scanning, not a replacement.

Third-party tools such as GitGuardian have offered public GitHub monitoring for years. The native option is attractive for GHEC DR customers because it is included with the licenses they already hold and keeps alerts in-region. Whether its coverage matches those tools is something the announcement doesn't let us judge.

Bottom line​

If you run GHEC DR with Advanced Security or Secret Protection, public monitoring is now something you can try, at no extra license cost. Confirm your verified domains first, then enable it under enterprise security settings. Expect some gaps from the domain-only attribution model, and watch for GitHub bringing its documentation in line with the announcement.

 

References

  1. Public monitoring now available with data residency GitHub Changelog 2026-10-22T18:12:58+00:00
  2. Public monitoring for secret scanning - GitHub Docs docs.github.com
  3. Secret scanning public monitoring for enterprises - GitHub Changelog github.blog