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

Before restoring operations after an attack, all passwords on the <strong>IT</strong> systems<br />

concerned should be changed. This also includes <strong>IT</strong> systems which were not<br />

directly affected by manipulation, but from which the attacker may already<br />

have obtained information about users and/or passwords.<br />

It should be assumed that once the "secure" condition has been restored, the<br />

adversary will attempt a further attack. For this reason the <strong>IT</strong> systems,<br />

especially the network connections, should be monitored using the appropriate<br />

monitoring tools (see also S 5.71 Intrusion detection and intrusion response<br />

systems).<br />

Documentation<br />

All actions performed while dealing with a security problem should be<br />

documented in as much detail as possible so as to<br />

- retain the details of what happened,<br />

- make it possible to retrace the problems which occurred,<br />

- be able to rectify any problems/faults which could result from hasty<br />

implementation of countermeasures,<br />

- be able to resolve problems already known more quickly should they occur<br />

again,<br />

- be able to eliminate the security weaknesses and draw up preventive<br />

measures and<br />

- collect evidence if a prosecution is to be brought.<br />

Such documentation includes not only a description of the actions carried out<br />

including the times at which they were taken, but also the log files of the<br />

affected <strong>IT</strong> systems.<br />

Reaction to deliberate action<br />

Where a security incident was triggered by an adversary, a decision must be<br />

made as to whether to stand back and watch the attack or whether<br />

countermeasures should be implemented as soon as possible. Naturally an<br />

attempt can be made to catch the adversary "red-handed" but this runs the risk<br />

that in the meantime he will destroy, tamper with or read data.<br />

Regrettably, investigation of security problems indicates that these are often<br />

caused by staff from within the organisation. This can be the result of an<br />

oversight, inappropriate working procedures or technical problems, but it<br />

could also be a case of failure to observe security measures or even deliberate<br />

action.<br />

Wherever security problems are caused internally, the trigger must be<br />

investigated. Often the problems turn out to stem from inappropriate or<br />

incomprehensible procedures. It is then necessary to amend the procedures<br />

accordingly or else to supplement them with additional measures, e.g. of a<br />

technical nature.<br />

If the security problems are the result of deliberate action or negligence,<br />

appropriate disciplinary measures should be taken.<br />

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

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

Change passwords<br />

Monitoring of the<br />

affected <strong>IT</strong> systems<br />

Dealing with insiders

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

Saved successfully!

Ooh no, something went wrong!