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.153 Documentation of Novell Netware 4.x<br />

networks<br />

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

Implementation responsibility: Administrators<br />

One measure which is important for ensuring reliable operation but often<br />

neglected due to a lack of time or personnel, is documentation of the essential<br />

information pertaining to a Novell Netware 4.x network. As a change in<br />

responsibilities or a shortage of personnel can occur at any time, it is<br />

absolutely necessary to record all relevant information concerning every<br />

Netware server and supply this information in clearly arranged documents.<br />

This facilitates training and orientation if a replacement becomes necessary,<br />

and shortens downtimes in case of a failure.<br />

This documentation should provide the following information (together with<br />

all the required parameters) in a form which is transparent and can easily be<br />

updated:<br />

NDS<br />

Particular attention must be directed to the documentation of the NDS,<br />

because instead of being located on a single, central server, it might be<br />

distributed among several partitions and stored on different Netware servers -<br />

particularly in the case of Netware networks with many WAN links. In<br />

individual cases, this can mean, for example, that a server with a read/write<br />

replication needs to be converted to a master replication partition, if a<br />

hardware failure entails a new installation of the current master partition.<br />

However, this problem can be avoided using suitable security mechanisms.<br />

This example alone demonstrates the potential complexity of an extensively<br />

branched NDS tree, and the accompanying need for appropriate<br />

documentation, which should certainly contain the structure of the NDS, as<br />

well as information on the allocated NDS and file rights.<br />

Time synchronisation<br />

As NDS and time synchronisation are closely related topics, it is advisable to<br />

link them together in the documentation too. This is because all relevant<br />

pieces of information exchanged via a Netware 4.x network carry time stamps.<br />

To allow proper time synchronisation in a Novell Netware 4.x network and<br />

ensure that the time-related information yields the desired results on every<br />

server, a clear specification is required as to which server should act as the<br />

clock-signal source and which time model should be used. For this reason, a<br />

correct representation of the time synchronisation and the related NDS<br />

services is indispensable in order to allow the right steps to be taken in the<br />

event of an error.<br />

<strong>The</strong> table below provides an example of this type of documentation.<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!