decrypt the data. For additional security, you can encrypt the keys that decrypt the data
using Diffie-Hellman asymmetric encryption. ESP can also authenticate data in the VPN
using MD5 and SHA-1 algorithms. You can use ESP to encrypt, authenticate, or encrypt
and authenticate data depending on your security requirements.
NOTE:
We strongly recommend that you do not use null AH with ESP.
Because ESP uses keys to encrypt and decrypt data, each VPN node must have the
correct key to send and receive VPN data through the VPN tunnel.
You can manually configure a key for each VPN node, or use a key exchange protocol to
automate key generation and distribution:
•
Manual Key IKE—In a manual key VPN, you specify the encryption algorithm,
authentication algorithm, and the Security Parameter Index (SPI) for each VPN node.
Because all security parameters are static and consistent, VPN nodes can send and
receive data automatically, without negotiation.
•
Autokey IKE—In an AutoKey IKE VPN, you can use the Internet Key Exchange (IKE)
protocol to generate and distribute encryption keys and authentication algorithms to
all VPN nodes. IKE automatically generates new encryption keys for the traffic on the
network, and automatically replaces those keys when they expire. Because IKE
generates keys automatically, you can give each key a short life span, making it expire
before it can be broken. By also exchanging authentication algorithms, IKE can confirm
that the communication in the VPN tunnel is secure.
Because all security parameters are dynamically assigned, VPN nodes must negotiate
the exact set of security parameters that will be used to send and receive data to other
VPN nodes. To enable negotiations, each VPN node contains a list of proposals; each
proposal is a set of encryption keys and authentication algorithms. When a VPN node
attempts to send data through the VPN tunnel, IKE compares the proposals from each
VPN node and selects a proposal that is common to both nodes. If IKE cannot find a
proposal that exists on both nodes, the connection is not established.
IKE negotiations include two phases:
•
In Phase 1, two members establish a secure and authenticated communication
channel.
•
In Phase 2, two members negotiate Security Associations for services (such as IPSec)
that require key material and/or parameters.
VPN nodes must use the same authentication and encryption algorithms to establish
communication.
•
Replay protection—In a replay attack, an attacker intercepts a series of legitimate
packets and uses them to create a denial-of-service (DoS) against the packet
destination or to gain entry to trusted networks. Replay protection enables your security
devices to inspect every IPSec packet to see if the packet has been received before—if
packets arrive outside a specified sequence range, the security device rejects them.
549
Copyright © 2010, Juniper Networks, Inc.
Chapter 12: Configuring VPNs
Summary of Contents for NETWORK AND SECURITY MANAGER 2010.3
Page 6: ...Copyright 2010 Juniper Networks Inc vi...
Page 36: ...Copyright 2010 Juniper Networks Inc xxxvi Network and Security Manager Administration Guide...
Page 52: ...Copyright 2010 Juniper Networks Inc 2 Network and Security Manager Administration Guide...
Page 90: ...Copyright 2010 Juniper Networks Inc 40 Network and Security Manager Administration Guide...
Page 144: ...Copyright 2010 Juniper Networks Inc 94 Network and Security Manager Administration Guide...
Page 146: ...Copyright 2010 Juniper Networks Inc 96 Network and Security Manager Administration Guide...
Page 234: ...Copyright 2010 Juniper Networks Inc 184 Network and Security Manager Administration Guide...
Page 310: ...Copyright 2010 Juniper Networks Inc 260 Network and Security Manager Administration Guide...
Page 364: ...Copyright 2010 Juniper Networks Inc 314 Network and Security Manager Administration Guide...
Page 366: ...Copyright 2010 Juniper Networks Inc 316 Network and Security Manager Administration Guide...
Page 478: ...Copyright 2010 Juniper Networks Inc 428 Network and Security Manager Administration Guide...
Page 576: ...Copyright 2010 Juniper Networks Inc 526 Network and Security Manager Administration Guide...
Page 580: ...Copyright 2010 Juniper Networks Inc 530 Network and Security Manager Administration Guide...
Page 592: ...Copyright 2010 Juniper Networks Inc 542 Network and Security Manager Administration Guide...
Page 684: ...Copyright 2010 Juniper Networks Inc 634 Network and Security Manager Administration Guide...
Page 690: ...Copyright 2010 Juniper Networks Inc 640 Network and Security Manager Administration Guide...
Page 696: ...Copyright 2010 Juniper Networks Inc 646 Network and Security Manager Administration Guide...
Page 698: ...Copyright 2010 Juniper Networks Inc 648 Network and Security Manager Administration Guide...
Page 748: ...Copyright 2010 Juniper Networks Inc 698 Network and Security Manager Administration Guide...
Page 778: ...Copyright 2010 Juniper Networks Inc 728 Network and Security Manager Administration Guide...
Page 870: ...Copyright 2010 Juniper Networks Inc 820 Network and Security Manager Administration Guide...
Page 872: ...Copyright 2010 Juniper Networks Inc 822 Network and Security Manager Administration Guide...
Page 898: ...Copyright 2010 Juniper Networks Inc 848 Network and Security Manager Administration Guide...
Page 908: ...Copyright 2010 Juniper Networks Inc 858 Network and Security Manager Administration Guide...
Page 910: ...Copyright 2010 Juniper Networks Inc 860 Network and Security Manager Administration Guide...
Page 995: ...PART 6 Index Index on page 947 945 Copyright 2010 Juniper Networks Inc...
Page 996: ...Copyright 2010 Juniper Networks Inc 946 Network and Security Manager Administration Guide...