Industries|Healthcare

Let Visiting Doctors In. Keep the Hospital Network Out.

App-level access for visiting doctors and vendors, not the network

How it works in Healthcare

01Sign in through the hospital’s identity provider

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.

03Record decisions and revoke when needed

Record decisions and revoke when needed

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

Benefits for healthcare providers

Provide application-specific access

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

Support unmanaged devices

Allow external users to work through their browsers without installing an endpoint agent for SwiftZAccess.

Apply contextual access policies

Restrict access using configured identity, device-context, location and time conditions.

Revoke access promptly

End access when a user’s privileges or vendor engagement expires.

Use Cases

Three access risks. One protected environment.

01

Visiting Consultants Across Hospitals

Scenario

A visiting consultant needs access to a hospital’s web-based clinical or scheduling application while working from another clinic.

COSGrid Solution

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.

Outcome

Consultants can access the applications required for their work without being granted unnecessary network access.

02

Insurance and Billing Partners

Scenario

An outsourced billing team needs to process claims through the hospital’s web portal from its own office.

COSGrid Solution

SwiftZAccess provides browser-based access to the approved portal, with access governed by the hospital’s identity and application policies.

Outcome

External billing teams can work with the required hospital application without being placed on the hospital network.

03

Revoking Access When a Vendor Contract Ends

Scenario

A medical-software vendor completes a support engagement, but its personnel still have valid credentials.

COSGrid Solution

The hospital revokes the user’s access through its configured access-management process. SwiftZAccess denies subsequent requests, including requests made during an existing session.

Outcome

Application access can be withdrawn without waiting for the vendor’s next login.

Keep Exploring

Solution

Go Deeper

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 →
Industry

Banking and Finance

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 →
Solution

The Next Solution

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 →