Authentication Header vs. IKE

There are two different things going on here. One is a key exchange and the other a data encryption protocol. IPSec consists of both a way to securely exchange cryptographic keys and then to transmit data securely over the Internet. The Internet Key Exchange (IKE) is the protocol for the key exchange and Authentication Header (AH) is one of the two encryption protocols.

IKE is used to set up the IPSec conversation and exchange the keys needed for encrypting the data through its secure tunnel. AH and Encapsulating Security Payload (ESP) are the two ways the data is encrypted after the keys are exchanged. Once IKE exchanges the keys, one of the two encryption protocols -- AH or ESP -- must be used. AH just authenticates the TCP packet without encrypting it, while ESP is stronger in that it both authenticates and encrypts the packet. So, AH may still be needed if it's the encryption protocol of choice over ESP in the IPSec set up. Is it still used? Not as much as ESP. There has been talk from time to time of deprecating AH, but it still hasn't been officially removed from any RFP about IPSec.

Though less secure than ESP, AH requires less processor power and is obviously less of a strain on the network. But, besides being less secure, it also can't be used for connecting outside a network using NAT. Despite these weaknesses, if the security risk is low behind a NATed firewall or router, and efficiency is paramount, AH can still be used in an internal network.

---

More information

Visit our resource center and learn more about authentication systems and protocols.

Learn how to secure public key transport to transmit data security over the Internet.

---