Chapter 21. Deploying Remote Access Solutions Using EZVPNs

This chapter covers the following subjects:

• Plan the deployment of a Cisco IOS Software EZVPN: Discusses the decision-making process that helps plan an EZVPN deployment. You must make choices about encryption algorithms, key management, and authentication among others to properly plan the deployment.

• Configure and verify a basic Cisco IOS Software VTI-based EZVPN server: Covers configuring and verifying operations on the EZVPN server on a Cisco IOS Software device.

• Configure the Cisco VPN client: Covers how to configure the Cisco VPN client parameters.

• Configure and verify VTI-based EZVPN remote client functionality on the Cisco ISR: Explains how to configure a Cisco ISR as an EZVPN remote hardware client. You also learn how to verify the operation of the hardware client.

• Configure and verify EZVPN server and VPN client PKI features: Covers how to configure and verify the use of PKI for authentication on the EZVPN server and the VPN client.

• Troubleshoot basic EZVPN operation: Covers the process to follow when troubleshooting EZVPN operation to ensure successful implementations.

The Cisco Easy VPN (EZVPN) solution provides access to internal resources across an untrusted network transport to a remote access Virtual Private Network (VPN) gateway that is running on the Cisco Integrated Services Router (ISR).

“Do I Know This Already?” Quiz

The “Do I Know This Already?” quiz helps you decide whether you really need to read the entire chapter. If you already intend to read the entire chapter, you do not necessarily need to answer these questions now.

The ten-question quiz, derived from the major sections in the “Foundation Topics” portion of this chapter, helps you determine how to spend your limited study time.

Table 21-1 outlines the major topics discussed in this chapter and the “Do I Know This Already?” quiz questions that correspond to those topics.

Table 21-1. “Do I Know This Already?” Foundation Topics Section-to-Question Mapping

image

Caution

The goal of self-assessment is to gauge your mastery of the topics in this chapter. If you do not know the answer to a question or are only partially sure of the answer, you should mark this question wrong for purposes of the self-assessment. Giving yourself credit for an answer that you correctly guess skews your self-assessment results and might provide you with a false sense of security.

1. What enables Cisco Integrated Services Routers to act as VPN gateways?

a. Cisco EZVPN Remote

b. PKI

c. Cisco EZVPN Server

d. None of these answers are correct.

2. What can the EZVPN server use to create cryptographic tunnel contexts? (Select all that apply.)

a. VTI

b. IPsec

c. Crypto map

d. B and C

e. None of these answers are correct.

3. Which of the following is preferred to EZVPN for deploying full tunneling?

a. IPsec tunnels

b. Traditional WAN circuits

c. Client-based tunneling

d. SSL VPNs

e. None of these answers are correct.

4. Which is an additional authentication mechanism that can be used in addition to group passwords?

a. XAUTH

b. RADIUS

c. TACACS+

d. IPsec

e. None of these answers are correct.

5. Recommended practice dictates limiting the size of which of the following to mitigate the fallout if a group password is compromised?

a. Networks

b. VPNs

c. User databases

d. Groups

6. Which type of authentication should you use to make the implementation resistant to a man-in-the-middle attack?

a. One-way

b. Two-way

c. PKI-based

d. Group password–based

e. None of these answers are correct.

7. Which of the following is authenticated when using XAUTH with the EZVPN remote hardware device?

a. Rrouter

b. User

c. Network

d. None of these answers are correct.

8. Which of the following are modes of operation of the EZVPN Remote feature on hardware clients? (Select all that apply.)

a. Client mode

b. Network extension

c. Network extension plus

d. Client plus

9. What issue is mitigated by using certificate-based, rather than group password–based, EZVPN implementations?

a. Man-in-the-middle attack

b. DoS attacks

c. Ping sweep

d. Reconnaissance attack

10. What are the two areas to investigate when troubleshooting VPNs?

a. Session establishment

b. Data flow

c. Your ISP

d. None of the answers are correct.

The answers to the “Do I Know This Already?” quiz are found in Appendix A. The suggested choices for your next step are as follows:

• 8 or less overall score: Read the entire chapter. This includes the “Foundation Topics” and the “Exam Preparation” sections.

• 9 or 10 overall score: If you want more review on these topics, skip to the “Exam Preparation” section. Otherwise, move on to Chapter 22, “Final Preparation.”

Foundation Topics

The basic EZVPN solution uses basic user authentication with usernames and passwords, client configuration, and IP address assignments, with a single access control policy. Configuring and verifying a basic EZVPN solution is covered in this chapter.

Plan the Deployment of a Cisco IOS Software EZVPN

With broadband access providing high-speed connections to the Internet, users have a new way to access sensitive enterprise resources at a remote location. This ease of access brings with it the need to secure the connection between the remote user and the enterprise. The need to provide authentication and encryption to ensure the protection of the data is required, but building a VPN between two routers can be complicated.

The Cisco EZVPN Remote feature implements the Cisco VPN client protocol, which allows most VPN parameters to be defined at the Cisco EZVPN Server. This server is typically a dedicated VPN device such as the Cisco ASA 5500 Series Adaptive Security Appliance or a Cisco IOS router that supports the Cisco VPN client protocol.

After the Cisco EZVPN Server has been configured, a VPN connection can be created with minimal configuration on a Cisco EZVPN Remote client, such as a Cisco Integrated Services Router (ISR). As the Cisco EZVPN Remote initiates a VPN tunnel, the Cisco EZVPN Server pushes the IP Security (IPsec) policies to the Cisco EZVPN Remote client and creates the corresponding VPN tunnel connection.

Internet Key Exchange (IKE) mode configuration allows a Cisco EZVPN Server to download an IP address and other network parameters to the Cisco EZVPN Remote as part of an IKE negotiation. In this exchange, the Cisco EZVPN Server assigns IP addresses to the Cisco EZVPN Remote to use as the “inner” IP address encapsulated under IPsec. This results in a known IP address from the client that will match against the IPsec policy.

To use IPsec VPNs between Cisco EZVPN Remotes with dynamic IP addresses and a Cisco EZVPN Server, an IPsec policy must be dynamically administered on the Cisco EZVPN Server after each client is authenticated. With IKE mode configuration, the Cisco EZVPN Server can set up the scalable policy for a very large number of clients, regardless of the IP addresses of those clients.

image

The Cisco EZVPN Remote feature provides automatic management of the following:

• Negotiation of tunnel parameters, such as addresses, algorithms, and lifetimes

• Building tunnels based on the parameters that were set

• Automatically create the Network Address Translation (NAT) or Port Address Translation (PAT) configuration and associated access control lists (ACL) that are needed

• Authenticate users by usernames, groups names, and passwords

• Managing security keys for encryption and decryption

• Authenticating, encrypting, and decrypting data through the tunnel

Cisco EZVPN Server enables Cisco Integrated Services Routers and Cisco ASA 5500 Series Adaptive Security Appliances to act as VPN gateways in site-to-site or remote access VPNs when the remote office device is using the Cisco EZVPN Remote feature. This feature allows security policies to be managed at the gateways and pushed to the remote VPN device. This ensures that the connections always have up-to-date policies before connections are established.

The Cisco EZVPN Server can also terminate IPsec tunnels that are initiated by remote users running VPN client software on their systems. This provides an ideal solution for mobile and remote workers to continue to be able to access enterprise resources while traveling.

Cisco EZVPN Remote allows the Cisco ISRs and the Cisco ASA 5500 Adaptive Security Appliances or Cisco VPN Software Clients to act as the remote VPN clients. The devices receive security policies from the Cisco EZVPN Server, which drastically minimizes the configuration and management requirements at the remote location. This is ideal for remote offices with little or no IT support.

Solution Components

A basic Cisco EZVPN solution is comprised of remote users with the Cisco VPN client software that is used to create an IPsec tunnel to a Cisco ISR EZVPN Server.

This basic solution typically uses bidirectional authentication, where the client authenticates the ISR with a group password for the authentication method and the ISR authenticates the user based on the group password and can optionally use a username and password method in addition to the group password. The Cisco ISR will apply a set of authorization and accounting rules to the user’s VPN session after successful authentication. Following this, the ISR will establish an acceptable VPN environment with the remote user. After the VPN environment is built, the client sends IP traffic into the IPsec tunnel using a virtual network interface that is created on the client by the Cisco VPN client. The client can now use an application to access any resource behind the ISR VPN gateway for which he has authorization.

The EZVPN Server can use either crypto maps or Virtual Tunnel Interfaces (VTI) to create the cryptographic tunnel contexts for remote users. This chapter covers the VTI-based EZVPN Server.

Deployment Tasks

image

Deploying a basic Cisco EZVPN on a Cisco ISR requires that the following deployment tasks be completed:

Task 1: Configure basic VTI-based EZVPN Server features. This includes configuring correct policies and profiles for IKE and IPsec. In this task, you configure groups that will contain client configuration settings as well as Internet Security Association and Key Management Protocol (ISAKMP) profiles for identifying multiple groups of remote users. The client configuration settings include network settings (DNS server, WINS server, domain suffix) and IP address assignment methods.

Task 2: (Optional) Configure the EZVPN Server and VPN client to use Public Key Infrastructure (PKI)–based authentication using certificates, instead of group pre-shared keys.

Task 3: Install the Cisco VPN client and configure it to connect to the ISR EZVPN Server.

Task 4: (Optional) Configure the Cisco ISR to run as a hardware VPN client.

Input Parameters

Prior to implementing the basic Cisco EZVPN Server, you must gather and analyze several pieces of information. These input parameters include the following:

• The IP addressing plan that will determine the VPN gateway addressing and the network-naming convention that will determine the name of the VPN gateway. This is needed to assign an IP address to the VPN-terminating interface on the ISR and to assign an appropriate name to the VPN gateway’s Secure Socket Layer/Transport Layer Security (SSL/TLS) identity certificate.

• The enterprise policy of user naming and the enterprise password to create a local user database on the ISR.

• The enterprise cryptographic policy to choose IKE and IPsec protocols that meet enterprise requirements.

• The IP addressing plan for remote clients. The ISR acting as an EZVPN Server must assign IP addresses to remote clients.

• Access policies that dictate the resources to which remote users have permission to access.

• A list of remote client platforms to be able to correctly provision the Cisco VPN client software image to clients.

Deployment Guidelines

image

When deploying the basic Cisco EZVPN solution using a Cisco IOS Software EZVPN Server, consider the following deployment guidelines:

• In general, the Cisco AnyConnect SSL VPN solution should be preferred over the EZVPN solution because it has much fewer issues with firewall traversal.

• Only use the basic EZVPN solution in low-risk environments where the risk associated with using static passwords for remote access is acceptable. Environments with higher risk levels should migrate to a solution that uses stronger forms of authentication such as certificates or one-time passwords.

• Consider using the basic EZVPN solution in environments that have little or no access control between the client and the ISR.

Configure and Verify a Basic Cisco IOS Software VTI-Based EZVPN Server

In the following sections, you configure the Cisco IOS Software EZVPN server. This includes configuring groups to which policy and profile settings will be applied as well as defining authentication mechanisms.

Group Pre-Shared Key Authentication

The basic EZVPN supports several levels of user and peer authentication. Peer authentication refers to the basic mutual authentication of two parties, such as the client and the ISR. With basic EZVPN, peer authentication uses group passwords that are configured on the ISR and on a group of VPN clients that typically share a common security policy. Extended Authentication (XAUTH) is an optional, one-way user authentication that can be added on top of the group passwords. XAUTH can support passwords or one-time passwords (OTP) and increases the security around remote access solutions in case the group password is compromised.

Group passwords are very vulnerable to compromise simply because of their shared nature. For example, if one laptop is stolen, the attacker will most likely be able to retrieve the group password from the system. If using XAUTH, this attacker would not have immediate access to internal resources because he would still need to provide valid user authentication credentials. However, having the group password would allow the attacker to launch a man-in-the-middle (MITM) attack and intercept the initial negotiation between the client and the ISR. The attacker would then be able to spoof the ISR’s identity (using the group password). The client would not be able to tell that it was communicating with the attacker and would send XAUTH credentials over the IKE session to the attacker, who could then use these credentials to log in to the VPN.

Extended Authentication (XAUTH) Overview

Extended Authentication is a feature that can be enabled during the IKE negotiation that provides one-way user authentication that is used in addition to the group peer authentication. XAUTH takes place after IKE phase 1 completes and before the IKE phase 2 (IPsec SA) negotiations begin. This process uses the encrypted IKE security association (SA) to send credentials from the client to the ISR.

XAUTH should be used to provide additional authentication for remote access users. It can also be used to provide per-user services such as per-user IP addresses or access rules.

The following sections provide configuration guidance for implementing XAUTH using the local user account configured on the EZVPN Server. However, it can very easily be configured to use authentication, authorization, and accounting (AAA) authentication methods to leverage the centralized nature of using RADIUS, TACACS+, or other authentication protocols.

Configuration Groups and ISAKMP Profiles

To enable group authentication and client configuration features, two configuration objects must be added to the configuration for each group of users:

• Client configuration groups: Client configuration groups are configuration objects in Cisco IOS Software that provide authentication credentials and network configuration parameters that are to be applied to all clients in the group. These parameters can include the IP addresses assigned to clients, Domain Name System (DNS) servers, domain suffix, and the optional split tunneling parameter.

• ISAKMP profiles: EZVPN Server uses ISAKMP profiles to bind an identity to a virtual tunnel interface and client configuration policy. In the EZVPN Server, the VPN gateway uses ISAKMP profiles to associate a particular user group identity to a VTI template interface and the client configuration group.

Configuration Tasks

image

The first deployment step for configuring the Cisco EZVPN solution is to configure basic EZVPN Server on the ISR. The following configuration tasks should be completed to accomplish this:

Task 1: (Optional) Configure an IKE policy for a key management session between the remote VPN client and the EZVPN Server. This permits the IKE policy on the ISR to be tuned to provide stronger cryptographic algorithms than what is provided for in the default IKE policies.

Task 2: Tune the ISR IPsec transform sets if there is a requirement for stronger cryptographic algorithms than what is provided for in the default IPsec transform sets.

Task 3: Configure a dynamic VTI template interface that the ISR will use to create tunnel interfaces for each remote user.

Task 4: Configure a client configuration group in which the group authentication credentials will be configured, along with the address assignment policy and, if needed, any optional client network parameters.

Task 5: Configure an ISAKMP profile that will bind the remote user group to the client configuration group.

Task 6: Configure a local AAA authentication method and add user accounts to the ISR local user database.

Task 7: Configure an existing ISAKMP profile to also use Extended Authentication (XAUTH) prior to permitting access.

Configuration Scenario

In the configuration sequence, basic EZVPN Server functionality will be enabled along with tuning IKE and IPsec policies on the ISR. A dynamic VTI template will be configured. The ISR will use its GigabitEthernet0/0 interface for its untrusted connection and the GigabitEthernet0/1 interface for its trusted connection.

Next, a client configuration group named MY-GROUP and an ISAKMP profile named MY-ISA-PROFILE will be created. The group name MY-GROUP, with a long, random group password, will be configured inside the client configuration group.

All clients will be assigned IP addresses in the 10.255.0.0/24 network, be given the IP address of an internal DNS server at 172.16.200.53, and enable split tunneling to only protect traffic to 10.0.0.0/8.

Finally, a user named vpnuser will be created in the local user database, and XAUTH will be required for the group MY-GROUP.

Task 1: (Optional) Verify an IKE Policy

The first configuration step is to configure a custom IKE (ISAKMP) policy on the EZVPN Server using the crypto isakmp policy command, as depicted in Example 21-1. If one is not configured, the EZVPN Server will use the default IKE policies.

Example 21-1. Configure an IKE Policy


router(config)# crypto isakmkp policy 10
router(config-isakmp)# authentication pre-share
router(config-isakmp)# lifetime 3600


Task 2: Configure an IPsec Transform Set and Profile

Task 2 involves configuring a specific transform set and binds it to a new IPsec profile, using the crypto ipsec transform-set and crypto ipsec profile commands, as shown in Example 21-2.

Example 21-2. Configure IPsec Transform Set and Profile


router(config)# crypto ipsec transform-set MY-TSET esp-aes esp-sha-hmac
router(cfg-crypto-trans)# exit
router(config)# crypto ipsec profile MY-PROFILE
router(ipsec-profile)# set transform set MY-TSET


Task 3: Configure a Dynamic VTI Template

In Task 3, you configure a virtual template interface of the type “tunnel” from which the common settings for all dynamic VTIs are defined. The VTI in Example 21-3 is configured with IP unnumbered to interface GigabitEthernet0/0, configured with an IPsec tunnel encapsulation, and given the IPsec profile called MY-PROFILE.

image

Example 21-3. Configure a Dynamic VTI Template


Router(config)# interface virtual-template 1 type tunnel
Router(config-if)# ip unnumbered GigabitEthernet0/0
Router(config-if)# tunnel mode ipsec ipv4
Router(config-if)# tunnel protection ipsec profile MY-PROFILE


Task 4: Create a Client Configuration Group

Task 4 involves configuring a client configuration group and all the necessary parameters for properly configuring remote clients. The associated commands are given in Example 21-4.

image

Example 21-4. Create a Client Configuration Group


Router(config)# ip local pool MY-POOL 10.255.0.1 10.255.0.100
!
Router(config)# ip access-list extended MY-SPLIT-TUNNEL
Router(config-ext-acl)# permit ip 10.0.0.0 0.255.255.255 any
!
Router(config) # crypto isakmp client configuration group MY-GROUP
Router(config-isakmp-group)# key Adjkj232902sdjiaf934892u@@akdlfj
Router(config-isakmp-group)# domain mydomain.com
Router(config-isakmp-group)# dns 172.16.200.53
Router(config-isakmp-group)# pool MY-POOL
Router(config-isakmp-group)# acl MY-SPLIT-TUNNEL


Configure a local pool of IP addresses using the ip local pool command. The address range needs to be large enough to support the expected number of remote users. Add an extended access list that defines the traffic that must be forwarded through the tunnel. This access list works in conjunction with the split tunneling feature that is enabled in the client configuration group parameters by using the acl command. Finally, create a named client configuration group using the crypto isakmp client configuration group command to create one called MY-GROUP in which client network parameters will be configured as well.

Task 5: Create an ISAKMP Profile

Task 5 creates an ISAKMP profile that will match the identity of remote users and enable client configuration and VTI interfaces for the group. The associated commands are given in Example 21-5.

image

Example 21-5. Create an ISAKMP Profile


Router(config)# aaa authorization network LOCAL-AUTHOR local
!
Router(conf-isa-prof)# crypto isakmp profile MY-ISA-PROFILE
Router(conf-isa-prof)# match identity group MY-GROUP
Router(conf-isa-prof)# isakmp authorization list LOCAL-AUTHOR
Router(conf-isa-prof)# client configuration address respond
Router(conf-isa-prof)# client configuration group MY-GROUP
Router(conf-isa-prof)# virtual-template 1
!
Router(config)# crypto ipsec profile MY-PROFILE
Router(ipsec-profile)# set isakmp-profile MY-ISA-PROFILE


Begin by configuring the local network AAA authorization list with the aaa authorization network command. This will tell the router to use only the locally configured user database on the router for its authorization resource. Then, create the named ISAKMP profile using the crypto isakmp profile command. Example 21-5 uses the MY-ISA-PROFILE ISAKMP profile with the following additional parameters:

• Use the match identity group command to identify the group name that this ISAKMP profile will use.

• Use the isakmp authorization list command to point to an existing AAA authorization list.

• Use the client configuration address respond command to tell the EZVPN Server to respond to client requests for IP addresses.

• Use the client configuration group command to specify the configuration group that is to be associated with this ISAKMP profile.

• Use the virtual-template command to bind this ISAKMP profile (group of users) to a specific local dynamic VTI interface.

Tasks 6 and 7: Configure and Enable User Authentication

If there is a requirement for an additional level of authentication, configure the EZVPN Server to require XAUTH. Begin by creating a new local AAA authentication method using the aaa authentication login command. Then, create local user accounts in the local user database. Finally, configure the requirement for Extended Authentication (XAUTH) inside the existing MY-ISA-PROFILE ISAKMP profile using the client authentication list command. Perform these commands as shown in Example 21-6.

image

Example 21-6. Configure and Enable User Authentication


Router(config)# aaa authorization login LOCAL-AUTHEN local
!
Router(config)# username vpnuser privilege 0 secret 438ajdkjGT980u1
!
Router(config)# crypto isakmp profile MY-ISA-PROFILE
Router(conf-isa-prof)# client authentication list LOCAL-AUTHEN


Cisco Configuration Professional Support

Cisco Configuration Professional (CCP) can be used to configure the Cisco EZVPN Server on a Cisco Integrated Services Router running Cisco IOS Software. The tool includes a wizard through which the administrator will be taken to create a new EZVPN Server function on the router. For authentication, CCP supports both using group keys and also extended user authentication. In addition, advanced deployments using certificate-based authentication are supported by Cisco Configuration Professional.

Manual configuration of the EZVPN Server feature can be performed in CCP as well. The network administrator can manually configure a new instance of EZVPN Server or discover an existing configuration by downloading it from a reachable router.

Note

Documentation for Cisco Configuration Professional can be found at www.cisco.com/en/US/docs/net_mgmt/cisco_configuration_professional/v2_4/olh/ccp.pdf.

Implementation Guidelines

When implementing a basic EZVPN solution, take the following implementation guidelines into consideration:

• If possible in the environment, create groups of users that are relatively limited in size. This way, if a group password is compromised, the numbers of connections that are vulnerable to attack are limited. This makes it easier to reconfigure the clients with a new group password.

• If the risk of a group password being compromised is too high, consider deploying PKI-based authentication. This will provide a stronger level of authentication and makes the peer authentication process resistant to a man-in-the-middle attack.

Configure the Cisco VPN Client

The second piece of the EZVPN solution is the Cisco VPN client. The following sections cover installing the client software.

Configuration Tasks

image

To deploy Cisco VPN clients in a basic Cisco EZVPN solution, the following configuration tasks should be completed:

Task 1: Install the Cisco VPN client on the systems.

Task 2: Configure the Cisco VPN client connection entry settings. These settings are the IP address of the EZVPN Server, the group name, and group password.

Task 3: Establish the EZVPN connection using the Cisco VPN client.

Configuration Scenario

In the configuration sequence, the Cisco VPN client will be configured on a Microsoft Windows XP system and configured to connect to an ISR at 172.16.1.1. The VPN client will use the MY-GROUP group name with a strong password. The remote user will use the vpnuser account to satisfy the XAUTH requirement.

Task 1: Install the Cisco VPN Client Software

You can find guidance for this task on Cisco.com.

Task 2: Configure the VPN Client Connection Entry

After the Cisco VPN client is installed, configure the connection entry that will provide the parameters to successfully establish a connection to the Cisco EZVPN Server. Perform the following steps to accomplish this:

Step 1: Start the Cisco VPN client.

Step 2: In the main window, click the New button to create a new connection entry.

Step 3: In the Connection Entry field, specify a name that describes the connection and optionally add a description.

Step 4: In the Host field, specify the IP address of the ISR untrusted interface (172.16.1.1).

Step 5: On the Authentication tab, select the group authentication method and enter the group name and password.

Step 6: Click Save to save the profile.

Task 3: Establish the EZVPN Connection

To test and verity the connection, select the configuration profile created in Task 2 and click the Connect button. When connected successfully, the Cisco VPN client will minimize itself by default.

Client-Side Verification

After the client is successfully connected, the ISR will push network configuration items to the client and provide the client with its IP address. Right-click the Cisco VPN Client system tray icon and choose to view Statistics. This will display connection details, including the assigned IP address, the negotiated cryptographic algorithms, and some statistical information on packets received and transmitted.

Navigate to the Route Details tab of the Statistics window and observe the network listed in the Secured Routes pane. The default of 0.0.0.0/0 indicates that all traffic is being protected by the tunnel, while an entry of 10.0.0.0/8 indicates that only 10.0.0.0/8 is being protected and any other traffic is simply forwarded out the system’s normal network interface.

Gateway-Side Verification

Use the show crypto session username command on the ISR to verify the client’s connection, as demonstrated in Example 21-7.

Example 21-7. show crypto session username Command Output


Router# show crypto session cisco


Crypto session current status
Interface: Virtual-Access2
Username: cisco
Profile: prof
Group: easy
Assigned address: 10.3.3.4
Session status: UP-ACTIVE
Peer: 10.1.1.2 port 500

  IKE SA: local 10.1.1.1/500 remote 10.1.1.2/500 Active
  IKE SA: local 10.1.1.1/500 remote 10.1.1.2/500 Inactive
  IPSEC FLOW: permit ip 0.0.0.0/0.0.0.0 host 3.3.3.4
        Active SAs: 2, origin: crypto map


Configure and Verify VTI-Based EZVPN Remote Client Functionality on the Cisco ISR

Cisco EZVPN Remote allows a Cisco ISR or Cisco ASA to also act as a remote hardware VPN client with minimal configuration to connect to the VPN gateway.

The remote device is configured with authentication credentials and the IP address of the EZVPN Server and then receives the rest of its network configuration from the server client configuration object. To the EZVPN Server, there is no difference between a software VPN client and the EZVPN Remote hardware devices.

The Cisco EZVPN Remote feature supports a two-part process for authenticating the remote router to the central Cisco EZVPN Server:

• Group-level authentication: The first step is group-level authentication. This is part of the creation of the control channel and can use two types of authentication credentials:

• PSKs: Pre-shared keys mean that each peer has the key of the other peer.

• Digital certificates: This provides support for using RSA signatures for EZVPN Remote devices, which is much more secure than PSKs.

• Extended Authentication (XAUTH): This is an optional, additional level of authentication that can be used in addition to the group authentication. The remote client (the Cisco EZVPN Remote hardware device) sends a username and password to the EZVPN Server just as it is done with the Cisco VPN Software Client. The difference is that when using the router, the router itself is being authenticated as opposed to a user. After the XAUTH is successful, all PCs behind the Cisco EZVPN Remote router have access to the VPN tunnel.

If XAUTH is being used, it must be decided where to store the authentication credentials:

• Store the XAUTH username and password in the configuration file on the router: This option is typically used if the router is shared between many PCs and the goal is to have the VPN tunnel up all the time.

• Do not store the XAUTH username and password on the router: If this option is used, a PC user who is connected to the router is presented with a web page that allows the username and password to be manually entered.

EZVPN Remote Modes

image

The Cisco EZVPN Remote feature on hardware clients supports three modes of operation:

• Client mode: NAT and PAT are used to allow PCs and other hosts on the client side of the VPN to form a private network that does not use any IP addresses in the IP address space of the destination server. This mode automatically configures NAT or PAT translation and the ACLs needed to implement the VPN connection. These are temporary and automatically deleted from the configuration when the tunnel is torn down. The disadvantage of this mode is that the PCs on the client side are not reachable for sessions initiated from the central site.

• Network Extension mode: In this mode, PCs and hosts on the client side are given routable IP addresses that are fully reachable over the tunneled connection. PAT is not used in this option.

• Network Extension plus mode: This mode is identical to network extension mode with the additional capability of being able to request an IP address through IKE mode configuration and automatically assign it to an available loopback interface. The IPsec SAs for this IP address are automatically created by Cisco EZVPN Remote.

All three modes support split tunneling if there is a need for it. This allows traffic to corporate resources to be protected by the tunnel while Internet access is allowed to flow straight out of the service provider’s connection to the Internet.

Configuration Tasks

image

To configure a Cisco ISR running Cisco IOS Software as an EZVPN Remote hardware client, perform the following tasks:

Task 1: Configure the EZVPN Remote connection profile on the EZVPN Remote hardware client.

Task 2: Designate the EZVPN interface roles on the EZVPN Remote hardware client.

Configuration Scenario

The Cisco EZVPN Remote feature will be configured on a Cisco ISR router. It will be configured to connect to a central Cisco ISR EZVPN Server and while operating in client mode that will use a group name and user name for identification and passwords for authentication.

Task 1: Configure EZVPN Remote Profile

Task 1 involves configuring the EZVPN Remote hardware feature by creating a local VTI template and configuring a connection profile that identifies the EZVPN Server, determines the hardware client’s mode, and provides authentication credentials.

Begin with creating a VTI template of type “tunnel” using the virtual-template command, specify that it should use IPsec tunnel mode. Next, create a named EZVPN Remote connection profile using the crypto ipsec client ezvpn command. Example 21-8 shows the configuration with the profile settings:

• Use the group command to specify the group name and group password to authenticate to the EZVPN Server as a part of a group.

• Use the username command to specify the stored username and password used to provide additional authentication using XAUTH.

• Use the virtual-interface command to specify the local VTI template that will be used to create a tunnel interface for this connection.

• Use the peer command to identify the EZVPN Server to connect to.

• Use the mode client command to specify that the client will use client mode when establishing a connection to the VPN.

image

Example 21-8. Configure an IKE Policy


Router(config)# interface virtual-template1 type tunnel
Router(config-if)# tunnel mode ipsec ipv4
Router(config-if)# crypto ipsec client ezvpn MY-EXVPN-CLIENT
Router(config-crypto-ezvpn)# group MY-GROUP key AkjAFert32892Aaf2323AADF
Router(config-crypto-ezvpn)# virtual-interface 1
Router(config-crypto-ezvpn)#  peer 172.16.1.1
Router(config-crypto-ezvpn)#  mode client
Router(config-crypto-ezvpn)#  username vpnuser password 48u34ERW5325


Task 2: Designate EZVPN Interface Roles

Task 2 designates local interfaces as either inside (trusted) or outside (untrusted) to inform the EZVPN Remote function so that it can properly apply NAT (in client mode) or identify the protected network (in network extension mode).

Designate local interfaces in interface configuration mode using the crypto ipsec client ezvpn command with either the inside or outside arguments, as displayed in Example 21-9.

image

Example 21-9. Configure IPsec Transform Set and Profile


Router(config)# interface FastEthernet0/0
Router(config-if)# crypto ipsec client ezvpn MY-EZVPN-CLIENT outside
Router(config-if)# exit
Router(config)# Interface FastEthernet0/1
Router(config-if)# crypto ipsec client exvpn MY-EXVPN-CLIENT inside


Implementation Guidelines

image

When implementing EZVPN Remote, consider the following guidelines:

• EZVPN Remote hardware clients are most appropriately implemented in a strict hub-and-spoke environment. The major advantage of using EZVPN is that it supports dynamically addressed spokes.

• If the remote network requires only outbound connectivity, use EZVPN Remote in client mode. If the remote network requires two-way connectivity, use the EZVPN Remote solution in network extension mode.

Configure and Verify EZVPN Server and VPN Client PKI Features

EZVPN solutions can be deployed using certificates instead of group passwords to provide bidirectional authentication between remote clients and the EZVPN Server. This method of authentication will require all EZVPN devices to have an identity certificate that was provisioned by a trusted PKI and the CA certificate to verify the peer’s certificate in the IKE peer authentication process.

Certificate-based EZVPN implementations can mitigate the MITM issue that is created by using group passwords.

Head-End PKI Configuration

image

To enable EZVPN Server to use certificates instead of group passwords for authentication, and to authenticate itself to a group of users, perform the following steps, as portrayed in Example 21-10:

Step 1: Enroll the EZVPN Server router into the PKI by creating a trustpoint, authenticating a CA, and obtaining an identity certificate.

Step 2: Specify the local identity of the router in the ISAKMP profile using the self-identify fqdn command and reference the identity specified in the PKI trustpoint.

Step 3: Inside the ISAKMP profile, specify the local trustpoint with the ca trust-point command.

Step 4: Use the match identity group command to specify the identity of remote clients. Enroll remote clients so that the Organizational Unit (OU) field in their identity certificate contains their group name.

image

Example 21-10. Head-End PKI Configuration


Router(config)# crypto pki trustpoint MY-TP
Router(ca-trustpoint)# fqdn vpn.mydomain.com
Router(ca-trustpoint)# subject-name cn=vpn.mydomain.com
Router(ca-trustpoint)# exit
Router(config)# crypto isakmp profile MY-ISA-PROFILE
Router(conf-isa-prof)# self-identity fqdn vpn.mydomain.com
Router(conf-isa-prof)# ca trust-poitn MY-TP
Match identity group MY-GROUP


VPN Client Configuration: SCEP Enrollment

image

To enroll the Cisco VPN client into a PKI, use the Simple Certificate Enrollment Protocol (SCEP) client that is a part of the Cisco VPN client to retrieve the CA certificate and to enroll into a PKI. Perform the following steps:

Step 1: In the Cisco VPN client interface, navigate to the Certificate tab and click the Enroll button.

Step 2: Choose Online in the Certificate Enrollment window. Specify the CA URL and the local domain in the CA Domain field. Click Next to continue.

Step 3: In the next window, enter the parameters that will determine the client’s name inside the certificate. The VPN group name should be used as the OU field of the certificate. Click Enroll to complete the enrollment request.

VPN Client Enrollment Verification

The Cisco VPN client will now retrieve the CA certificate from the SCEP server and periodically poll the SCEP server to retrieve its identity certificate. The validity of the issued certificate can be verified by clicking the Verify button. The fields of the certificate will be displayed in a new window, allowing the information in the certificate (especially the OU that must match the group name) and the validity dates of the certificate.

VPN Client Configuration: Profile

To configure a connection profile that will use certificate-based authentication, perform the following steps on the Cisco VPN client:

Step 1: Start the Cisco VPN client.

Step 2: In the Cisco VPN client main window, click the New button to create a new connection entry.

Step 3: In the Connection Entry field, enter a locally significant name and an optional description.

Step 4: In the Host field, enter the IP address of the ISR untrusted interface (172.16.1.1).

Step 5: On the Authentication tab, select the certificate authentication method and select the proper identity certificate from the drop-down list.

Step 6: Click Save to save the profile.

Troubleshoot Basic EZVPN Operation

To provide the same stability with a VPN connection that is achieved with traditional circuits, you must be able to troubleshoot and restore the connectivity.

Troubleshooting Flow: VPN Session Establishment

To troubleshoot issues with session establishment, perform the following steps:

Step 1: Check that IKE and IPsec protocols successfully negotiated based on matching IKE and IPsec policies on the client on the ISR. The debug crypto isakmp and debug crypto ipsec commands display information helpful to identifying mismatched parameters.

Step 2: Verify that user authentication works. Use the debug aaa authentication command to display the AAA functions and output.

Step 3: Verify that the router is able to assign IP addresses to the client. The ISR will indicate failures to assign an IP address in the output of the debug crypto isakmp command.

Troubleshooting Flow: VPN Data Flow

If the EZVPN session establishes successfully but connectivity over the tunnel fails, perform the following troubleshooting steps:

Step 1: If using split tunneling, check that the correct routes are being protected and that they are present in the routing table.

Step 2: Verify that the ISR is not denying traffic from the VPN tunnel.

Step 3: Verify that the protected network has a route to the client-assigned addresses by examining the routing tables of routers on the internal network.

Exam Preparation

As mentioned in the section, “How to Use This Book,” in the Introduction, you have several choices for exam preparation: the exercises here, the memory tables in Appendix C, the final exam preparation chapter, and the exam simulation questions on the CD-ROM. The following questions present a bigger challenge than the exam itself because they use an open-ended question format. By using this more difficult format, you exercise your memory better and prove your conceptual and factual knowledge of this chapter. You can find the answers to these questions in Appendix A, “Answers to the DIKTA Quizzes and Fill in the Blanks Questions.”

Review All Key Topics

Review the most important topics in the chapter, noted with the Key Topics icon in the margin of the page. Table 21-2 lists a reference of these key topics and the page numbers on which each is found.

Table 21-2. Key Topics

image

Complete Tables and Lists from Memory

Print a copy of Appendix C, “Memory Tables” (found on the CD), or at least the section for this chapter, and complete the tables and lists from memory. Appendix D, “Memory Table Answers,” also on the CD, includes completed tables and lists to check your work. Although this chapter doesn’t have any memory tables, you will find some that are applicable in other chapters.

Define Key Terms

Define the following key terms from this chapter, and check your answers in the Glossary:

Cisco Easy VPN Server

Cisco Easy VPN Remote. Extended Authentication (XAUTH)

Client configuration groups

EZVPN Client mode

EZVPN Network Extension mode

EZVPN Network Extension plus mode

Fill in the Blanks

  1. Hosts behind the remote VPN router are not reachable for a session initiated from the central site in _____ mode.
  2. The Easy VPN client can be the Cisco VPN client or an Easy VPN Remote hardware device such as the _____.
  3. The Cisco Easy VPN Server can _____ IPsec tunnels that are initiated by remote users running VPN client software on their systems.
  4. As the Cisco Easy VPN Remote initiates a VPN tunnel, the Cisco Easy VPN _____ pushes the IP Security (IPsec) policies to the Cisco Easy VPN Remote _____ and creates the corresponding VPN tunnel connection.
  5. XAUTH takes place _____ IKE phase 1 completes and _____ the IKE phase 2 (IPsec SA) negotiations begin.
  6. Group passwords are very vulnerable to compromise simply because of their _____ nature.
  7. Configuring a basic Cisco ISR Easy VPN _____ consists of basic gateway configuration, group authentication, client configuration, and user authentication configuration.
  8. The Cisco ISR can be used as an Easy VPN Remote _____.
  9. You can enhance authentication by using _____ on remote clients and the Easy VPN Server.

Reference

Cisco IOS Security Command Reference, www.cisco.com/en/US/docs/ios/security/command/reference/sec_book.html.