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 - Hardware & Software Remarks<br />

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

S 4.92 Secure operation of a system management<br />

system<br />

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

Implementation responsibility: Administrators<br />

To ensure the secure operation of a system management system, which may<br />

consist of a number of different management tools (see S 2.171 Selection of a<br />

suitable system management product), the configuration of all components<br />

involved must be examined to ascertain that it is secure (see also S 4.91<br />

Secure installation of a system management system). To do this it is necessary<br />

to provide appropriate security for the operating systems of the components<br />

which are administered by the system management system and which<br />

therefore have installed parts of the system in the form of software and/or<br />

data. <strong>The</strong> provision of security also includes the secure siting of the computers<br />

that perform central tasks for the management system (management servers or<br />

computers with management databases). In addition, provision must be made<br />

for secure data transmission (see S 5.68 Use of encryption procedures for<br />

network communications).<br />

Particular attention should be paid to the following points during operation of<br />

a management system:<br />

- <strong>The</strong> new hardware and software components added by the management<br />

system must be documented in the course of updating of the system<br />

documentation.<br />

- Changes to the management system itself must also be documented and/or<br />

logged.<br />

- Updating must be carried out in the same way for the emergency procedure<br />

manual. In particular the startup and recovery plans must be modified,<br />

because after the introduction of a management system many standard<br />

functions of the administered operating systems can only be executed with<br />

the aid of the functions of the management system. On the other hand,<br />

however, the emergency procedure manual must also include instructions<br />

on how the system can be made available without the management system<br />

(for example in the event of total failure of central components) to a<br />

sufficient degree within a short time (emergency operation regulation; see<br />

also Section 3.3 Contingency planning concept).<br />

- Access to the components or data of the management system is generally<br />

carried out exclusively by the management system itself or by other<br />

authorised system mechanisms (such as a data backup system). Access<br />

must therefore be prohibited for normal users. In normal cases this also<br />

applies to the role of the local administrator of an individual computer. If it<br />

does become necessary in exceptional cases to access the local components<br />

of the management system on a computer (for example for crash recovery<br />

or when installing new components, assuming the management system<br />

does not support this as part of its management function), this authorisation<br />

should be granted explicitly, and only for performing this particular task.<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!