Question

Difficulty: MediumRemote Access and Site-to-Site VPN Concepts

An enterprise needs to grant external consultants secure access to web-based internal applications from their personal, unmanaged laptops. The security policy strictly forbids requiring local administrative rights or installing persistent client software on the end-user endpoints. Which VPN deployment model best satisfies these operational constraints?

  1. Clientless SSL/TLS VPN accessed through a native web browserAnswer
  2. B
    Site-to-site IPsec VPN operating in Tunnel Mode between boundary routers
  3. C
    Remote access IPsec VPN using full-tunnel client software
  4. D
    IPsec VPN with Generic Routing Encapsulation (GRE) in transport mode

Answer

Clientless SSL/TLS VPN accessed through a native web browser
Clientless SSL/TLS VPN allows users to securely connect to web-based internal network resources using only a standard web browser. Because the browser handles the SSL/TLS session, no administrative privileges or specialized client applications are required on the host device.

Step-by-Step Solution

1
Analyze the endpoint software and permission requirements
The scenario dictates no local admin rights and no persistent software installation on end-user devices.
Personal unmanaged endpoints cannot run managed client software installations.
2
Evaluate VPN deployment models against endpoint constraints
Clientless SSL VPN uses standard HTTPS browser connections, requiring no client installation.
Browser-based TLS sessions encapsulate application data without needing specialized local drivers or software.
3
Differentiate from Site-to-Site and Client-based IPsec alternatives
IPsec site-to-site connects gateways; IPsec remote access requires software installation.
Only Clientless SSL VPN meets both the application scope (web-based) and device policy constraints.

Key Concept

Clientless SSL VPN vs Client-based Remote Access VPN Architecture
Rate this question