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

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Service level filtering<br />

Because most services use well-known <strong>TCP</strong>/UDP port numbers, it is possible to<br />

allow or deny services by using related port information in the filter. For example,<br />

an FTP server listens for connections on <strong>TCP</strong> port 21, <strong>and</strong> for a non-passive<br />

mode client, makes outbound data connections from port 20. Therefore, to<br />

permit FTP connections to pass through to a secure network, the router can be<br />

configured to permit packets that contain 20 <strong>and</strong> 21 as the <strong>TCP</strong> port in its<br />

header. However, there are some applications, such as NFS, that use RPC <strong>and</strong><br />

use different ports for each connection. Allowing these kind of services might<br />

cause security problems.<br />

Source/destination level filtering<br />

The packet-filtering rules allow a router to permit or deny a packet according to<br />

the destination or the source information in the packet header. In most cases, if a<br />

service is available, only that particular server is permitted to outside users.<br />

Other packets that have another destination or no destination information in their<br />

headers are discarded.<br />

Advanced filtering<br />

As mentioned previously (see 22.1.1, “Common attacks against security” on<br />

page 772), there are different types of attacks that threaten the privacy <strong>and</strong><br />

network security. Some of them can be discarded by using advanced filtering<br />

rules such as checking <strong>IP</strong> options, fragment offset, <strong>and</strong> so on.<br />

Packet-filtering limitations<br />

Packet-filtering rules are sometimes very complex. When there are exceptions to<br />

existing rules, it becomes much more complex. Although there are a few testing<br />

utilities available, it is still possible to leave some holes in the network security.<br />

Packet filters do not provide an absolute protection for a network. For some<br />

cases, it might be necessary to restrict some set of information (for example, a<br />

comm<strong>and</strong>) from passing through to the internal secure network. It is not possible<br />

to control the data with packet filters because they are not capable of<br />

underst<strong>and</strong>ing the contents of a particular service. For this purpose, an<br />

application-level control is required.<br />

Application-level gateway (proxy)<br />

An application-level gateway is often referred to as a proxy. An application-level<br />

gateway provides higher-level control on the traffic between two networks in that<br />

the contents of a particular service can be monitored <strong>and</strong> filtered according to the<br />

798 <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!