By NHI Mgmt Group Editorial TeamBased on Yoti: “The hidden risks of carrying your physical ID” (September 10, 2025)

TL;DR: Physical IDs expose full identity data, are hard to revoke when lost, and can be misused without visibility or accountability, according to Yoti. The governance shift is toward selective disclosure, consent, and device-bound verification, not broader data collection.


At a glance

What this is: Yoti argues that physical identity documents create avoidable privacy and misuse risk because they reveal too much, are hard to revoke, and provide little visibility once handed over.

Why it matters: For IAM and identity verification teams, the issue is not just convenience but governance: identity checks should minimise data exposure, improve consent, and make misuse easier to prevent and trace.


Context

Physical identity documents still work as broad, all-or-nothing proof of who someone is, but that model conflicts with modern identity governance. A single card or passport can expose far more data than a venue, retailer, or employer actually needs, and once it is shown there is little control over copying, retention, or reuse.

This matters across identity verification, access control, and privacy programmes because the operational problem is not just lost documents. It is the absence of selective disclosure, traceability, and revocation once a physical credential leaves the holder's control. In that sense, the article is about moving identity proofing toward a more governed disclosure model rather than collecting more identity data.


Key questions

Q: How should teams prevent oversharing in identity verification workflows?

A: Start by defining a minimum disclosure contract for each workflow and require the presenter to preview the exact fields before release. Then enforce mandatory provenance markers, so verified and self-asserted attributes are not treated as equal. Finally, make sensitive fields step-up gated and keep the request single-use and time-limited.

Q: Why are physical IDs risky when they are lost or stolen?

A: Because the document itself cannot be revoked, a lost or stolen ID may still be used until the holder notices and takes action. The risk window is especially dangerous when the card contains enough personal data to support impersonation, account opening, or unauthorised access.

Q: What breaks when organisations treat physical ID as a sufficient trust signal?

A: They lose control over traceability, retention, and scope. A physical card can be copied, photographed, borrowed, or reused without logs that show who viewed it or where it was presented, which makes later investigation and accountability much weaker than with governed digital credentials.

Q: When should organisations use digital credentials instead of document capture and selfie checks?

A: Organisations should prefer digital credentials when they need higher assurance, less friction, and less data exposure than traditional document workflows. They are well suited to age checks, KYC onboarding, account recovery, and step-up authentication. The key advantage is deterministic verification from a trusted issuer, which reduces reliance on fuzzy matching, manual review, and repeated identity reproofing.


Technical breakdown

Why physical identity credentials create a disclosure problem

A physical ID is a static credential that combines proof of identity with a bundle of unrelated personal data. In practice, the relying party sees everything printed on the document, even when it only needs one attribute such as age, name, or residency. That creates a disclosure problem, not just a verification problem. The broader the credential surface, the greater the privacy exposure and the harder it becomes to justify data minimisation. This is where digital credentials change the design assumption by allowing selective disclosure instead of full-document inspection.

Practical implication: Treat full-document ID checks as an oversized disclosure pattern and redesign flows to request only the attribute actually needed.

How loss and theft turn a document into a standing identity risk

Physical IDs are difficult to revoke because the document itself has no live control plane. If a wallet is lost or a card is stolen, the credential can still be used until the holder notices and acts, and even then there is no technical lock on the card itself. That makes physical IDs more like standing identity artefacts than governed credentials. The risk is not limited to the initial loss. It is the window of untraceable misuse before replacement, reporting, or downstream detection catches up.

Practical implication: Build identity checks and fraud processes around revocability and traceability, not around the assumption that a document can simply be trusted once presented.

Selective disclosure and device binding reduce identity oversharing

Digital credentials are designed to separate proof from payload. Instead of exposing a full identity record, the verifier can receive only the claim required for the transaction. When the credential is bound to a mobile device and protected by local authentication, the relying party can also reduce the chance of casual reuse or third-party handling. That matters because identity systems fail when they collect more data than the use case needs. Selective disclosure changes the governance model from broad trust in the document to narrower trust in the presentation.

Practical implication: Adopt presentation flows that support attribute-level verification and device-bound use cases where the business only needs a narrow identity claim.


NHI Mgmt Group analysis

Physical identity documents create a disclosure boundary failure, not just an authentication weakness. The core problem is that the verifier sees far more than the transaction requires, which makes data minimisation impossible in practice. That is a governance failure as much as a privacy failure, because identity proofing should validate a claim, not broadcast an entire identity record. Practitioners should treat over-disclosure as a control gap, not a user convenience tradeoff.

Revocation is the hidden weakness in physical identity governance. Once a wallet, card, or passport is out in the world, there is no live lock or usage telemetry to stop misuse. The issue is not simply that the document can be stolen, but that its legitimacy persists after control is lost. That makes physical credentials fundamentally weaker than device-bound presentation models for high-frequency identity checks. Practitioners should prioritise credential models that can be disabled, traced, and scoped.

Selective disclosure is the named concept that should replace all-or-nothing identity checks. A venue, retailer, or service should not need a full birth date, address, or identity number when it only needs a single assertion. This is where digital identity governance intersects directly with privacy engineering and identity verification. The practical conclusion is that identity teams should move from document inspection to claim verification wherever the business case permits.

Device binding changes the accountability model for identity presentation. A credential tied to a controlled device is easier to govern than a paper artefact that can be copied or passed between people. That does not eliminate fraud, but it narrows the misuse path and improves the chance of user-level consent. Identity programmes should therefore assess whether they are still relying on paper-era assumptions in digital workflows.

The article reflects a broader shift in identity assurance: prove less, know more. Mature identity governance increasingly values contextual verification, consent, and traceable presentation over large data collection. That approach aligns better with privacy regulation and modern trust expectations because it reduces the amount of sensitive data in circulation. Practitioners should treat this as a design principle for the next generation of identity checks.

What this signals

Selective disclosure should now be treated as a baseline identity design principle. Identity teams that still depend on full-document checks are accepting unnecessary exposure for routine proofing. The practical shift is to verify claims, not to warehouse personal data.

Physical documents are weak governance objects because they cannot be centrally controlled once issued. That limitation matters for onboarding, age checks, and access to physical spaces where traceability and consent are increasingly expected. Programmes that need stronger assurance should prefer presentation methods that can be bound to a device and restricted to a specific transaction.


For practitioners

  • Redesign identity checks around selective disclosure Replace full-document inspection with attribute-level verification where the business only needs age, residency, or identity confirmation.
  • Review revocation assumptions for physical and digital credentials Map where your current identity checks rely on artefacts that cannot be disabled, traced, or time-limited once they leave the holder's control.
  • Limit identity data retention after verification Define what data is kept, why it is kept, and who can access it after an ID check is complete, then remove unnecessary copies.
  • Prefer device-bound credentials for repeat checks Use credentials tied to a controlled device and user authentication when the workflow repeats often and does not require full-document capture.

Key takeaways

  • Physical IDs still function as broad disclosure artefacts, but that design exposes more personal data than many transactions require.
  • The hardest governance problem is revocation, because a lost or stolen document can keep working without traceability.
  • Selective disclosure and device-bound presentation are the controls that narrow exposure and improve identity governance.

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, NIST CSF 2.0 and NIST SP 800-53 Rev 5 set the technical controls, while GDPR defines the regulatory obligations.

FrameworkControl / ReferenceRelevance
NIST SP 800-63SP 800-63A — Enrollment and Identity ProofingThe article is about proving identity with less data and stronger assurance.
Recommendation — Use SP 800-63A to reduce proofing data to what the transaction actually requires.
GDPRArt.5 — Principles relating to processing of personal dataThe article centres on data minimisation and consent in identity checks involving personal data.
Recommendation — Apply Art.5 principles to minimise collection, retention, and disclosure during ID verification.
NIST CSF 2.0PR.AA-05 — Access Permissions, Entitlements and AuthorizationsIdentity checks here function as access decisions that should be scoped to the transaction.
Recommendation — Scope identity proofing outputs so each relying party receives only authorised attributes.
NIST SP 800-53 Rev 5IA-8 — Identification and Authentication (Non-Organizational Users)The article concerns proving and using identity for external users in digital and physical contexts.
Recommendation — Use IA-8 to govern how external identities are verified and accepted across channels.

Key terms

  • Selective Disclosure: Selective disclosure is the practice of sharing only the identity attributes needed for a specific decision. In credential-based systems, it reduces oversharing, lowers retention burden, and limits exposure when a verifier does not need the full record to make a trustworthy judgment.
  • Device-bound Credential: A device-bound credential is a key or token that can only be used from an approved device or authenticator. In practice, it reduces replay and theft risk, but it also raises the stakes of enrollment, attestation, and revocation because the credential can act repeatedly until invalidated.
  • Identity proofing: The process of verifying that a person is who they claim to be before granting or restoring access. In higher-risk recovery paths, proofing can include stronger evidence checks such as government ID validation or liveness-based facial verification so the assurance level matches the sensitivity of the request.
  • Data Minimization: Data minimization is the practice of limiting personal data collection to what is adequate, relevant, and necessary for a specific purpose. It reduces exposure by shrinking what is gathered, transferred, retained, and processed. Strong minimization depends on careful form design, purpose review, and strict collection discipline.

Deepen your knowledge

The NHI Foundation Level course, the industry's only accredited NHI security programme, covers NHI governance, machine identity security, and identity lifecycle control. It helps practitioners connect identity assurance decisions to broader security and privacy governance.
NHIMG Editorial Note
Published by the NHIMG editorial team on August 2, 2026.
Updated on October 12, 2026.
NHI Mgmt Group, the independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org