Remediation made simple: Introducing new validity checks for GitHub tokens
GitHub now tells you whether GitHub tokens found by secret scanning are active so you can prioritize and escalate remediation efforts.
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.
Coming soon: We’ll validate secrets that belong to our 100+ secret scanning partners too. Learn more about how you can secure your repositories with secret scanning.
Tags:
Written by
Related posts
Tame Dependabot: Group your updates, slow the cadence, keep security fast
Dependabot keeps your dependencies current, but its defaults can flood your repository with pull requests. Here’s how grouping updates, slowing the cadence, and keeping security fixes fast cut the noise on a Microsoft open source project.
Disrupting supply chain attacks on npm and GitHub Actions
Explore the changes we’ve shipped across npm and GitHub Actions over the past few months to disrupt supply chain attack techniques and limit their impact.
The case for a cooldown: Why Dependabot now waits before issuing version updates
A new default three-day cooldown delays version update pull requests so maintainers and security researchers can address findings in a release before it gets into your code.