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.91 Determining a security strategy for the<br />

Windows NT client-server network<br />

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

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

Before a start can be made on the actual configuration and installation of<br />

Windows NT in a client-server network, two fundamental observations must<br />

first be made:<br />

First of all, it must be clarified which services are to be provided by the<br />

operating system and in what context it is to be used.<br />

This can be illustrated using a number of examples:<br />

- <strong>The</strong> system is deployed in a server-supported PC network as a server for a<br />

fairly large workgroup in which different rights can be assigned. If<br />

necessary, due to specific requirements, Peer-to-Peer functions should also<br />

be implemented in a limited manner. For example, individual printers<br />

should be able to be used jointly via Peer-to-Peer functionality.<br />

- <strong>The</strong> system is deployed as the client in a server-supported PC network with<br />

Windows NT servers which can dispense with Peer-to-Peer functionality<br />

for the exchange of data.<br />

- <strong>The</strong> system is deployed as the client in a server-supported PC network with<br />

Novell NetWare servers.<br />

- <strong>The</strong> system is deployed as the server in a PC network with MS-DOS, MS<br />

Windows, WfW or Windows 95 clients.<br />

- <strong>The</strong> system is deployed as the server in a network in which there are<br />

exclusively Windows NT clients.<br />

Extra security problems can arise as a result of the use of Peer-to-Peer<br />

functions within a Windows NT network (in this respect see also 6.3 Peer-to-<br />

Peer network). For this reason the use of Peer-to-Peer functions within<br />

Windows NT networks should be avoided. Peer-to-Peer functions should, at<br />

best, be allowed as a temporary solution in a restricted way, if, for example,<br />

WfW computers or non-networkable printers are to be integrated into the<br />

Windows NT network.<br />

Following this, the above considerations must be translated into a security<br />

strategy.<br />

Here it can be seen that depending on the already existing system environment<br />

and organisational structure, together with the restrictions on possible Peer-to-<br />

Peer functions that may have to be allowed for, a greater or lesser effort is<br />

necessary in the development of a suitable security strategy.<br />

A methodical procedure is shown below which can be used to develop a<br />

comprehensive security strategy for a client-server network. However, as<br />

Windows NT can be deployed in various configurations, an individual<br />

decision should be taken for the respective characteristic as to which of the<br />

steps outlined should be applied.<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!