DC CORE
Central vs VPN-based remote access.
A VPN-based design provides a route into a network or to selected resources. Central combines supported private access paths with device visibility and management tools. The right choice depends on what the operator needs to reach and do.
Separate network access from device management.
Scroll sideways to compare all columns →
| Decision | Central | Alternative: what to check |
|---|---|---|
| Reachability | Supported agent paths use outbound connections to reach approved targets. | Identify the VPN endpoint, client requirements and routes that must be available. |
| Permissions | Central applies organisation, device and function permissions; local services retain their authentication. | Check which resources the VPN policy permits and how the target service authenticates users. |
| Device health | Inventory and available telemetry sit alongside management tools. | Determine which separate tools provide host and service monitoring. |
| Encryption | L0 and L1 have different boundaries; L1 encrypts between endpoints. | Review the selected VPN protocol, termination points and application-level protection. |
When each approach fits.
A VPN can be a suitable choice when existing applications need the network reachability it provides and your team already operates the supporting controls. Central fits when you also want enrolled-device visibility and supported management tools. Neither approach removes the need for endpoint and application security.
Check Central compatibility · Review remote-access methods · Examine security boundaries
Try the workflow that matters to your team.
Choose a representative device and test the required access, permissions and session closure before rolling out. Review Central pricing and separately charged consumption. Managed operations are optional and need their own agreement.