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

access rights, so that security pitfalls are created. In particular, the<br />

possibility of granting rights to all users (GRANT ... TO PUBLIC) should<br />

not be used.<br />

In general, only the owner of a database object is allowed to grant access<br />

rights to other users. However, some database systems also allow the<br />

owner of a database object to authorise other users to grant access rights.<br />

This facility should only be made use of in exceptional cases, as it no<br />

longer allows the access control of data and database objects.<br />

- Restrictive access to data via applications<br />

Applications should support restrictive access to data, i.e. only those<br />

functions and data actually required by users for fulfilling their<br />

responsibilities should be made available to them (in accordance with the<br />

user IDs and the group memberships). One method of implementing this is<br />

through the use of stored procedures.<br />

Stored procedures are sequences of SQL statements which have been<br />

stored in the database in a pre-optimised manner. To invoke a stored<br />

procedure, only its name and, if applicable, certain parameters need to be<br />

entered in order to execute the underlying SQL statements. This is<br />

advantageous, because not all of the SQL statements need to be transferred<br />

to the database server, thus reducing the load on the network when<br />

complex operations are involved. Furthermore, the database system is able<br />

to store the SQL statements in an optimised manner, so that they can be<br />

executed more rapidly. <strong>The</strong> greatest restriction which can be imposed for<br />

the purpose of access control is to allocate access rights for stored<br />

procedures instead of tables or views. If access rights are just allocated for<br />

stored procedures, then users can only invoke operations which have been<br />

enabled by the database administrators.<br />

Examples:<br />

1. In MS Access, different access rights can be granted for the database itself<br />

(open/execute, exclusive, administer) as well as for the tables and queries<br />

(read data, update data, delete data, add data). <strong>The</strong>se rights can be assigned<br />

to various users and user groups. In MS Access, the groups named<br />

"administrators" and "users" have been configured by default; the "users"<br />

group contains the "read data" and "update data" rights for tables and<br />

queries, and the "open/execute" rights for databases. To allow a detailed<br />

control of access rights, it is possible to define separate groups which can<br />

be assigned different rights. This can be done in the menu titled Extras<br />

under the items Access rights and User and group accounts.<br />

2. In an Oracle database, a group named "Department_1" can be created with<br />

the following instruction:<br />

CREATE ROLE Department_1 IDENTIFIED BY ;<br />

In the following example, the group named "Department_1" is granted the<br />

right to establish a connection with a database and to create a session:<br />

GRANT CONNECT, CREATE SESSION TO Department_1;<br />

In the following example, the same group is granted the right to perform a<br />

SELECT on the table named "Test":<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!