GitHub has added support for securing SSH Git operations using FIDO2 security keys for added protection from account takeover attempts.

GitHub now officially requires token-based authentication for its command line interface, third-party apps, and services that access Git repositories hosted on the platform.

GitHub has recently moved to a new format for all of its tokens, including personal access, OAuth access, user-to-server and server-to-server, and refresh tokens. As GitHub engineer Heather Harvey ...

Multiple high-profile open-source projects, including those from Google, Microsoft, AWS, and Red Hat, were found to leak GitHub authentication tokens through GitHub Actions artifacts in CI/CD ...

Developers from hundreds of companies have included access tokens for their Slack accounts in public projects on GitHub, putting their teams' internal chats and other data at risk.

GitHub Actions Secrets example One of the ongoing challenges DevOps professionals face when developing continuous integration workflows that integrate with disparate systems is how to protect that ...

Build artifacts generated by GitHub Actions often contain access tokens that can be abused by attackers to push malicious code into projects or compromise cloud infrastructure.

One of the key benefits to the Bitbucket App Password or the GitHub Access Token is that a user can receive administrative access to Git repositories, but have no rights at all to scripted pipelines, ...

Widening impact assessment The tj-actions developers had previously reported they could not determine exactly how attackers gained access to their GitHub personal access token.