View Zero Trust Service Catalogue 1 Match IdentityVerifiable Credentials

Zero Trust Service Catalogue

UNIFY's identity-first catalogue spanning the core Zero Trust pillars.

IDENTITY

Capabilities that establish, migrate, and assure digital identities.

  • Trusted Sign-in
  • Streamlined Identity Lifecycle
  • Verifiable Credentials
  • Identity Protection
  • Migration to Entra
  • Identity Verification and Proofing
  • Application Provisioning
  • Identity SOC
ACCESS

Controls that govern how users, customers, and partners gain the right access.

  • Secure External Access
  • Organisational Identity Access Management
  • Controlled Delegation
  • Partner Identity Access Management
  • Just-In-Time Privilege
  • Adaptive Access
  • Multifactor Identification
  • Risk-Based Authentication
GOVERNANCE

Oversight capabilities that enforce policy, compliance, and least privilege.

  • Enterprise Governance
  • Controlled Delegation
  • Access Lifecycle
  • Entitlement Management
  • Data Protected
  • Access Reviews
  • Just-In-Time Privilege
  • Adaptive Access
SECURITY

Security operations services that protect, detect, and respond across identities.

  • Intelligent Threat Detection
  • Dark Web & Supply Chain Insight
  • Information Protection and Governance
  • Endpoint & Cloud Protection
  • Vulnerability Management
  • Security Operations Centre as a Service (SOCaaS)
  • Risk Management

An ecosystem is the people, technology, and rules that let credentials be issued, stored, and checked across organisations without bespoke integrations.

Separable roles
Issuer (creates), holder (carries), verifier (checks), and trust governance stay decoupled to preserve choice.
Trust registries
Accreditation and metadata allow verifiers to trust issuers without bespoke integrations.
Lifecycle control
Revocation and status signalling are essential for real-world assurance.
Interoperability
Standards + profiles + conformance create practical, vendor-neutral ecosystems.

What makes an ecosystem work

Successful VC ecosystems treat trust as a governance capability, not a platform feature. The goal is to create consistent assurance outcomes while allowing multiple issuers, verifiers, and wallet providers to participate — including access systems that need to verify proofs before granting entry.

In plain English: keep roles separate, publish who to trust, and make status/revocation work reliably.

Key principles:

  • Role separation keeps architecture adaptable and avoids lock-in.
  • Trust registries and accreditation provide consistent signals to verifiers.
  • Lifecycle management (renewal, revocation, status) drives real-world reliability.
  • Standards profiles and conformance make interoperability practical, not theoretical.

How ecosystems mature

Pilot first
Start with narrow use cases and validate usability, assurance, and lifecycle assumptions.
Federated scale
Multiple issuers and verifiers operate under a shared trust framework.
Broader participation
Extend trust to regulated partners once governance and assurance are proven.
Flexible delivery
SaaS and self-operated models can coexist under common governance.

In plain English: start small, prove trust and usability, then scale participation.


Example ecosystems

These are common patterns we see across sectors. Each can be implemented with different vendors and delivery models, provided trust and lifecycle governance are consistent.

Public sector trust framework
Multiple agencies issue identity, authority, and entitlement credentials under shared accreditation and trust registries.
Education credential network
Universities and training providers issue qualifications that employers and regulators can verify without direct integrations.
Workforce & partner access
Enterprises issue role and clearance credentials that partners present to access systems or facilities.
Supply chain provenance
Manufacturers and logistics providers issue credentialed assertions for compliance, origin, and chain-of-custody checks.

In plain English: the same ecosystem pattern shows up in government, education, workforce, and supply chain.

View all Verifiable Credentials use cases


Standards posture

W3C Verifiable Credentials
Shared data model for representing claims and proofs. W3C Verifiable Credentials Data Model
OpenID issuance & presentation
OID4VCI and OID4VP for online flows and integration with OAuth/OIDC. OpenID for Verifiable Credential Issuance (OID4VCI) · OpenID for Verifiable Presentations (OID4VP)
SD-JWT
Selective disclosure for JWT-based credentials. IETF SD-JWT VC draft
ISO mobile documents
In-person and offline credential presentation patterns. ISO/IEC 18013-5 (mobile document standard)

Why it matters: open standards make credentials portable; profiles and conformance make them actually interoperate.

Format choice should be driven by context (online vs offline, disclosure needs, device capabilities), not by vendor preference.


Operational realities

Assurance tiers
Map credential risk to appropriate assurance and controls.
Revocation & status
Tune status checks to verifier expectations and latency needs.
Wallet policy
Balance user trust with ecosystem security requirements.

In plain English: the hard parts are risk tiers, status checks, and wallet rules.


How to adopt Verifiable Credentials in staged, operationally sound ways.
See typical use cases and operating patterns for Verifiable Credentials.

Quick glossary

  • Issuer: the organisation that creates a credential.
  • Holder: the person or organisation that stores and presents it.
  • Verifier: the service that checks a credential.
  • Trust registry: the published list of who is allowed to issue or verify.
  • Lifecycle: how credentials are updated, suspended, or revoked.
Looks good!
Please enter your name.
Looks good!
Please enter your company.
Looks good!
Please enter your e-mail address so we can contact you.
This form uses Google ReCaptcha to ensure interactions with our site are from legitimate users. Please accept the use of recommended storage before submitting the form. Find out more at the Privacy Center.
Your message has been sent. You should hear from us soon.
Your message could not be sent. Try again later.

You may also be interested in:

A practical, standards-aligned view of Verifiable Credentials for organisations building trusted ecosystems.