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 - Organisation Remarks<br />

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

- Modifications to file organisation<br />

In view of the numerous possibilities of manipulation during the use of<br />

standard file management systems, complete logging is of particular<br />

importance here (for example, as regards database management).<br />

- Implementation of data backup measures<br />

As such measures (backup, restore) are related to the copying and<br />

overwriting of data stocks, and are mainly required in exceptional cases,<br />

logging is of special importance in this context.<br />

- Use of administration tools<br />

<strong>The</strong> usage of all administration tools must be protocoled to help ascertain<br />

whether unauthorised people have subversively acquired system<br />

administration rights.<br />

- Attempts at unauthorised login and transgressions of rights<br />

Given effective authentication procedures and an appropriate allocation of<br />

rights, particular emphasis must be laid on maintaining a complete record<br />

of all ”abnormalities” occurring during login and the use of<br />

hardware/software components. System administrators are also to be<br />

considered as users in this context.<br />

During the processing of person related data, the following user activities must<br />

be logged selectively or fully in accordance with the sensitivity of the<br />

processes and information involved:<br />

- Input of data<br />

Input monitoring is always process-oriented (e.g. logging in files if these<br />

are used, direct logging in the data stock if no files are used). Even if<br />

transgressions of rights are assumed to be logged using a different<br />

technique, complete logging of data inputs should be considered as a<br />

standard procedure.<br />

- Data transfer<br />

Selective logging of data transfer can be considered sufficient only if<br />

complete logging is not legally specified.<br />

- Use of automatic retrieval procedures<br />

Complete logging of retrieval and the reasons underlying them (procedure,<br />

reference, etc.) is generally necessary to detect unauthorised handling<br />

outside the scope of the access rights granted.<br />

- Deletion of data<br />

<strong>The</strong> deletion of data must be logged.<br />

- Invocation of programs<br />

It might be necessary to log the invocation of especially sensitive programs<br />

which, for example, must only be used during certain periods or on certain<br />

occasions. Complete logging is recommended in such cases. This also<br />

makes it possible to exonerate authorised users (proof of exclusive right to<br />

invoke a program).<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!