In short
Island Private Access is Island's zero trust network access, built into the Island Enterprise Browser and sold as the per-user Zero Trust add-on. It gives access to private web and desktop applications per app and per session, based on identity and device posture, through connectors in your network, and adds last-mile data controls. It also works alongside an existing ZTNA.
Get a quote for Island Private Access
Tell us roughly how many users or sites you have and we will reply by email with options and a quote.
What Island Private Access is
Island makes the Island Enterprise Browser, a full business web browser with security and IT controls built in and managed from a cloud console. Island Private Access is the zero trust network access capability inside it, licensed as the Zero Trust add-on on top of the browser.
Island describes Private Access as a complete ZTNA solution for both web and desktop applications that works natively with the Enterprise Browser, with no separate agents, VPNs, web portals or end-user configuration. The user opens the browser, signs in with their work identity and sees the internal applications their policy allows.
For the browser itself, including its data protection and safe browsing features, see Island Enterprise Browser on our cloud security site.
Island Enterprise Browser architecture: how access works
People often search for how the Island Enterprise Browser works, and for ZTNA the architecture has three parts:
| Part | What it does |
|---|---|
| The Island Enterprise Browser | Runs on the user's device and acts as the policy enforcement point: it signs the user in, assesses the device and applies access and data rules per application |
| Island's cloud management console | Where administrators define who can reach which applications, under which conditions, and what they can do with the data |
| Connectors | Island describes these as lightweight virtual machines deployed in your private cloud or data centre, able to run in several regions, through which the browser reaches private applications |
| Your identity provider | Users authenticate with their work identity; Island integrates with providers such as Microsoft Entra ID and Okta |
Island says it continuously assesses device posture and adjusts access permissions and security controls throughout each session, taking account of identity, device posture and signals such as geolocation and network type. That lines up with the NCSC's requirement to use multiple signals and to re-evaluate access as context changes, described in our NCSC ZTNA guidance summary.
Network requirements, including firewall rules for the connectors, are confirmed against Island's current documentation when we design a deployment.
Not sure which option fits? Ask us
Tell us what you need and we will recommend the right option for your organisation, with a quote.
Last-mile controls: the difference from network ZTNA
A network ZTNA decides whether a device may connect to an application. Once connected, what the user does with the data is outside its view. Because Island is the browser, it can also govern the last mile:
- Data movement: control copy and paste, downloads, uploads, printing and screenshots per application and context
- Application boundaries: keep corporate data inside approved applications
- Watermarking and redaction of sensitive screens
- Work and personal separation: work activity is logged, personal browsing stays private, which helps staff accept it on their own devices
- Audit: detailed activity logs that can be sent to your SIEM
That is why Island Private Access is often chosen for contractors, offshore teams and BYOD: you can give access to an internal system on a device you do not manage, without the data being free to leave it. The broader options for that use case are on agentless ZTNA.
Working alongside your existing ZTNA or SSE
Island says it integrates with existing ZTNA technologies: you can keep a current ZTNA provider and use Island for the browser layer, or use Private Access as the ZTNA itself. Cisco, for example, lists Island among the enterprise browsers that integrate with Cisco Secure Access for more secure clientless access to private applications.
That gives three common patterns:
| Pattern | How it works | When it fits |
|---|---|---|
| Island Private Access as the ZTNA | Private applications reached only through the Island browser | Mostly web and browser-delivered applications; contractors and BYOD |
| Island alongside an SSE or ZTNA | Network ZTNA for managed devices and non-browser traffic; Island for browser access and data controls | Organisations already running Cisco Secure Access or another ZTNA |
| Island for third parties only | Staff keep the existing ZTNA or VPN; contractors get Island | A quick, contained first step |
Compare network ZTNA products on ZTNA providers.
Is Island Private Access the right fit for you?
We will check it against your systems and requirements and recommend the right option.
Platforms and licensing
The Island Enterprise Browser runs on Windows, macOS and Linux desktops, on IGEL OS for thin clients, and on mobile devices including iOS and iPadOS; we confirm support for your exact device mix before quoting. Island says no agents, kernel extensions, proxies or MDM are needed on personal devices; managed devices can receive the browser through your existing software distribution or MDM.
Licensing is per user: Island Browser Professional plus the Zero Trust add-on for the people who need private access, so you can license private access only for the groups that use it. Island also offers Island Enterprise Network, which it describes as its SASE; if that is of interest, ask us and we will scope it separately. For editions and add-ons see Island Enterprise Browser licensing. We do not publish prices: ask us for a quote.
When Island Private Access is the right answer
- Contractors and partners need a few internal applications, and you do not want to ship laptops or build VDI
- BYOD is common and you need data controls on devices you do not manage
- Applications are mostly browser-based, so the browser is the natural control point
- You already run a network ZTNA and want to add last-mile controls rather than replace it
It is a weaker fit where most traffic is non-browser, server-to-server or legacy; a network ZTNA or VPN as a service will usually be needed alongside. We test your key applications in a pilot before you commit.
Rolling out Island Private Access
- Pick one use case: for example contractors who need one internal system, or staff who reach a single web application over VPN today.
- Connect identity: link your identity provider so users sign in with their work account and leavers lose access when their account is disabled.
- Deploy connectors in the private cloud or data centre that hosts the applications, in more than one region if resilience matters.
- Define access and data policies per application: who can reach it, from which kinds of device, and whether they may download, print, copy or capture the screen.
- Pilot with a small group, test the applications in the browser and review the activity logs.
- Widen the rollout, then retire the VPN access or portal those users relied on, so there is no second route around the new policy.
Starting small keeps the change visible and reversible, and it gives you real evidence for the business case before the wider rollout. Broader planning advice is on VPN alternatives for business and secure remote access solutions.
How Forever Systems helps
We can help you decide where Island fits beside your existing remote access, design per-application access and data policies, deploy connectors, connect your identity provider and run a pilot with one team or one group of contractors before widening the rollout. Scope and timescales are confirmed at quote. Contact us to talk through your use case.
How Forever Systems helps with ZTNA and SASE
We are an independent IT and cyber security provider. We supply and support several zero trust access and SASE platforms, so we can recommend what fits how your people work rather than one vendor's answer to everything.
- Assess first: we look at your current VPN, firewall, identity set-up and the applications people need to reach before suggesting anything new
- Vendor-aware advice across ZTNA, SSE and SASE options, including Cisco Secure Access and Check Point Harmony SASE
- Pilots and phased roll-out: we can help you start with one group of users or one application, then extend access policy by policy
- VPN replacement: planning the move away from remote access VPNs, including identity provider integration and device posture checks
- Ongoing support: policy changes, licence reviews and renewals, with the details confirmed at quote
We work with businesses, schools, charities and public sector organisations. Pricing depends on users, features and term, so ask us for a quote.
Frequently asked questions
What is Island Private Access?
Island's zero trust network access, built into the Island Enterprise Browser and licensed as the per-user Zero Trust add-on. It gives access to private web and desktop applications based on identity and device posture, per application and per session, without a separate agent or VPN.
How does the Island Enterprise Browser work for private access?
The browser on the user's device enforces policy set in Island's cloud console. It signs the user in with their work identity, assesses the device, and reaches private applications through connectors deployed in your private cloud or data centre, while applying data controls to what the user does.
Does Island Private Access replace a VPN?
For applications reached through the browser, often yes. Island describes it as a complete ZTNA solution for web and desktop applications. Legacy or non-browser traffic may still need a network ZTNA or VPN, so we review your applications first.
Can Island work with our existing ZTNA?
Yes. Island says it integrates with existing ZTNA technologies, so you can keep your current provider and add Island for browser access and data controls. Cisco, for example, lists Island among the enterprise browsers that integrate with Cisco Secure Access.
Does Island need MDM on personal devices?
No. Island says contractors and staff simply install the browser on a personal device and sign in, with no agents, kernel extensions, proxies or MDM needed, and personal browsing stays private, which makes it practical for BYOD.
Still have a question about Island Private Access?
Ask us and a member of our team will reply by email.
More zero trust access guides
Cisco universal ZTNAOne per-app zero trust policy for remote and on-site users, enforced by Secure Access and Secure Firewall.Secure remote accessSecure remote access by use case: staff, admins, suppliers and personal devices, with the products for each.How ZTNA worksA ZTNA connection step by step: signals, policy engine, connectors, client and clientless access.