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 - Organisation Remarks<br />

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

S 2.74 Selection of a suitable packet filter<br />

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

Implementation responsibility: Administrators<br />

Packet filters are routers or computers with special software which use the<br />

information in layers three and four of the TCP/IP protocol family (IP, ICMP,<br />

ARP, TCP and UDP) for filtering packets. Access and deny lists are used in<br />

this regard.<br />

In the event that a packet filter is required for a firewall, the following<br />

demands should be made upon purchase:<br />

- <strong>The</strong> filtering must be possible separately for each interface.<br />

- It must be possible to filter incoming and outgoing packets separately.<br />

- <strong>The</strong> filtering must be possible separately for individual computers or for<br />

complete sub-networks according to source and destination address.<br />

- <strong>The</strong> filtering must be possible separately according to source and<br />

destination port.<br />

- <strong>The</strong> order in which the filter rules are evaluated should not be<br />

automatically changed by the packet filter.<br />

- <strong>The</strong> order in which the filter rules are evaluated should be easily<br />

recognised, i.e. sufficiently documented.<br />

- <strong>The</strong> entry and control of filter rules must be simple and clear, e.g. by<br />

symbolic service and protocol names.<br />

- In case of TCP packets, it should be possible to determine whether an<br />

existing connection is being used or a connection is being established, i.e.<br />

to distinguish between packets with and without ACK.<br />

- It must be possible to record IP numbers, service, time and date for each<br />

packet. Selective logging for certain packets (e.g. only packets with a<br />

specific source address) has also to be possible.<br />

- It must be possible to send all logging information to an external host.<br />

- Special, adjustable events must lead to an immediate warning (e.g.<br />

repeated incorrect authentication attempts).<br />

- If a router is used as a packet filter, it should be possible to use static<br />

routing tables. In general, however, routers should not be used as packet<br />

filters as they have a very wide range of functions so that the filter<br />

attributes are often just offered as add-ons. This accordingly influences the<br />

creation and testing of the related software.<br />

- If a router is used as a packet filter, dynamic routing must be configured in<br />

such a way that routing packets (e.g. RIP) which affect the network<br />

requiring protection are only permitted on the interface connected to the<br />

network requiring protection.<br />

- It must be possible to reject packets with source routing information by<br />

default.<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!