Cybersecurity
What Is Two-Step Authentication and Why Do Admin Accounts Need It?
Two-step authentication asks for a second proof besides the password, so a leaked password alone is not enough to sign in. For admin accounts, this layer should be treated as a baseline requirement.
SEO and Content Specialist
3 min read Reviewed by Legia Cybersecurity Team
Short answer: two-step authentication asks for a second proof besides the password at login, for example a code from an authenticator app or a physical security key. A password that leaks, or is handed over on a fake site, is no longer enough to get in. Admin accounts come first because one such account can open an entire server, cloud, or system, and CIS Controls v8 calls for MFA on all administrative access accounts.
Passwords can be guessed, reused, stolen, or captured through a fake login page. Two-step authentication closes that gap with one extra requirement. Securing admin access as a whole is covered in Securing Server Admin Access.
What is two-step authentication?
Two-step authentication is a login process that asks for a second proof of identity after the password. According to CISA, such proof falls into something you know (the password), something you have (a phone or a security key), and something you are (a fingerprint or a face).
The stricter term is multi-factor authentication (MFA). NIST SP 800-63B defines assurance level AAL2 as proof of possession and control of two distinct authentication factors. Two steps of the same kind, such as a password followed by a secret question, are not as strong as two different factors.
Why is it required for admin accounts?
An admin account can change configuration, read data, and create other accounts, so an attacker who takes it over controls the systems beneath it. CIS Controls v8 Safeguard 6.5 calls for MFA on all administrative access accounts, where supported, on all enterprise assets, whether managed on-site or by a third party. That safeguard applies in every Implementation Group, including the basic group (IG1).
The scope is not just server logins, but also the cloud console, the email administrator account, the domain and DNS panel, and the CMS panel.
Types of second step, from strongest
Not every second step is equally strong. The table below summarizes the assessments from NIST, CISA, and Microsoft:
| Type | Resistance to phishing | Notes |
|---|---|---|
| Physical security key or passkey (FIDO2/WebAuthn) | Resistant | CISA calls FIDO/WebAuthn the only widely available phishing-resistant authentication |
| One-time code from an authenticator app | Not resistant | NIST classes it as not phishing-resistant, while Microsoft still rates it far safer than a password alone |
| Approval through a phone notification | Not resistant | CISA suggests number matching to hinder notification-flooding attacks |
| Code by SMS or phone call | Not resistant | NIST restricts use of the telephone channel for verification, and warns of risks such as SIM changes |
CISA’s principle: any MFA is better than none, and phishing-resistant authentication is the standard to aim for. For admin accounts, prefer a security key or passkey, and keep an authenticator app as a fallback. Use SMS last.
Steps to set it up for admin accounts
- List all admin accounts, then turn on two-step authentication on each, starting with the cloud console and servers.
- Register two methods per account, for example two security keys or one key plus an authenticator app, so losing one device does not lock the account.
- Store recovery codes in a safe place separate from daily devices.
- Make sure accounts are created in the company’s name, not an individual’s, and revoke access when the owner leaves.
- Test login with the second method before relying on it.
In the Server Installation & Management service, Legia sets up SSH keys and two-step authentication for admin access, along with per-person access rights and access logs. More on security is on the Cyber Security page.
Sources
- CISA, More than a Passwordcisa.gov
- NIST, SP 800-63B-4 Digital Identity Guidelines: Authentication and Authenticator Managementpages.nist.gov
- Microsoft Learn, Microsoft Entra authentication overviewlearn.microsoft.com
- CIS Controls Assessment Specification, Safeguard 6.5: Require MFA for Administrative Accesscontrols-assessment-specification.readthedocs.io

