Ipsec: Authentication Header (Ah) : The Ah Protocol Provides A Mechanism For
Ipsec: Authentication Header (Ah) : The Ah Protocol Provides A Mechanism For
For example, the security settings in the Internet Connection Firewall that ships
with Windows XP and later versions enables users to turn on IPSec for
transmissions. IPSec is a set of protocols developed by the IETF (Internet
Engineering Task Force; www.ietf.org) to support secure exchange of packets.
IPSec has been deployed widely to implement VPNs.
IPSec has two encryption modes: transport and tunnel. The transport mode works
by encrypting the data in each packet but leaves the header unencrypted. This
means that the source and destination addresses, as well as other header
information, are not encrypted. The tunnel mode encrypts both the header and the
data.
This is more secure than transport mode but can work more slowly. At the
receiving end, an IPSec-compliant device decrypts each packet. For IPSec to work,
the sending and receiving devices must share a key, an indication that IPSec is a
single-key encryption technology. IPSec also offers two other protocols beyond the
two modes already described:
Either protocol can be used alone to protect an IP packet, or both protocols can be
applied together to the same IP packet.
IPSec can also work in two modes. Those modes are transport mode and tunnel
mode. Transport mode is the mode where IPSec encrypts the data, but not the
packet header. Tunnelling mode does encrypt the header as well as the packet data.
There are other protocols involved in making IPSec work. IKE, or Internet Key
Exchange, is used in setting up security associations in IPSec. A security
association is formed by the two endpoints of the VPN tunnel, once they decide
how they are going to encrypt and authenticate. For example, will they use AES
for encrypting packets, what protocol will be used for key exchange, and what
protocol will be used for authentication?
All of these issues are negotiated between the two endpoints, and the decisions are
stored in a security association (SA). This is accomplished via the IKE protocol.
Internet Key Exchange (IKE and IKEv2) is used to set up an SA by handling
negotiation of protocols and algorithms and to generate the encryption and
authentication keys to be used.
The first exchange between VPN endpoints establishes the basic security policy;
the initiator proposes the encryption and authentication algorithms it is willing to
use. The responder chooses the appropriate proposal and sends it to the initiator.
The next exchange passes Diffie-Hellman public keys and other data.
Those Diffie-Hellman public keys will be used to encrypt the data being sent
between the two endpoints. The third exchange authenticates the ISAKMP session.
This process is called main mode. Once the IKE SA is established, IPSec
negotiation (Quick Mode) begins.
In other words, Quick Mode uses the Diffie-Hellman keys exchanged in main
mode, to continue exchanging symmetric keys that will be used for actual
encryption in the VPN.
Aggressive Mode squeezes the IKE SA negotiation into three packets, with all data
required for the SA passed by the initiator. The responder sends the proposal, key
material, and ID, and authenticates the session in the next packet. The initiator
replies by authenticating the session. Negotiation is quicker, and the initiator and
responder ID pass in the clear.