Skip to main content

Glossary

This glossary provides public, non-secret definitions used across the UbID Documentation Center. Product and protocol pages provide additional context.

Identity and participants

TermPublic meaning
AccountA service relationship used to manage access, preferences, devices, or operations; it is not the complete digital identity of a person.
SubjectPerson, organization, device, or entity described by credential claims.
HolderParticipant that controls receipt and presentation of a credential; the holder and subject can be different.
IssuerOrganization accountable for validating and signing the claims in a credential.
VerifierParticipant that checks presented evidence under an approved verification policy.
Relying partyOrganization or service that uses the verification result to make its own decision.
Proofing providerService that produces identity, document, biometric, or other evidence used by an issuer or policy.
CustodianParticipant entrusted with a bounded custody or recovery responsibility.
ControllerParty that determines the purposes and means of personal-data processing under applicable law.
ProcessorParty that processes personal data on documented instructions from a controller.
Digital identityA managed set of identifiers, credentials, keys, devices, relationships, and policies used to represent an entity digitally.
IdentifierValue used to distinguish or reference an entity within a defined context.
Scoped identifierIdentifier limited to a relying party, purpose, relationship, or context to reduce correlation.

Credentials and evidence

TermPublic meaning
ClaimA statement about a subject, such as a qualification, role, or attribute.
CredentialA set of claims and associated metadata issued by an accountable authority.
Verifiable Credential (VC)Tamper-evident claims whose issuer and integrity can be cryptographically verified.
SD-JWTIETF mechanism for selective disclosure of claims in a signed JSON Web Token.
SD-JWT VCCredential profile that applies SD-JWT to verifiable credential use cases; its exact specification version must be declared.
DisclosureClaim or disclosure element intentionally released for one presentation.
Selective disclosureHolder-controlled presentation of only the claims required for a transaction.
Derived claimFact computed or asserted from source data, such as an age threshold result, without disclosing every source value.
PresentationPackage of credential-derived evidence delivered to a verifier for a defined purpose.
Holder bindingCryptographic or policy relationship showing that the presenter is authorized to use a credential.
Credential statusIssuer-controlled indication used to evaluate suspension, revocation, or another lifecycle state.
SchemaVersioned definition of claim names, types, constraints, and semantics.
EvidenceReviewable record of observations, authorization, policy, and outcome without unnecessary secret or personal content.
Evidence chainLinked artifacts or references that make an operation and its decision path independently reviewable.
AssuranceConfidence supported by defined evidence, process, controls, and review.

Identifiers, protocols, and access

TermPublic meaning
DIDDecentralized Identifier resolved through a DID method to verification or service material.
DID documentResolved data describing verification methods, services, or relationships for a DID.
DID methodRules for creating, resolving, updating, and deactivating a class of DIDs.
DIDCommIdentity-bound encrypted messaging for authorized agents and services.
OpenID4VCIOpenID protocol for offering and issuing credentials to compatible wallets.
OpenID4VPOpenID protocol for requesting and presenting credentials or proofs.
DCQLQuery language used by OpenID4VP to express credential and claim requirements.
OpenID Connect (OIDC)Identity layer used to establish authenticated sessions; it is not a verifiable-credential format.
OAuth 2.0Authorization framework for delegated API access; it does not itself prove credential truth.
WebAuthnW3C API for public-key credentials, including passkeys and hardware authenticators.
PasskeyPhishing-resistant public-key credential used for authentication, often synchronized or device-bound.
MCPModel Context Protocol for controlled discovery and invocation of resources, prompts, and tools by AI-enabled applications.
Trust APIGoverned interface exposing bounded trust capabilities without granting access to internal data stores or unrestricted cryptographic material.

Cryptography and security

TermPublic meaning
Private keySecret cryptographic value used to sign, decrypt, or prove control; it must not be published.
Public keyCryptographic value that can be distributed to verify signatures or establish protected exchanges.
KIDKey identifier binding a cryptographic operation to a named key and version.
KMSKey management service governing creation, protection, use, rotation, and retirement of institutional keys.
HSMHardware security module designed to protect and perform operations with cryptographic keys.
TEETrusted execution environment that can isolate sensitive computation and produce attestation evidence.
AttestationEvidence about the identity and measured state of hardware, software, or a protected environment.
Zero TrustSecurity model requiring explicit verification and least privilege at each access and service boundary.
Defense in depthMultiple independent controls so that failure of one layer does not become complete compromise.
NonceOne-time or freshness value used to reduce replay and bind an operation to a challenge.
AudienceIntended recipient or verifier to which a token, proof, or presentation is bound.
Replay attackReuse of a previously valid message, token, challenge, or presentation in an unauthorized context.
Crypto-agilityAbility to change algorithms, key sizes, providers, and formats under controlled migration.
Post-quantum cryptography (PQC)Cryptographic algorithms designed to resist known attacks from sufficiently capable quantum computers.
Hybrid cryptographyCombination of classical and post-quantum mechanisms so security does not depend on one family during migration.

Privacy, lifecycle, and governance

TermPublic meaning
Data minimisationCollecting, disclosing, processing, and retaining only what is necessary for a declared purpose.
Purpose limitationRestricting data use to specified, legitimate, and compatible purposes.
Privacy by designEmbedding privacy objectives and controls into architecture, defaults, lifecycle, and operations.
ConsentOne possible legal basis or authorization mechanism; it is not universally valid or required for every processing activity.
RetentionApproved period and conditions for keeping a defined data class.
RevocationIssuer or authority action indicating that a credential or authorization should no longer be accepted under policy.
SuspensionTemporary lifecycle state pending review, correction, or another event.
RecoveryGoverned process for restoring legitimate identity or wallet access without creating a universal administrator secret.
Threshold recoveryRecovery requiring an approved subset of independent shares, custodians, or authorizations.
Jurisdiction profileVersioned policy overlay translating local legal, sector, role, and purpose requirements into controls.
Trust policyRules defining acceptable issuers, credentials, formats, algorithms, status, disclosure, assurance, and context.
Policy versionImmutable identifier for the exact rules evaluated for a historical decision.
Human reviewAuthorized assessment of an indeterminate, disputed, exceptional, or consequential result.
CertificationFormal status issued under a recognized scheme for a defined scope and validity period.
Conformity assessmentEvaluation of a product, service, or process against specified requirements.
Operational accountabilityAbility to explain who acted, under which policy, with what evidence, and what outcome occurred.