1-minute read of a 3 min report

Imprivata EAM Keeps Appliance Keys Trusted Until Redeployment

By

1-minute read

What a defender needs to know

Imprivata Enterprise Access Management versions 26.2.6 and below reuse their RSA key pair to generate the X.509 certificate that identifies an appliance to clinical workstations, EHR platforms and shared-device authentication workflows. CERT/CC’s September 23 note says the appliance has no supported post-deployment key-pair rotation. If someone obtains the private key from an appliance filesystem, backup or hypervisor snapshot, that person could impersonate the appliance to an endpoint that trusts its certificate. CERT/CC says redeployment is the available replacement path for a compromised identity. It reports no fix or timeline; Imprivata is reportedly working toward a resolution.

Find affected appliances and the endpoints that trust each certificate. Restrict privileged filesystem and administrative access, narrow backup and snapshot read/export permissions, and review existing access records for unexplained exports. Enforce perfect forward secrecy on upstream connections to limit retrospective exposure of previously captured traffic. A certificate renewal using the same key leaves the underlying exposure intact.

Verify the access-control entries on the appliance filesystem, backup store and hypervisor snapshot repository. Expected result: only named, authorized key-copy holders retain read or export access. If a copy is unaccounted for, preserve access evidence and coordinate redeployment with Imprivata and the owners of trusting endpoints. CERT/CC supplies no key-theft or impersonation signature, so access history and custody of backups and snapshots are the useful local triage inputs.

Primary sources