GitHub organization without required 2FA
When a GitHub organization doesn't require 2FA, any member can sign in with just a password — and everything they can push to or release is one credential away.
Why it matters
Source code access means secrets in the history, your build pipeline, and the ability to slip malicious changes into a release. Developer accounts are a prime phishing target.
Requiring 2FA org-wide removes the weakest link in one setting, for every current and future member.
How to check for it
- GitHub → your organization → Settings → Authentication security shows whether 2FA is required.
- Via the API: GET /orgs/:org and check two_factor_requirement_enabled.
How to fix it
- Turn on 'Require two-factor authentication for everyone in the organization' (Organization → Settings → Authentication security).
- Members without 2FA are removed when you enforce it, so give notice and have them enrol first.
- Pair it with SSO/SAML where you have an identity provider.
SkyShield checks this automatically
Connect your AWS, Cloudflare, GitHub, GitLab, Hetzner or DigitalOcean account read-only and SkyShield flags this across every account and region, with the fix in plain words — alongside the agent that watches your servers. Start free.
FAQ
- What happens to members who don't have 2FA when I enforce it?
- They're removed from the organization until they enable 2FA and are re-invited, so announce the change and set a deadline before turning it on.