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.13 Careful allocation of identifiers<br />

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

Implementation responsibility: Administrators<br />

In UNIX systems, user IDs and group IDs of processes and files are used,<br />

inter alia, to establish the originators of actions and to allocate rights.<br />

<strong>The</strong>refore, assignment of such IDs should be handled very carefully.<br />

Every log-in name, every user ID (UID) and every group ID (GID) must be<br />

unique. Even after deletion of a user or a group, the log-in name and the UID<br />

or GID should not be reassigned for a certain period of time. On networked<br />

systems, steps must be taken to ensure that it is not possible for the same user<br />

names and IDs to be assigned elsewhere on the system more than once. This is<br />

especially important where NFS is used due to the conversion of UIDs, in<br />

order that no data can be read without authorisation.<br />

Every user must be a member of at least one group. Every GID appearing in<br />

the /etc/passwd file must be defined in the /etc/group file.<br />

Every group should comprise only those users who are absolutely required.<br />

This is particularly important in the case of system groups (such as root, sys,<br />

bin, adm, news, uucp, nuucp or daemon).<br />

Log-ins with the UID 0 (superuser) may, apart from the system administrator<br />

root, be granted only for administrative log-ins in accordance with previously<br />

established rules (cf. S 2.33 Division of Administrator roles under UNIX).<br />

It is good policy to lay down naming conventions for log-in names and<br />

UIDs/GIDs. Checks should also be made at regular intervals as to whether all<br />

the UIDs are reasonable. For example, they should consist entirely of<br />

numerals and not contain any invalid combinations such as 00 or 000.<br />

<strong>The</strong> files /etc/passwd and /etc/group should not be edited using editors, as<br />

errors can greatly impair the security of the system. Only the appropriate<br />

administration tools should be used, although these are highly system-specific.<br />

Additional controls:<br />

- What procedures are used to allocate IDs?<br />

- Are the /etc/passwd and /etc/group files regularly checked for consistency?<br />

- Does the UID field in /etc/passwd really contain numerals?<br />

- Are all UIDs reasonable?<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!