Chapter 14. Introduction to Cisco IOS Site-to-Site Security Solutions

This chapter covers the following subjects:

• Choose an appropriate VPN LAN topology: Covers the four main LAN topologies that are appropriate for VPNs to help you choose the correct one for your environment.

• Choose an appropriate VPN WAN technology: Covers the main WAN technologies that are used in site-to-site VPNs.

• Evaluate core features of IPsec VPN technology: Covers the core features of IPsec VPN technologies.

• Choose appropriate VPN cryptographic controls: Covers the various cryptographic controls for VPNs along with criteria for choosing appropriate controls for your needs.

This chapter introduces site-to-site VPN technologies offered by Cisco IOS Software. An IPsec Virtual Private Network (VPN) is a technology that is deployed, in some cases, as an alternative to or as an augmentation to a traditional WAN infrastructure. IPsec VPNs typically are used to provide connectivity between an organization’s sites. For example, a branch office can be connected to enterprise headquarters using IPsec VPN technology. IPsec VPNs are also used in conjunction with traditional WAN technologies, such as Frame Relay and Asynchronous Transfer Mode (ATM) circuits. IPsec VPNs do not change WAN requirements; however, they support multiple WAN Layer 2 protocols and provide higher reliability and scalability while usually being more cost-effective. This chapter overviews the many topologies and technologies that are possible with IPsec VPNs.

“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 14-1 outlines the major topics discussed in this chapter and the “Do I Know This Already?” quiz questions that correspond to those topics.

Table 14-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 network topology is in use when two sites interconnect using a secure VPN using point-to-point connectivity?

a. Hub-and-spoke network

b. Partially meshed network

c. Individual point-to-point VPN connection

d. Fully meshed network

e. Star topology network

2. Which network topology is in use when one central site is considered a hub and all other sites connect directly to the hub site? Most user traffic flows between their respective spoke networks and the hub, but when necessary, two spoke sites can communicate by the hub network acting as a relay between the spoke networks.

a. Partially meshed network

b. Star topology network

c. Hub-and-spoke network

d. Fully meshed network

e. Individual point-to-point VPN connection

3. Which network topology is in use when multiple sites interconnect with each other dependent upon their communication needs? Each site can have multiple connections to other sites, but there is no one site that is more important than another. If connectivity is needed between two sites that does not exist, another direct VPN connection is added to the network topology.

a. Hub-and-spoke network

b. Individual point-to-point VPN connection

c. Star topology network

d. Fully meshed network

e. Partially meshed network

4. Which network topology is in use when every network has a direct VPN connection to every other network? This topology provides any-to-any communication and provides the most optimal direct path for network traffic.

a. Fully meshed network

b. Star topology network

c. Partially meshed network

d. Individual point-to-point VPN connection

e. Hub-and-spoke network

5. Which of the following VPN technologies uses nontunneled IPsec as its encapsulation mode?

a. Individual IPsec tunnels

b. Cisco Easy VPN

c. Dynamic Multipoint VPN (DMVPN)

d. Group Encrypted Transport (GET) VPN

6. Which VPN technology can dynamically and automatically build spoke-to-spoke IPsec tunnels?

a. Individual IPsec tunnels

b. Cisco Easy VPN

c. Dynamic Multipoint VPN (DMVPN)

d. Group Encrypted Transport (GET) VPN

e. None of these answers are correct.

7. The Internet Key Exchange (IKE) protocol communicates over which port?

a. UDP 500

b. UDP 50

c. TCP 500

d. ESP 500

e. TCP 443

8. Which encapsulation mode, when deployed in tunnel mode, provides confidentiality, authenticity, integrity, and antireplay by encapsulating and protecting the entire original IP packet?

a. Authentication Headers (AH)

b. Internet Security Association and Key Management Protocol (ISAKMP)

c. Diffie-Hellman key exchange with Perfect Forward Secrecy (PFS)

d. Encapsulating Security Payload (ESP)

9. What should be performed to determine that optimal VPN policies are chosen?

a. Use default settings for everything.

b. Use 802.1X as the encryption algorithm.

c. Perform a formal or informal risk assessment.

d. Install Cisco MARS.

10. Most cryptographic systems fail because of what reason?

a. Cryptographic keys are too short

b. Using pre-shared keys over certificate-based authentication

c. Inadequate key management operational processes

d. Weak encryption keys

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” section.

• 9 or 10 overall score: If you want more review on these topics, skip to the “Exam Preparation” section. Otherwise, move on to Chapter 15, “Deploying VTI-Based Site-to-Site IPsec VPNs.”

Foundation Topics

Site-to-site VPNs are a popular way to provide secure communication between sites. Secure communication is essential when transmitting over public networks, and IPsec provides protection to important data. There are several choices to be made when designing site-to-site VPN architectures, including the following:

• Choosing an appropriate VPN LAN topology

• Choosing an appropriate VPN WAN technology

• Choosing appropriate VPN cryptographic controls

Upon completion of this chapter, you will have adequate information to make these decisions.

Choose an Appropriate VPN LAN Topology

A network topology depicts the way in which nodes in a network interconnect to form a network. Network topologies for VPN technologies are typically logical in nature because of the fact that the physical connectivity does not affect the capability of the VPN to successfully establish. As long as the two end devices can reach each other, the underlying physical connectivity is insignificant.

image

The four typical VPN topologies used to create site-to-site VPNs are as follows:

• Individual point-to-point (P2P) VPN connection: Two sites connect to each other using secure VPN technologies. Each required connection between two sites requires manually creating a VPN connection.

• Hub-and-spoke network: There is a central site that is considered to be a hub and all other sites (the spokes) peer only with the hub. Most traffic patterns exist from spoke to hub, but connectivity between spokes can be relayed through the hub site.

• Partially meshed network: Multiple sites requiring connectivity with other sites. VPNs are built as the need arises so that each site will have multiple VPN connections to several other sites.

• Fully meshed network: Multiple sites that have a VPN connection to each and every other site. This topology provides the most optimal traffic flow.

Table 14-2 provides a summary of VPN topology details.

Table 14-2. VPN Topology Comparison

image

Input Parameters for Choosing the Best VPN LAN Topology

Information about a network must be gathered and analyzed to choose the best VPN topology for an environment. Traffic patterns must be identified so that connectivity requirements can be determined. These patterns can be learned by using Cisco NetFlow capabilities or other traffic analysis tools. In addition to normal traffic patterns, business application requirements should be reviewed to determine whether there are certain applications that have special connectivity requirements. This will have an impact on the topology that is chosen.

General Deployment Guidelines for Choosing the Best VPN LAN Topology

Consider the following general guidelines when determining which VPN topology provides the optimum path and performance for a network:

• Using individual, manually configured site-to-site VPN connections if the number of required connections is low and managing them can be easily accomplished.

• Converting an existing partially meshed network to either a fully meshed network or a hub-and-spoke network to facilitate deployment of VPN topologies.

• Using the hub-and-spoke VPN topology if the physical network infrastructure is already a hub-and-spoke design. This will lend itself to easier deployment and management of the VPN topology.

• Using the full-mesh VPN topology if there is a requirement for any-to-any connectivity with optimal traffic flow.

Choose an Appropriate VPN WAN Technology

Although IPsec provides standards for transmission protection and key management, there are several deployment choices that must be made. Proper analysis of network traffic patterns and business requirements is required to make these deployment decisions.

image

The main choices that must be made when deploying site-to-site VPN technologies are in the following areas:

• User traffic encapsulation technology: IPsec provides many different encapsulation methods (Authentication Header [AH] and Encapsulating Security Payload [ESP]) and several encapsulating modes (transport mode, tunnel, and a mixed hybrid mode used by Group Encrypted Transport [GET] VPN). Most implementations use IPsec tunnel mode or a combination of IPsec and generic routing encapsulation (GRE) as a method of transport. GET is a mixed encapsulation method that is usually considered as a nontunneling mode and therefore is not recommended for use over public networks.

• Configuration scalability: In an environment with a large number of required VPN peers or one that is expected to grow substantially, the network architect should choose a VPN technology that includes configuration scalability to make managing (adding and removing sites from VPNs) VPNs easier.

• Authentication scalability: As with configuration scalability, authentication of peers in an IPsec VPN architecture can become cumbersome. Each peer must authenticate a large number of other peers, especially if the partially or fully meshed topologies are deployed. Using a pre-shared key that must be manually shared between peers will not scale well. The number of passwords that need to be shared among peers is found with the formula n*(n-1)/2. A network that is fully meshed with 100 nodes would require manually sharing 4500 passwords. Using Public Key Infrastructure (PKI) to provide authentication using certificates provides a scalable solution but requires a properly deployed and maintained PKI and supporting infrastructure to already be in place.

Input Parameters for Choosing the Best VPN WAN Technology

Choosing the appropriate VPN technology for an environment requires analysis of the underlying network. If the VPN will be built across a public transport network, you must choose a tunneling VPN method. You must also consider configuration and authentication scalability when choosing a VPN technology because it will greatly affect network manageability. Table 14-3 summarizes the input parameters.

Table 14-3. VPN Technology Input Requirement Parameters

image

image

Four main site-to-site VPN WAN technologies are available in the Cisco IOS Software:

• Individual IPsec tunnels: This technology is implemented using Virtual Tunnel Interfaces (VTI) or GRE over IPsec tunnels. A separate point-to-point tunnel must be provisioned for each and every tunnel peering, limiting this solution with very low configuration scalability. If pre-shared keys are used for authentication between the two peers, this solution is considered to have low authentication scalability. Individual IPsec tunnels are adequate for any transport and can therefore be used across the public Internet, but should be used only in environments where the number of tunnels is very small.

• Cisco Easy VPN: Created to support hub-and-spoke networks, Easy VPN provides very high hub configuration scalability and authentication scalability using either pre-shared keys or PKI. Although this book does not cover Easy VPN configuration for site-to-site VPNs, it is very similar to Easy VPN remote access VPN deployment. Easy VPN does support IP tunneling; therefore, it is adequate for users over any transport network, including the Internet.

• Cisco Dynamic Multipoint VPN (DMVPN): DMVPN is based on a hub-and-spoke configuration but allows spoke-to-spoke tunnels to be dynamically and automatically provisioned. Configuration scalability is high because only spoke-to-hub peering needs to be configured, and as long as PKI is used for authentication, authentication scalability is high as well. DMVPN can be used in hub-and-spoke, partial mesh, and full mesh environments. It is also adequate for connections that traverse public networks, such as the Internet, because it supports IP tunnels.

• Cisco GET VPN: Cisco GET VPN uses a mixed encapsulation in which the IP addressing of the packets does not get changed as it is encapsulated. Because of this, it can only be deployed over networks that can route the internal addresses, such as Multiprotocol Label Switching (MPLS) or private WAN circuits. GET VPNs cannot be deployed over the Internet because of this. Cisco GET defaults to a full mesh topology with a small number of policy/authentication hubs called key servers. Because of this, Cisco GET provides high configuration and authentication scalability.

Table 14-4 summarizes the features of the four VPN technology choices.

Table 14-4. VPN Technology Comparison

image

General Deployment Guidelines for Choosing the Best VPN WAN Technology

image

Consider the following general guidelines when determining which VPN technology provides the optimum site-to-site IPsec VPN protection:

• A VPN technology that supports tunneling must be chosen if the transport network does not route internal VPN address spaces. All Cisco IOS Software IPsec VPN technologies except GET VPN use IP tunneling.

• Fully meshed networks demand configuration and authentication on every device. This can be achieved by deploying PKI-based authentication.

• Hub-and-spoke implementations require high configuration and authentication scalability on the hub device. This makes a hub-and-spoke network much easier to deploy in some cases.

Core Features of IPsec VPN Technology

IPsec is a set of security protocols that work together to provide security to IP traffic while in transit. Defined in RFC 4301, “Security Architecture for the Internet Protocol,” IPsec provides access control, integrity, authentication, and protection against replays and confidentiality. These services are implemented at the IP layer and therefore protect IP and upper-layer protocols.

IPsec enables a system that chooses various security protocols, determines the necessary algorithms to use for a chosen service, and implements the cryptographic keys needed for those services. IPsec can be used to protect paths between a pair of hosts, between a pair of security gateways (typically a router or firewall), and between a gateway and a host.

In addition to providing encryption at the IP network layer, IPsec also defines a new set of headers that are added to the IP datagram. This new header is inserted after the original IP header and before the Layer 4 protocol. Table 14-5 provides a list of the protocols that comprise IPsec and descriptions of each.

image

Table 14-5. IPsec VPN Protocols

image

IPsec Security Associations

IPsec uses the concept of a Security Association (SA) as a means to describe fundamental security parameters, such as encryption algorithms, keys, traffic specifications, and others. SAs are used by AH and ESP, as well as by one of the major functions within the IKE protocol. SAs are created as a result of an IPsec VPN connection being established between two hosts or two gateways. When a protected connection is created, there will be two SAs that are created, one for each direction.

Internet Key Exchange (IKE)

IKE is a protocol defined by RFC 2408 that uses parts of several other protocols, such as Internet Security Association Key Management Protocol (ISAKMP), Oakley, and Secure Key Exchange Mechanism (SKEME), to dynamically create a shared security policy and authenticated keys for services that require keys, such as IPsec. IKE establishes a secure, authenticated connection that is defined by an IKE SA. This SA is completely distinct from the IPsec SA. The IKE SA is established between two entities and is used to negotiate IPsec SAs. This process calls for the two entities to authenticate themselves to each other and then establish shared session keys that IPsec encapsulations and algorithms use to convert clear-text messages into cipher text.

Reasons to implement IKE in an IPsec configuration include

• Scalability. Without IKE, all IPsec VPN negotiations must be performed manually, on all hosts.

• Manageable manual configuration.

• SA characteristics negotiation.

• Automatic key generation.

• Automatic key refresh.

IPsec Phases

image

IPsec has two phases:

• Phase 1: Two IKE peers establish a secure, authenticated channel and establish shared keying information using a Diffie-Hellman key exchange. This channel is known as the IKE (or ISAKMP) SA. Phase 1 can function in either main mode or aggressive mode.

• Phase 2: Additional SAs are established for use by services, such as IPsec or any other service that needs secure keying material or parameter negotiation, or both. IPsec session keys are derived from the initial keying material that was obtained during the Phase 1 Diffie-Hellman key exchange. The IPsec session keys can be optionally created using new, independent Diffie-Hellman key exchanges by enabling the Perfect Forward Secrecy (PFS) option. This Phase 2 exchange is called the IKE Quick Mode. IKE Quick Mode is one of two modes of IKE Phase 2, with the other being the Group Domain of Interpretation (GDOI) Mode used by GET VPN.

IKE Main and Aggressive Mode

IKE Phase 1 can operate in either main or aggressive mode:

• Main mode: Permits more flexible IKE policy negotiation and always protects peer identity. This means that an eavesdropper cannot discover the identity of either peer in the IKE exchange. IKE main mode does not support peers with dynamically assigned addresses when using pre-shared keys for authentication. It does support them when PKI-based authentication is in use.

• Aggressive mode: Does not provide very much IKE policy negotiation and does not protect peer identity, which could make your VPN susceptible to session hijacking. IKE aggressive mode does support pre-shared key authentication for dynamically addressed peers using names to authenticate. Aggressive mode is faster than main mode but clearly provides a lower level of security.

Encapsulating Security Payload

ESP encapsulation provides a mixture of security services for IPv4 and IPv6, such as confidentiality, authenticity, and integrity of IP data. ESP also provides protection from antireplay by encrypting, sequencing, and authenticating data that is to be protected; placing it in the data portion of the IP ESP payload; and then sequencing and authenticating the ESP encapsulated packet. Figure 14-1 depicts the headers and trailers that are added to the IP packet as well as what portion of the packet is encrypted or authenticated by ESP.

image

Figure 14-1. ESP Packet Encapsulation

image

Note

There is a performance cost associated with using ESP. This cost is primarily because of the encryption and decryption processes that take place on the data, but there is a packet size cost because of the additional overhead in bytes that ESP adds to an IP packet.

In tunnel mode, ESP encapsulates and protects the entire IP packet. Because the entire IP packet is encapsulated, including the original IP header, a new header is created so that the packet can be forwarded. The new header will have the IP addresses of the encrypting routers. The overhead added to a packet for the ESP encapsulation process is 20 bytes.

Choose Appropriate VPN Cryptographic Controls

As equally as important as choosing an appropriate VPN topology and VPN technology, choosing the proper cryptographic controls ensures that user data is adequately protected.

Choosing the right controls means analyzing risk assessments, the underlying network environment, and customer requirements. There are several cryptographic features about which the network designer must make decisions:

• Choosing IKE peer authentication and algorithms as well as credentials of adequate strength.

• Choosing a policy to protect the IKE key management session (IKE SA). This includes choosing an IKE session encryption algorithm, IKE packet authentication algorithm, and IKE packet integrity assurance algorithms.

• Choosing a policy to protect user traffic. This includes choosing traffic encryption, authentication, and integrity assurance algorithms.

• Choosing key management procedures and processes. This includes key creation, secure key exchange, key storage, key revocation, and key destruction.

IPsec Security Associations

Choosing adequate cryptographic controls means understanding the sensitivity of the data being protected and the trustworthiness of the underlying transport network. Highly sensitive data and an untrusted transport network (such as the Internet) would require stronger controls and longer key lengths.

Another factor that will affect choices about cryptographic controls is the hardware and software capability of existing network devices. IPsec mechanisms can require high-performance CPUs. Some VPN features might require a specific version of Cisco IOS Software that could require a memory upgrade. Table 14-6 summarizes the input parameters.

Table 14-6. Cryptographic Control Input Parameters

image

Algorithm Choices

The two main factors to take into consideration when choosing an encryption algorithm are as follows:

• The views of the cryptographic community will indicate to you whether a particular algorithm is considered trustworthy. Most new algorithms are broken fairly easily, and the ones that have been in use for a long time protecting data are recommended.

• The algorithm under consideration must provide key lengths that meet the organization’s data protection requirement. Typically, breaking an encryption algorithm is done through brute-force attacks, so key length is paramount to withstanding these attacks.

In addition to these basic security criteria, performance of an algorithm is another factor that affects which one is chosen. For example, Advanced Encryption Standard (AES) is typically much faster than Triple DES (3DES) on the same hardware.

The cryptographic controls that comprise an ISAKMP policy are discussed in the sections that follow. These are the choices you must make to ensure that your VPN meets the security requirements of your organization.

Encryption Algorithms

Both AES and 3DES are good, trusted choices, with 128-bit AES preferred over other key lengths of AES because of recently discovered noncritical weaknesses in 192-bit and 256-bit AES. 3DES is not recommended for use with Cisco GET VPNs because of possible reuse of its reinitialization vector when using the same group key for many peers.

HMAC Algorithms

Secure Hash Algorithm 1 (SHA-1) is recommended for the Hash-based Message Authentication Code (HMAC) integrity and authentication algorithm. It is the only recommended choice for Cisco IOS Software IKE/IPsec implementations, even though it does contain weaknesses.

Peer Authentication/Signature Algorithms

Rivest, Shamir, and Adelman (RSA) is recommended for asymmetric algorithms as long as an adequately long key is used and the private key is well protected.

Key Exchange Algorithms

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

Table 14-7 summarizes the algorithm choices you must make when deploying IPsec VPNs along with the recommended cryptographic control.

image

Table 14-7. Algorithm Choices

image

Key Length Recommendations

Key length can have a direct influence on the strength of protection provided by a particular algorithm. With most algorithms, the level of protection provided is directly dependent on the key length chosen. Choosing a key length should be done so that the key will protect data for an adequate period of time as long as the algorithm is a trusted algorithm.

Table 14-8 shows minimum recommended key lengths for asymmetric and symmetric encryption algorithms.

Table 14-8. Key Length Recommendations

image

General Deployment Guidelines for Choosing Cryptographic Controls for a Site-to-Site VPN Implementation

Consider the following general guidelines when choosing appropriate cryptographic controls for a site-to-site VPN implementation:

• Always base cryptographic control choices on the result of either formal or informal risk assessment to ensure that the best protection is deployed across untrusted networks. If assessments are not available and cannot be performed, use the strongest protection controls available to reduce risk.

• Consider the dependencies between cryptographic controls so as to not introduce a weakness that actually increases risk to organizational data.

• Most attacks against cryptographic systems today are aimed at the key management system, which is vulnerable to attack because of human factor involvement. To mitigate this, ensure that very efficient key management processes and procedures exist (manually creating keys, revoking keys, storing keys, and so on).

Design and Implementation Resources

Cisco has provided several design and implementation guides that are available on Cisco.com. The Design Zone for WAN/MAN has an IPsec VPN design overview document. In addition, there are several, more specific design guides found on the site. The guides include the following:

• Group Encrypted Transport VPN Design Guide

• Infrastructure Protection and Security Service Integration Design for the Next Generation WAN Edge

• Dynamic Multipoint VPN Design Guide

• Point-to-Point GRE over IPsec Design Guide

• Layer 3 MPLS VPN Enterprise Consumer Guide

• V3PN: Redundancy and Load Sharing Design Guide

• IPsec Direct Encapsulation VPN Design Guide

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 this chapter, noted with the Key Topics icon in the margin of the page. Table 14-9 lists a reference of these key topics and the page numbers on which each is found.

Table 14-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:

Internet Key Exchange (IKE)

Authentication Headers (AH)

Encapsulating Security Payload (ESP)

site-to-site VPN

hub-and-spoke network

partially meshed network

fully meshed network

P2P tunnels

Group Encrypted Transport (GET) VPN

generic routing encapsulation (GRE)

Public Key Infrastructure (PKI)

Virtual Tunnel Interfaces (VTI)

Cisco Easy VPN

Dynamic Multipoint VPN (DMVPN)

Security Association (SA)

AES

DES

HMAC algorithm

Fill in the Blanks

  1. Use individual P2P VPN peering only when the number of VPN connections is _____.
  2. When using any-to-any communications with direct communication paths with low latency and high throughput, a _____ topology is typically the only choice.
  3. A VPN technology that starts with a hub-and-spoke topology but allows dynamically and automatically built VPNs between spoke sites is _____.
  4. Cisco GET VPN is considered to be a _____ encapsulation mode and therefore cannot be used on transport networks that cannot route internal VPN addresses.
  5. _____ provides a framework that provides policy negotiations and key management processes.
  6. _____ is a set of security protocols that work together to provide security to IP traffic while in transit.
  7. _____ provides a mixture of security services for IPv4 and IPv6, such as confidentiality, authenticity, and integrity of IP data.
  8. A VPN technology that supports _____ must be chosen if the transport network does not route internal VPN address spaces.

References

BlueKrypt - Cryptographic Key Length Recommendation, www.keylength.com.

IPsec VPN WAN Design Overview, www.cisco.com/en/US/docs/solutions/Enterprise/WAN_and_MAN/IPSec_Over.html.

Group Encrypted Transport VPN Design Guide, www.cisco.com/en/US/prod/collateral/vpndeve/ps6525/ps9370/ps7180/GETVPN_DIG_version_1_0_External.pdf.

Infrastructure Protection and Security Service Integration Design for the Next Generation WAN Edge, www.cisco.com/en/US/docs/solutions/Enterprise/WAN_and_MAN/IPSNGWAN.html.

Dynamic Multipoint VPN Design Guide, www.cisco.com/en/US/docs/solutions/Enterprise/WAN_and_MAN/DMVPDG.html.

Point-to-Point GRE over IPsec Design Guide, www.cisco.com/en/US/docs/solutions/Enterprise/WAN_and_MAN/P2P_GRE_IPSec/P2P_GRE.html.

Layer 3 MPLS VPN Enterprise Consumer Guide, www.cisco.com/en/US/docs/solutions/Enterprise/WAN_and_MAN/L3VPNCon.html.

V3PN: Redundancy and Load Sharing Design Guide, www.cisco.com/en/US/docs/solutions/Enterprise/WAN_and_MAN/VPNLoad/VPN_Load.html.

IPsec Direct Encapsulation VPN Design Guide, www.cisco.com/en/US/docs/solutions/Enterprise/WAN_and_MAN/Dir_Encap.html.