Topic starter
10/07/2026 9:21 pm
TL;DR: Healthcare access in distributed care settings now depends on identity, context, and least-privilege controls because VPN-centric models still grant broad trust after login, according to Appgate's analysis. That model increases lateral movement risk, weakens auditability, and complicates secure third-party access.
Editorial analysis by NHI Mgmt Group, based on content published by Appgate: “Why Legacy Access Models Fail Healthcare Organizations”.
Key questions
Q: Why do VPN-style access models create risk in healthcare?
A: VPN-style models usually trust a user once they are inside the network, which gives them broad reach that is too coarse for healthcare.
A: Healthcare organisations should treat third-party access as part of their core security model, not as an exception.
Q: What signs show that healthcare access controls are too broad?
A: Common warning signs include vendors with standing connectivity to large network segments, multiple remote access tools that overlap, and access privileges that outlast the task they were created for.
Practitioner guidance
- Replace broad VPN trust with resource-scoped access Limit remote access to the specific applications, devices, or services required for each role instead of exposing the broader network path.
- Separate vendor connectivity from internal network reach Treat third-party maintenance access as a narrowly governed identity path with explicit resource boundaries, not as general remote access into the environment.
- Map access policies to clinical workflow needs Validate that identity and context rules still allow rapid access to EHR, imaging, and telehealth systems without opening unnecessary lateral movement paths.
Bottom line: Healthcare access security is moving away from perimeter trust because distributed care has outgrown network-wide assumptions about who should be trusted after login.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
10/07/2026 9:43 pm
Perimeter trust is the wrong operating assumption for healthcare access. The old model assumes a user becomes broadly trusted after network login, but modern care delivery is distributed across facilities, homes, vendors, and cloud services. That assumption fails because healthcare access is now task-specific, time-sensitive, and context-dependent. The implication is that healthcare IAM has to stop treating network entry as a proxy for trust.
A few things that frame the scale:
- 60% of healthcare organisations do not assess a vendor's security before signing a contract that grants access to protected health information, according to Ponemon Institute's 2023 Third-Party Risk in Healthcare report.
A question worth separating out:
Q: Should healthcare organisations prioritise privilege reduction over more login controls?
A: They should do both, but privilege reduction often delivers the bigger risk reduction once phishing or stolen credentials are already in play. Login controls help prevent access, yet the severity of a breach is determined by what the account can reach after entry. That is why entitlement scope matters so much.
👉 Read our full editorial: Healthcare access security is moving beyond perimeter trust