Identity Verification In the Digital World | Blog | Vouched

KBA, Document Uploads, and MFA Are Living in the Past

Written by Vouched Team | Nov 19, 2026, 4:00:00 PM

Verify the person, not what an attacker can get

Most health systems verify identity at registration, portal enrollment, and account recovery with some mix of three methods: knowledge-based questions, document uploads, and one-time codes. Each was built for a world where personal details were private, documents were hard to fake, and a code sent to a phone reached only its owner. Breaches, generative AI, and real-time phishing have broken each of those assumptions.

Knowledge-based questions test what a caller can look up

Knowledge-based verification asks a person to prove who they are by answering questions about themselves: a date of birth, an address, the last four digits of a Social Security number. Breaches have put those answers in other people’s data files.

The HHS HC3 alert on help desk social engineering, published April 3, 2024, shows what that looks like in practice. Callers passed identity checks by supplying the last four digits of an employee’s Social Security number and a corporate ID number. The American Hospital Association warned about the same scheme in January 2024.

NIST has taken this position for years. Its 2022 FAQ on SP 800-63 says knowledge-based verification cannot satisfy the verification requirements for identity assurance level 2 or 3 in identity proofing. The final SP 800-63A-4, published in July 2025, states it outright: knowledge-based verification and knowledge-based authentication shall not be used for identity verification. The one exception is a fraud management program, where a credential service provider may use knowledge-based verification as one signal. Revision 4 puts a long-running position into plain words.

A file in an upload field is not proof of a document

Many registration and enrollment flows ask the person to upload a photo of a driver’s license or an insurance card. An upload shows that someone submitted an image. It doesn’t show that the person holds the document. Generative tools can now create or alter document images, and a photo of someone else’s real document is just another file.

A meaningful check has to answer two questions: is the document real, and is the person presenting it the person on it?

One-time codes can be relayed in real time

A code or push prompt proves that someone with the phone approved a request. It doesn’t prove the request came from the right place. A lookalike login page can ask for the code and pass it to the real site at the same moment, so the code works for the attacker.

Health systems have seen how convincing lookalike messages can be. By Aug. 24, more than a dozen U.S. health systems had warned patients about fake MyChart emails, Healthcare Dive reported, and Becker’s Health IT covered the “Medicare kit” version of the scam. On the workforce side, a Health-ISAC report from August 24, 2026 described a caller posing as internal security staff who sent employees to a lookalike single sign-on page. One employee entered credentials and approved an MFA push. Health-ISAC noted that attackers regularly bypass standard MFA by pairing phone-led contact with reverse-proxy phishing kits. In that case, device-trust controls stopped the attacker from going further, a reminder that no single control carries the load.

Verify the live person against a validated document

Each of these methods checks something an attacker can get: an answer, a file, or a code. A stronger check asks for something an attacker can’t hand over, which is the live person at the moment of the request.

In practice, the person gets a link by text or email, holds a government ID up to their phone’s camera, and takes a selfie. Vouched’s visual identity verification checks that the document is real and that the face in the selfie belongs to a live person who matches the document photo. Because the check happens at the moment of the action, it doesn’t depend on a secret the user could be tricked into sharing.

None of this requires ripping out what health systems already run. Knowledge-based checks can stay as one fraud signal, as NIST allows, and codes can stay as a second factor. The live check goes on top at the points where the stakes are highest: registration, portal enrollment, and account recovery. For health systems on Epic, Vouched works inside MyChart at account creation and recovery, and Vouched’s medical identity verification solutions cover other registration points.

Vouched holds Ready to Operate approval from the Kantara Initiative for NIST 800-63A IAL2. The assessment covers document verification, biometric matching, liveness detection, and fraud controls.

Move past the old checks

Vouched verifies the live person at registration, portal enrollment, and account recovery, with no secrets to steal or codes to relay. Talk to our team to see it in action, or see how Vouched supports health systems.