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.

Networked Systems<br />

_________________________________________________________________________________________<br />

Force majeure<br />

- T 1.1 Loss of personnel<br />

- T 1.2 Failure of the <strong>IT</strong> system<br />

Organisational shortcomings:<br />

- T 2.59 Opertion of non-registered components<br />

- T 2.60 Strategy for the network system and management system is not laid down or<br />

insufficient<br />

- T 2.61 Unauthorised collection of personal data<br />

Human Failure:<br />

- T 3.34 Unsuitable configuration of the management system<br />

- T 3.35 Disabling the server while in operation<br />

- T 3.36 Misinterpretation of events<br />

Technical Failure:<br />

- T 4.38 Failure of components of a network management system or system management<br />

system<br />

Deliberate Acts:<br />

- T 5.86 Manipulation of management parameters<br />

Recommended Countermeasures (S)<br />

For the implementation of <strong>IT</strong> baseline protection, selection of the required packages of safeguards<br />

("modules") as described in chapters 2.3 and 2.4, is recommended.<br />

<strong>The</strong> system to be managed consists of individual computers, gateways and the physical network. Each<br />

of these components presents a potential security risk for the whole system. <strong>The</strong>se risks cannot be<br />

eliminated entirely through the implementation of management software. This is due to the fact that it<br />

is not usually possible to include all systems in a management system to the same extent. <strong>The</strong> basic<br />

requirements for the security of the system are the definition and implementation of a security policy<br />

for the whole enterprise. In the case at question, this policy must be expressed particularly in the<br />

configuration of hardware and software. For this reason, particular attention should be paid to the<br />

safeguards of the modules listed in chapter 6. Module 6.7 can be used as a starting point.<br />

As management systems are designed with a centralist structure, the management station is of<br />

particular importance for security considerations, and a particular effort must therefore be made to<br />

protect it. Thus, important components of a management system should be set up in rooms which<br />

correspond to the requirements for a server room (see chapter 4.3.2). If no server room is available,<br />

they can alternatively be set up in a server cabinet (see chapter 4.4 Protective Cabinets).<br />

In order to successfully set up a network and system management system, a series of measures should<br />

be taken, starting with the design, then going on to the purchase and operation. <strong>The</strong> steps and measures<br />

involved are described below:<br />

1. Creation of a management concept based on the requirements which result from the existing <strong>IT</strong><br />

system.<br />

1.1 Requirement analysis (see S 2.168 <strong>IT</strong> system analysis before the introduction of a system<br />

management system)<br />

_________________________________________________________________________________________<br />

<strong>IT</strong>-<strong>Baseline</strong> <strong>Protection</strong> <strong>Manual</strong>: Otober 2000

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

Saved successfully!

Ooh no, something went wrong!