Does GitHub support 2FA?

How to enable 2FA on GitHub

1. Sign in to your GitHub account.
2. Open Account settings → Security (the exact path varies; see the official docs link above).
3. Choose your preferred method from the list — TOTP and hardware keys are the recommended options.
4. For TOTP: scan the QR code with Kaito or your authenticator app of choice. Verify the first 6-digit code before saving.
5. For hardware keys: insert your key when prompted and tap to enroll. Register at least two keys per account so loss of one doesn't lock you out.
6. Save the recovery codes somewhere safe — they're your last resort if you lose your authenticator and your hardware keys.

Hardware keys supported

GitHub documents support for: YubiKey 5, Titan, Solokey.

Recovery

https://docs.github.com/en/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials

Sharing GitHub 2FA with a team (with Kaito)

GitHub org owner is one of the highest-impact shared-2FA cases. Require all org members to enable MFA, then store the org-owner shared TOTP in Kaito with full-seed permission limited to two named admins.

1. In Kaito, go to Tokens → New and add the GitHub 2FA seed (or scan the QR).
2. Permission the token to a group: code-only for most teammates, full-seed only for the admins who would handle rotation.
3. Stream the audit log to your SIEM if you want a complete record of which team members generated codes for GitHub and when.

GitHub permits shared access in their terms of service.

Frequently asked questions