Ipsec Presentation
Ipsec Presentation
Ipsec Presentation
Presented by
Avinash R Desai
AGENDA
Why Do We Care?
Many organizations are trying to use IPSec VPN to costs
and simplify new connections
VPN allows
Shared Internet and Enterprise access
Reduced access line costs
Ease of provisioning, flexibility
Increased security
Agenda
Introduction and Motivation
IPSec Basics
Enterprise IPSec VPN
Managing VPN
Wrap-up
IPSec Basics
IPSec uses a Security Association (SA) and crypto key to encrypt
selected data between a pair of sites
This key is used with the DES, 3DES, or AES forms of encryption
to both encrypt and decrypt data
The key is automatically established, changed, and managed by
IPSec devices using IKE (Internet Key Exchange), a.k.a. ISAKMP
Before a key can be established, IKE does authentication
Shared secret or Certificate Authority are two ways to do this
IKE uses public key crypto to securely do its job
IKE uses public key crypto to securely do its job
Diffie-Hellman is the technique used to securely exchange encryption
keys
Message Hashing
Message Hashing is used to detect altered messages
Message bits a secret key are combined into short hash code
Hash code sent in header
If received message hash doesnt match, message was altered
Two forms: SHA and MD5
SHA is a bit stronger
Message Hashing
Message bits a secret key are combined into short hash code
Hash code sent in header
If received message hash doesnt match, message was altered
Two forms: SHA and MD5
SHA is a bit stronger
Message Hashing
IPSec comes in two forms
AH provides a keyed hash and authentication data
Ensures data comes from peer router (authentication)
Detects alterations (keyed hash)
But does not encrypt for confidentiality
ESP encrypts
Two sub-modes: tunnel and transport
In tunnel mode, the new IP header hides source and
destination addresses: keeps server address confidential
Keyed hash for detecting alterations
Authentication
Encryption
What to Encrypt
The crypto map you configure references an access list for
interesting packets
What to encrypt (outbound)
What to decrypt (inbound)
ESP encrypts
If the router encrypts or decrypts the wrong packet, it gets
nonsense and a bad checksum discarded packet!
Agenda
Managing VPN
Wrap-up
Design Assumptions
Avoiding Fragmentation
We want to avoid fragmenting the IPSec packets
They have to be re-assembled at the termination router to be
decrypted
Re-assembly is process switched
Slow + CPU impact
So create fragments BEFORE IPSec encrypts!
Reduce GRE tunnel MTU to 1400+ Bytes
Consider enabling Path MTU Discovery on the tunnels
Which Router?
Cisco tested ESP tunnels with GRE to 2 head-end sites, 240
branch routers
Recommendations are based on 55-65% CPU for a specific traffic
mix.
This is a summary: see the Cisco documents for details. In
particular, specific models within a product family may have
lower performance than that shown. Your Mileage May Vary.
Other Recommendations
Have a summarizable addressing scheme
It can makes crypto ACLs simpler, less of an issue with GRE
Use route summarization
For central DHCP, use helper addresses remotely
Use IPSec Tunnel Mode with 3DES
Dont use IKE keepalives
Base number of head-end devices on number of remote sites
and throughput
Use appropriate (recent) Cisco IOS releases
Avoid IPSec through NAT points
Service Provider
Service Provider 2
Many or even most ISPs do not honor the L3 QoS markings
Your voice traffic may experience unacceptable delay or jitter
Whenever possible, you need SLAs
Covering overall delay and jitter, repair time, etc.
Or for QoS-aware service guaranteeing certain delay and jitter
levels for various classes of traffic, based on agreed-upon markings
Otherwise, you can deploy and later discover your IPSec VPN isnt
working very well: no recourse!
Multiple ISPs is harder
SLAs generally only apply within a single ISPs network
Beware: some home cable & DSL services block IPSec unless
business grade service is paid for
SLAs
CPN Multi-service VPN standards:
Jitter less than or equal to 20 msec
Delay less than or equal to 60 msec one way
Packet Loss less than or equal to 0.5 percent
Configuration Steps
Step 1: Configure IKE policy
Step 2: Specify IPSec transform and protocol
Step 3: Create access lists (ACLs) for encryption
Step 4: Configure crypto map
Step 5: Apply crypto map
Agenda
Introduction and Motivation
IPSec Basics
Enterprise IPSec VPN
Managing VPN
Wrap-up
Agenda
Introduction and Motivation
IPSec Basics
Enterprise IPSec VPN
Managing VPN
Wrap-up
See Also
AVVID Enterprise Site-to-Site VPN Design
http://www.cisco.com/application/pdf/en/us/guest/netsol/ns142/c649/ccmigratio
n_09186a00800d67f9.pdf
Summary
Use GRE + IPSec in a hub and spoke design for easily managed
IPSec VPN with redundancy and failover
Cisco has tested performance under load for 240 remote branch
routers going to 2 central routers
Fragment before IPSec for much betterperformance
Q&A
THANKYOU