Remote Browser Isolation for Contractors: Give Vendors the App, Not the Network

Thinfinity remote browser isolation for contractor access to internal web apps

When a contractor needs one internal portal for a two-week project, giving them a VPN account can feel like using a master key to open a meeting room. The connection may be convenient, but it can expose far more of the environment than the person needs. Remote browser isolation offers a narrower option for work that happens inside a web application: deliver the application through a controlled browser session instead of placing an unmanaged device on the corporate network.

That distinction is useful for vendors, auditors, temporary specialists and other third parties who need to complete a defined task without receiving broad network access or a company-managed laptop.

Start with the application, not the tunnel

A conventional VPN extends network reachability to the remote device. Segmentation can limit what happens next, but the device still enters a network environment that IT must trust and maintain. A contractor’s laptop may be outside the organisation’s patching, endpoint-management and monitoring processes.

For a browser-based workflow, the requirement is often much smaller. The contractor needs a finance portal, an internal dashboard or an administration console — not a route to every server that happens to sit nearby. Designing access around that one application makes the policy easier to explain and review.

Run the browser where the application lives

Cybele Software describes a remote browser isolation model for Thinfinity Workspace in which the contractor’s browser session runs inside an ephemeral container, or pod, on Oracle Kubernetes Engine (OKE) in Oracle Cloud Infrastructure (OCI). The internal application is rendered in that isolated environment, while the contractor interacts with the session from an ordinary HTML5 browser.

The application code, cookies, tokens and network connections remain in the isolated pod rather than being delivered to the contractor’s endpoint. The user connects to the Thinfinity Gateway over TCP 443. The hosts and pods establish outbound connections, so the protected environment does not need inbound ports opened for the contractor workflow.

When the session ends, the pod is discarded. That makes the isolation part of the session lifecycle rather than a cleanup task someone has to remember after the engagement.

Make access expire with the contract

Isolation controls what reaches the endpoint. Identity and access policy determine who can start the session, which application they can reach and when that permission should end.

Thinfinity’s published architecture combines Universal Zero Trust Network Access (ZTNA) with Just-in-Time (JIT) Access. The contractor is brokered to the specific application they are approved to use, rather than being given a route into a network segment. A JIT window can limit the grant to the duration of the engagement, so access expires automatically instead of remaining active until someone remembers to revoke it.

Clipboard use, file upload, download and printing can also be controlled by session and role. For a sensitive admin portal, an organisation may decide that none of those channels should be available. A project that genuinely requires file exchange can define a narrower, approved transfer process.

Build a contractor workflow that is easy to audit

A practical rollout does not need to begin with every vendor. Pick one recurring engagement and map the access journey from request to closure:

  • Name the person and sponsor. Record the contractor, the internal owner, the business reason and the application required. Avoid generic shared access where an individual identity is possible.
  • Scope the resource. Grant access to the named web application only. Check that the session cannot browse adjacent internal services or discover unrelated systems.
  • Set the time window. Match the JIT period to the work schedule and include a clear process for extensions. An extension should be approved, not assumed.
  • Choose the data channels. Decide whether clipboard, upload, download and printing are needed. Start with restrictive defaults and open only the channels required for the task.
  • Test the end state. Confirm that the session closes, the temporary pod is removed and the contractor cannot reconnect after the approved window expires.

Keep the evidence with the access request: who approved it, which resource was granted, when the session started and ended, and whether any exception was made. That gives the service desk and security team a useful record without relying on informal email trails.

Know when browser isolation is the right tool

Remote browser isolation is a strong fit for browser-delivered applications such as intranets, portals, dashboards, ticketing systems and web-based admin consoles. It is not a universal replacement for every remote-work pattern. A contractor who needs a thick-client engineering application or a full Windows desktop may need virtual desktop infrastructure (VDI) or a published application instead.

It is also not a substitute for endpoint security on the contractor’s own device. Isolation protects the application session being brokered; it does not make the rest of that laptop safe. Performance should be tested with the actual application and expected user locations, and compliance decisions still need to be assessed against the organisation’s specific obligations.

Prove the model with one real engagement

For an initial pilot, choose a web application that contractors use regularly and measure the things that matter to operations: time to provision access, time to revoke it, number of helpdesk interventions, session performance and any attempted access outside the approved scope. Ask the application owner whether the workflow feels natural, and ask the security team whether the resulting audit trail is sufficient.

If the pilot works, expand by application and contractor group rather than opening a broad remote-access programme all at once. That keeps the policy understandable and makes it easier to spot where a full desktop or a different access method is genuinely required.

The goal is straightforward: give outside users the application they need for the time they need it, without making their device part of the internal network. With remote browser isolation, least-privilege access and a self-expiring session, contractor access can become a controlled workflow instead of a standing exception.

About Cybele Software Inc.
We help organizations extend the life and value of their software. Whether they are looking to improve and empower remote work or turn their business-critical legacy apps into modern SaaS, our software enables customers to focus on what’s most important: expanding and evolving their business.

About Version 2 Limited
Version 2 Digital is one of the most dynamic IT companies in Asia. The company distributes a wide range of IT products across various areas including cyber security, cloud, data protection, end points, infrastructures, system monitoring, storage, networking, business productivity and communication products.

Through an extensive network of channels, point of sales, resellers, and partnership companies, Version 2 offers quality products and services which are highly acclaimed in the market. Its customers cover a wide spectrum which include Global 1000 enterprises, regional listed companies, different vertical industries, public utilities, Government, a vast number of successful SMEs, and consumers in various Asian cities.