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

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

S 6.67 Use of detection measures for security<br />

incidents<br />

Initiation responsibility: <strong>IT</strong> Security Management<br />

Implementation responsibility: <strong>IT</strong> Security Management<br />

It is very important to detect when security incidents occur as well as trying to<br />

prevent them. <strong>The</strong>re are a number of security-relevant irregularities whose<br />

detection can be automated using appropriate technical measures, enabling<br />

them to be detected early. <strong>The</strong>se detection measures generally increase the<br />

reliability of detection and significantly reduce the time between the<br />

occurrence of an irregularity and its detection. However, the gain in the ability<br />

to react early comes at the effort that is required to implement and monitor<br />

such measures. This effort should be estimated in advance. If the potential<br />

damage is very large or even entails personal injury, then there is virtually no<br />

choice but to adopt such detection measures.<br />

Examples of this kind of detection measures include:<br />

- alarm annunciation devices (see S 1.18 Intruder and fire detection devices)<br />

- remote indication of malfunctions (see S 1.31 Remote indication of<br />

malfunctions)<br />

- virus scanning programs (see S 2.157 Selection of a suitable computer<br />

virus scanning program)<br />

- intrusion detection and intrusion response systems (see S 5.71 Intrusion<br />

detection and intrusion response systems)<br />

- cryptographic checksums (see S 4.34 Using encryption, checksums or<br />

digital signatures)<br />

Not all security incidents can be detected promptly using only technical<br />

measures. Often organisational measures must be used as well. <strong>The</strong> reliability<br />

of automatic detection measures generally depends on how up-to-date these<br />

are and how well suited they are to the actual circumstances. <strong>The</strong> effectiveness<br />

of organisational detection measures depends heavily on the reliability of the<br />

persons tasked with implementing them and also on how easily the measures<br />

lend themselves to being implemented in actual ongoing operations.<br />

Typical examples of detection measures which are wholly or partially of an<br />

organisational nature are:<br />

- obtaining information on security weaknesses of the system (see S 2.35<br />

Obtaining information on security weaknesses of the system)<br />

- regular security checks of selected <strong>IT</strong> systems (e.g. see S 2.92 Performing<br />

security checks in the Windows NT client-server network, S 4.93 Regular<br />

integrity checking and S 5.8 Monthly security checks of the network)<br />

- regular analysis of log files (e.g. see S 2.64 Checking the log files, S 4.5<br />

Logging of PBX administration jobs, S 4.25 Use of logging in UNIX<br />

systems, S 4.47 Logging of firewall activities, S 4.54 Logging under<br />

Windows NT, S 5.9 Logging at the server)<br />

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

<strong>IT</strong>-<strong>Baseline</strong> <strong>Protection</strong> <strong>Manual</strong>: Oktober 2000<br />

Uncovering security<br />

incidents<br />

Combination of technical<br />

and organisational<br />

measures

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

Saved successfully!

Ooh no, something went wrong!