GitHub's October 23 security update turns public monitoring from a passive list into a triage workflow. Eligible enterprise security teams can now dismiss and reopen findings, view their history, filter by source and credential type, and receive ongoing validity checks for supported tokens. A status of Active, Inactive or Unknown helps distinguish an exposed live key from a dead one.
The operational feature is the enterprise webhook named secret_scanning_public_monitoring_alert, backed by an API endpoint for querying attributed public leaks. In principle, that could feed a lightweight incident dashboard, a ticket or a Slack notification without waiting for somebody to visit the GitHub security page. Importantly, closing an alert does not revoke the credential or remove it from a repository; revocation is still the response that matters.
This particular public-monitoring capability is a GitHub Enterprise Cloud preview included with GitHub Advanced Security or Secret Protection licensing. It is not a free feature for every private personal repository. GitHub does separately provide free automatic secret scanning for public repositories, so a useful immediate check is to inspect the Security tab of the repositories you actually operate and confirm what is enabled.
For a small software operation, the high-value takeaway is to distinguish detection, validity and remediation in any security workflow. A simple inventory of where API keys are stored and how quickly they can be rotated is more useful than adopting a large enterprise tool just because the changelog sounds impressive.