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

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

S 4.71 Restrictive utilisation of database links<br />

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

Implementation responsibility: Administrators<br />

Database links allow a database to access the information in another database.<br />

To ensure adequate protection of such information however, database links<br />

should only be used when absolutely necessary.<br />

To allow access control of users employing database links, a suitable concept<br />

of defining user IDs is necessary. In principle, a user is able to access an<br />

extraneous database if it recognises the ID with which the user logs into the<br />

local database. Additional security is provided by the possibility of<br />

establishing links with an explicit specification of the user ID and a password.<br />

In principle, every database user is entitled to establish database links<br />

(provided that the user is able to execute the related CREATE command). In<br />

general however, only the administrator should be authorised to establish such<br />

links. This applies especially to database links which can be employed by all<br />

users (PUBLIC DB-Links). <strong>The</strong> right to establish database links should<br />

explicitly not be granted to standard user IDs.<br />

Furthermore, the number of database links which can be employed<br />

simultaneously by a user must be restricted in order to control the loads on the<br />

database servers. Otherwise an intruder could exploit this situation to obstruct,<br />

or even completely paralyse, the operation of the database servers.<br />

Documentation of the database links configured by the administrator is<br />

indispensable. In addition to the types of link (established via a special user<br />

ID, or given that the locally applicable database ID has also been configured,<br />

for the connected database) the documentation should also list the user groups<br />

authorised to make use of each database link. As already mentioned, database<br />

links defined as PUBLIC can be used by all database IDs.<br />

Additional controls:<br />

- Does a concept for defining user IDs exist, and if so, to what extent does it<br />

take the possible use of database links into account?<br />

- Which user IDs are authorised to establish database links?<br />

- Does a concept for employing database links exist, and if so, has it been<br />

implemented?<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!