Your intranet may hold internal procedures, commercial documents, staff resources and operational information. Employees need convenient access to it, including when working away from the office. That does not mean the application needs to be openly reachable from the public internet.
VPN-controlled access can provide a private route to an intranet and limit who can reach it. For a B2B business, this can support remote working while keeping an additional access boundary around internal systems. It needs to be planned alongside the intranet itself, rather than treated as a security switch that makes everything safe.
What is a business VPN?
A virtual private network, or VPN, creates an encrypted connection between a user's device and a business-controlled network or gateway. Once the user is authenticated, authorised traffic can travel through that connection to the internal services they are allowed to reach.
This is different from using a consumer VPN to change the apparent location of your browsing. A business remote-access VPN is configured around your organisation's users, devices, network and access policy.
A VPN can also connect office and hosting networks through a site-to-site connection. That may be useful where an intranet is hosted separately from the office, but it does not replace the need to control individual users.
How does VPN-controlled intranet access work?
The intranet is placed on a private network, or behind access rules that allow only approved network routes. Staff connect through the business VPN before opening the intranet in their browser. The hosting and network setup must support this arrangement.
A typical remote-access journey
- The employee uses an approved, maintained device.
- They connect to the business VPN using their own account and the required authentication checks.
- Network rules permit the connection to reach the intranet, without unnecessarily opening other systems.
- The intranet authenticates the employee, potentially through company single sign-on.
- Application permissions determine which pages, documents and actions that employee can access.
Private DNS or another agreed naming arrangement helps users find the intranet. Firewall rules, routing and hosting controls determine whether the connection can actually reach it. These details need to be coordinated with the business's IT or network provider.
The important distinction is between reaching the application and being authorised to use its information. A VPN controls the network route; the intranet still needs its own user and permission controls.
What are the advantages for a B2B business?
Less public exposure. When correctly configured, network restrictions can prevent unsolicited public connections from reaching the intranet. Hiding a link or choosing an obscure address does not provide the same protection.
Controlled remote working. Staff can use a defined access route from outside the office, rather than relying on ad hoc document sharing or exposing additional services for convenience.
A clearer access policy. Individual accounts and managed groups make it easier to define who should connect, review that access and remove it when roles change.
Protection for traffic across untrusted networks. The VPN encrypts traffic carried inside its tunnel. HTTPS should still be used for the intranet; the VPN is not a reason to remove application-level transport protection.
What does a VPN not protect against?
A VPN does not fix vulnerable software, excessive permissions or a compromised laptop. If an attacker gains access to an authorised account or device, the private connection could become a route into the business.
Keep the intranet, VPN gateway and supporting infrastructure updated. Apply least-privilege access: users should receive only the network routes and application permissions needed for their work. Sensitive or administrative functions may need stronger restrictions.
Multi-factor authentication makes a stolen password less useful, but it is not a substitute for account reviews, device protection or monitoring. The VPN gateway is itself a security-critical system that needs maintenance and oversight.
VPN access also does not automatically make an intranet compliant with data protection requirements. Information handling, retention, user rights and the wider security arrangements still need assessment.
How should the intranet and VPN be planned together?
Begin with the users and information, not a preferred VPN product. Identify who needs access, where they work, which devices they use and whether contractors or external partners need a different access arrangement.
Then agree the responsibilities across application development, hosting and network management. The intranet developer needs to understand the identity and access requirements; the IT team needs to understand which services and routes the application requires.
- Where will the intranet be hosted, and can public access be restricted appropriately?
- Will existing company identities support VPN access and intranet single sign-on?
- Which users need which resources, and how will access be approved and revoked?
- Who manages certificates, gateway updates, firewall rules and security alerts?
- How will connection failures, performance issues and account lockouts be handled?
Where a business already has a managed VPN, the practical starting point is to assess how the intranet can fit that environment. Where it does not, the access architecture should be agreed before development and hosting decisions are finalised.
Test the boundary and plan ongoing support
Before launch, confirm that an authorised user can complete the intended tasks and that a connection outside the approved route cannot reach the restricted service. Check any alternative hostnames or direct origin routes, not just the main intranet address.
Test what happens when access is revoked, when a user attempts to open another account's information and when the VPN is unavailable. Document support and recovery procedures so an outage does not lead to improvised public access.
After launch, review access regularly, monitor relevant connection and application events, and maintain backups with tested restoration procedures. Agree who responds to incidents and who keeps each part of the system current.
Is a VPN always the right approach?
No. An intranet restricted to an office network may not need remote-access VPN connections. Other organisations may use an identity-aware access gateway or zero-trust network access to grant access to individual applications instead of a broader private network.
The right choice depends on your existing infrastructure, users, devices, risk and support arrangements. The objective is controlled access to the right resources, not installing a VPN for its own sake.
Plan the intranet and its access controls as one project.
BBI develops intranets and business platforms around the way organisations work. For a VPN-restricted intranet, the application, hosting and identity requirements need to be coordinated with the team responsible for the business network.
That means agreeing the access model early, building appropriate application permissions and testing the complete user journey. Explore BBI's portals and platforms service to discuss the requirements for your business.
Start with who needs access and what they need to do
A VPN can be a useful layer in protecting an intranet, particularly when employees need access away from the office. Its value comes from a properly configured boundary combined with strong identity controls, appropriate permissions and ongoing maintenance.
Map those requirements before choosing technology. You can then build a system that supports everyday work without treating convenience and security as opposing goals.
