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.52 Regular backup of configuration data of<br />

active network components<br />

Initiation responsibility: Head of <strong>IT</strong> Section, <strong>IT</strong> Security Management<br />

Implementation responsibility: Administrators<br />

Central active network components need to remain highly available because a<br />

large number of users are generally dependent upon the smooth operation of a<br />

local network. To allow operations to be resumed as quickly as possible<br />

following the occurrence of a malfunction, all the configuration data of the<br />

active network components should be backed up electronically (also refer to S<br />

6.32 Regular data backups). In principle, such backups can be performed<br />

locally on the individual components, or via the network using a network<br />

management tool, for example. Once the data have been backed up<br />

electronically, the corresponding configurations can be restored more quickly<br />

and reliably, thus eliminating the need for time-consuming manual entries.<br />

<strong>The</strong> data can be restored automatically, for example, by means of a central<br />

network management tool, or manually by an administrator.<br />

When backing up configuration data via the network though, it must be noted<br />

that, in contrast to a local backup, it might be possible for potential intruders<br />

to monitor the transferred data and thus obtain security-critical information on<br />

the configuration of the active network components, such as passwords, and<br />

consequently even acquire details on the overall network configuration. <strong>The</strong><br />

Trivial File Transfer Protocol (TFTP) or Remote Copy Protocol (RCP) is<br />

generally used here; wherever possible, use should be made of RCP with<br />

authentication (refer to S 5.20 Use of the security mechanisms of rlogin, rsh<br />

and rcp). In contrast, TFTP does not offer any mechanisms for protection<br />

against unauthorised access to configuration data (also refer to S 5.21 Secure<br />

use of telnet, ftp, tftp and rexec), so that its use is not recommended.<br />

For all backup techniques, a test is required to ascertain whether the backup<br />

was performed successfully and whether the configuration data can be<br />

restored properly. This particularly applies to backups performed via the<br />

network, because the occurrence of an error here may give rise to a situation<br />

in which restoration is no longer possible via the network.<br />

Additional controls:<br />

- Have the configuration data of all active network components been backed<br />

up?<br />

- Are generated data backups being documented?<br />

- Is the backup process in conformity with the data backup policy, where<br />

established (cf. S 6.13 Development of a data backup policy)?<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!