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

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Safeguard Catalogue - Organisation Remarks<br />

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

S 2.135 Save transfer of data to a database<br />

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

Implementation responsibility: Administrators<br />

In many database systems, it is necessary for applications to take over data<br />

from other systems. A basic distinction can be made between the following<br />

categories here:<br />

- Transfer of initial or old data<br />

This involves the transfer of data from old systems, required when a new<br />

database system is procured in order to increase productivity, for example.<br />

In this case, the following measures must be specially observed:<br />

- <strong>The</strong> data must be available in a format which is accepted by the<br />

destination database<br />

- <strong>The</strong> data must be complete, i.e. data must be available for all the<br />

fields of the destination database which need to be filled<br />

- <strong>The</strong> consistency and integrity of the database must be guaranteed<br />

Before data is actually transferred, it is necessary to form a concept<br />

describing how the data is to be prepared for the process of transfer, and<br />

how this process is to take place. In addition, a full backup of the old data<br />

is absolutely necessary. If the data is to be transferred in several steps, an<br />

independent data backup should be performed before each step.<br />

- Regular transfer of data<br />

If the destination database already contains data which must remain<br />

unaltered during the subsequent transmission of additional data, or if new<br />

data is transferred to the database at regular intervals, the following<br />

measures must be observed:<br />

- A full backup of the database must be created before the transfer of<br />

new data<br />

- If possible, data transfer should take place outside regular operating<br />

hours<br />

- Users whose activities will be influenced by the impending transfer<br />

of data must be informed duly, particularly if availability and<br />

response times are likely to be affected<br />

- Prior to the initial transfer of new data, it is necessary to form a<br />

concept describing how the data is to be prepared for the process of<br />

transfer, and how this process is to take place. In particular, this<br />

concept must include a description of how to avoid conflicts<br />

between the data already existing in the destination database and the<br />

data to be transferred, i.e. the extent to which the integrity and<br />

consistency of the destination database remain protected. In addition,<br />

measures must be taken to prevent multiple transfer of the same<br />

data.<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!