01
Access to specific resources
Identify required networks and services. Routing all internet traffic differs from routing only company resources in both capacity and network design.
SOLUTIONS / BUSINESS VPN
Controlled access to the resources your team needs.
Plan remote access alongside your team’s network, identity and device requirements. For a VPN server deployed on FibaCloud, define the software, reachable networks and operating owner. Planning how access is removed matters as much as verifying that an authorized connection works.
FibaCloud platformBusiness VPN
Workload first
Access to specific resourcesDevice identityAn operable setup
01 / Overview
A tunnel is one part of an access policy.
A VPN can establish an encrypted connection between defined endpoints. Which resources a user can reach also depends on routes, firewall rules, key or certificate management and application permissions. An active tunnel should not imply access to every resource.
Evaluate software such as WireGuard and OpenVPN against operating systems, client support and team skills. This solution describes VPN infrastructure you operate; it does not promise an included VPN licence, automatic user management or an anonymity service.
02
Device identity
Manage keys or certificates with suitable access limits. Shared identities can make removing one device without affecting others more difficult.
03
An operable setup
Document configuration, client rollout and recovery. Consider a separate management path so changes do not remove your own server access.
02 / Architecture
A controlled VPN access path
Example access flow: an authenticated device reaches only permitted networks and applications. VPN software, routes and access policies require configuration.
Selection guideArchitecture explained
- Authorized device
- VPN server
- Network rules
- Target application
03 / Selection guide
VPN design decisions
| Consider | How to decide | Why it matters |
|---|---|---|
| Traffic scope | Choose whether target networks or all traffic should enter the tunnel. | Routes, DNS and transfer requirements differ. |
| Identity lifecycle | Define creation, storage and revocation for each device. | Access from a lost device can be removed deliberately. |
| Address planning | Check client and target networks for overlapping ranges. | You can prevent routing conflicts despite a working tunnel. |
| Operating owner | Assign updates, logs and access requests. | Initial setup remains connected to ongoing maintenance. |
04 / Use cases
Define VPN use around the requirement
Remote team access
List the applications and networks needed for work. Define device enrolment, access checks and removal when a person leaves.
Administrative connections
Consider restricting management services to required networks and identities. VPN connectivity does not replace the server’s own authentication.
Connections between networks
Review overlapping addresses, routes and rules at both ends. Verify that the selected software and topology support the intended arrangement.
05 / From planning to operation
From setup to access removal
Limit the scope
Identify required resources. Prepare routing and firewall policies around that list.
Prepare the server
Choose supported operating system and software versions. Preserve management access and protect private keys.
Test both outcomes
Check access to an allowed destination and denial to an excluded one. Verify client DNS and routing behaviour.
Manage the lifecycle
Document new devices, lost devices, key changes and revocation. Test that old access stops working after removal.
Does a VPN make every application secure?
No. Devices, application permissions, updates and server security still need management. An encrypted tunnel does not remove those responsibilities.
Should I choose WireGuard or OpenVPN?
Consider client support, identity handling, network requirements and operating experience. Test your own use case rather than assuming a universal winner.
Must all internet traffic use the tunnel?
Not always. Routes for selected networks and routes for all traffic solve different needs. Assess DNS, security and transfer implications together.
Is this an included managed VPN service?
This model describes a VPN built on cloud servers. Separately verify deployment, licensing, client administration and support scope in the service terms you choose.
Go deeper with practical guides.
Connect product decisions with installation, configuration and operating knowledge.
Technical references
These references explain the technical concepts discussed on this page. Available configurations and service scope are defined by FibaCloud product and order information.
FIBACLOUD / Business VPN
Start with your project. Build on the right resources.
Tell us about your application, expected usage and operating requirements. Let’s bring the resource choices together.