22.12.2012 Views

Front cover - IBM Redbooks

Front cover - IBM Redbooks

Front cover - 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.

the receiving peer share the same secret key. A successful checksum<br />

evaluation means the packet was originated by the expected peer and the<br />

packet was not modified in transit.<br />

2. Encapsulating Security Payload (ESP): Provides a confidentiality guarantee<br />

for packets by encrypting packets with defined encryption algorithms. A<br />

packet with ESP that is successfully decrypted means the packet was not<br />

intercepted and modified.<br />

3. IP payload compression (IPcomp): IPcomp provides a way to compress<br />

packet before encryption by ESP. The purpose of this is to improve effective<br />

data throughput, because once the packet has been encrypted by ESP its<br />

potential for normal data compression is low or impossible.<br />

4. Internet Key Exchange (IKE): AH and ESP need a shared secret key between<br />

peers. IKE provides for secure key negotiation and exchange between<br />

different locations.<br />

The IPsec protocols provide security for transmission of sensitive information<br />

over unprotected IP networks. IPsec acts at the network layer, protecting and<br />

authenticating IP packets between participating peer devices. It is similar to<br />

SOCKS in that it requires a client; however, it does not require a proxy server.<br />

IPsec network gateways are used as the intermediary network proxy. It is<br />

commonly implemented in network routers, since it is essentially a network-layer<br />

proxy. As a result, it is generally more efficient than SOCKS because it is<br />

operating within only the lower three OSI layers (physical, data, and network).<br />

The primary popular use of IPsec has been as a means to provide VPN (virtual<br />

private network) access from unprotected networks (such as the Internet) into a<br />

trusted, protected network.<br />

4.1.2 Firewall products<br />

In our lab scenarios in this book, we were not necessarily concerned with the<br />

firewall products themselves. Rather, we were more interested in what the Lotus<br />

and WebSphere applications were doing, or were likely to do, across a firewall.<br />

In describing the implementation of a multi-zone architecture, it should not matter<br />

which firewall products are used. It is assumed that in each case the important<br />

information for a firewall administrator is primarily the ports and protocols used. It<br />

is up to the firewall administrator to use that information to establish the<br />

appropriate firewall configuration and access control lists.<br />

The following is a brief list of some common firewall products that provide at least<br />

stateful filtering capability and beyond, but fall short of being a full-fledged<br />

application-layer proxy. This is included only as a guide and the descriptions are<br />

based on the vendor’s own marketing material.<br />

Chapter 4. Security components and layers 121

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

Saved successfully!

Ooh no, something went wrong!