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

Examples:<br />

- Users can be denied the rights to create or modify database objects<br />

(e.g. tables).<br />

- Users can be granted read-only access to a table, but denied writeaccess<br />

to it.<br />

- Individual users can be denied access to particular tables or table<br />

fields.<br />

- Some users can be denied access to data records with certain<br />

attributes (e.g. an official in Bonn can be denied access to the data of<br />

an official in Cologne).<br />

- Some manufacturers offer the possibility of defining groups as well as<br />

roles. This allows differentiated access control to database objects. Related<br />

requirements must be clarified in advance and taken into consideration<br />

when selecting the database software.<br />

- <strong>The</strong> database software must also be examined with respect to the<br />

monitoring and control mechanisms it offers. Related requirements must be<br />

defined and compared with the features of the products (examples are<br />

provided in S 2.133 Checking the Log Files of a Database System and S<br />

2.126 Creation of a Database Security Concept).<br />

- It must be checked as to whether the database software supports distinction<br />

between the roles of administrator and auditor. It should be possible to<br />

configure the role of an auditor who is solely authorised to analyse and<br />

delete log files. This prevents potential manipulations by the database<br />

administrator.<br />

- To protect the integrity of the database, the database software must be<br />

equipped with a complete transaction system in compliance with the ACID<br />

principle. Nowadays, this requirement is fulfilled by all major relational<br />

database management systems.<br />

- Mechanisms for backing up the database must be available (refer to S 6.49<br />

Data Backup in a Database).<br />

Clarification is required in advance as to which data backup features the<br />

database software needs to provide. For example, a partial database backup<br />

is not possible with all commercially available products. In individual<br />

cases, a check is therefore required as to whether the prepared database<br />

backup policy can be implemented with the available mechanisms.<br />

<strong>The</strong>se criteria must be used as a basis for testing and evaluating the available<br />

database systems. <strong>The</strong> software finally selected should fulfil the specified<br />

requirements to the greatest possible extent. Any remaining requirements<br />

should be covered using externally or internally developed add-ons. Before<br />

procurement, clarification is required as to which external add-ons are<br />

available for which database software, in order to avoid costly internal<br />

development.<br />

Most commercial database management systems are available in different<br />

versions. Versions of the same database management system can differ in<br />

terms of their functionality, also as regards data security. Due to intense<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!