Credential revocation and deauthorization by token type
UpdateVerifiedAdded Sep 22, 2026
Building on our self-service credential revocation experiences for incident response, you can now take token-type and user-specific actions to deauthorize and revoke user credentials during a security incident. This gives you finer-grained control when responding to a compromise.
Topics: Security, Developer tools
Summaries of vendors' own notes. Product names and logos belong to their owners; logos via logo.dev.
More GitHub Advanced Security releases
Every GitHub Advanced Security release| Date | Release | Type |
|---|---|---|
| Aug 19 | Track organization code quality trends GA | GA |
| Aug 20 | Code scanning adds a mitigated alert dismissal reason Update | Update |
| Aug 20 | Track GitHub Code Quality enablement changes in the audit log Update | Update |
| Aug 13 | License data quality improvements Update | Update |
| Aug 25 | Block users directly from security advisories Update | Update |
| Aug 7 | Secret scanning coverage updates Update | Update |
| Aug 4 | Customize code scanning default setup at scale Update | Update |
| Aug 4 | Customize Dependabot pull request branch names Update | Update |
