25.02.2013 Views

TCP/IP Tutorial and Technical Overview - IBM Redbooks

TCP/IP Tutorial and Technical Overview - IBM Redbooks

TCP/IP Tutorial and Technical Overview - IBM Redbooks

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Before describing the details of the key exchange <strong>and</strong> update messages, some<br />

explanations are necessary:<br />

► Internet Security Association <strong>and</strong> Key Management Protocol (ISAKMP)<br />

A framework that defines the management of Security Associations<br />

(negotiate, modify, delete) <strong>and</strong> keys, <strong>and</strong> it also defines the payloads for<br />

exchanging key generation <strong>and</strong> authentication data. ISAKMP itself does not<br />

define any key exchange protocols, <strong>and</strong> the framework it provides can be<br />

applied to security mechanisms in the network, transport, or application layer,<br />

<strong>and</strong> also to itself.<br />

► Oakley<br />

A key exchange protocol that can be used with the ISAKMP framework to<br />

exchange <strong>and</strong> update keying material for Security Associations.<br />

► Domain of Interpretation (DOI)<br />

Definition of a set of protocols to be used with the ISAKMP framework for a<br />

particular environment; also a set of common definitions shared with those<br />

protocols regarding the syntax of SA attributes <strong>and</strong> payload contents,<br />

namespace of cryptographic transforms, <strong>and</strong> so on. In relation to <strong>IP</strong>Sec, the<br />

DOI instantiates ISAKMP for use with <strong>IP</strong>.<br />

► Internet Key Exchange (IKE)<br />

A protocol that uses parts of ISAKMP <strong>and</strong> parts of the Oakley <strong>and</strong> SKEME<br />

key exchange protocols to provide management of keys <strong>and</strong> Security<br />

Associations for the <strong>IP</strong>Sec AH <strong>and</strong> ESP protocols <strong>and</strong> for ISAKMP itself.<br />

Protocol overview<br />

ISAKMP requires that all information exchanges must be both encrypted <strong>and</strong><br />

authenticated, so that no one can eavesdrop on the keying material. The keying<br />

material will be exchanged only among authenticated parties. This is required<br />

because the ISAKMP procedures deal with initializing the keys, so they must be<br />

capable of running over links where no security can be assumed to exist.<br />

In addition, the ISAKMP methods have been designed with the explicit goals of<br />

providing protection against several well-known exposures:<br />

► Denial of service: The messages are constructed with unique cookies that can<br />

be used to quickly identify <strong>and</strong> reject invalid messages without the need to<br />

execute processor-intensive cryptographic operations.<br />

► Man-in-the-middle: Protection is provided against the common attacks such<br />

as deletion of messages, modification of messages, reflecting messages<br />

back to the sender, replaying of old messages, <strong>and</strong> redirection of messages<br />

to unintended recipients.<br />

830 <strong>TCP</strong>/<strong>IP</strong> <strong>Tutorial</strong> <strong>and</strong> <strong>Technical</strong> <strong>Overview</strong>

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!