19.12.2012 Views

IT Baseline Protection Manual - The Information Warfare Site

IT Baseline Protection Manual - The Information Warfare Site

IT Baseline Protection Manual - The Information Warfare Site

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.

Safeguard Catalogue - Communications Remarks<br />

____________________________________________________________________ .........................................<br />

S 5.39 Secure use of protocols and services<br />

Initiation responsibility: Head of <strong>IT</strong> Section, <strong>IT</strong> Security Management<br />

Implementation responsibility: <strong>IT</strong> Security Management, Administrators<br />

<strong>The</strong> following short descriptions of the protocols and services most commonly<br />

used on the Internet explain what information is carried by these protocols and<br />

what is therefore eligible for filtering by a firewall. It also describes other<br />

points which should be borne in mind when using the various protocols and<br />

services.<br />

With a TCP/IP communication, a connection is normally established by a<br />

client process from a random port with a port number > 1023 to a server<br />

process with a port number < 1024 (well known port). <strong>The</strong> ports with numbers<br />

< 1024 are also known as privileged ports, because they may only be used by<br />

processes with root privileges. However, the restriction that ports < 1024 may<br />

only be used by processes with root privileges, is only a convention and it may<br />

be circumvented. No security strategy, therefore, may assume that the <strong>IT</strong><br />

systems really do protect their privileged ports in this way. Even if FTP is<br />

used, for instance, to access ports 20 or 21, this cannot be regarded as a secure<br />

connection.<br />

IP<br />

<strong>The</strong> Internet Protocol (IP) is a connectionless protocol. An IP header includes<br />

two 32 bit addresses (IP numbers) for the target and source of the computers<br />

communicating with each other.<br />

As the IP numbers are not protected by cryptographic procedures, they may<br />

only be used for authentication in very specific topographies, i.e. only when it<br />

is certain that the addresses cannot be changed. For example, packets coming<br />

from outside but whose source address is an address from the network to be<br />

protected, may not be admitted by the firewall.<br />

ARP<br />

<strong>The</strong> Address Resolution Protocol (ARP) is used to find the correct 48 bit<br />

hardware or Ethernet address for a 32 bit IP address. If it cannot find the<br />

corresponding entry in the computer’s internal table, an ARP broadcast packet<br />

is sent with the unknown IP number. <strong>The</strong> computer with this IP number then<br />

returns an ARP response packet with its hardware address. As the ARP<br />

response packets are not tamper-proof, they can only be used in very specific<br />

topographies (see above).<br />

ICMP<br />

<strong>The</strong> Internet Control Message Protocol (ICMP) is a transport layer protocol<br />

whose purpose is to transport error- and diagnostic information for the IP<br />

protocol. It is initiated and processed internally by IP, TCP or UDP and may<br />

be applied at user level by the command ping.<br />

If a computer or network is not accessible, a message such as Destination<br />

Unreachable is generated, and this can be misused to interrupt all connections<br />

between the participating computers.<br />

____________________________________________________________________ .........................................<br />

<strong>IT</strong>-<strong>Baseline</strong> <strong>Protection</strong> <strong>Manual</strong>: Oktober 2000

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

Saved successfully!

Ooh no, something went wrong!