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 - Hardware & Software Remarks<br />

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

S 4.68 Ensuring consistent database management<br />

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

Administrators<br />

Implementation responsibility: Administrators<br />

In principle, the ID of the database administrator is not subject to any<br />

restrictions concerning the use of the database system, which increases the<br />

threat of errors and misuse. For this reason, the database administrator should<br />

receive a standard user ID in addition to his administrator ID, and only use the<br />

latter when absolutely necessary.<br />

Appropriate allocation of tasks, specification of guidelines, and measures for<br />

co-ordination are required to ensure that administrators do not perform any<br />

inconsistent or incomplete operations. <strong>The</strong> following requirements must be<br />

met here:<br />

- <strong>The</strong> techniques of performing and documenting modifications are to be<br />

specified.<br />

- <strong>The</strong> type and scope of modifications, as well as their reasons, are to be<br />

described.<br />

- In principle, changes to database objects or data must be approved by the<br />

administrator of the related <strong>IT</strong> application. Modifications to central<br />

database objects require the approval of all the administrators of the<br />

concerned <strong>IT</strong> applications.<br />

- <strong>The</strong> times of planned changes must be specified and announced.<br />

- A full backup of the database must be created before any changes are<br />

performed.<br />

To avoid misuse to the greatest possible extent and preclude inconsistencies,<br />

all the database objects of an application should be managed under a user ID<br />

created specially for that application. As a result, changes to the database<br />

objects can only be performed under this special user ID, and are not possible<br />

even under the ID of the database administrator. <strong>The</strong> password of this special<br />

user ID should only be known to the database administrator responsible for the<br />

application in question.<br />

Example:<br />

<strong>The</strong> data of three applications, A, B and C are managed in a database. All<br />

database objects allocated exclusively to application A are configured under<br />

the database user ID apnA and managed only via this ID. <strong>The</strong> database objects<br />

of the other two applications are assigned similarly. As a result, modifications<br />

to the database objects of any of the three applications can only be performed<br />

using the corresponding database user ID (provided that appropriately<br />

restrictive access rights have been defined).<br />

Database objects required by at least two of the three applications should be<br />

created and managed under a central database ID.<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!