Two-Step Verification for Website Admins and Company Email

By · 11 November 2026 · 4 min read

Illustration of an admin login protected by a password and a security key as the second step

Imagine the password for your website admin, or your director's email, leaks today. Perhaps it was reused on another service, written in a chat group or typed into a fake login page. If that password is the only thing protecting the account, someone else can now log in as you.

Two-step verification (often called 2FA or MFA) means a leaked password is not enough to get in. It is one of the cheapest security steps with the biggest impact. This article explains which accounts to protect first, which methods are safest, and how to apply it to your company website and email.

What is two-step verification?

Two-step verification asks for two proofs at login: something you know (the password) and something you have, such as a code from an app on your phone or a physical security key. According to CISA, the US cybersecurity agency, if one factor such as a password is compromised, unauthorised users still can't get in without the second factor.

CISA urges organisations to use MFA for all users and all services, including email, file sharing and access to financial accounts.

Which accounts come first?

If you can't do everything at once, start with the accounts that would do the most damage if broken into:

  1. Company email, especially admin and senior management accounts. Almost every other account can be reset through email, so whoever controls the email can take over the rest.
  2. Website and CMS admin, because this is where the website's content can be changed.
  3. Hosting, domain and DNS. These accounts decide where your website and email point.
  4. Backup storage and other services that hold company data.

Hosting and domain accounts are often set up by a vendor or by staff who left long ago, and nobody knows whose phone is registered on them. Before turning on two-step verification, first make sure these accounts are in the company's name and held by the right people.

Which method is safest?

Not all two-step verification is equally strong. CISA ranks the methods from strongest:

  • Security keys or passkeys (FIDO/WebAuthn). CISA calls this the gold standard because it resists phishing, and strongly urges system administrators and other high-value targets to use it.
  • Authenticator apps that generate codes, or push notifications with number matching. According to CISA, these are the best options for small and medium-sized businesses that can't move to phishing-resistant methods straight away. The codes can still be stolen through a fake login page.
  • Push notifications without number matching. Vulnerable to "push bombing": the user is flooded with prompts until they finally press "Approve".
  • Codes by SMS or phone call. Vulnerable to phishing and number takeover (SIM swap). CISA calls this a last resort, although it is still better than no MFA at all.

Turning it on for company email

If your company email runs on Google Workspace, a super admin can set up two-step verification under Security > Authentication > 2-step verification in the Admin console. Google suggests this order: tell employees, let them turn it on themselves, track who has enrolled, then enforce it from a set date. Admins can also block SMS and phone codes, or require security keys.

If you use Microsoft 365, Microsoft Entra has a security defaults feature that requires every user to register for MFA and admins to always use it. It also blocks older email protocols that don't support MFA. According to Microsoft, more than 99.9% of common identity attacks are stopped by MFA and blocking legacy authentication. See also our guide to company email on your own domain.

Turning it on for website admins

WordPress's security guide recommends two-step verification, but it isn't built into WordPress itself. One option is the community-developed Two Factor plugin in the official WordPress.org directory. It supports authenticator app codes, email codes and backup codes. For passkeys or security keys, it points to an additional plugin.

For other CMSs, check the account settings or ask your website provider. If your CMS doesn't support two-step verification at all, record it as a risk. CISA recommends upgrading or replacing systems that don't support MFA, and escalating the risk to senior leadership. This step is also part of our monthly WordPress security checklist.

Prepare a fallback before a phone goes missing

  • Keep backup codes in a password manager or another safe place, not on the same phone.
  • Register more than one method, for example an authenticator app plus a security key.
  • Make sure there is more than one admin. Microsoft recommends that organisations keep emergency admin accounts for when other admins are locked out.
  • Write down the recovery procedure, including who may reset an employee's two-step verification.

Common mistakes

  • One admin account, one phone, many people. Codes get forwarded through a chat group, and the protection is gone.
  • Approving login prompts without reading them. If you aren't logging in, reject it.
  • A former employee's phone is still registered. Remove their device during offboarding.
  • Admins still on SMS. For the most important accounts, move up to an authenticator app or a security key.
  • Only admins are protected. Microsoft notes that attackers often target ordinary users too, and move on from there.

Passwords will leak one day. Two-step verification makes sure that leak doesn't turn straight into a break-in.

Want to know how strong the admin access to your website and systems really is? See how we test security on our pentest page, or request a pentest quote.