Device Trust Management
My role:
Product Designer
Team:
PM’s, engineers, developers
Imprivata, 2026
Overview
The difference between being connected and being trusted.
🏥
In a hospital, doctors and nurses use workstations to access sensitive patient data.
🖥️
The system checks whether a workstation is connected to the hospital’s secure network, but not if it’s an approved device.
🚫
This means that an unknown device that gains access to the network could also attempt to authenticate.
Hospital IT Administrator
Manages the hospital’s clinical workstations and secure access systems. They need to keep approved devices connected and available for staff, while quickly identifying and removing devices that should no longer be trusted.
Problem
The authentication service could verify that a request came from the hospital’s secure network, but it could not verify whether the request came from an approved hospital workstation.
This meant that an unknown or compromised device that reached the secure network could still attempt to authenticate as a trusted device.
Goal
Establish device-level trust and give IT administrators clear control over which workstations can authenticate.
Solution
A centralized admin experience for managing trusted devices. Administrators can add device trust connections, review their status, activate or deactivate them, and revoke access when necessary.
Key Takeaways
- Translated a complex security requirement into a clear admin workflow.
- Made device trust visible and actionable.
- Designed for both everyday management and security-related exceptions.
- Focused on helping administrators make confident access decisions.