Skip to content

MFA is enabled: why phishing-resistant methods still matter

Read this article in ไทย 中文

MFA is enabled: why phishing-resistant methods still matter

An extra step does not make every method phishing-resistant

Can employees still enter an authenticator-app code into a fake login page after a company enables MFA? Yes: a code manually supplied by the user can be phished and relayed. The question is not only how many accounts have MFA, but which method each service enforces and whether weaker entry paths remain available.

CISA distinguishes FIDO/WebAuthn and PKI-based authentication from OTP codes and ordinary approval prompts. Number matching helps reduce careless approval, but should not be described as providing the same phishing resistance as FIDO/WebAuthn. This article addresses method selection and enforcement testing; the linked Chawinnix article provides complementary account-recovery planning for a lost phone.

Passkeys change what is presented to a website

A passkey is a credential associated with an account and its registered website or app. The browser or operating system selects the matching credential, and the user unlocks the device, for example with a PIN or fingerprint. This differs from typing a remembered secret into any website. Google explains that the service stores a public key and biometric information is not sent to the website.

Not every USB-key-shaped device uses the same authentication method. Verify the service and authenticator support the required standard and configuration, including the difference between provider-synced passkeys and device-bound credentials. This affects multi-device use, replacement and control of the sync account. Inventory compatibility before purchasing hardware.

Map entry paths before organization-wide enforcement

List email, file storage, administration and other high-privilege services. Record each owner, normal sign-in method, fallback and emergency accounts. Include older applications or paths outside the normal login screen. The objective is to establish actual coverage, rather than rely on one enabled setting.

Choose a pilot group with varied devices and workflows. Use test accounts and record enrollment, login, logout, device replacement and fallback results. Test both successful use of the new method and rejection of methods disallowed by policy. This does not require creating a deceptive website for employees or collecting anyone’s real secrets.

Do not let fallback undermine the primary method

Hypothetical example: administrators receive FIDO keys, but can still choose password plus SMS at every login. Successful key enrollment has not proved enforcement of phishing-resistant authentication. Define who may use fallback, under what circumstances, who approves it and how it is logged, while retaining controlled recovery so users are not locked out.

If a critical system lacks support, do not disable existing MFA while waiting for a replacement. Document the limitation and agree interim controls and an improvement plan with the business owner. Assign responsibility and review triggers. An ownerless exception makes it unclear whether the obstacle is technology, budget or user support.

Measure enforcement and understand its limits

After the pilot, compare enrolled accounts with those actually covered by enforcement. Separate unsupported devices, user confusion and policy errors before expansion. Phishing resistance during authentication does not make a malware-infected endpoint safe or guarantee that a stolen session is unusable. Endpoint protection, privileges and incident response remain necessary.

For an IT-security discussion with Chawinnix, bring a service inventory, device models, fallback problems and failed test results. These support risk assessment and system planning more effectively than buying many keys first. Do not send passwords, recovery codes or real credentials for a consultation.

Conceptual laptop shield, security key and phone on a blue desk

Sources

Back to all articles

Start the conversation

Tell us briefly what concerns you and our team will get back to you. What you send stays confidential.