View Zero Trust Service Catalogue 1 Match IdentityVerifiable Credentials
Zero Trust Service Catalogue
UNIFY's identity-first catalogue spanning the core Zero Trust pillars.
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
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
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 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
Overview
Hospitals and clinics can verify a visiting practitioner’s credentials instantly using verifiable, issuer‑signed claims.
Why it matters
Credential verification is critical to patient safety but often slow and manual. In time‑critical or remote settings, delays can put outcomes at risk.
Ecosystem roles
- Issuer: Regulatory bodies and training organisations issuing certifications.
- Holder: The practitioner storing credentials in a wallet.
- Verifier: The hospital or clinic validating credentials on arrival.
Assurance and access
Status checks ensure licenses and certifications are current. The verifier can confirm scope of practice without requesting unnecessary personal data.
| Objective | Enable a hospital to verify the credentials of a visiting practitioner. |
| Description | Use verifiable credentials to allow a visiting medical practitioner to prove their credentials. |
| Actors | Visiting medical practitioner |
| Dependencies | Visiting medical practitioner has certifications in their wallet |
| Preconditions | The visiting practitioner is to provide health care services at the hospital |
| Postconditions | The hospital permits the visiting medical practitioner to operate at the hospital. |
flowchart LR
REG@{icon: "fa:scale-balanced", label: "Regulator", pos: "b"} -->|Issues licence VC| WAL@{icon: "fa:wallet", label: "Wallet", pos: "b"}
EDU@{icon: "fa:certificate", label: "Training body", pos: "b"} -->|Issues certification VC| WAL
WAL -->|Presents credentials| VER@{icon: "fa:hospital", label: "Hospital / verifier", pos: "b"}
VER -->|Status check| REG2@{icon: "fa:book", label: "Credential registry", pos: "b"}
sequenceDiagram
participant Regulator
participant Trainer as Training body
participant Wallet
participant Practitioner
participant Verifier as Hospital / verifier
participant Registry as Credential registry
Regulator-->>Wallet: Issue licence VC
Trainer-->>Wallet: Issue certification VC
Practitioner->>Wallet: Stores credentials
Practitioner->>Verifier: Present licence + certification
Verifier->>Registry: Check status
Registry-->>Verifier: Valid
Verifier-->>Practitioner: Access granted