09.07.2015 Views

Firebox SSL VPN Gateway Administration Guide - WatchGuard ...

Firebox SSL VPN Gateway Administration Guide - WatchGuard ...

Firebox SSL VPN Gateway Administration Guide - WatchGuard ...

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

<strong>Firebox</strong> <strong>SSL</strong> Overview<strong>SSL</strong> for authentication. Enabling single sign-on for the SecureAccess client facilitates operations on the remote computer suchas installation scripts and automatic drive mapping.Establishing the Secure TunnelOnce the Secure Access client has been started, it establishes asecure tunnel over HTTPS port 443 (or any configured port onthe <strong>Firebox</strong> <strong>SSL</strong>) and sends authentication information to validatethe tunnel. Once the tunnel is established, the <strong>Firebox</strong> <strong>SSL</strong>sends configuration information to the Secure Access clientdescribing the networks to be secured and containing an IPaddress if you enabled IP address visibility.Tunneling Destination Private Address Traffic over<strong>SSL</strong> or TLSAfter the Secure Access client is authenticated and started, allnetwork traffic destined for certain private networks is capturedand redirected over the secure tunnel to the <strong>Firebox</strong> <strong>SSL</strong>.The <strong>Firebox</strong> <strong>SSL</strong> intercepts all network connections made by theclient computer and multiplexes/tunnels them over <strong>SSL</strong> to the<strong>Firebox</strong> <strong>SSL</strong>, where the traffic is de-multiplexed and the connectionsare forwarded to the correct host and port combination,determined by the client-server application in real time. TheSecure Access client streams any dynamic port traffic over <strong>SSL</strong>to the <strong>Firebox</strong> <strong>SSL</strong> where connections are re-established to theserver at its desired dynamic port. On both the <strong>Firebox</strong> <strong>SSL</strong> andthe Secure Access client, RTP packets are prioritized and processedbefore any other packets.The connections are subject to flexible administrative securitypolicies which can apply to a single application, a subset ofapplications, or an entire intranet. You use the <strong>Firebox</strong> <strong>SSL</strong><strong>Administration</strong> Tool to specify the resources (ranges of IPaddress/netmask pairs) that remote users can access through the<strong>VPN</strong> connection.All IP packets, regardless of protocol, are intercepted and transmittedover the secure link. This functionality is what providesIPSec equivalent functionality to the <strong>Firebox</strong> <strong>SSL</strong>. Consider TCPconnections, for example. Connections from local applicationson the client computer are securely tunneled over to the <strong>Firebox</strong><strong>SSL</strong>, which re-establishes the connections to the target server.10 <strong>Firebox</strong> <strong>SSL</strong> <strong>VPN</strong> <strong>Gateway</strong> <strong>Administration</strong> <strong>Guide</strong>

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!