Phishing-resistant authentication and digital identity rules: outlook to 2027
NIST now defines phishing resistance and admits synced passkeys at AAL2, federal agencies must use it for their own people, New York demands MFA everywhere, and mobile driver's licenses run on a temporary federal waiver.
The question for 2027
US authentication rules now run on two tracks. Federal agencies are told to use phishing-resistant authentication for their own people, and NIST's fourth revision of its digital identity guidelines defines what that means, including where synced passkeys fit. Banks, insurers and health systems mostly answer to rules that require multi-factor authentication of some kind and leave its strength to the regulator's judgment. Alongside both, mobile driver's licenses have reached airport checkpoints under a temporary federal waiver. This outlook sets out where each strand stands as checked on November 16, 2026.
NIST SP 800-63-4: the technical baseline
NIST published SP 800-63-4, Digital Identity Guidelines, in final form on July 31, 2025, after drafts dated June 8, 2020, December 16, 2022 and August 21, 2024; it supersedes SP 800-63-3 [1]. A planning note dated October 6, 2026 says an implementation resource hub for it is now available [1]. The guidelines bind federal agencies; private-sector organizations and state, local and tribal governments may consider using them where appropriate [2].
The authentication volume, SP 800-63B-4, makes phishing resistance a defined term: the protocol must keep secrets and authenticator outputs from an impostor verifier without relying on the vigilance of the user, and authenticators that involve manual entry of an output, such as one-time codes and out-of-band codes, shall not be considered phishing-resistant [3]. At AAL2, verifiers shall offer at least one phishing-resistant option, and federal agencies shall require their staff, contractors and partners to use phishing-resistant authentication to reach federal information systems [3]. At AAL3 the authenticator shall have a non-exportable private key and provide phishing resistance [3].
Syncable authenticators, the cloud-synced credentials usually sold as passkeys, get their own normative appendix [3]. It says that “since syncable authenticators … require the private key to be exportable, syncable authenticators SHALL NOT be used at AAL3,” and that “authentication at AAL2 may be supported subject to the above requirements,” which include storing synced keys only in encrypted form and protecting access to the sync fabric with AAL2-equivalent MFA [3]. For federal enterprise use it adds that sync fabrics must have FISMA moderate protections or equivalent and that devices holding federal enterprise keys be protected by device management or configuration controls “that prevent the syncing or sharing of keys to unauthorized devices or sync fabrics”; it also sets out the WebAuthn flags federal agencies should check when building syncable authenticator implementations to align with AAL2 [3]. Password rules changed too: a password used as the only factor must be at least 15 characters, one used inside multi-factor authentication at least eight, and verifiers shall not impose composition rules or require periodic changes [3]. The identity proofing volume, SP 800-63A-4, lists a mobile driver's license as an example of digital identity evidence [4].
Moraph's view
Moraph's view: the syncable-authenticator appendix is the most consequential change for organizations outside government. It gives a federal yardstick under which a consumer passkey can count at AAL2, which removes the main argument for keeping one-time codes as the strongest option offered to customers. Examiners who read NIST will start asking why a phishable method is still the default.
Federal agencies: M-22-09 still stands, and sign-in moves to Login.gov
OMB's M-22-09, issued January 26, 2022, set agencies to meet its zero trust standards by the end of fiscal year 2024 [5]. It requires phishing-resistant multi-factor authentication for agency staff, contractors and partners, requires that it be an option for public users, and bars password policies that demand special characters or regular rotation [5]. Public-facing systems that support multi-factor authentication had to offer a phishing-resistant option within one year of the memo; it names PIV and the W3C Web Authentication standard as phishing-resistant approaches, and says that for the general public this will mean supporting Web Authentication-based approaches such as security keys [5].
As checked on November 16, 2026, OMB's current memoranda page lists memoranda from M-25-10 through M-27-01 of October 23, 2026, and none of their titles rescinds M-22-09 [6]. M-26-18, dated August 31, 2026, says agencies should follow applicable law and existing OMB policy to manage digital identity, naming M-22-09 among that policy [7]. The phishing-resistant requirement for the federal workforce therefore remains in force.
M-26-18 shifts attention to the public. Its appendix of actions and deadlines tells agencies to report an inventory of public-facing websites that have authentication “within 60 days,” to conduct a digital identity risk management process consistent with SP 800-63-4 “within 240 days,” deploy Login.gov on in-scope sites of High Impact Service Providers within one year, and on all in-scope sites within two years, or send OMB a notice [7]. NIST is to publish a resource for that risk process within 120 days, and GSA is to report within 180 days on digital identity opportunities such as verifiable digital credentials [7]. The memo is dated August 31, 2026 and states these deadlines only as periods; it gives no calendar dates for them [7].
CISA's guidance gives the same direction to everyone else. Its October 2022 fact sheet calls phishing-resistant MFA the gold standard, ranks FIDO/WebAuthn and PKI-based methods strongest, and says the only widely available phishing-resistant authentication is FIDO/WebAuthn [8].
Banks: FFIEC guidance and New York's Part 500
The FFIEC members issued Authentication and Access to Financial Institution Services and Systems on August 11, 2021, replacing the 2005 internet banking guidance and its 2011 supplement [10] [11]. It covers employees, board members, third parties and customers, and applies to community banks [10]. Its test is risk-based: where single-factor authentication with layered security is inadequate, MFA or controls of equivalent strength can more effectively mitigate risk, and institutions should identify high-risk users such as privileged users, remote users and senior management [9]. It names phishing as a common threat but does not use the term phishing-resistant, and it states that it does not impose any new regulatory requirements [9]. As checked, neither the OCC's bulletin page nor the Federal Reserve's SR 21-14 page carries a notice that the guidance has been rescinded [10] [11].
New York sets a harder line for the banks, insurers and other licensees it regulates. Section 500.12 requires MFA for any individual accessing any information system of a covered entity; entities with a limited exemption need it for remote access, remote access to third-party applications holding nonpublic information, and privileged accounts [12]. A CISO may approve reasonably equivalent or more secure compensating controls in writing, reviewed at least annually [12]. The Department's July 2025 summary says the universal requirement applies starting November 1, 2025 [13].
The Department's FAQs do not mandate a type of MFA, but they set a strength test: a possession factor commonly involves cryptographic proof of possession, a remember-this-device cookie does not qualify, and software certificates that can be exported qualify only as part of compensating controls [14]. They also say push-based MFA is not phishing-resistant and should use number matching and limits on retries [14]. A February 26, 2026 training listed common themes in MFA examinations, including incomplete coverage, privileged access exceptions and gaps in authentication and session control [15]. The Department regulates over 3,000 financial institutions [15].
Moraph's view
Moraph's view: the FFIEC text is five years old and written for a world before passkeys; we do not expect the federal agencies to rewrite it while they are trimming guidance elsewhere. New York is where bank authentication will actually be tested in 2027. Its FAQ already reads like a phishing-resistance standard without the label, and the first examination cycle after November 2025 is the likeliest source of findings and orders that name section 500.12.
Health systems: MFA waits on the HIPAA Security Rule
OCR's proposed Security Rule update, published January 6, 2025, would add multi-factor authentication as a new defined term [16]. It would require MFA for all technology assets in relevant electronic information systems and for any action that changes a user's privileges, with exceptions including assets that cannot support it under a written migration plan and for emergencies [16]. Its discussion cites CISA's phishing-resistant MFA fact sheet, but the proposed text defines MFA by the three factor categories, not by phishing resistance [16].
As checked on November 16, 2026, the Federal Register lists only the proposed rule under RIN 0945-AA22 [17]. The 2026 Unified Agenda places it among long-term actions and shows final action for July 2027 [18]. Our healthcare cybersecurity outlook expects no final rule by July 31, 2027.
Mobile driver's licenses and REAL ID
REAL ID enforcement began on May 7, 2025 [21]. A DHS final rule of October 25, 2024, effective November 25, 2024, lets TSA waive, temporarily and state by state, the requirement that mobile driver's licenses be REAL ID-compliant before federal agencies accept them [19]. Each waiver is valid for 3 years from issuance, and federal agencies accepting mDLs must use a reader to retrieve and validate mDL data following ISO/IEC 18013-5 [19]. The rule calls itself Phase 1, a bridge until a Phase 2 rulemaking repeals the waiver provisions and sets full requirements [19]. TSA put the rule's 10-year cost at $829.8 million undiscounted, and noted that 10 states provided mDLs as of December 2023 [19].
As listed by TSA on November 16, 2026, 24 jurisdictions have mDLs approved for federal use: 22 states plus Puerto Rico and the District of Columbia [21]. The same page says Utah's mDL will no longer be accepted by TSA from January 1, 2027 and West Virginia's from May 4, 2027 [21]. TSA says digital IDs work at more than 250 of its checkpoints [22]. A Federal Register search finds no Phase 2 proposal [23]. A separate January 2025 rule lets agencies phase in card-based REAL ID enforcement but requires full enforcement by May 5, 2027 [20].
Moraph's view
Moraph's view: mDLs will matter to banks and health systems first as identity evidence in remote account opening and patient portals, because NIST already treats them that way, not because any financial or health rule requires them. The federal waiver list is the signal to track. A list that shrinks as early waivers lapse would slow acceptance by private relying parties; a Phase 2 proposal would be the moment to plan reader and verification work.
What to watch in 2027
- M-26-18's “within 240 days” step: agencies' SP 800-63-4 risk management processes for public-facing services; the memo, dated August 31, 2026, gives the period but no calendar date [7].
- May 5, 2027: full card-based REAL ID enforcement by federal agencies [20].
- July 2027: the agenda date for a final HIPAA Security Rule [18].
- New York consent orders citing section 500.12, now that the universal requirement is in force [13].
- Any FFIEC or agency action on the 2021 authentication guidance, and changes to TSA's waiver list [10] [21].
Data and method
Two figures here are counted by us. The M-26-18 deadlines are given only as the memo states them, as periods (“within 240 days”), with the memo's own date of August 31, 2026; we do not convert them to calendar dates [7]. The count of 24 jurisdictions is the number of names in the list headed "mDLs Approved for Federal Use" on TSA's REAL ID mDL page as opened on November 16, 2026, counting Puerto Rico and Washington, D.C. once each and Utah and West Virginia as still listed [21]. The count of 22 states is that list less Puerto Rico and the District of Columbia [21]. Statuses are as checked on November 16, 2026.
What this means for you
- Federal agencies: Plan to finish the M-26-18 inventory and SP 800-63-4 risk process on the memo's clock, including the 240-day step [7], and check that any passkey offering for staff meets the AAL2 syncable-authenticator conditions, since synced keys are barred at AAL3 [3].
- Banks and insurers in New York: Map every MFA exception against section 500.12 and the CISO-approved compensating controls it allows [12]; the Department's FAQs single out remember-device cookies, exportable certificates and unprotected push prompts [14].
- Banks outside New York: Expect examiners to keep using the 2021 FFIEC guidance's high-risk-user and layered-security tests [9]; CISA's fact sheet is the clearest official statement of which methods resist phishing [8].
- Health systems: Treat MFA as a likely requirement but not yet a rule: the proposal would require it across relevant systems and for privilege changes [16], and no final rule had been published as checked [17].
- Identity verification teams: Track TSA's waiver list before relying on any state's mDL [21]; NIST already counts a mobile driver's license as digital identity evidence [4].
Moraph predictions
Every prediction is Moraph's view, not a fact. Each has a date, a confidence level (70% means we expect to be wrong about three times in ten) and a test anyone can apply. We score them on this page when the date comes and never remove one. How we make and score predictions.
P1 By Confidence 70% Open
The New York State Department of Financial Services publishes at least one consent order, dated in 2027, that finds a violation of 23 NYCRR 500.12.
How we will check: A consent order on the Department's website dated between January 1 and December 31, 2027 that cites a violation of section 500.12.
Basis: Section 500.12 requires MFA for any individual accessing any information system [12], a requirement in force since November 1, 2025 [13]; the Department lists incomplete MFA coverage and privileged access exceptions among common examination themes [15].
P2 By Confidence 65% Open
DHS or TSA does not publish a Phase 2 proposed rule on REAL ID mobile driver's licenses in the Federal Register.
How we will check: No proposed rule published in the Federal Register on or before December 31, 2027 that would replace the mDL waiver provisions of the October 2024 final rule with permanent requirements.
Basis: The October 2024 rule describes itself as Phase 1 and anticipates a later Phase 2 rulemaking [19]; as checked on November 16, 2026, the Federal Register shows no Phase 2 document [23].
P3 By Confidence 55% Open
TSA's list of mDLs approved for federal use names at least 25 jurisdictions.
How we will check: The count of states, territories and the District of Columbia listed under "mDLs Approved for Federal Use" on TSA's REAL ID mDL page, as shown on December 31, 2027 (or in the last Internet Archive capture of that page on or before that date), is 25 or more.
Basis: As listed by TSA on November 16, 2026, 24 jurisdictions were approved, and TSA said it would no longer accept the Utah and West Virginia mDLs from dates in 2027 [21]; 10 states provided mDLs as of December 2023 [19].
P4 By Confidence 75% Open
The 2021 FFIEC authentication and access guidance is neither rescinded nor replaced.
How we will check: No OCC bulletin, Federal Reserve SR letter, FDIC financial institution letter or FFIEC release dated on or before December 31, 2027 rescinds or replaces Authentication and Access to Financial Institution Services and Systems.
Basis: The guidance was issued August 11, 2021 and, as checked, carries no rescission notice on the OCC or Federal Reserve pages [10] [11]; it states that it imposes no new regulatory requirements [9].
P5 By Confidence 80% Open
OMB does not rescind M-22-09's requirement of phishing-resistant MFA for agency staff, contractors and partners.
How we will check: No OMB memorandum dated on or before December 31, 2027 rescinds M-22-09 or removes its phishing-resistant MFA requirement for agency users.
Basis: M-26-18 of August 31, 2026 names M-22-09 as existing OMB policy agencies should follow [7], and SP 800-63B-4 itself requires federal agencies to use phishing-resistant authentication for staff, contractors and partners [3].
Facts on this page link to their sources. Text marked "Moraph's view", and every prediction, is our own analysis, not a fact or advice. Methodology.
Spotted an error? Tell us and we will check it and correct the piece where needed.