Chapter 20. Deploying Remote Access Solutions Using SSL VPNs

This chapter covers the following subjects:

• Choose an appropriate remote access VPN technology: Covers the decisions and considerations you need to make to select the appropriate remote access VPN technology for your environment.

• Choose appropriate remote access VPN cryptographic controls: Covers choosing the proper cryptographic controls to meet the security requirements for your organization.

• Plan the deployment of a Cisco IOS Software SSL VPN gateway: Covers gathering input and making decisions that are necessary for a successful SSL VPN gateway deployment.

• Configure and verify common SSL VPN parameters: In this section, you configure and verify the most common SSL VPN parameters.

• Configure and verify client authentication and policies on the SSL VPN gateway: For clients to connect to your gateway, it must be configured with parameters that can be matched by the clients. This section covers configuration and verification of client authentication and policies.

• Configure and verify full tunneling connectivity on the Cisco IOS SSL VPN gateway: Covers configuring the SSL VPN gateway to allow full tunneling for your clients.

• Install and configure the Cisco AnyConnect client: Covers configuring the Cisco AnyConnect client. There are many parameters that must match the policies on the SSL VPN gateway.

• Configure and verify clientless access on the Cisco IOS SSL VPN gateway: The SSL VPN gateway can also be configured to allow clientless access. This section covers the configuration of the necessary parameters to allow this type of connectivity.

• Troubleshoot the basic SSL VPN operation: Now that you have configured several different methods of VPN connectivity on the Cisco IOS SSL VPN gateway, you learn how to perform basic troubleshooting steps.

Remote access Virtual Private Network (VPN) technologies allow mobile workers to access internal resources over untrusted networks. The access is provided using transmission protection and access authentication and authorization technologies. Cisco IOS Software provides a set of remote access VPN features from which to choose. This chapter will discuss a comparison of remote access VPN technologies and then cover configuring, verifying, and troubleshooting a basic client-based and clientless SSL VPN solution on a 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 13-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 20-1 outlines the major topics discussed in this chapter and the “Do I Know This Already?” quiz questions that correspond to those topics.

Table 20-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. Which type of SSL VPN architecture supports any IP application without application modification?

a. Full tunneling

b. Split tunneling

c. Clientless tunneling

d. None of these answers are correct.

2. Which type of VPN architecture allows remote users URL and CIFS file access to internal resources through a web browser?

a. Split tunneling

b. Full tunneling

c. Clientless

d. Terminal services

e. None of these answers are correct.

3. What provides endpoint authentication for both the client and the server?

a. Web browser

b. SHA-1

c. TCP traffic

d. SSL/TLS

e. None of these answers are correct.

4. What can directly influence the strength of protection provided by algorithms such as 3DES or AES?

a. Key length

b. Firewall rules

c. IPS inspection engine

d. Certificate expiration date

e. None of these answers are correct.

5. What are the two choices of SSL VPNs?

a. Clientless with a web browser

b. Cisco AnyConnect VPN client

c. Proxy mode

d. None of these answers are correct.

6. After authentication, what does the Cisco ISR apply a set of to the user session?

a. Static routes

b. Split tunneling routes

c. Authorization rules

d. None of these answers are correct.

7. The SSL VPN gateway is enabled on the Cisco ISR with which command?

a. inservice

b. ssl vpn enable

c. gateway

d. vpn enable

e. None of these answers are correct.

8. For proper authentication, what must be provisioned to the Cisco ISR?

a. Memory upgrade

b. IOS upgrade

c. Identity certificate

d. CA ROOT certificate

9. By default, which kind of certificate does the ISR create upon each reboot that will cause client warnings when attempting SSL VPN access because the certificate cannot be verified?

a. Certificate authority

b. Certificate CA

c. Self-signed X.509 certificate

d. ROOT certificate

10. What is assigned to the client as it connects in full tunnel mode?

a. A unique client ID number

b. A list of software to install

c. IP address

d. ROOT certificate

11. What is required for the initial installation of the Cisco AnyConnect client?

a. On-site technician

b. Terminal services session

c. Administrative privilege

d. Memory upgrade

12. What can users use to access internal resources with the ISR performing as a proxy to provide internal content on its SSL VPN portal?

a. SSH

b. Telnet

c. Web browser

d. Terminal session

13. What should be alleviated first as a factor for troubleshooting?

a. Authentication problems

b. Verify that the service is running

c. Connectivity issues

d. Proper authorization

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:

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

• 11 or more overall score: If you want more review on these topics, skip to the “Exam Preparation” section. Otherwise, move on to Chapter 21, “Deploying Remote Access Solutions Using EZVPN.”

Foundation Topics

This chapter covers making appropriate choices of VPN technologies and cryptographic controls on a Cisco Integrated Services Router (ISR) for remote access. This chapter also covers basic SSL VPN implementation in detail.

Choose an Appropriate Remote Access VPN Technology

Remote access VPNs connect individual remote users to a set of resources on an organization’s internal network. In some cases, it might connect them to a perimeter, extranet, or other exterior buffer type of network. Remote access (RA) VPNs typically use very strong client authentication, which requires users to prove their identity and encryption to protect transmissions across an untrusted network, typically the Internet.

Many RA VPNs employ various security controls above and beyond authentication and transmission protection, such as strictly limiting access to resources or assessing the security posture of remote clients prior to permitting access to the internal network.

Cisco IOS Software Remote Access VPN Options

Cisco IOS Software running on the Integrated Services Router (ISR) provides a wide array of remote access VPN technologies. These technologies differ in how they encapsulate user traffic and in the transmission protection (encryption) they provide.

The two primary encapsulation methods for deploying VPNs are SSL/TLS and IPsec cryptographic encapsulation protocols. Both offer authentication and transmission security features. There are two major modes for encapsulating user traffic:

• Full tunneling VPNs: Require VPN client software to be installed on the remote computer or dedicated VPN devices (hardware clients) to enable full routed IP access to internal resources. Cisco IOS Software provides support for SSL VPNs and IPsec (Easy VPN, or EZVPN) full tunneling software clients. The Cisco ISR acts as the remote access VPN gateway to which the remote user VPN sessions terminate. An ISR can also perform as an EZVPN IPsec hardware client, which would provide access to the VPN for an entire remote network.

• Clientless VPN: Access to corporate resources can be provided to remote users even when the remote device is not managed nor is there any VPN client software. Clientless deployments require that the user open a web browser, which acts as the VPN client, and the VPN gateway acts as a proxy device to the internal resources. This solution also allows organizations to provide a web portal interface to remote users from which they can launch applications to which they have been granted access. Clientless VPNs are easier to deploy than a full tunneling remote access VPN, but they typically provide limited access to resources when compared to the full tunnel.

Full Tunneling Remote Access SSL VPN: Features

In the full tunneling VPN architecture, remote users use the Cisco AnyConnect VPN client to establish a Secure Socket Layer/Transport Layer Security (SSL/TLS) tunnel with the Cisco ISR. After successful mutual authentication, the Cisco ISR will apply a set of authorization and accounting rules to the user’s session. Next, after the Cisco ISR establishes a VPN environment for the remote user, the remote user can forward IP traffic into the SSL/TLS tunnel. This is done by the Cisco AnyConnect client creating a virtual network interface on the client through which all protected traffic is forwarded. The client can use any application to access any resource behind the Cisco ISR VPN gateway that is within the user’s authorization rules.

Full Tunneling Remote Access SSL VPN: Benefits and Limitations

Table 20-2 lists the benefits and limitations of the full tunneling SSL VPN architecture.

Table 20-2. Benefits and Limitations of Full Tunneling SSL VPN Architecture

image

Clientless Remote Access SSL VPN: Features

In the clientless remote access VPN architecture, remote users use their web browser to establish an SSL/TLS session with the Cisco ISR. After successful mutual authentication, the Cisco ISR will apply a set of authorization and accounting rules to the user’s session and the user is presented with a web portal. The Cisco ISR can also deploy advanced security controls, such as a virtual desktop or a posture assessment to the VPN session.

Clientless SSL VPNs do not provide full network access like the full tunneling VPNs. To allow clientless remote access users to access corporate applications, the security appliance (ISR) acts as a proxy. It converts web and even some nonweb applications so that they can be protected by SSL. The Cisco ISR offers the following techniques to provide resource and application access:

• URL and Common Internet File System (CIFS) file access: When the client browser establishes the SSL session and the user is authenticated, the gateway can present a page with resource bookmarks. These allow the user to access preconfigured web pages or file shares. The user can also enter an address of a resource and access it that way if it is within the user’s permission.

• Port forwarding: Provides access to TCP-based applications by mapping application-specific ports on the remote computer to application-specific ports on the internal servers. Port forwarding requires that a Java applet be downloaded to the client. This applet listens on ports on the client machine and forwards the connection to the gateway.

Clientless SSL VPN: Benefits and Limitations

Table 20-3 lists the benefits and limitations of the clientless SSL VPN architecture.

Table 20-3. Benefits and Limitations of Clientless SSL VPN Architecture

image

Software Client Remote Access IPsec VPN (EZVPN): Features

The third remote access VPN architecture support on the Cisco ISR is the full tunneling client-based IPsec VPN architecture. With this option, remote users use the Cisco VPN client to build an IPsec tunnel with the Cisco ISR. Just as with the full tunneling remote access SSL VPN, after mutual authentication has taken place, the Cisco ISR will apply a set of authorization and accounting rules to the user’s session. After the Cisco ISR establishes the appropriate VPN policy for the remote user, the user can transmit IP traffic into the IPsec tunnel. The client can use any application to access any resource to which he has authorization to access.

Hardware Client Remote Access IPsec VPN (EZVPN): Features

Another variation of the full tunneling IPsec VPN architecture is one in which the remote VPN endpoint is a hardware client device, such as another Cisco ISR. The hardware client device can provide remote access for an entire remote network and uses the same policies and configuration as software VPN clients.

Remote Access IPsec VPN: Benefits and Limitations

Table 20-4 lists the benefits and limitations of the full tunneling IPsec architecture.

Table 20-4. Benefits and Limitations of Full Tunneling IPsec Architecture

image

VPN Access Methods: Use Cases

Table 20-5 provides information to assist in choosing an appropriate VPN architecture.

Table 20-5. VPN Access Methods: Use Cases

image

Choose Appropriate Remote Access VPN Cryptographic Controls

Choosing the appropriate cryptographic controls for traffic that will traverse your remote access VPN is just as important as choosing the remote access VPN technology. The level of protection required by your organizational security policy should dictate the cryptographic controls that are implemented in your remote access VPN solution.

SSL/TLS Refresher

Transport Layer Security (TLS) and its predecessor, Secure Socket Layer (SSL), are cryptographic protocols that provide security for transmissions of public transports such as the Internet. These protocols are most often found in applications such as web browsing, electronic mail, and Voice over IP (VoIP).

The SSL protocol was developed by Netscape in 1994 to protect web transactions. Netscape developed SSL until version 3.0. In 1999, the IETF adopted SSL and called it Transport Layer Security (TLS). TLS is also known as SSL version 3.1.

Note

TLS version 1.0 is not compatible with SSL version 3.0 because TLS uses Diffie-Hellman and DSS (Data Security Standard) while SSL uses RSA (Rivest, Shamir, and Adelman). See RFC 2246 for further details.

Most web browsers have implemented SSL version 3.0 or 3.1 (TLS 1.0). Many other applications, such as SSL VPN clients, also use SSL/TLS for transmission protection.

SSL/TLS provides endpoint authentication for the client and the server, data encryption to ensure confidentiality, and data integrity/authentication to ensure data integrity. This protects traffic as it flows over public networks such as the Internet.

SSL/TLS is designed to do the following:

• Authenticate the server to the client

• Authenticate the client to the server (optional)

• Select joint cryptographic algorithms

• Generate shared secrets

• Build a protected connection (SSL/TLS tunnel) to secure TCP and UDP connections

Session and Key Management

Both the SSL and TLS protocols work in two phases:

• Session establishment phase: When the negotiation of parameters and peer authentication takes place.

• Data transfer phase: User data is exchanged securely between encapsulating endpoints.

Both phases take place inside the SSL/TLS Record Protocol.

Three subphases comprise the session establishment phase:

• In subphase 1, hello messages are exchanged to negotiate parameters including authentication and encryption algorithms.

• In subphase 2, one-way or two-way authentication between the client and server is performed. Unlike most authentication solutions where server authentication is optional, with HTTP and SSL, it is client authentication that is optional. A master key is also sent by the client using the public key of the server to start protecting the session.

• In subphase 3, the session key is calculated and the cipher suite is activated. Data integrity is provided by Hash-based Message Authentication Code (HMAC) using either Secure Hash Algorithm 1 (SHA-1) or Message Digest 5 (MD5). Confidentiality will be DES-40, DES-CBC, 3DEC-EDE, 3DES-CBC, RC4-40, or RC4-128.

Session keys are created using one of the following:

• RSA, where a shared secret is encrypted using the public key of the other peer.

• A fixed Diffie-Hellman (DH) key exchange, which uses a fixed DH value contained in a certificate.

• An ephemeral DH key exchange, which is based on the actual DH value signed with the private key of the sender. This provides the best protection because each session will have a different set of keys.

• An anonymous DH key exchange with no certificates or signatures. This should be avoided because it cannot prevent a man-in-the-middle attack because of the anonymity.

After the session keys are exchanged, SSL and TLS transmit data that is encapsulated inside an SSL- or TLS-encrypted envelope. This is the data transfer phase of the SSL/TLS protocols.

Each SSL session has a session ID that is exchanged during the authentication process. It differentiates between new and old sessions because sometimes old session IDs might be cached.

SSL can resume a session even if the TCP communication is interrupted. The client can request that the server resume an existing SSL session. The server will resume the SSL session if the server still has the session ID in its cache.

Transmission Protection

The SSL/TLS Record Protocol provides cryptographic envelopes to data being protected between the client and server. Application data is split into chunks (records) that are cryptographically protected (encrypted), and then a header and trailer are added. A series of these SSL records is then forwarded down to TCP or UDP for transmission.

Four record types are defined for signaling and secure data exchange. One record can contain up to 16,384 data bytes. The other three types are special records that exist for handshakes, signaling cipher change, and alert messages. Each record has a header, and data has an HMAC. Both the data and the HMAC are encrypted. There is also an option to compress the data portion.

Algorithm Choices in Cisco SSL Remote Access VPNs

Choosing the correct cryptographic control depends on the criticality of the data and the transport over which it is being sent. Table 20-6 provides a breakdown with recommendations.

image

Table 20-6. Algorithm Choices for Cisco SSL VPNs

image

It is recommended to use SSL 3.0 and TLS 1.x. Avoid version 2.0 of the SSL protocol because of known vulnerabilities in that version.

For encryption, Ron’s Code 4 (RC4), Advanced Encryption Standard (AES), and Triple DES (3DES) are good choices typically trusted by the industry. AES 128-bit is preferred over the other key lengths of AES because of noncritical weaknesses in the 192-bit and 256-bit versions of AES.

For HMAC integrity and authentication, SHA-1 is recommended over MD5.

IKE Remote Access VPN Extensions

In IPsec remote access VPNs, the IKE protocol has built-in extensions for user authentication and remote system configuration. These properties are

• IKE extended authentication (XAUTH): XAUTH provides an additional user authentication step after IPsec peers have mutually authenticated each other. XAUTH supports user authentication using static and one-time passwords.

• IKE mode configuration: This allows the gateway to configure network parameters on the client. This feature can configure parameters such as assigning a client a tunnel IP address and configuring the client DNS servers, WINS servers, and split tunneling routes.

Both extensions take place after IKE peer authentication (IKE phase 1) and before IPsec policy negotiation (IKE phase 2).

Algorithm Choices in Cisco IPsec Remote Access VPNs

For IPsec remote access, use the guidelines as summarized in Table 20-7, which provides a breakdown with recommendations.

image

Table 20-7. Algorithm Choices for Cisco IPsec VPNs

image

For encryption, both AES and 3DES are good, trusted choices, with AES-128 being the preferred one.

For HMAC integrity and authentication, SHA-1 is recommended over MD5.

With asymmetric algorithms, RSA is recommended, provided that long-enough keys are used and the private key is adequately protected. Pre-shared keys can be used, but RSA is recommended.

For key exchange in IPsec, the Diffie-Hellman algorithm is trusted, provided that long-enough keys are used.

With many algorithms, the key length used directly affects the effectiveness of that algorithm. Table 20-8 provides recommended minimum key lengths for different uses.

image

Table 20-8. Key Length Recommendations

image

Deploying Remote Access Solutions Using SSL VPNs

The Cisco IOS Software SSL VPN solution provides a choice to users by allowing either a client-based or clientless connection to a remote access VPN gateway that is implemented on a Cisco Integrated Services Router (ISR). A basic SSL VPN uses user authentication using usernames and static passwords and a single access control policy that applies to all users. This chapter describes how to configure, verify, and troubleshoot a basic client-based or clientless SSL VPN on the Cisco ISR.

Solution Components

The basic Cisco IOS Software SSL VPN solution entails remote users using either the Cisco AnyConnect VPN client or a web browser to create an SSL/TLS connection with the SSL VPN gateway running on the Cisco IOS Software–based ISR.

The basic SSL VPN uses bidirectional authentication, in which the client authenticates the ISR with a certificate-based authentication method and the ISR authenticates the user based on a username and password against its local user database. Upon successful authentication, the Cisco ISR will apply authorization and accounting rules to the user’s session. After the ISR has established a secure VPN with the remote user, the user will be able to either securely transmit IP traffic into the SSL/TLS tunnel created by the AnyConnect client or use a web browser to request resources that are behind the Cisco ISR.

Deployment Tasks

image

The basic deployment tasks for creating a basic Cisco IOS Software SSL VPN with either the client-based or clientless solution are as follows:

Task 1: Configure the ISR with basic SSL VPN gateway features to include provisioning a certificate to enable SSL/TLS server authentication. This task is covered in detail in the section, “Configure and Verify Common SSL VPN Parameters.”

Task 2: Configure basic user authentication by adding user accounts with passwords and creating an access policy for all remote users. This task is covered in detail in the section, “Configure and Verify Client Authentication and Policies on the SSL VPN Gateway.”

Task 3: (Optional) Configure full tunneling VPN access to internal resources if the connection requires access that is like being connected to the internal network directly. This task is covered in further detail in the section, “Configure and Verify Full Tunneling Connectivity on the Cisco IOS SSL VPN Gateway.”

Task 4: (Optional) Deploy the Cisco AnyConnect VPN client if full tunneling is required. This task is covered in further detail in the section, “Install and Configure the Cisco AnyConnect Client.”

Task 5: (Optional) Configure clientless VPN access to internal resources if the connection only requires browser-based access. This task is covered in further detail in the section, “Configure and Verify Clientless Access on the Cisco IOS SSL VPN Gateway.”

Input Parameters

Prior to implementing the basic Cisco IOS Software SSL VPN solution, you must gather and analyze several pieces of information about the network and system environments. These input parameters include the following:

• The IP addressing plan will determine the VPN gateway addressing, and the network-naming convention 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 SSL/TLS identity certificate.

• The corporate certificate policy and certificate settings to enroll the ISR into a Public Key Infrastructure (PKI) and include all required fields in an identity certificate that was received from the certificate authority (CA).

• The enterprise policy for usernames and passwords to create the local user on the ISR.

• The enterprise cryptographic policy to choose the appropriate SSL/TLS protocol versions and algorithm combinations.

• The IP addressing plan for remote clients. This applies only when using full tunneling SSL VPNs because the ISR must assign IP addresses to remote clients.

• Access policies that control resources that can be accessed by remote VPN users.

• A list of remote users’ client platforms to properly install the Cisco AnyConnect software images on the users’ machines and the ISR.

Configure and Verify Common SSL VPN Parameters

The first deployment step for configuring a full tunnel SSL VPN is to configure basic SSL/TLS server parameters on the ISR. This includes installing a server identity certificate that the ISR will send to remote clients so that they can authenticate to the ISR, enabling the SSL/TLS server functionality on an interface, and optionally tuning the parameters to match local cryptographic policy.

By default, the ISR will create a self-signed X.509 certificate on each reboot that will cause client warnings when attempting SSL VPN access because the certificate cannot be verified because it is self-signed. This can be addressed in two ways:

• Create a permanent self-signed certificate that is persistent across reboots. This certificate can be saved on clients and used if they access the ISR initially over a trusted network. This is usually not true and therefore not recommended.

• Enroll the ISR into an existing PKI, with the clients authenticating the ISR identity certificate on each access by validating it using a valid CA certificate that was used to sign the ISR’s identity certificate. This CA certificate would need to be provisioned on all clients for this authentication to work properly.

Configuration Tasks

image

Perform the following sequence to configure basic ISR SSL VPN gateway features:

Task 1: (Optional) Verify the SSL VPN license on the ISR that is intended to be used as the SSL VPN gateway.

Task 2: Provision an identity server SSL/TLS certificate to the ISR. This certificate will be used to identify the ISR to remote clients, and based on this certificate, remote clients will be able to authenticate to it.

Task 3: On the ISR, enable the SSL VPN gateway feature and configure the necessary parameters.

Task 4: Configure and optionally tune SSL/TLS settings on the ISR.

Task 5: (Optional) Configure stateless gateway high availability if gateway failover using two ISRs is required.

Configuration Choices

Some configuration choices must be made based on locally significant policies.

The first decision is whether to use self-signed or PKI-provisioned certificates. Self-signed certificates are usually only recommended for test purposes and not to be used in production because the clients can never validate the certificate. It is highly recommended to provision a certificate for a certificate authority that is trusted by the remote clients.

The second choice is whether to tune SSL/TLS settings regarding protocol modes and cryptographic algorithms. Typically, the default ISR SSL/TLS settings are adequate.

Configuration Scenario

A Cisco ISR is acting as an SSL VPN gateway and is connected to an untrustworthy external network and an internal enterprise network.

It is assumed that the ISR has already been configured with an identity certificate from a PKI trustpoint using the procedures learned in previous chapters.

Task 1: (Optional) Verify SSL VPN Licensing

Beginning with Cisco IOS Release 15.0(1)M, the SSL VPN gateway is a seat-licensed feature on the Cisco 880, Cisco 890, Cisco 1900, Cisco 2900, and Cisco 3900 platforms running the Cisco IOS Advanced Security feature set.

The first task of this sequence is to verify that the platform is properly licensed to support SSL VPN access. Use the show webvpn license command to see the number of licensed concurrent users. Example 20-1 shows the output from this command.

Example 20-1. Displaying Supported SSL Licenses


Router# show webvpn license


Available license count : 100
Reserved license count  : 100
In-use count : 0


Task 2: Provision an Identity Server SSL/TLS Certificate to the ISR

Task 2 is to provision an identity certificate by creating a PKI trustpoint in the router’s configuration. This procedure can be performed by following the steps described in previous chapters.

Task 3: Enable the SSL VPN Gateway and Context

Task 3 involves creating an SSL VPN gateway object and an SSL VPN context object on the ISR. The gateway object defines the network parameters of the SSL VPN gateway server process, such as interface and the port that it will bind to and the SSL/TLS protocol parameters supported by the SSL VPN server. The SSL VPN context defines user authentication, authorization, and accounting (AAA) and configuration parameters applied to the users using the SSL VPN gateway.

As depicted in Example 20-2, first create an SSL VPN gateway object using the webvpn gateway command and give the gateway a name. Inside the gateway configuration, specify a local IP address configured on the router, along with the port number, using the ip address command to bind the SSL VPN gateway server to the IP address and port. Use the logging enable command to enable syslog messaging of SSL VPN–related messages. Activate the gateway using the inservice command.

Next, create an SSL VPN context using the webvpn context command and give it a name. The context defines the VPN-related properties of the SSL VPN gateway such as authentication methods and the user interface. Inside the context, associate it with the configured SSL VPN gateway using the gateway command and then activate the context with the inservice command.

Example 20-2. Enable the SSL VPN Gateway and Context Parameters


router(config)# webvpn gateway MY-GATEWAY
router (config-webvpn-gateway)#? ip address 172.16.1.1 port 443
router (config-webvpn-gateway)# ssl trustpoint MY-TRUSTPOINT
router (config-webvpn-gateway)# logging enable
router (config-webvpn-gateway)# inservice
!


Task 4: Configure and Tune SSL/TLS Settings

Task 4 involves creating and tuning SSL/TLS protocol settings of the SSL VPN gateway inside its webvpn gateway object. Specify the PKI trustpoint that will provide the SSL VPN server with an identity certificate. Optionally, enable specific SSL/TLS algorithm bundles (cipher suites) to be active on the gateway.

Enter SSL VPN gateway object configuration mode using the webvpn gateway command and use the ssl trustpoint command to specify a local named trustpoint to the SSL VPN gateway. In this mode also, optionally configure specific cipher suites using the ssl encryption command. See Example 20-3 for the configuration command usage.

Example 20-3. Configure and Tune SSL/TLS Settings


router (config)# webvpn gateway MY-GATEWAY
router (config-webvpn-gateway)# ssl trustpoint MY-TRUSTPOINT
router (config-webvpn-gateway)# ssl encryption 3des-sha1 aes-sha1


Task 5: (Optional) Configure Gateway High Availability

Task 5 is an optional task for integrating the SSL VPN server with the Cisco IOS Software Hot Standby Router Protocol (HSRP) feature to yield stateless redundancy using two ISR devices. HSRP will fail over to the other peer in the HSRP group if an interface fails. HSRP can also track interfaces in the router to trigger a switchover. Example 20-4 shows what the commands should look like.

Example 20-4. Configure Gateway High Availability


router (config)# interface GigabitEthernet0/0
router (config-if)# standby 1 ip 172.16.1.1
router (config-if)# standby 1 name SSLVPN-HSRP
router (config)# webvpn gateway MY-GATEWAY
router (config-webvpn-gateway)#  ip address 172.16.1.1 port 443 standby SSLVPN-HSRP


Gateway Verification

Use the show webvpn gateway command to confirm successful configuration of the gateway. The output should show the gateway in an up/up state, as shown in Example 20-5. The administrative status of the gateway will always be up or down. This status is configured with the inservice command. The operational status will always be up or down as well. This status is only in the up state if the gateway is in service and configured with a valid IP address.

Navigating to the URL of the SSL VPN gateway should present a default SSL VPN portal login page. If the identity certificate has been configured properly, there should be no certificate warnings.

Example 20-5. show webvpn gateway Command Output


router# show webvpn gateway


Gateway Name    Admin    Operation
------------    -----    ---------
MY-GATEWAY      up       up


Implementation Guidelines

image

Consider the following implementation guidelines when configuring Cisco IOS Software SSL VPN gateway features:

• Self-signed certificates should not be used if they can be avoided. In cases where the clients initially access the ISR over a trusted network, they can be considered, but it is generally not recommended to use them.

• Ensure that the name on the gateway is configured correctly in the identity certificate to avoid certificate issues.

Configure and Verify Client Authentication and Policies on the SSL VPN Gateway

When client-based or clientless users that authenticate with passwords connect to the ISR gateway, the ISR will initially assign them to the configured SSL VPN context attached to the gateway (MY-CONTEXT context that was configured in the previous topic). This context will define a default policy (MY-POLICY) that will be assigned to all users connecting to the gateway and will enforce a common set of clientless and client-based access settings to authenticate, authorize, and enable accounting for all RA VPN sessions.

Gateway, Contexts, and Policy Groups

Figure 20-1 shows the interaction between the SSL VPN gateway, context, and policy group objects. The gateway defines the basic network and cryptographic settings of the SSL VPN server used by the SSL VPN gateway. The SSL VPN context defines common building blocks used in user policies and the authentication methods used to authenticate remote users. Policy groups define sets of configuration and AAA settings that are applied to users. One policy group is dedicated as the default policy group for a context.

Figure 20-1. Gateway, Contexts, and Policy Groups

image

Basic User Authentication Overview

The simplest form of user authentication is to use the router’s local user database and static passwords. The SSL VPN gateway can also use a remote AAA authentication method such as a RADIUS or TACACS+ server, client certificate-based authentication, or a combination of client certificates and local or remote passwords.

Configuration Tasks

image

Perform the following configuration sequence to configure basic authentication and a common policy for all users on the Cisco IOS Software SSL VPN gateway:

Task 1: Create a default policy and apply it to a context.

Task 2: Add users and their passwords to the ISR local user database and enable AAA authentication in the SSL VPN context.

Configuration Scenario

On the ISR, inside the MY-CONTEXT SSL VPN context, a new policy named MY-POLICY will be configured, and it will be assigned as the default policy for the context. Additionally, a new user named vpnuser with a static password and limited privileges will be created.

Task 1: Create and Apply a Default Policy

Task 1 is to enter SSL VPN context configuration mode by issuing the webvpn context command and creating a new policy named MY-POLICY using the policy group command. The new policy will also be made the default policy for the SSL VPN context by issuing the default-group-policy command. Example 20-6 shows this configuration.

Example 20-6. Create and Apply a Default Policy


router(config)# webvpn context MY-CONTEXT
router(config-webvpn-context)# policy group MY-POLICY
router(config-webvpn-context)# banner "Welcome to SSL VPN"
router(config-webvpn-context)# default-group-policy MY-POLICY


Given that there can be only one default policy group, a way to dynamically assign a user to any group policy is needed. RADIUS attributes can be used for this purpose. During authentication, the RADIUS server can push down the webvpn:user-vpn-group attribute. This Cisco AV-pair can designate the policy group to which the authenticating user will be assigned.

Task 2: Enable User Authentication Using Local AAA

In Task 2, a local AAA authentication method will be configured. In addition, as shown in Example 20-7, a local user account will be created, and the new AAA authentication method will be applied to the SSL VPN context.

Example 20-7. Enable User Authentication Using Local AAA


router(config)# aaa authentication login LOCAL-AUTHEN local
!
router(config)# username vpnuser privilege 0 secret 5
$25$05ikadSDAjaksfdjDw32PDij34214$4213
!
router(config)# webvpn context MY-CONTEXT
router(config-webvpn-context)# aaa authentication list LOCAL-AUTHEN


Implementation Guidelines

image

Consider the following implementation guidelines when implementing basic user authentication and common policy in an SSL VPN solution:

• Only use static passwords in small, single-device, low-risk environments.

• In a multidevice environment, migrate to a centralized AAA server.

• For stronger authentication, consider using certificates or one-time passwords.

• Ensure that the privileges (authorization) of local VPN user accounts are limited.

Configure and Verify Full Tunneling Connectivity on the Cisco IOS SSL VPN Gateway

Today’s business trends toward saving costs and doing more with less are causing the use of remote connectivity to grow. Deploying full tunneling capability on the SSL VPN gateway provides a method of connectivity for your remote users that closely mimics working from the office.

Configuration Tasks

image

To configure basic AnyConnect full tunnel access using the Cisco IOS Software SSL VPN gateway, perform the following tasks:

Task 1: Enable full tunnel access in the SSL VPN policy group.

Task 2: Configure an IP address pool and assign the configured address pool to the SSL VPN policy group.

Task 3: (Optional) Configure client configuration parameters and assign them to the SSL VPN policy group.

Task 4: (Optional) Configure split tunneling to allow remote clients to directly access networks not located beyond the ISR VPN gateway and assign it to the SSL VPN policy group.

Task 5: (Optional) Configure an access control list (ACL) to implement access control to internal resources.

Configuration Scenario

Figure 20-2 depicts the network for this configuration scenario. The ISR will use an IP address from the 192.168.1.0/24 network for client IP addresses. Split tunneling will be allowed to access only the 10.0.0.0/8 network through the SSL VPN tunnel. Clients will be configured with an internal Domain Name System (DNS) server for host name resolution, and split DNS will be configured to forward queries for mydomain.com to the internal DNS server.

An ACL will allow only DNS resolution to the internal DNS server and HTTP access to an internal web server at 10.10.1.1. Assumptions are that the basic SSL VPN gateway settings for the SSL VPN gateway and contexts are previously configured on the Cisco ISR.

Figure 20-2. Full Tunneling Scenario

image

Task 1: Enable Full Tunneling Access

Task 1 in this configuration sequence involves downloading the Cisco AnyConnect client from Cisco.com and transferring it to the ISR flash memory. Transfer the Cisco AnyConnect software image to the ISR for all client operating systems that are required.

On the ISR, use the webvpn install svc command, as shown in Example 20-8, to install the image into the SSL VPN gateway, which will allow the gateway to install this image to users that connect through the SSL VPN portal.

Example 20-8. Enable Full Tunneling Access


router(config)# webvpn install svc flash://anyconnect-win-2.4.0202-k9.bin
SSLVPN Package SSL-VPN-Client (seq:1): installed successfully
!
router(config)# webvpn context MY-CONTEXT
router(config-webvpn-context)# policy group MY-POLICY
router(config-vpn-policy)# functions svc-enabled
router(config-vpn-policy)# svc keep-client-installed


Next, enter the default policy group and enable full tunneling with the functions svc-enabled command and ensure that the gateway will not uninstall the AnyConnect client from the remote user’s computer by issuing the keep-client-installed command.

Task 2: Configure Local IP Address Assignment

When clients connect with the full tunnel mode, the ISR assigns them an IP address that will be used by the clients to source their traffic. Private addresses can be used, but they must be able to be routed properly by the gateway in the internal network so that internal users know how to respond to them.

For Task 2, Example 20-9 shows the pool of IP addresses being created with the ip local pool command and then being configured as part of the default policy group with the svc address-pool command.

Example 20-9. Configure and Assign Local IP Address


router(config)# ip local pool MY-POOL 192.168.1.2 192.168.1.150
router(config)# webvpn context MY-CONTEXT
router(config-webvpn-context)#policy group MY-POLICY
router(config-vpn-policy)#svc address-pool MY-POOL


Task 3: (Optional) Configure Client Configuration

Task 3 involves configuring the ISR to push optional network configuration items such as the domain suffix and the IP address of internal DNS servers to the remote users.

Example 20-10 displays the configuration necessary to specify the domain suffix by using the svc default-domain command. The first DNS server that remote clients will use can be pushed to them using the svc dns-server primary command. An additional DNS server can also be pushed using the svc dns-server secondary command.

Example 20-10. (Optional) Configure Client Configuration


Router(config)# webvpn context MY-CONTEXT
Router(config-webvpn-context)# policy group MY-POLICY
Router(config-vpn-policy)# svc default-domain mydomain.com
Router(config-vpn-policy)# svc dns-server primary 10.1.1.1


Task 4: (Optional) Configure Split Tunneling

Task 4 involves configuring split tunneling to allow direct access to certain networks without using the VPN tunnel (bypassing it). This does increase risk by allowing remote users to have access to internal resources and other untrusted networks at the same time. Additional security controls should be considered if using this option.

Example 20-11 displays how to configure split DNS using the svc split include command. To have remote users use their non-VPN DNS servers to provide name resolution for the alternate non-VPN network, use the svc split dns command.

Example 20-11. (Optional) Configure Split Tunneling


Router(config)# webvpn context MY-CONTEXT
Router(config-webvpn-context)# policy group MY-POLICY
Router(config-vpn-policy)# svc split dns mydomain.com
Router(config-vpn-policy)# svc split include 10.0.0.0 255.0.0.0


Task 5: (Optional) Configure Access Control

The fifth task is to optionally configure an ACL that restricts remote users access to internal resources. Example 20-12 shows an ACL that permits access to UDP port 53 for access to a DNS server at 10.1.1.1 and TCP port 80 for access to HTTP services on the same server. This task is accomplished by first configuring a Cisco IOS Software stateless ACL and then applying it to the policy group using the filter tunnel command.

Example 20-12. (Optional) Configure Split Tunneling


Router(config)# ip access-list extended MY-ACL
Router(config-ext-acl)# permit udp any host 10.1.1.1 eq domain
Router(config-ext-acl)# permit tcp any host 10.1.1.1 eq www
!

Router(config)# webvpn context MY-CONTEXT
Router(config-webvpn-context)# policy group MY-POLICY
Router(config-vpn-policy)# filter tunnel MY-ACL


Cisco Configuration Professional Support

Cisco Configuration Professional 2.4 can be used to initially configure and tune the SSL VPN gateway on Cisco ISR devices. There is a configuration wizard or manual mode option that can be used for the configuration requirements. Navigate to Configure > Security > VPN > SSL VPN > SSL VPN Manager to begin the configuration steps.

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.

Install and Configure the Cisco AnyConnect Client

The Cisco AnyConnect SSL VPN client provides users with secure VPN connections to either the Cisco ISR SSL VPN gateway or the Cisco ASA 5500 Series Adaptive Security Appliances.

Network administrators must configure the AnyConnect client features on the ISR. After this is complete, the client software must be loaded on the ISR so that it will be automatically downloaded to remote users when they log in, or it can be manually installed as an application on the remote users’ systems. The client has support for user profiles that are displayed in the user interface. The network administrator can assign features that are specific to individual users or groups through these profiles.

Note

The Cisco AnyConnect client requires administrative privileges for the initial installation.

The AnyConnect SSL VPN client packages must be downloaded from Cisco.com and uploaded to the Cisco ISR so that it can be downloaded in an on-demand fashion by clients from the SSL VPN portal.

The web launch installation method requires that the client connect to the ISR with a compliant web browser using HTTPS. The user must log on and successfully authenticate, and the ISR will redirect the user to the SSL VPN client through an ActiveX or Java applet. After the AnyConnect SSL VPN client has been successfully installed, the ISR will automatically log the user on to the network using the credentials provided during the original clientless connection.

The manual installation process involves obtaining the installer package (MSI for Windows) and installing the Cisco AnyConnect SSL VPN client. The configuration sequence in this topic covers this method of installation.

AnyConnect 2.4–Supported Platforms

The Cisco AnyConnect SSL VPN client supports the following operating systems:

• Microsoft Windows 7, Windows Vista, and Windows XP

• Apple Mac OS X (version 10.5 or later) on either Intel or PowerPC architectures

• Red Hat Linux (version 9 or later)

• Ubuntu 9 or later

See the Release Notes at Cisco.com for more information about full requirements and supported versions.

Configuration Tasks

image

To install and configure the AnyConnect client in a basic AnyConnect full tunnel implementation, perform the following tasks:

Task 1: Install the AnyConnect client.

Task 2: Verify that the client has valid root CA certificates installed. Each client should have a local, authentic copy of the root CA certificate that was used to issue the ISR identity certificate.

Task 3: Configure basic AnyConnect profile settings (fully qualified domain name [FQDN] of the ISR).

Task 4: Establish the SSL VPN full tunnel connection.

Configuration Scenario

The AnyConnect client will be installed and configured on Microsoft Windows XP, and the ISR will use an identity certificate issued by a global PKI. The name vpn.mydomain.com will resolve to the IP address of the untrusted ISR interface. This name will also be the canonical name of the ISR in the identity certificate.

Task 1: Enable Full Tunneling Access

The first task is to install the predeployed version of the AnyConnect client. Perform the following steps on the client:

Step 1: Obtain the MSI installation package from Cisco.com and transfer it to the client system.

Step 2: Double-click the MSI installation package to start the installation process.

Step 3: Click Next to start the installation dialog process.

Step 4: Examine the license agreement, select the I Accept the Terms of the License Agreement check box, and click Next.

Step 5: Click Install to start the installation process.

Step 6: Click Finish to close the installer.

Task 2: Verify Server Certificate Authentication Chain

On the client, look at the installed root CA certificates to make sure that the CA that issued the ISR identity certificate is in the list. This keeps the client from issuing certificate warnings when it attempts to create an SSL VPN connection.

Task 3: Configure Basic AnyConnect Profile Settings

Task 3 involves configuring profile settings on the client. Start the AnyConnect client and configure it with the ISR SSL VPN gateway information. Enter the FQDN, vpn.mydomain.com, in the Connect To field. This name must match exactly what is in the canonical name (CN) field on the ISR’s identity certificate to avoid certificate warnings. Click Select to make the client connect to the ISR.

Task 4: Establish the SSL VPN Connection

After the connection is established, the ISR pushes instructions for the next step of establishing the connection. After being prompted for user authentication, enter the login credentials and click Connect.

Note

Alternatively, the WebLaunch feature can be used to start the VPN connection using a browser. If clientless SSL VPN is not enabled on the ISR untrusted interface, the ISR automatically starts the AnyConnect client after the user logs in to the main page. This is an alternative to Tasks 3 and 4.

Client-Side Verification

The AnyConnect SSL VPN client GUI will automatically minimize after a successful connection establishment. Click the AnyConnect icon in the Windows system tray to restore the GUI. In the Statistics pane, observe the state of the connection, the client’s assigned IP address, the bytes sent and received, and the connection time. More detailed features can be displayed by clicking the Route Details tab, as illustrated in Figure 20-3.

To verify split tunneling and routing on the client, navigate to the Route Details tab of the Details window.

The network that is displayed in the Secured Routes pane shows the network segments that are being protected by the client. For example, a network of 130.39.0/16 in the Secured Routes pane indicates that this client traffic is being sent through the tunnel, while all other traffic would bypass the VPN client altogether.

Figure 20-3. Cisco AnyConnect Route Details Tab

image

Gateway-Side Verification

On the ISR, use the show webvpn session context command to see the list of connected clients. The show webvpn session user command can also be used to show detailed information about a particular user’s VPN session. Example 20-13 demonstrates some sample output from both commands.

Example 20-13. Verifying Operation on the SSL VPN Gateway


Router# show webvpn session context SSL VPN


WebVPN context name: SSL VPN
Client_Login_Name  Client_IP_Address  No_of_Connections  Created  Last_Used
user1               10.2.1.220                   2         04:47:16  00:01:26
user2               10.2.1.221                   2         04:48:36  00:01:56

Router# show webvpn session user user1 context all

WebVPN user name = user1 ; IP address = 10.2.1.220; context = SSL VPN
    No of connections: 0
    Created 00:00:19, Last-used 00:00:18
    CSD enabled
    CSD Session Policy
       CSD Web Browsing Allowed
       CSD Port Forwarding Allowed
       CSD Full Tunneling Disabled
       CSD FILE Access Allowed
    User Policy Parameters
      Group name = ONE
    Group Policy Parameters
      url list name = "Cisco"
      idle timeout = 2100 sec
      session timeout = 43200 sec
      port forward name = "EMAIL"
      tunnel mode = disabled
      citrix disabled
      dpd client timeout = 300 sec
      dpd gateway timeout = 300 sec

      keep stc installed = disabled
      rekey interval = 3600 sec
      rekey method = ssl
     lease duration = 3600 sec


Cisco Configuration Professional

Navigate to the Monitor > Security > VPN Status > SSL VPN (All Contexts) pane to verify the client connections on the ISR. CCP provides aggregate monitoring statistics as well as individual user session monitoring.

Configure and Verify Clientless Access on the Cisco IOS SSL VPN Gateway

In situations in which your remote users do not require full connectivity or your security policy does not permit it, you can configure clientless access on the SSL VPN gateway and give them access to a smaller list of applications. The following sections cover configuring clientless access on the Cisco IOS SSL VPN gateway.

Basic Portal Features

Users can access internal resources by using a web browser with the ISR performing as a proxy to provide internal content on its SSL VPN portal. This type of connection is referred to as the clientless SSL VPN. Figure 20-4 shows the Bookmarks pane in which links to internal resources can be found. The Application Access pane displays a link to a Thin Client Application.

The portal will provide a free URL field in which users can enter a URL manually as well. By default, the Cisco ISR SSL VPN web portal does not restrict users and allows authenticated users to access all internal resources. Basic portal tuning can be configured so that the portal appearance is altered to either enable or disable some of the user’s interface functionality.

Figure 20-4. SSL VPN Web Portal

image

Cisco Secure Desktop for Clientless Access

Cisco Secure Desktop (CSD) was developed to minimize the risk posed by allowing access to internal resources by remote devices using either the Cisco Clientless SSL VPN or the Cisco AnyConnect Client.

Prior to permitting a Cisco clientless or client-based connection, the remote machine will scan for a large set of antivirus and antispyware applications, firewalls, operating systems, and process names.

It also scans for any registry entries, filenames, and process names, collectively called the basic host scan. With an Advanced Endpoint Assessment License, Cisco Secure Desktop can use optional criteria as conditions for granting rights.

Inspections performed by the Cisco Secure Desktop inspectors can detect antivirus, personal firewall, and antispyware software and learn the version, product, and revision information about them to make policy decisions on the WebVPN gateway. The CSD inspectors will gather the “defined” information on the endpoint and send it to the WebVPN gateway. The gateway uses the user’s login credentials, the computer scan results, and profile matching to assign a Dynamic Access Policy (DAP).

Cisco Secure Desktop encrypts data and files associated with, or downloaded during, the SSL VPN session. The session information is stored in the secure vault desktop partition.

When the session closes, Cisco Secure Desktop tries to minimize the risk posed by having information remaining on a client after a Cisco clientless SSL VPN or a Cisco AnyConnect session terminates. The goal is to reduce the possibility that cookies, browser history, temporary files, and downloaded content will remain on a system after a remote user logs out or an SSL VPN session times out. CSD overwrites and attempts to remove session data by using a U.S. Department of Defense (DoD) sanitation algorithm to provide endpoint security protection.

Port Forwarding Overview

The default web portal permits users to access web (HTTP or HTTPS) or file (CIFS) resources that are behind the gateway by translating the resources into the user’s browser. To enable the use of native applications such as email clients or terminal programs over the clientless SSL VPN connection, the gateway implementation supports a feature called port forwarding.

Port forwarding uses a Java helper applet that is downloaded to remote users to provide access to certain applications that are not supported by the clientless SSL VPN by default. The Java helper needs the application to make a connection to the local host to provide port-forwarding functionality. This requires some modification of application settings:

Step 1: After logging in to the SSL VPN portal, the Java applet that is downloaded from the SSL VPN portal dynamically modifies the local host’s file. The Java applet then listens on the remote host’s loopback address at port 3001 and forwards any incoming connections over the SSL VPN session.

Step 2: The user opens a Telnet client and attempts to connect to an internal server on port 3001.

Step 3: The local host’s file will be analyzed by the applet. It has an entry for the internal server that points to the loopback address (127.0.0.1) of the remote client. The Telnet client connects to the local host on port 3001, and the Java applet forwards this connection to the SSL VPN gateway through the tunnel.

Step 4: The gateway extracts the TCP session from the SSL VPN session, establishes a TCP connection with the internal target host on the standard Telnet port, and acts as a data relay between the two TCP sessions.

Port Forwarding Benefits and Limitations

The benefit of using the port forwarding feature is that it supports the use of fully featured, native applications that already exist on the remote machine.

The limitations of using the port forwarding feature are as follows:

• Port forwarding supports only simple, static-port TCP applications.

• Port forwarding requires preinstalled native applications on the remote systems.

• Users must change application settings such as the destination port of the server.

• Port forwarding requires administrative privileges because it changes the local host’s file.

As you can see, port forwarding is appropriate for only limited access to applications. It is not appropriate for full access to the remote site. To access more applications at the remote end, you should consider using the full tunnel connection.

Portal ACLs

Normal access controls, such as the ISR interface ACL or the Zone-Based Policy Firewall access control model, are not used by the ISR clientless SSL VPN feature. Instead, it provides its own access control through the use of web-type ACLs. These ACLs are applied on a per-user or per-group basis and permit or deny access to URLs that are reachable through the SSL VPN portal. URL patterns can be used to specify allowed or denied URLs or even use multiple rules inside a web-type ACL. They use the same logic as a classic Cisco IOS Software ACL in that the first rule matched dictates the action, and there is an implicit deny all statement at the end of the ACL.

Note

Enabling or disabling portal features such as the free URL entry does not prevent a user from accessing particular internal resources. It only removes the user interface option. If a user enters a properly constructed URL into the browser address field, he can still access the resource behind the URL if properly authenticated. Web-type ACLs must be used to control access to internal resources with any reliability.

Configuration Tasks

image

To configure basic clientless access to a Cisco IOS Software SSL VPN gateway (ISR), perform the following tasks:

Task 1: Configure the SSL VPN portal features that are to be available to remote clientless users.

Task 2: (Optional) Configure port forwarding to allow native application access over the clientless session.

Task 3: (Optional) Configure the Cisco Secure Desktop to mitigate the risk associated with sensitive data being left on remote systems.

Task 4: (Optional) Configure web-type ACLs to limit access to internal resources.

Configuration Scenario

Figure 20-5 illustrates the scenario for the following configuration sequence. Remote users can only access a single web server at http://intranet.mydomain.com in the protected network and a file server share at cifs://W2K3S/share. Predefined bookmarks to access the web server home page and the file share name “share” will be created. To browse the W2K3S server and the rest of the Windows domain, the ISR will also be configured to query an internal WINS server at 172.16.1.137 for CIFS host name resolution.

The ISR will also be configured to download and enable the Java port-forwarding applet to the client. The client will listen on the local host’s loopback on TCP 3001 and forward incoming connections to the internal terminal server 10.10.1.1.

The last configuration task is to load and enable the Cisco Secure Desktop on the Cisco ISR and use CSD to provide a protected environment from within which remote users can access internal resources.

Figure 20-5. Cisco Secure Desktop Operational Sequence

image

Task 1: Enable Full Tunneling Access

The first task is to configure the SSL VPN portal features that are available to the remote clientless users.

Note

By default, the SSL VPN portal allows access to all features to be used but does not provide any bookmarks or predefined port-forwarding links to assist users.

First, configure an optional web bookmark list that defines an internal web server for users of a policy group. In the SSL VPN context object, use the url-list command to define new bookmarks, and then, inside the web bookmark’s configuration mode, use the url-text and url-value commands to add one or more bookmarks. When you are done adding bookmarks, enter the policy group configuration mode and assign the web bookmarks list to the policy group using the url-list command.

Continue by adding optional CIFS bookmarks in the same fashion. Use the cifs-url-list command to define new bookmarks and then assign them using the cifs-url-list policy group configuration command. Examine Example 20-14 to see the commands for this first task.

Example 20-14. Configure Split Tunneling


router(config)# webvpn context MY-CONTEXT
router(config-webvpn-context)# url-list "MY-WEB-BOOKMARKS"
router(config-webvpn-url)# url-text "Internal Web Server" url-value
http://intranet.mydomain.com
router(config-webvpn-url)# exit
router(config-webvpn-context)# cifs-url-list "MY-CIFS-BOOKMARKS"
url-text "Internal File Server" url-value "cifs://w2k3s/share"
router(config-webvpn-context)# nbns-list "MY-AD-NAMESERVERS"
router(config-webvpn-context)# nbns-server 10.10.1.1
!
router(config-webvpn-context)# policy-group MY-POLICY
router(config-webvpn-group)# url-list "MY-WEB-BOOKMARKS"
router(config-webvpn-group)# cifs-url-list "MY-CIFS-BOOKMARKS"
router(config-webvpn-group)# nbns-list "MY-AD-NAMESERVERS"
router(config-webvpn-group)# functions file-access
router(config-webvpn-group)# functions file-browse
router(config-webvpn-group)# functions file-entry


Task 2: (Optional) Configure Port Forwarding

Task 2 involves configuring an optional port-forwarding list of applications that are available to the remote clientless user through port forwarding.

Use the port-forward context object command to create a named list of ports to be forwarded by the Java applet. As shown in Example 20-15, inside the port forward object’s configuration mode, use the local-port command to specify the local port on which the Java applet will listen, the remote-server and remote-port commands to enter the server to which the connection is to be relayed, and the description argument to provide a friendly name for remote users.

To apply this port-forwarding rule, enter the policy group configuration mode and assign the port-forwarding list using the port-forward command.

There can be multiple port forward rules in a port forward object, and you can also assign the same list to multiple policy groups, if required.

Example 20-15. (Optional) Configure Port Forwarding


router(config)# webvpn context MY-CONTEXT
router(config-webvpn-context)# port-forward "MY-PORT-FORWARD"
router(config-webvpn-port-fwd)# local-port 3001 remote-server "10.10.1.1" remote-
port 3389 description "Terminal Services"
router(config-webvpn-port-fwd)# exit

router(config-webvpn-context)# policy-group MY-POLICY
router(config-webvpn-group)# port-forward "MY-PORT-FORWARD" auto-download


Task 3: (Optional) Configure Cisco Secure Desktop

In Task 3, Cisco Secure Desktop is deployed to remote users if required. First, the Cisco Secure Desktop software must be downloaded from Cisco.com and then transferred to the ISR flash memory. On the Cisco ISR, use the webvpn install csd command to install the image into the SSL VPN gateway, which will enable the gateway to push the package to clientless remote users. See Example 20-16 for the correct commands.

To enable CSD for remote clientless users, use the csd enable command inside the SSL VPN context object. This applies to all clientless users regardless of their policy group.

Example 20-16. (Optional) Configure Cisco Secure Desktop


Router(config)# webvpn install csd flash://csd_3.5.841-k9.pkg
SSLVPN Package Cisco-Secure-Desktop : installed successfully

Router(config)# webvpn context MY-CONTEXT
Router(config-context)#csd enable


By default, CSD is not configured with any default policies, and there must be at least one Cisco Secure Desktop “location” and an associated policy in which to enable Cisco Secure Desktop features. Configure CSD by connecting to the ISR with a browser using HTTPS and requesting the csd_admin.html page. Authenticate to the page using the username “admin” and the enable secret of your ISR as the password.

Task 4: (Optional) Configure Access Control

Task 4 involves configuring optional access control to be applied to clientless users. Because clientless remote access users operate in a proxy-based mode or port forwarding, their access is not affected by traditional Cisco IOS Software ACLs or other rules or zones applied to interfaces. The SSL VPN uses web-type ACLs to control access for clientless users.

First, configure a named ACL in the SSL VPN context object that permits or denies access to particular URLs for portal-based access, and configure access to IP or TCP services for port-forwarding services. You cannot specify destination ports for port forwarding, but ports are already specified as part of the port-forwarding list. When this is done, apply the web-type ACL to the policy group with the acl command. Complete these commands as shown in Example 20-17.

Example 20-17. (Optional) Configure Access Control


router(config)# webvpn context MY-CONTEXT
router(config-webvpn-context)# acl "MY-PORTAL-ACL"
router(config-webvpn-acl)# permit url http://intranet.mydomain.com
router(config-webvpn-acl)# permit url "cifs://w2k3s/share"
router(config-webvpn-acl)# permit tcp any 10.10.1.1 255.255.255.255
router(config-webvpn-acl)# exit
!
router(config-webvpn-context)# policy-group MY-POLICY
router(config-webvpn-group)# acl "MY-PORTAL-ACL"


Basic Portal Verification

Portal feature configuration verification is achieved by successfully creating an SSL VPN session and logging in to the portal. Successfully accessing resources defined in the predefined bookmarks is an indication that the portal is configured correctly.

Web Application Access

The browser will display a floating toolbar with application-specific navigation icons that are to be used to return to the home page, open a URL over the clientless SSL VPN session, create user-specific bookmarks, move the toolbar to the other side of the window, or close the SSL VPN session.

File Server Access

To verify that access to file shares is working, browse to an internal resource using a browser interface, click a CIFS bookmark, or enter a URL in the free URL entry box.

Port Forwarding Access

To confirm the port-forwarding operation, log on to the SSL VPN portal and click the appropriate link that will cause the Java applet to forward a connection to the SSL VPN gateway. Most browsers require authentication to successfully connect.

Cisco Secure Desktop Verification

The Cisco Secure Desktop functionality can by tested by visiting the SSL VPN portal URL. The Cisco Secure Desktop applet should download and then analyze the remote user’s computer. If CSD is configured to provide a secure desktop, the secure desktop should launch and a browser will open inside it.

Gateway-Side Verification

Confirmation of configuration can also be attained on the Cisco ISR by using the show webvpn session context command to see the list of connected remote clients. The show webvpn session user command will provide detailed information such as the configured portal features and user interface elements, such as bookmarks.

Troubleshoot the Basic SSL VPN Operation

Troubleshooting basic SSL VPN configuration includes performing troubleshooting actions on the SSL VPN gateway and on the client. The following sections cover the process of troubleshooting SSL VPN connectivity.

Port Forwarding Access

Troubleshooting SSL VPN session establishment can possibly call for troubleshooting on the client and on the ISR. First, discover and alleviate any connectivity issues using commands such as ping and traceroute, and use tools such as nslookup and dig to verify successful name resolution.

Troubleshooting Flow (VPN Establishment)

image

When having problems successfully establishing a VPN session, follow these steps to troubleshoot:

Step 1: Verify that the SSL session initially succeeds and that no negotiation problems exist. The debug ssl openssl errors command will show issues such as incompatible protocol versions or cipher suites.

Step 2: Make sure that there are no user authentication issues. Use the debug aaa authentication command to verify user authentication.

Step 3: Check to see whether the policy group allows SSL VPN tunnels by looking at the policy group configuration for the function svc-enabled command.

Step 4: Verify that the ISR is able to assign an IP address to the client. The debug webvpn tunnel command can assist with this.

Troubleshooting Flow (Data Flow)

image

When having problems connecting to resources over the tunnel, after the SSL VPN session establishes, use the following suggestions to troubleshoot:

Step 1: Verify that the correct routes are being protected (routed into the tunnel).

Step 2: Verify that the ISR is not denying traffic from the VPN tunnel. Check syslog messages on the Cisco ISR to look for these denies.

Step 3: Verify that the protected network has a route to the client-assigned IP addresses by looking at the routing tables of internal routers. Verify SSL VPN tunnels by looking at the policy group configuration for the function svc-enabled command.

Gateway-Side Issue

To troubleshoot on the Cisco ISR side, the debug ssl openssl errors and the debug webvpn tunnel commands will show items such as incompatible cipher suites or failed address assignments because of missing local IP pools on the router.

Client-Side Issues: Certificates

One of the most common issues on the client are the certificate warning messages that are received during the VPN establishment. Three main reasons exist for this:

• If the ISR identity certificate cannot be verified because of a missing CA certificate on the client, install an authentic copy of the CA certificate to the client.

• A name mismatch between the name specified in the AnyConnect profile (the Connect To field) or the browser URL and the canonical name (CN) field in the ISR identity certificate. Fix these values so that they match to resolve this issue.

• An expired ISR identity certificate. Renew the identity certificate.

These types of issues should never occur in a production network. If users get accustomed to “accepting” invalid certificates upon receiving the warning messages, the VPN connection will be susceptible to man-in-the-middle attacks.

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 20-9 lists a reference of these key topics and the page numbers on which each is found.

Table 20-9. 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.

Define Key Terms

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

full tunneling VPNs

Transport Layer Security (TLS)

Secure Socket Layer (SSL)

port forwarding

client-based remote user

clientless remote user

Fill in the Blanks

  1. The ISR uses the identity certificate to _____ itself to remote clients.
  2. _____ can increase the risk to remote clients and internal resources because the clients can potentially act as a relay between untrusted and trusted networks.
  3. When terminating a clientless VPN, the ISR acts as a _____ to provide access to internal resources to remote users.
  4. _____ VPNs require VPN client software to be installed on the remote computer or dedicated VPN devices (hardware clients) to enable full routed IP access to internal resources.
  5. _____ VPNs are easier to deploy than a full tunneling remote access VPN, but they typically provide limited access to resources when compared to the full tunnel.
  6. Clientless deployments require that the user open a web browser, which acts as the VPN client, and the VPN gateway acts as a _____ device to the internal resources.
  7. The recommended algorithms for IKE session encryption are _____ and _____.
  8. The recommended hash algorithm to provide message authentication and integrity is _____.
  9. The recommended algorithms for encryption of user traffic are _____ and _____.
  10. _____ requires administrative privileges because it changes the local host’s file.

References

Cisco IOS SSL VPN Policy Groups, www.cisco.com/en/US/prod/collateral/iosswrel/ps6537/ps6586/ps6657/prod_white_paper0900aecd8051ac3a.html.

Cisco Secure Desktop (CSD) on IOS Configuration Example Using SDM, www.cisco.com/en/US/products/ps6496/products_configuration_example09186a008072aa7b.shtml.