Get a sneak peek into the must-attend sessions, speakers, workshops, and GitHub certifications available at our global developer event.
If you’re on an application security team, you might use secret scanning to reduce the risk of leaked credentials, like passwords and API keys. When an exposed credential is found, your first step is probably to check whether the token is still active, and what access it has. Now, with validity checks for GitHub tokens, we can help you do just that.
Validity checks determine whether a token is still active and, when possible, whether it was ever active. This is useful when you’re deciding how to remediate an exposure. For example, you might prioritize remediating active secrets before checking your security logs for unauthorized access via API keys that have already been revoked.
To check a GitHub token’s validity, open a secret scanning alert for the leaked GitHub token and the alert will tell you whether the secret is still active. If we can’t accurately detect the validity—this can happen when a token found on GitHub.com belongs to a GitHub Enterprise Server instance—we’ll provide insight on where to look for remediation.