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

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

partners. Communication on the link as far as the first encrypting network<br />

switching element, however, takes place without encryption, and therefore<br />

holds a residual risk. Authentication is only possible between the switching<br />

elements. <strong>The</strong> communication partners themselves are not authenticated with<br />

this method.<br />

If sensitive data is transmitted via a network (even within an intranet), it is<br />

advisable to use encryption mechanisms. If the chosen applications do not<br />

have their own encryption mechanisms or if the available procedure is<br />

considered to be too weak, use should be made of the possibility of encryption<br />

on the operating system side. Procedures such as SSL suggest themselves<br />

here, which were designed for transparent encryption at the operating system<br />

level. Depending on the security policy it is also possible to use encrypting<br />

network switching elements, for example in order to implement a virtual<br />

private network (VPN) with a communication partner via the Internet<br />

(appropriate software mechanisms are generally also available in firewall<br />

systems (see Section 7.3 Firewall)).<br />

Considerable planning within the framework of the security policy of a<br />

company or agency is necessary when using encrypted communication and<br />

mutual authentication. In the context of the communication encryption<br />

methods discussed here, particular attention should be paid to the following<br />

points:<br />

- Which procedures are to be used or are offered for encryption (in routers,<br />

for example)?<br />

- Do the encryption mechanisms that are employed support or use existing or<br />

planned standards (IPSec, IPv4, IPv6, IKE)?<br />

- Have sufficiently strong procedures and correspondingly long keys been<br />

chosen, in accordance with the security policy?<br />

- Are the keys held in secure storage?<br />

- Are the keys generated in a secure environment, and do they have a secure<br />

route to the place where they are needed (computer, software component)?<br />

- Are key recovery mechanisms required?<br />

If certificates are used for the authentication of communication partners,<br />

similar questions have to be considered.<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!