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

- How quickly can a RAS connection be restored (by replacement of<br />

equipment, restarting the system)?<br />

- Which component failures require that the RAS system is shut down even<br />

though technically RAS connections can still be established (e.g. failure of<br />

logging, encryption of communications or of the authentication server)?<br />

For remote users, an emergency call number should be available so that they<br />

can notify the responsible persons promptly of any RAS problems. Moreover,<br />

the RAS system should be permanently monitored at critical periods (e.g.<br />

office hours, periods in which data is primarily exchanged by RAS).<br />

Suitable procedures should be developed for individual damage scenarios in<br />

the form of contingency documentation. All the data that is necessary to<br />

resolve an emergency should be included in this documentation and presented<br />

in such a way that deputising staff can also work with it. <strong>The</strong> contingency<br />

documentation should also contain information on alternative connection<br />

paths, e.g. alternative telecommunications providers or alternative<br />

transmission media.<br />

Depending on the availability requirements for the RAS system, it may be<br />

necessary to hold replacement equipment in reserve so that faulty items can be<br />

replaced immediately. To ensure that the RAS system can be started up again<br />

after equipment replacement or a system crash, the contingency<br />

documentation must contain a recovery plan. If necessary, it may even be<br />

necessary for it to be possible to replace certain components while the system<br />

is running. Such a hot swap must be supported by the components used.<br />

Depending on the RAS system, the consistency of data being transmitted by<br />

RAS during a system crash cannot be assured. After every failure the integrity<br />

of this data should therefore be checked and a problem analysis should be<br />

carried out in order to avoid repetitions as far as possible.<br />

In certain situations it can be necessary to operate the RAS system with<br />

limited functionality or performance. In this case a corresponding fallback<br />

configuration must be activated (see also S 4.111 Secure configuration of the<br />

RAS system). This enables the security of the RAS system (access security,<br />

communication security) to be maintained even during restricted operation.<br />

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

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

Setting up emergency<br />

call numbers<br />

Create contingency<br />

documentation<br />

Prepare recovery plan<br />

Check data integrity after<br />

failures<br />

Secure emergency<br />

configuration

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

Saved successfully!

Ooh no, something went wrong!