We're going to step into a discussion about the two IKE
versions for the next two modules.
This one's going to be all about the original version of IKEv1.
It's what many people in the industry know best due to its
popularity and its ease of configuration.
Many devices today still support this method of SA establishment.
Throughout this module,
we'll get into the meat and potatoes of the IKEv1 protocol and
figure out what it is and how to configure it.
First,
we're going to detail what IKE is and add to the
conversations that we had earlier about it.
Then, we'll detail the authentication mechanisms that we can use with it.
After that,
we're going to discuss the phases for IKE and what
makes them fit into the IPsec puzzle.
We'll cover each of the three modes for IKEv1 in
detail and show their functionality.
After that, we'll review what we learned in this module and move on.
Continuing on our conversation earlier about IKE being our
method of managing and exchanging key material,
IKE is crucial to establishing the SAs necessary for IPsec to function.
IKE is made up of those protocols that we talked about earlier,
ISAKMP, OAKLEY, and SKEME.
It uses these in its phases to establish the SAs by
exchanging that keying material securely.
IKE has three different modes that are all used for different
purposes within the functionality of it.
We'll talk about those later on in the module.
IKEv1 is actually obsolete according to many in the industry,
despite the fact that it's still in use today.
So why are we still talking about it then?
If this thing has security gaps and is considered obsolete,
why are we learning about it?
Well, it's because we see this version still in use today,
and it's still supported on a lot of devices out there.
It's also, in my opinion, much easier to configure on devices.
It's likely because these were the VPNs that I started out
configuring and learning about years ago.
So IKEv1 is still a very important aspect to an organization's infrastructure. Let's talk about the ways to authenticate it.