GitLab group without enforced 2FA
Without enforced 2FA on a GitLab group, members can sign in with a password alone — and their access to your repositories is one phished credential away.
Why it matters
Repository access exposes secrets in history, your CI/CD pipeline, and the ability to push changes into releases. Developer accounts are heavily targeted by phishing.
Enforcing 2FA at the group level fixes the weakest link for every member in one setting.
How to check for it
- GitLab → Group → Settings → General → Permissions shows whether 2FA is required for the group.
- Via the API: GET /groups/:id and check require_two_factor_authentication.
How to fix it
- Turn on 'Require all users in this group to set up two-factor authentication' (Group → Settings → General → Permissions).
- Set a grace period so members can enrol, then let it take effect.
- Protect the default branch of each project too, so even a compromised account can't rewrite main unreviewed.
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
- Does this apply to subgroups?
- Enforcing 2FA on a top-level group applies to its members; review subgroups and projects as well, and protect their default branches for defence in depth.