Document-based identity proofing becomes harder because eIDAS 2.0 pushes higher assurance, stronger fraud resistance, and better linkage between the presented document and the real person. Teams must handle document authenticity, liveness, cross-channel consistency, and evidence retention, rather than relying on a scanned ID and manual review alone.
Why document-based proofing becomes harder under eIDAS 2.0
eIDAS 2.0 raises the assurance bar, so a copied document and a manual visual check are no longer enough on their own. The proofing flow has to show that the document is genuine, that the presenter is physically present and live, and that the evidence from capture, review, and later audit all line up with the claimed person.
That shift changes document proofing from a lightweight onboarding step into a higher-integrity control with fraud resistance, evidence quality, and cross-channel consistency baked in. It also means teams need stronger controls for tamper detection, replay resistance, and retention of proofing evidence that can stand up to challenge later.
What changes in the proofing workflow
Under older document-centric models, organisations often relied on one scanned ID, a selfie, and a manual reviewer. Under eIDAS 2.0, the workflow has to support stronger binding between the identity document, the person presenting it, and the transaction context. That makes the process more sensitive to camera quality, metadata integrity, document template validation, and whether the same person is consistently present across steps.
The practical consequence is that proofing can no longer be treated as a single verification event. It becomes a sequence of checks where failure in any one stage, document authenticity, liveliness, face match, or evidence integrity, can undermine the whole identity assertion. For that reason, teams should treat the proofing process as a controlled chain rather than a one-off approval.
Why fraud resistance and evidence quality matter more
Higher assurance means the organisation must assume a more capable adversary. Fraudsters can combine forged documents, synthetic identities, injected video, replayed images, or coerced manual review to bypass weak onboarding. Identity proofing and KYC controls therefore need to be designed around document authenticity, liveness detection, and presentation attack resistance, not just identity data capture.
eIDAS 2.0 also makes evidence handling more important. If an identity decision is later challenged, organisations need to show what was checked, when it was checked, what the system accepted or rejected, and how the record was protected from alteration. That is why auditability and secure retention are now part of the proofing requirement, not a separate back-office concern. Remote video identification is a useful example of why session evidence, operator rules, and injection risk must be documented, not assumed.
Where teams usually need to tighten controls
Most organisations need to harden three areas at once: document capture, biometric or face comparison, and post-decision evidence retention. If any one of those is weak, the overall assurance level drops. The result is often a mismatch between policy language and actual operating practice, especially when teams still allow manual overrides, inconsistent reviewer judgement, or incomplete logging.
That is also why the operational boundary between identity proofing and later account recovery matters. A weak initial proofing step can create downstream risk in wallet enrolment, trust service registration, or high-value account access. NIST SP 800-63A-4 identity proofing is a useful comparator for the kinds of evidence, verification pathways, and fraud controls teams now have to think about when stronger assurance is required.
Risk and Threat Considerations
As assurance rises, the main risk is not just more work, it is false confidence from controls that look strong but do not actually bind the document to the live person. Attackers benefit when organisations accept weak scans, tolerate replayed media, or cannot prove what was checked at the time of enrolment.
Failure mechanism: Document fraud, injection attacks, and inconsistent review practices can let a bad identity pass initial onboarding while leaving little reliable evidence to reconstruct the decision later.
Impact: The organisation may issue high-trust credentials or accept a false identity into a regulated workflow, creating downstream fraud, compliance exposure, and difficult-to-contest assurance failures.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
NIST SP 800-63 and NIST SP 800-53 Rev 5 set the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST SP 800-63 | IAL2 — Identity Assurance Level 2 | Higher-assurance proofing is central to the question. |
| IAL3 — Identity Assurance Level 3 | Stronger fraud resistance and live-person proofing align to elevated assurance. | |
| Recommendation — Use IAL2-style evidence and verification paths when document proofing must bind the person to the identity. Apply IAL3-grade controls when the enrolment must resist advanced impersonation and document fraud. | ||
| NIST SP 800-53 Rev 5 | IA-12 — Identity Proofing | The subject is explicitly about proofing evidence and identity assertion quality. |
| AU-11 — Audit Record Retention | The answer depends on keeping proofing evidence available for later challenge. | |
| IA-5 — Authenticator Management | Proofing outcomes often lead to credential issuance and lifecycle control. | |
| Recommendation — Require documented proofing evidence and validation steps before issuing high-trust identity assertions. Retain proofing records long enough to reconstruct the decision and support audit or dispute handling. Rotate or revoke credentials promptly when proofing evidence or enrolment integrity is in doubt. | ||
Practitioner Guidance
What to verify: Validate that your process proves three things separately: the document is authentic, the presenter is live and present, and the record of the decision is tamper-evident. If those are blended into one generic approval step, the control is usually weaker than the policy claims.
Decision rule: If your proofing flow cannot demonstrate document authenticity and liveness under challenge, treat it as insufficient for higher-assurance enrolment even if manual reviewers are involved. Human review is helpful, but it is not a substitute for traceable evidence and fraud-resistant capture.
Practitioner takeaway: Under eIDAS 2.0, document proofing is judged by how well it resists fraud and how well it can defend the identity decision later, not by how quickly a document can be scanned and approved.
Related resources from NHI Mgmt Group
- Guide: Digital Identity, eID and Identity Wallets Guide
- eIDAS 2.0
- Why does document-based KYC become less effective under digital identity frameworks?
- When should organisations require document-based identity proofing?
- Why do identity-based attacks become harder to contain when organisations rely on legacy access controls?
Deepen Your Knowledge
Free weekly newsletter
Subscribe to the NHI & AI Identity Journal
The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.
Bonus 33% off our NHI Course when you subscribe.
Reviewed and updated by the NHIMG editorial team on November 9, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org