GitHub Expands Public Monitoring to Data Residency Customers
According to GitHub. New public preview feature allows enterprises to detect exposed credentials in public commits while maintaining strict data residency compliance.
- • Public monitoring is now available in public preview for GitHub Enterprise Cloud with data residency.
- • Attribution of exposed credentials is managed through verified domain matching to ensure tenant isolation.
- • The feature is included at no additional cost for users with GitHub Advanced Security or Secret Protection licenses.
Enhanced Security for Data Residency
GitHub has introduced public monitoring to extend secret scanning capabilities beyond internal repositories. For enterprises hosted in data residency regions, the system uses verified domain matching to attribute exposed credentials. Because these environments maintain strict tenant isolation, the system encrypts alerts and delivers them directly to the enterprise dashboard, ensuring that sensitive data remains within the designated geographic boundaries.
Eligibility and Access
The feature is currently available in public preview for GitHub Enterprise Cloud customers who utilize data residency. Access requires an active GitHub Advanced Security or GitHub Secret Protection license. Enterprise administrators and security managers can enable the functionality directly through their enterprise security settings. GitHub confirms that this monitoring capability is included with existing licenses at no additional cost.
- 1. github.blogOpen source