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

<strong>The</strong> following events should also be logged:<br />

- Hardware errors which might lead to the failure of an <strong>IT</strong> system<br />

- Impermissible changes to the IP address of an <strong>IT</strong> system (in a TCP/IP<br />

environment)<br />

Auditing can be performed online or offline. During online auditing,<br />

categorised events are reported directly to the auditor, who can initiate<br />

measures immediately, if required. <strong>The</strong>se events must be assigned to suitable<br />

categories, so that the responsible administrator or auditor can retain a clear<br />

perspective and respond to important events immediately without being<br />

overwhelmed by a flood of information. During offline auditing, data from log<br />

files or special auditing files are prepared with the help of a tool and then<br />

examined by the auditor. In this case, measures for maintaining or restoring<br />

security can only be initiated after a time delay. Generally it is advisable to<br />

employ a mixture of online and offline auditing. During online auditing,<br />

security-critical events are filtered and reported to the auditor immediately.<br />

Events of a less critical nature are analysed offline.<br />

Standard management protocols such as SNMP and RMON (which is based<br />

on SNMP) as well as specific protocols of the employed network management<br />

product can be used for logging and auditing.<br />

On no account should user passwords be collected as part of auditing or<br />

logging! A high security risk would arise if unauthorised access were gained<br />

to this data. Incorrect password entries should not be logged either, as they<br />

usually differ from the corresponding, correct passwords only by one<br />

character or two interchanged characters.<br />

A stipulation is also required as to who will analyse the logs and audit data. A<br />

suitable distinction must be made here between the originator of events and<br />

the evaluator of events (e.g. administrator and auditor). Regulations<br />

concerning data privacy must also be adhered to. Earmarking in accordance<br />

with § 14 of the BDSG must be observed in particular for all gathered data.<br />

Log files and audit files must be analysed at regular intervals. Such files can<br />

quickly grow to large proportions. To keep the size of log files and audit files<br />

within a useful range, the evaluation intervals should not be impractically<br />

short, but short enough to allow a clear examination.<br />

Additional controls:<br />

- Are the recorded log files and audit files examined at regular intervals?<br />

- Are the possible consequences of security-critical events analysed?<br />

- Are user passwords logged?<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!