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.142 Development of a network realisation plan<br />

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

Implementation responsibility: Administrators<br />

When developing a network realisation plan, it is necessary to determine<br />

whether a completely new network configuration, or a modification /<br />

extension to an existing configuration is required.<br />

During the configuration of a completely new network, the required steps<br />

must be inferred from the network concept which has already been prepared<br />

(refer to S 2.141 Development of a network concept). Once planning has been<br />

completed, the network is set up by laying the required communications<br />

cables, configuring rooms for the technical infrastructure, installing the<br />

technical infrastructure itself, integrating the necessary coupling elements<br />

(bridges, switches, routers etc.), configuring the network management<br />

stations, fitting the terminal devices with corresponding network adapters and<br />

configuring these terminal devices.<br />

If an existing network is to be modified or extended, the network concept<br />

prepared in accordance with S 2.141 Development of a network concept<br />

should be compared with the actual situation as described in S 2.139 Survey of<br />

the existing network environment. Based on any resulting differences, a<br />

realisation plan for network migration can be outlined, taking into account the<br />

above-mentioned measures. Here, it must be noted that the greater the<br />

deviation between the network concept and the actual situation, the greater the<br />

realisation effort.<br />

Example of migrating from a shared Ethernet to a switched Fast Ethernet<br />

Migration from one network topology to another normally takes place in<br />

stages. A migration from a shared Ethernet to a Fast Ethernet with switching<br />

technology is outlined as an example in the following. Under real conditions<br />

however, the constraints need to be checked thoroughly and a special<br />

migration concept needs to be prepared for each individual case.<br />

- Migration step 1<br />

In the first migration step, the existing backbone can be replaced by a Fast<br />

Ethernet backbone, or a new one can be installed if necessary. <strong>The</strong><br />

remaining shared Ethernet segments are connected via the backbone's<br />

network components which must accordingly also support Standard<br />

Ethernet.<br />

- Migration step 2<br />

Establishment of structured cabling, i.e. a conversion is performed from a<br />

Standard Ethernet with breakout cabling to a cabling concept in which<br />

every workstation is connected in star configuration to a distributor room<br />

without abandoning the topological bus structure.<br />

- Migration step 3<br />

<strong>The</strong> servers are connected centrally to a switch with Fast Ethernet adapters<br />

(installation of a so-called server farm).<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!