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.126 Creation of a database security concept<br />

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

Implementation responsibility: <strong>IT</strong> Security Management<br />

<strong>The</strong> long-term keeping of centralised data is of crucial importance for the<br />

information management at authorities and corporations. For this reason, it is<br />

essential to create a database concept. Such a concept defines the preparations<br />

necessary for putting the database into operation, and should always include a<br />

database security concept which focuses on the operation of the database.<br />

Inadequate protection of data might result in a loss of confidentiality,<br />

availability or integrity. To prevent this, it is absolutely necessary to prepare a<br />

detailed database security concept.<br />

To ensure the security of a database, a suitable database management system<br />

(DBMS) needs to be employed. To offer effective protection, the database<br />

management system needs to meet the following requirements: <strong>The</strong> DBMS<br />

must be<br />

- based on a comprehensive security policy<br />

- incorporated into the <strong>IT</strong> security concept of the organisation<br />

- installed correctly and<br />

- administered correctly.<br />

Direct access to the database (e.g. via SQL interpreters such as SQL*Plus)<br />

must only be possible for administrative users, in order to prevent<br />

manipulation of the data and database objects (e.g. tables and indices).<br />

Modifications to database objects must always be controlled via special IDs.<br />

For this purpose, the database management system must incorporate a suitable<br />

access control and login concept (refer to S 2.129 Controlling Access to<br />

Database <strong>Information</strong> and S 2.128 Controlling Access to a Database System).<br />

User IDs which can only perform data modifications via an application must<br />

not be granted direct access to the database, while IDs for managing database<br />

objects must be granted direct, controlled access.<br />

A database security concept must also settle the following important issues:<br />

- <strong>The</strong> physical storage or mirroring of database files (e.g. the database<br />

management software, the database itself, or the log files) as well as their<br />

distribution must be specified in order to increase availability and<br />

reliability, for example. For security reasons, mirrored control files should<br />

be stored on different hard disks. This would prevent a loss of all the<br />

control files in case of a failure on one hard disk. If the database objects of<br />

an application are stored in separate data files, these files should be<br />

distributed so as to prevent a failure on a hard disk from affecting all<br />

applications.<br />

Example:<br />

A database manages the data of two applications, using one data file each<br />

for the tables and indices. <strong>The</strong>se data files can be distributed as required<br />

among four hard disks.<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!