A self-derived digital travel credential is created by the holder from an existing ePassport and is used with the passport still needed at least once for border use. An authority-issued credential is generated and issued directly by the state, with the passport serving as reference or replaced by a paperless model. The difference is primarily in issuance control and reliance on the physical document.
How the two credentials differ in who creates them
The key difference is issuance authority. A self-derived digital travel credential is created by the traveller from an existing ePassport and usually depends on the passport at least once for border use. An authority-issued credential is produced directly by the state, so the issuing authority controls the credential lifecycle from the start.
That distinction matters because it changes who can bind the credential to the underlying identity, what trust steps are required, and whether the credential is a derivative of an existing passport record or a separate state-issued document. In practice, the issuance model is part of the security model, not just an administrative detail.
A useful way to think about it is that self-derived credential lean on a pre-existing trusted document, while authority-issued credentials create trust through the issuer's own process and records. That affects how issuance, revocation, and replacement are handled, especially when the credential is meant to work in more than one border context.
Why the passport's role changes the trust model
In a self-derived model, the physical ePassport remains part of the trust chain, at least initially. The digital credential is effectively a companion to the passport rather than a full replacement, which means the holder still needs the passport for verification or fallback in some journeys.
An authority-issued model can reduce dependence on the physical booklet because the state is issuing the digital credential itself. That is why these products are often described as more paperless: the document no longer has to originate from the traveller's own extraction of passport data, and the border authority can rely on its own issuance process.
From a practitioner perspective, the operational question is not simply whether the credential is digital, but whether it is a dependent representation or a separately issued artefact. That difference drives how much confidence the border system has in the credential alone, and how much it still expects the passport to remain in play.
What this means for lifecycle, recovery, and adoption
The lifecycle is shorter and more constrained for self-derived credentials because they inherit the scope and limitations of the source passport. If the passport changes, is renewed, or is lost, the derived credential may need re-issuance or may lose usefulness faster than an authority-issued model.
Authority-issued credentials shift more lifecycle responsibility to the issuer. That usually gives the state better control over expiry, revocation, and replacement, but it also increases the burden on the issuing process and the supporting identity records.
If you are comparing the two for deployment, the practical test is whether the system needs a low-friction bridge from an existing passport or a more durable state-controlled digital document. Self-derived credentials are usually easier to introduce incrementally; authority-issued credentials are stronger when the goal is to make the digital credential stand on its own.
Risk and Threat Considerations
The main risk difference is trust concentration. Self-derived credentials can inherit weaknesses from the source passport and from the process used to derive the digital form, while authority-issued credentials concentrate risk in the issuer's enrollment, issuance, and revocation systems.
Failure mechanism: If the passport source data, derivation process, or issuer-side records are weak, an attacker may exploit inconsistencies between the physical document and the digital credential, or abuse gaps in revocation and replacement handling.
Impact: The result can be identity confusion, unauthorized travel credential use, slower incident response, or a border-control failure where the system cannot confidently distinguish a valid credential from a compromised or stale one.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
OWASP API Security Top 10 addresses the attack surface, NIST SP 800-53 Rev 5 and NIST SP 800-63 set the technical controls, and ISO/IEC 27001:2022 defines the regulatory obligations.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST SP 800-53 Rev 5 | IA-8 — Identification and Authentication (Non-Organizational Users) | Border travel credentials depend on proving an external person's identity. |
| IA-12 — Identity Proofing | The issuance model hinges on how the traveller's identity is established. | |
| Recommendation — Require strong proofing and authentication for issuance and use. Tie credential issuance to verified identity proofing evidence. | ||
| ISO/IEC 27001:2022 | A.5.16 — Identity management | The question turns on how identities are registered and issued. |
| Recommendation — Define who may create, issue, and revoke travel identities. | ||
| OWASP API Security Top 10 | API2 — Broken Authentication | Digital travel credential use depends on reliable authentication and token validation. |
| Recommendation — Validate credential authenticity and reject weak or stale authentication tokens. | ||
| NIST SP 800-63 | IAL — Identity Assurance Level | The comparison hinges on how much assurance each issuance model provides. |
| Recommendation — Match issuance rigor to the assurance level required for border use. | ||
Practitioner Guidance
What to verify: Check whether the credential can be independently validated, how often it must fall back to the physical passport, and what happens when the passport is renewed or revoked. Those three questions tell you whether the model is truly digital or only digitally assisted.
Decision rule: If your objective is faster adoption with minimal issuer infrastructure, a self-derived model is usually the lower-friction path. If your objective is stronger issuer control and a paperless border journey, an authority-issued model is the better fit, provided the revocation and lifecycle processes are mature.
Practitioner takeaway: The real distinction is not format, it is control, a self-derived credential inherits trust from an existing passport, while an authority-issued one shifts trust and lifecycle responsibility to the state.
Related resources from NHI Mgmt Group
- What is the difference between a biometric passport and a Digital Travel Credential?
- What is the difference between a self-assessment framework and one that requires external certification?
- What is the difference between an API that is undocumented and one that is self-documenting?
- What is the difference between a least privilege named credential and one configured for broad tenant access?
Deepen Your Knowledge
Reviewed and updated by the NHIMG editorial team on September 29, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org
