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 - Organisation Remarks<br />

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

S 2.30 Provisions governing the designation of users<br />

and of user groups<br />

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

Implementation responsibility: Administrators<br />

Provisions governing the designation of users and of user groups are the<br />

prerequisite for adequate allocation of access rights and for ensuring orderly<br />

and controlled operations.<br />

A blank form should be in existence so that, as a first step, the required data<br />

can be obtained from each user or each user group:<br />

- Surname, first name<br />

- Proposed user name and group ID, if not already allocated by convention,<br />

- Organisational unit<br />

- Reachability (e.g. telephone, room)<br />

- If applicable: project<br />

- where appropriate, information on the planned activity within the system<br />

and the rights required for that purpose and on the duration of the activity;<br />

- where appropriate, restriction on times, terminals, disk volumes, access<br />

rights (for certain directories, remote access, etc.), restricted user<br />

environment;<br />

- If applicable: Approval by superiors<br />

If access rights are provided which go beyond those provided as standard, this<br />

must be justified. This can also be done by electronic means, e.g. by a special<br />

log-in, the name and password of which will be made known to the designated<br />

users. <strong>The</strong>re, a pertinent program will be run which ends with a log-out. A<br />

print-out may be made of the recorded data for submission to the superior. A<br />

password given to a new user for first-time use of the system must be altered<br />

after that use. This should be initiated by the system.<br />

A limited number of authorisation profiles must be specified. A new user will<br />

then be assigned to such a profile and thus obtain the exact authorisation<br />

required for his activity. In this regard, the system-specific options will have<br />

to be taken into account when configuring users and groups. It is advisable to<br />

lay down naming conventions for the names of users and groups (e.g. user ID<br />

= initials of organisational unit serial number).<br />

Authorisation to have access to files must be confined to users and/or groups<br />

having a justified interest. If several persons have to access a given file, a<br />

group should be established for these users. As a rule, every user must be<br />

assigned his own user ID; no ID must be used by several users. A home<br />

directory must be provided for each user.<br />

For user/group configuration within a system, an administrative role should be<br />

established: configuration should be effected by means of a special log-in<br />

under which an appropriate program or shell script is started. Thus, the<br />

responsible administrators can configure users and/or user groups only in a<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!