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.130 Ensuring the integrity of a database<br />

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

Implementation responsibility: Administrator; staff responsible for the<br />

individual <strong>IT</strong> applications<br />

<strong>The</strong> integrity of a database needs to be monitored and secured in order to<br />

ensure the correctness of the related data and the consistency of the database<br />

state. <strong>The</strong> following techniques must be employed to avoid the occurrence of<br />

incorrect data and inconsistent states in a database:<br />

- Access control<br />

Access control implies the protection of the database against unauthorised<br />

access by assigning corresponding access rights as described in S 2.129<br />

Controlling access to database information. This prevents manipulations<br />

of the data and database objects (such as tables).<br />

<strong>The</strong> database administrator is responsible for implementing access control.<br />

A detailed description of access control has been omitted here, as it is<br />

provided in S 2.129 Controlling access to database information.<br />

- Synchronisation control<br />

Synchronisation control is intended to prevent inconsistencies which could<br />

arise through parallel access to the same data. Several techniques are<br />

available for this purpose, including the locking of database objects and the<br />

allocation of timestamps.<br />

<strong>The</strong> persons in charge of individual <strong>IT</strong> applications are responsible for<br />

implementing synchronisation control, insofar as a mechanism exceeding<br />

the scope of the database management system needs to be provided<br />

additionally.<br />

A detailed description has been left out here, as synchronisation control is<br />

performed by most database management systems. We strongly advise<br />

against the use of a database management system which does not offer this<br />

feature.<br />

- Integrity control<br />

This involves the avoidance of semantic errors and semantically<br />

inconsistent database states through the observance and monitoring of<br />

database integrity constraints. <strong>The</strong>se can pertain to individual relations or<br />

to groups of several mutual relations (referential integrity). Examples here<br />

are the specification of a primary key for a relation, definition of value<br />

ranges for individual attributes, and formulation of special constraints by<br />

means of an assertion clause.<br />

Integrity control can be carried out by the database management system<br />

automatically by means of a monitor created using triggers or stored<br />

procedures. In principle, this allows any type of transaction to be<br />

performed; however, the database management system rejects those<br />

transactions which would impair the consistency of the database.<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!