Conventional Private Networks

Virtual Private Networks

VPNs

• A Virtual Private Network (VPN) provides the same network

connectivity for remote users over a public infrastructure as
they would have over a private network.
• VPN services for network connectivity include:
– Authentication
– Data integrity
– Confidentiality
Characteristics of VPNs
VPN Concepts

• A secure VPN is a combination of concepts:

VPN Packet Encapsulation
VPN Packet Encapsulation
Two Types of VPNs

• Site-to-Site VPNs:
– Intranet VPNs connect corporate headquarters, remote offices, and branch
offices over a public infrastructure.
– Extranet VPNs link customers, suppliers, partners, or communities of
interest to a corporate Intranet over a public infrastructure.

• Remote Access VPNs:

– Which securely connect remote users, such as mobile users and
telecommuters, to the enterprise.
Site-to-Site VPNs
Site-to-Site VPNs
Remote Access VPNs
Remote Access VPNs
Remote Access VPNs
Cisco VPN Product Line
Product Choice Remote-Access VPN Site-to-Site VPN

Cisco VPN-Enabled Router Secondary role Primary role

Cisco PIX 500 Series Security Appliances (Legacy) Secondary role Primary role

Cisco ASA 5500 Adaptive Security Appliances Primary role Secondary role

Cisco VPN 3000 Series Concentrators Primary role Secondary role

Home Routers (Linksys, D-Link, …) Primary role Secondary role

Layer 3 Tunneling

• There are 2 popular site-to-site tunneling protocols:

– Cisco Generic Routing Encapsulation (GRE)
– IP Security Protocol (IPsec)

• When should you use GRE and / or IPsec?

Yes
User Traffic IP Only?

No

No Yes
Unicast
Use GRE Tunnel Use IPsec VPN
Only?
Generic Routing Encapsulation (GRE)

• GRE can encapsulate almost any other type of packet.

– Uses IP to create a virtual point-to-point link between Cisco routers
– Supports multiprotocol (IP, CLNS, …) and IP multicast tunneling (and
therefore routing protocols)
– Best suited for site-to-site multiprotocol VPNs
– RFC 1702 and RFC 2784

GRE header adds 24 bytes

of additional overhead
Optional GRE Extensions

• GRE can optionally contain any one or more of these fields:

– Tunnel checksum
– Tunnel key
– Tunnel packet sequence number

• GRE keepalives can be used to track tunnel path status.

Generic Routing Encapsulation (GRE)

• GRE does not provide encryption!

– It can be monitored with a protocol analyzer.

• However, GRE and IPsec can be used together.

• IPsec does not support multicast / broadcast and therefore
does not forward routing protocol packets.
– However IPsec can encapsulate a GRE packet that encapsulates
routing traffic (GRE over IPsec).
Five Steps to Configuring a GRE Tunnel

1. Create a tunnel interface: interface tunnel 0

2. Assign the tunnel an IP address.
3. Identify the source tunnel interface: tunnel source
4. Identify the tunnel destination: tunnel destination
5. (Optional) Identify the protocol to encapsulate in the GRE tunnel:
tunnel mode gre ip
– By default, GRE is tunneled in an IP packet.
Five Steps to Configuring a GRE Tunnel

R1(config)# interface tunnel 0 R2(config)# interface tunnel 0

R1(config–if)# ip address 10.1.1.1 255.255.255.252 R2(config–if)# ip address 10.1.1.2 255.255.255.252
R1(config–if)# tunnel source serial 0/0 R2(config–if)# tunnel source serial 0/0
R1(config–if)# tunnel destination 209.165.200.225 R2(config–if)# tunnel destination 209.165.201.1
R1(config–if)# tunnel mode gre ip R2(config–if)# tunnel mode gre ip
R1(config–if)# R2(config–if)#
GRE Tunnel Example
IPsec - Internet Protocol Security

• A “framework” of open standards developed by the IETF to

create a secure tunnel at the network (IP) layer.
– It spells out the rules for secure communications.
– RFC 2401 - RFC 2412

• IPsec is not bound to any specific encryption or

authentication algorithms, keying technology, or security
algorithms.
• IPsec allows newer and better algorithms to be implemented
without patching the existing IPsec standards.
Encryption / Decryption

• Encryption transforms information (clear text) into ciphertext which

is not readable by unauthorized users.
• Decryption transforms ciphertext back into clear text making it
readable by authorized users.
• Popular encryption algorithms include:
– DES
– 3DES
– AES
Authentication / Hashing

• Guarantees message integrity by using an algorithm to convert a

variable length message and shared secret key into a single fixed-
length string.
• Popular hashing methods include:
– SHA (Cisco default)
– MD5
Non-repudiation

• Is the ability to prove a transaction occurred.

– Similar to a signed package received from a shipping company.

• This is very important in financial transactions and similar

data transactions.
Diffie-Hellman Key Exchange

• How do the encrypting and decrypting devices get the

shared secret key?
– The easiest method is Diffie-Hellman public key exchange.

• Used to create a shared secret key without prior knowledge.

• This secret key is required by:
– The encryption algorithm (DES, 3DES, AES)
– The authentication method (MD5 and SHA-1)
Pre-Shared Key

• Identifies a communicating party during a phase 1 IKE

negotiation.
• The key must be pre-shared with another party before the
peers routers can communicate.
IPsec - Internet Protocol Security

• A “framework” of open standards developed by the IETF to

create a secure tunnel at the network (IP) layer.
– It spells out the rules for secure communications.

• IPsec is not bound to any specific encryption or

authentication algorithms, keying technology, or security
algorithms.
IPsec Protocol Framework
IPsec Protocol Framework

ESP
AH ESP
+ AH

3
DES AES SEAL
DES

MD5 SHA

PSK RSA

DH1 DH2 DH5 DH7

IPsec Protocol Framework
Confidentiality
Integrity
Authentication
Secure Key Exchange

ESP
AH ESP
+ AH

3
DES AES SEAL
DES

MD5 SHA

PSK RSA

DH1 DH2 DH5 DH7

768 bits 1024 bits 1536 bits

Used by DES and 3DES Used by AES

IPsec Framework Protocols

• IPsec uses two main protocols to create a security framework:

– AH: Authentication Header
– ESP: Encapsulating Security Payload
Authentication Header (AH)

• AH provides authentication and optional replay-detection

services.
– It authenticates the sender of the data.
– AH operates on protocol number 51.
– AH supports the HMAC-MD5 and HMAC-SHA-1 algorithms.
Authentication Header (AH)

• AH does not provide confidentiality (encryption).

– It is appropriate to use when confidentiality is not required or
permitted.
– All text is transported unencrypted.

• It only ensures the origin of the data and verifies that the
data has not been modified during transit.
• If the AH protocol is used alone, it provides weak protection.
• AH can have problems if the environment uses NAT.
Encapsulating Security Payload (ESP)

• ESP provides the same security services as AH

(authentication and integrity) AND encryption service.
– It encapsulates the data to be protected.
– It operates on protocol number 50.
Encapsulating Security Payload (ESP)

• ESP can also provide integrity and authentication.

– First, the payload is encrypted using DES (default), 3DES, AES, or
SEAL.
– Next, the encrypted payload is hashed to provide authentication
and data integrity using HMAC-MD5 or HMAC-SHA-1.
Transport Mode and Tunnel Mode

• ESP and AH can be applied to IP packets in two different

modes.
Transport Mode

• Security is provided only for the Transport Layer and above.

– It protects the payload but leaves the original IP address in
plaintext.

• ESP transport mode is used between hosts.

• Transport mode works well with GRE, because GRE hides
the addresses of the end devices by adding its own IP.
Tunnel Mode

• Tunnel mode provides security for the complete original IP

packet.
– The original IP packet is encrypted and then it is encapsulated in
another IP packet (IP-in-IP encryption).

• ESP tunnel mode is used in remote access and site-to-site

implementations.
Key Exchange

• The IPsec VPN solution:

– Negotiates key exchange parameters (IKE).
– Establishes a shared key (DH).
– Authenticates the peer.
– Negotiates the encryption parameters.

• The negotiated parameters between two devices are known as a

security association (SA).
Security Associations (SAs)

• SAs represent a policy contract between two peers or hosts,

and describe how the peers will use IPsec security services
to protect network traffic.
• SAs contain all the security parameters needed to securely
transport packets between the peers or hosts, and
practically define the security policy used in IPsec.
SA Security Parameters
IKE - Internet Key Exchange

• IKE helps IPsec securely exchange cryptographic keys

between distant devices.
– Combination of the ISAKMP and the Oakley Key Exchange
Protocol.
• Key Management can be preconfigured with IKE (ISAKMP)
or with a manual key configuration.
– IKE and ISAKMP are often used interchangeably.

• The IKE tunnel protects the SA negotiations.

– After the SAs are in place, IPsec protects the data that Alice and
Bob exchange.
How IPsec uses IKE

1. Outbound packet is sent from 4. Packet is sent from Alice to

Alice to Bob. No IPsec SA. Bob protected by IPsec SA.

IPsec IPsec
IKE - Internet Key Exchange

• There are two phases in every IKE negotiation

– Phase 1 (Authentication)
– Phase 2 (Key Exchange)
• IKE negotiation can also occur in:
– Main Mode
– Aggressive mode
• The difference between the two is that Main mode requires
the exchange of 6 messages while Aggressive mode
requires only 3 exchanges.
IKE Main Mode Phases

• IKE Phase One:

– Negotiates an IKE protection suite.
– Exchanges keying material to protect the IKE session (DH).
– Authenticates each other.
– Establishes the IKE SA.
– Main Mode requires the exchange of 6 messages while Aggressive mode
only uses 3 messages.

• IKE Phase Two:

– Negotiates IPsec security parameters, known as IPsec transform sets.
– Establishes IPsec SAs.
– Periodically renegotiates IPsec SAs to ensure security.
– Optionally performs an additional DH exchange.
IKE Phases
Five Steps of IPsec

Step 1 Host A sends interesting traffic destined for Host B.

IKE Phase 1 authenticates IPsec peers and negotiates IKE SAs to create a secure
Step 2
communications channel for negotiating IPsec SAs in Phase 2.

IKE Phase 2 negotiates IPsec SA parameters and creates matching IPsec SAs in the
Step 3
peers to protect data and messages exchanged between endpoints.

Data transfer occurs between IPsec peers based on the IPsec parameters and keys
Step 4
stored in the SA database.

Step 5 IPsec tunnel termination occurs by SAs through deletion or by timing out.
Step 1 – Interesting Traffic
Step 2 – IKE Phase 1

IKE Policy Negotiation

Step 2 – IKE Phase 1

DH Key Exchange

RouterA randomly chooses a string RouterB hashes the received string

and sends it to RouterB. together with the pre-shared secret
and yields a hash value.

RouterA calculates its own hash of

the random string, together with the
pre-shared secret, and matches it RouterB sends the result of hashing
with the received result from the back to RouterA.
other peer.
If they match, RouterB knows the
pre-shared secret, and is considered
authenticated.
Step 2 – IKE Phase 1

DH Key Exchange

Now RouterB randomly chooses a

RouterA also hashes the received different random string and sends it
string together with the pre-shared to RouterA.
secret and yields a hash value.

RouterB calculates its own hash of

RouterA sends the result of hashing the random string, together with the
back to RouterB. pre-shared secret, and matches it
with the received result from the
other peer.
If they match, RouterA knows the
pre-shared secret, and is considered
authenticated.
Step 2 – IKE Phase 1

Peer Authentication
Step 3 – IKE Phase 2

IPsec Negotiation
Step 3 – IKE Phase 2

Transform Set Negotiation

Step 3 – IKE Phase 2

Security Associations
Step 4

IPsec Session
Step 5

Tunnel Termination
CCP ‘Wizards’

• Examples of CCP wizards include:

– Startup wizard for initial router configuration
– LAN and WAN wizards
– Policy-based firewall and access-list management to easily configure firewall
settings based on policy rules
– IPS wizard
– One-step site-to-site VPN wizard
– One-step router lockdown wizard to harden the router
VPN Configuration Page
VPN Configuration Page
Site-to-Site VPN Components

• VPN wizards use two sources to create a VPN connection:

– User input during the step-by-step wizard process
– Preconfigured VPN components
• CCP provides some default VPN components:
– IPsec transform set for Quick Setup wizard
• Other components are created by the VPN wizards:
– Two IKE policies
• Some components (for example, PKI) must be configured
before the wizards can be used.
VPN Configuration Page
Quick Setup
Quick Setup
Quick Setup
Step-by-Step Setup

• Multiple steps are required to configure the VPN

connection:
– Defining connection settings: Outside interface, peer address,
authentication credentials
– Defining IKE proposals: Priority, encryption algorithm, HMAC,
authentication type, Diffie-Hellman group, lifetime
– Defining IPsec transform sets: Encryption algorithm, HMAC, mode
of operation, compression
– Defining traffic to protect: Single source and destination subnets,
ACL
– Reviewing and completing the configuration
Configuring Connection Settings
Configuring IKE Proposals
Configuring the Transform Set
Defining Source and Destination Subnet
Defining Interesting Traffic
Adding Rules to ACLs
Configuring a New ACL Rule Entry
Review the Generated Configuration
Test Tunnel Configuration and Operation

Check VPN status.

Test the VPN Create a mirroring configuration

configuration. if no CCP is available on the peer.
Test Tunnel Configuration and Operation
Teleworking Benefits
Remote-Access Solutions

• There are two primary methods for deploying remote-

access VPNs:

IPsec Remote Any Anywhere SSL-Based

Access VPN Application Access VPN
Remote-Access Solutions

SSL IPsec

Web-enabled applications, file sharing,

Applications e-mail
All IP-based applications

Moderate Stronger
Encryption
Key lengths from 40 bits to 128 bits Key lengths from 56 bits to 256 bits

Strong
Moderate
Authentication Two-way authentication using shared
One-way or two-way authentication
secrets or digital certificates
Moderate
Ease of Use Very high Can be challenging to nontechnical
users
Strong
Moderate
Overall Security Only specific devices with specific
Any device can connect
configurations can connect
SSL VPN
Clientless, Thin Client, or Full Client
Establishing SSL Session
Cisco Easy VPN
Cisco Easy VPN Components

• Cisco Easy VPN Server - A Cisco IOS router or Cisco PIX / ASA Firewall
acting as the VPN head-end device in site-to-site or remote-access
VPNs.
• Cisco Easy VPN Remote - A Cisco IOS router or Cisco PIX / ASA
Firewall acting as a remote VPN client.
• Cisco Easy VPN Client - An application supported on a PC used to
access a Cisco VPN server.
Cisco Easy VPN Exchange
Configuring Easy VPN Server
Configuring Easy VPN Server Physical
Interface
Configuring IKE Proposals
Configuring Transform Set
Configuring VPN Authentication Method List
Configuring VPN Authentication Group
Policy
Configuration Summary
Edit Easy VPN Server
Easy VPN Server Test
Connecting Using the Client

R1 R1-vpn-cluster.span.com