Security practitioners using GitHub Enterprise Cloud can now triage public secret leaks and integrate findings into their incident response workflows through REST API access and webhooks. Public monitoring remains in public preview, including data residency environments. It requires GitHub Advanced Security or GitHub Secret Protection, with no additional charge.
GitHub continuously checks token validity for supported providers, displaying Active, Inactive or Unknown to help prioritize response. Alerts can be closed, reopened, commented on and filtered, with a timeline recording actions and state changes.
Enterprise admins and security managers can query findings through the API, while a webhook reports newly attributed leaks. Closing an alert does not revoke the credential or remove it from the public repository.
Choose a sign-in method or comment as a guest below.