13.07.2015 Views

WatchGuard Firebox System 4.6 User Guide

WatchGuard Firebox System 4.6 User Guide

WatchGuard Firebox System 4.6 User Guide

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Using authentication to define remote user VPN access8 Click OK.Using authentication to define remote user VPN access<strong>WatchGuard</strong> uses two built-in <strong>Firebox</strong> groups to identify currently active remote uservirtual private network users.• pptp_users – Names authorized to use Remove <strong>User</strong> VPN with PPTPFor more information, see “Adding remote access users” on page 134.• ipsec_users – Names authorized to use Mobile <strong>User</strong> VPN with IPSecWhen a user successfully connects to the <strong>Firebox</strong> using Remote <strong>User</strong> VPN,<strong>WatchGuard</strong> automatically adds the assigned IP address to one of these built-inaliases (depending on the VPN method). When the user shuts down the VPN session,<strong>WatchGuard</strong> automatically removes the address associated with that user from thealias.When a Remote <strong>User</strong> VPN connection is made to the <strong>Firebox</strong>, <strong>WatchGuard</strong> checks theclient’s username and password against the <strong>Firebox</strong> domain. For this reason, Remote<strong>User</strong> VPN users must have an account in the <strong>Firebox</strong> domain and must be a memberof the appropriate VPN group for access, regardless of any other authenticationscheme in use.When users authenticate using their account in the <strong>Firebox</strong> domain, <strong>WatchGuard</strong>automatically adds their IP address to all <strong>Firebox</strong> domain groups of which they are amember, including pptp_users or ipsec_users.By default, Remote <strong>User</strong> VPN users (or any users) have no access privileges through a<strong>Firebox</strong>. To allow Remote <strong>User</strong> VPN users to access machines on the Trustednetwork, you must add their usernames (or the group alias) to service icons in theServices Arena.A typical use of built-in groups is to allow incoming connections to certain Trustedservers from the pptp_users or ipsec_users group members. This is an easy way toprovide outside access to critical machines inside your network, withoutcompromising general security.Example: Configuring a service for Remote <strong>User</strong> VPNTo allow outgoing Telnet but only allow incoming Telnet if the request comes from aRemote <strong>User</strong> VPN user, follow this procedure:From Policy Manager:1 Add a Telnet icon to the Services Arena if one does not already exist.For information on how to add services, see “Adding an existing service” on page 47.2 Configure the Outgoing tab to allow from Any to Any.3 Configure the Incoming tab to allow from pptp_users to Any.4 Click OK.92

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

Saved successfully!

Ooh no, something went wrong!