Cyber Essentials v3.2 raises expectations: all cloud services must use MFA, with stronger methods recommended over SMS when available. Organisations should adopt phishing-resistant authentication to cut AiTM and push-fatigue risk, but there doesn't need to be just one way to do it. You can satisfy CE while improving UX via either of two mature technologies:

• FIDO2/WebAuthn passkeys, widely supported across browsers, OSs and modern IdPs.

• WWPass, a usernameless and passwordless approach using the WWPass Key app and client-side crypto to remove usernames and passwords and enable strong MFA and SSO.

Bottom line: pick one, or run both where it makes sense. Cyber Essentials cares that MFA is enforced and robust, not that everyone uses the same brand of authenticator.

Plain-English Definitions

Cyber Essentials (CE) v3.2: UK scheme defining baseline controls. From 28 April 2025, all new assessments use v3.2. MFA is required for all cloud services, and SMS is explicitly not the most secure when stronger alternatives exist.

Phishing-resistant MFA: Stops credential forwarding (AiTM) and code interception. NCSC flags FIDO2 as phishing-resistant; other national authorities echo this.

Passkeys (FIDO2/WebAuthn): Origin-bound public-key credentials (platform or roaming) used via built-in OS support and security keys.

WWPass (aka WWPass Key): Usernameless, passwordless login using the WWPass Key mobile app to scan or tap a dynamic QR code, establishing a cryptographically protected session without usernames or passwords. Supports recovery, MFA, and SSO.

Why "weak 2FA" fails, and why two strong alternatives are better

Attacks bypassing legacy 2FA: adversary-in-the-middle (AiTM) proxying, SIM-swap on SMS, and "push-bombing" user fatigue. NCSC and CISA push organisations toward phishing-resistant approaches to shut these down.

Two strong choices:

• FIDO2/WebAuthn binds authentication to the real domain with public-key crypto, resisting AiTM and credential replay. It's supported by major platforms and modern identity providers.

• WWPass removes usernames and passwords entirely and uses a dynamic QR ceremony with client-side encryption, cutting both phishing surface and password lifecycle issues. It layers MFA signals (device + app PIN/biometric) and integrates with SSO.

NCSC & CE guidance: what "good" looks like

• CE v3.2: "Authentication to cloud services must always use MFA," and SMS is not the most secure, use stronger alternatives when available.

• NCSC "Recommended types of MFA": FIDO2 offers guessing, phishing, and theft resistance and is appropriate broadly; other methods rank lower.

• Testing & timelines: the CE+ Test Specification (v3.2) and 2025 changes confirm scope and assessment baselines.

Quick comparison: weak 2FA vs. phishing-resistant options

Mapping CE MFA to your access control policy

Embed these anchors, adapted and expanded from your original guide:

• Scope: Enforce MFA for all cloud services, admin, and internet-exposed accounts.

• Preferred methods: Mandate phishing-resistant options (choose FIDO2/WebAuthn or WWPass per system capability).

• Enrollment & recovery: Require at least two strong authenticators per user (e.g., platform passkey + security key or WWPass Key on two devices with recovery configured).

• Admin separation: Use dedicated admin accounts with strong MFA.

• Federation first: Prefer IdP-centric enforcement; if not possible, enable MFA in-app.

• Zero-Trust alignment: Pair strong MFA with device and context checks (aligned with government playbooks).

Architecture patterns that satisfy CE (and reduce risk)

• IdP-centric (recommended): Enforce either FIDO2/WebAuthn or WWPass at your IdP (e.g., Azure AD/Entra, Okta, Ping) and federate apps via SAML/OIDC.

• Non-federated SaaS: Turn on the strongest available MFA in each service (FIDO2 where supported; WWPass SSO gateway where appropriate) and capture evidence.

• Remote access & admin consoles: Treat VPN/RDP/VDI as internet-exposed; prefer phishing-resistant methods.

Implementation guide (weeks 1-10)

Buyer's checklist (for RFPs/vendors)

• Supports phishing-resistant MFA: FIDO2/WebAuthn and/or WWPass.

• Federation: SAML/OIDC with passkey or WWPass integrations.

• Recovery & resilience: Multiple authenticators per user; documented break-glass. (WWPass Key recovery process is app-guided.)

• Zero-Trust signals: Device and context aware policies.

• Shared responsibility: Clarify MFA enforcement for SaaS.

Policy language you can copy

MFA Requirement: All cloud services, administrator accounts, and internet-exposed systems must enforce multi-factor authentication. The organisation prefers phishing-resistant methods and will implement either FIDO2/WebAuthn passkeys or WWPass where supported. SMS/email OTP may be used only as a documented fallback with compensating controls.

FAQs

Does Cyber Essentials mandate phishing-resistant MFA?
CE mandates MFA and advises stronger methods than SMS when alternatives are available. You can meet this using FIDO2/WebAuthn or WWPass.

Is FIDO2 the only "right" answer?
No. NCSC recommends FIDO2 highly, but CE's goal is robust MFA. WWPass achieves passwordless, phishing-resistant outcomes via a different UX and crypto flow. Many estates benefit from running both.

What if some users can't use security keys?
Use platform passkeys (Windows Hello, Touch ID) or deploy WWPass Key on managed mobiles; both avoid SMS.

How does WWPass recover if a phone is lost?
WWPass provides an app-driven recovery using the email set during setup plus the user's WWPass Key PIN, streamlining business continuity.