
Sign in through the hospital’s identity provider
Visiting clinicians and vendors authenticate through the hospital’s identity provider, using supported SAML or OIDC authentication.
Industries|Healthcare
App-level access for visiting doctors and vendors, not the network

Visiting clinicians and vendors authenticate through the hospital’s identity provider, using supported SAML or OIDC authentication.

SwiftZAccess checks every request against the policy set for that application, considering factors such as user group, reported operating system and browser, source IP, country and time of day.

Allow and deny decisions are recorded with the reason, and logs can be streamed to the hospital’s SIEM as supported by the deployment. Revoked users are denied on subsequent requests.
Why it matters

Give visiting clinicians and vendors access to the web applications they need, rather than broad network connectivity.

Allow external users to work through their browsers without installing an endpoint agent for SwiftZAccess.
Restrict access using configured identity, device-context, location and time conditions.

End access when a user’s privileges or vendor engagement expires.
Use Cases
01
A visiting consultant needs access to a hospital’s web-based clinical or scheduling application while working from another clinic.
SwiftZAccess authenticates the consultant through the hospital’s identity provider and applies the relevant application and contextual policies. The consultant can access the authorised application without receiving a general hospital network account.
Consultants can access the applications required for their work without being granted unnecessary network access.
02
An outsourced billing team needs to process claims through the hospital’s web portal from its own office.
SwiftZAccess provides browser-based access to the approved portal, with access governed by the hospital’s identity and application policies.
External billing teams can work with the required hospital application without being placed on the hospital network.
03
A medical-software vendor completes a support engagement, but its personnel still have valid credentials.
The hospital revokes the user’s access through its configured access-management process. SwiftZAccess denies subsequent requests, including requests made during an existing session.
Application access can be withdrawn without waiting for the vendor’s next login.
See how agentless access works
Let third-party vendors and auditors reach approved banking applications from any browser, with no client install, using SwiftZAccess.
Read the full solution →See how COSGrid provides solutions for Banking and Finance
Let’s see how COSGrid secures connectivity and detects advanced threats across branches, while keeping data and audit trails under the bank’s control.
Explore the Industry →See how Compliant Device Access works
Check every laptop, workstation, and branch device against the bank’s security policy before it connects, using ZT-NAC.
Read the full solution →
IT registers the devices that are allowed to join the hospital network. Unregistered devices are denied by default.

When a device connects, ZT-NAC checks it against the hospital’s configured requirements, which can include patch level, antivirus status and disk encryption.

The agent and host-firewall enforcement admit approved devices, deny unregistered ones and quarantine devices that fail posture checks.
Why it matters

Prevent unknown laptops from gaining network access before they are approved.

Evaluate configured security requirements such as patch status, antivirus and disk encryption.

Quarantine devices that fail the configured checks until the identified issues are addressed.

Apply the same agent-based admission approach across supported campuses and clinics.
Use Cases
01
A hospital laptop returns to the network with missing updates or disk encryption disabled.
ZT-NAC checks the laptop against the hospital’s configured posture requirements when it connects. A device that fails can be quarantined through its host firewall until the issue is resolved.
Devices that do not meet the hospital’s configured security standard can be restricted from the network hosting patient-facing systems.
02
Medical and nursing students rotate through hospital departments and need network access during their placements.
ZT-NAC admits devices that IT has registered and that run the required agent and pass configured posture checks. Unregistered devices are denied by default.
Student and trainee access can follow the hospital’s device-admission requirements without relying on unmanaged devices being trusted automatically.
03
A hospital group operates a main campus alongside diagnostic centres and smaller clinics, some with limited local IT support.
ZT-NAC applies admission controls through the device agent and host firewall at supported locations.
Central IT can apply a consistent device-admission approach across participating facilities without a separate switch or VLAN project at every site.
See how agentless access works
Let third-party vendors and auditors reach approved banking applications from any browser, with no client install, using SwiftZAccess.
Read the full solution →See how COSGrid provides solutions for Banking and Finance
Let’s see how COSGrid secures connectivity and detects advanced threats across branches, while keeping data and audit trails under the bank’s control.
Explore the Industry →See how Compliant Device Access works
Check every laptop, workstation, and branch device against the bank’s security policy before it connects, using ZT-NAC.
Read the full solution →
NetShield NDR analyses traffic inside the hospital network, including east-west communication between internal systems.

It examines flow information and TLS handshake metadata, without decrypting encrypted traffic, to identify patterns that may warrant investigation.

Security teams review each alert as a lead, not as proof of compromise. Where supported integrations are available, findings can be used alongside other security records.
Why it matters

Examine communication between devices and systems inside the hospital network.

Flag behaviour that differs from expected communication patterns for investigation.

Analyse supported flow and TLS handshake metadata without decrypting session content.

Help security teams identify suspicious communication between administrative systems and internal servers.
Use Cases
01
A billing or registration workstation is compromised through a phishing email and begins probing multiple internal hosts and ports.
NetShield NDR is designed to flag this broad internal scanning pattern because it is unusual for an administrative workstation.
The security team receives an investigation lead before the suspicious activity potentially reaches more sensitive systems.
02
A server that normally communicates with its own database begins opening remote-administration sessions to other servers in the hospital data centre.
NetShield NDR is designed to flag changes in connection behaviour between servers using network-flow metadata.
The security team can investigate unexpected internal communication that may indicate an attempt to move between systems.
03
A file server holding administrative or patient-related documents begins sending an unusually large volume of traffic to an unfamiliar external address.
NetShield NDR is designed to flag the unusual flow for review. Where supported integrations are available, findings can be forwarded to the hospital’s existing security tools.
The security team gets a lead to investigate possible data exfiltration while the activity is occurring. The finding is an indicator for investigation, not confirmation of data theft.
See how agentless access works
Let third-party vendors and auditors reach approved banking applications from any browser, with no client install, using SwiftZAccess.
Read the full solution →See how COSGrid provides solutions for Banking and Finance
Let’s see how COSGrid secures connectivity and detects advanced threats across branches, while keeping data and audit trails under the bank’s control.
Explore the Industry →See how Compliant Device Access works
Check every laptop, workstation, and branch device against the bank’s security policy before it connects, using ZT-NAC.
Read the full solution →Necessary Cookies
Performance Cookies
Targetting Cookies
Functional Cookies