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 />

Appropriation of log data<br />

In accordance with the almost fully identical data privacy regulations<br />

applicable on the federal and state levels, log data are largely immune to<br />

appropriation (e.g. § 14 Sec. 4 and § 31 BDSG, § 13 Abs. 5 HDSG). Such data<br />

must only be used for the purposes for which they were originally saved.<br />

<strong>The</strong>se purposes usually consist of general monitoring tasks specified in a<br />

security concept, ”checks for the proper usage of programs for processing<br />

person related data” stipulated by most data security laws (for example, refer<br />

to § 18 Sec. 2 BDSG, § 8 Abs. 3 LDSG-SH) and monitoring by internal or<br />

external data security officers. Only in exceptional cases do locally applicable<br />

regulations allow the appropriation of such data for other purposes such as<br />

criminal prosecution.<br />

Storage period<br />

Unless specified otherwise by locally applicable regulations, the storage<br />

period for logs is defined by the deletion guidelines forming part of generally<br />

applicable data privacy laws. <strong>The</strong> ”fulfilment of responsibilities” is used as a<br />

yardstick here. If no compelling reasons exist for the further retention of log<br />

data, these must be deleted by law (for example, refer to § 20 Sec. 2 BDSG).<br />

<strong>The</strong> following factors serve as orientation here:<br />

- <strong>The</strong> probability that irregularities might still be detected<br />

- <strong>The</strong> possibility of ascertaining the reasons for such irregularities using the<br />

logs and other documents<br />

Empirical results have shown that a retention period of one year is sufficient<br />

here.<br />

Shorter retention periods should be considered for logs which are prepared for<br />

the purpose of selective checks. Storage up to the point of actual checking is<br />

usually adequate. Here, too, locally applicable regulations must be observed.<br />

Basic technical and organisational requirements<br />

<strong>The</strong> effectiveness of logging and its evaluation as part of monitoring depends<br />

decisively on technical and organisational conditions. In this context, the<br />

following aspects should be considered:<br />

- A review concept should be prepared for the purpose of clearly defining<br />

the purpose of the logs and their monitoring functions, as well as security<br />

mechanisms for the rights of users and other people involved.<br />

- Measures must be taken to ensure the inevitability and completeness of the<br />

logging functions, and to safeguard entries in the log files against<br />

manipulation.<br />

- In accordance with the degree of appropriation applicable to the data stock,<br />

effective access restrictions must be implemented.<br />

- <strong>The</strong> logs must be designed to allow effective checking. This also includes<br />

<strong>IT</strong>-supported evaluations.<br />

- Possibilities of evaluation should be ascertained and stipulated at the start.<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!