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

Create successful ePaper yourself

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

Safeguard Catalogue - Hardware & Software Remarks<br />

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

- On top of the RAS system configuration, dividing the network into subnets<br />

can also be useful for access control. For reasons of <strong>IT</strong> security it can<br />

therefore be appropriate to set up access networks (see also S 5.77<br />

Creation of subnets).<br />

- <strong>The</strong> routing settings of the network switching elements within the RAS<br />

system should be used to restrict the flow of network traffic. Network<br />

packets should only be forwarded on permitted connections. In addition,<br />

the latest network switching elements allow selective forwarding of<br />

packets within permitted network connections (packet filter function). In<br />

this way it is possible, for example, to ensure that only connection requests<br />

are forwarded to the HTTP service of a server.<br />

- Restricting access to RAS clients is especially difficult to implement with<br />

mobile computers. With mobile RAS clients it is therefore especially<br />

important that users adhere strictly to the defined rules (e.g. to protect<br />

against theft; see also module 5.3 Laptop PCs).<br />

- <strong>The</strong> secure configuration of the RAS server software requires that the<br />

security settings which are offered by the software and are appropriate in<br />

the existing operational scenario are also enabled and can be used. <strong>The</strong> use<br />

of certain security settings may presuppose that other components of the<br />

RAS system also possess corresponding functions and/or can be<br />

correspondingly configured. Thus, for example, when the Calling Line<br />

Identification Protocol (CLIP) is used, it is important to ensure that this is<br />

also enabled for the selected connection. For example, user identification<br />

on access over the Internet using X.509 certificates requires that the storage<br />

location of the user certificates is known to the RAS system. So the RAS<br />

software must either support external authentication servers or else offer a<br />

certificate management module of its own.<br />

It is therefore necessary to check in advance whether all the security<br />

mechanisms offered can also be used or whether different and/or additional<br />

hardware or software is necessary for this. Once the RAS system is up and<br />

running, regular checks must then be made in order to verify that the<br />

settings are correct.<br />

- <strong>The</strong> requirements which apply to the secure configuration of the RAS<br />

client software are similar to those which apply to the server software. In<br />

addition, care must be taken to ensure that passwords required for RAS<br />

access are not stored within the software, even though this option is<br />

frequently offered. If this cannot be technically prevented, all users must be<br />

forbidden from making use of the option. Moreover, all users must be<br />

informed of the problem.<br />

- In order that clients and server can communicate in a secure manner, care<br />

must be taken to ensure that the components involved are configured in a<br />

consistent manner (e.g. as regards the method used to protect<br />

communications).<br />

- <strong>The</strong> secure and consistent configuration of client and server can be<br />

supported by specifying a standard configuration for RAS clients<br />

(hardware and software) in the RAS concept and implementing it through<br />

appropriate organisational measures. <strong>The</strong> result of doing this is that only a<br />

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

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

Setting up access<br />

networks<br />

Routing settings<br />

Use of existing security<br />

mechanisms<br />

Client configuration<br />

Setting up standard <strong>IT</strong><br />

systems

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

Saved successfully!

Ooh no, something went wrong!