More Network Access Than Required
A connection created for one application may also make unrelated systems reachable. Permissions that are broader than the task increase the consequences of a compromised account or endpoint.
The challenge in designing secure remote access solutions is not simply connecting users. It is limiting what each connection can reach while accommodating different application protocols, user devices and network environments. Conventional network-based access can introduce avoidable exposure and operational complexity.
A connection created for one application may also make unrelated systems reachable. Permissions that are broader than the task increase the consequences of a compromised account or endpoint.
Browser-based portals, legacy client-server software and administrative tools require different connection methods. Managing them through disconnected access mechanisms makes application policies harder to maintain.
Directly publishing internal application services or relying on network location as a trust signal can widen the attack surface. Access must be restricted to approved users, applications and conditions.

Give authorised users browser-based access to multiple private web applications without installing a client on every device. This approach is suited to large, geographically dispersed user populations.
Secure remote access solutions can use internet connectivity as an alternative route when a private WAN or MPLS link is unavailable. Keep approved business applications reachable without redesigning the branch network.
Deploy secure remote access solutions for supported legacy and client-server software that cannot operate through a standard browser. Use encrypted application tunnels without requiring changes to the applications.
Make approved RDP and SSH services available through defined application permissions for remote maintenance, rather than creating an open route to a wider administration network.

