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.20 Restrictive allocation of attributes for UNIX<br />

user files and directories<br />

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

Implementation responsibility: Administrator, <strong>IT</strong> users<br />

<strong>The</strong> measures listed here apply to the files and directories of a user (including<br />

Mail files).<br />

Users should set the attributes of their files and directories in a form which<br />

prevents access by other users. If other users are to be allowed access,<br />

appropriate user groups should be established.<br />

For user-specific configuration files such as .profile, .exrc, .login, .cshrc, only<br />

the owner of the file should hold rights.<br />

On UNIX systems, various programs have user-specific configuration files,<br />

such as .exrc, .emacs or .mailrc, which are automatically executed when the<br />

program is called up and which set variables and options for the user. To<br />

prevent implantation of any Trojan horses into such files, only their owner<br />

should be authorised to access them.<br />

<strong>The</strong> file .exrc is read before the editors ex or vi are started. If a file with the<br />

same name is already contained in the current directory, it will be evaluated by<br />

some UNIX versions. All UNIX versions used must be checked in this regard<br />

as operating system commands can be carried out each time the editor is<br />

called up.<br />

<strong>The</strong> s bit should be set only when absolutely required. In the case of shell<br />

scripts, the s bit should not be set. <strong>The</strong> s bit should only be set after<br />

consultation with the Administrator; reasons should be given for the need to<br />

do so, which must be documented.<br />

umask<br />

With umask (user file creation mode mask), it is laid down for each user<br />

which attributes for regulating the access rights will be contained in a file<br />

newly created by him. In the user-specific configuration files such as<br />

/etc/profile or the $HOME /.profile files, umask = 0027 (-rw-r-----) or umask =<br />

0077 (-rw-------) should be set so that the file attributes for new files will only<br />

grant access rights to the originator (and possibly to the group).<br />

Mail files<br />

<strong>The</strong> attributes of mail files should be checked regularly to ensure that only the<br />

respective user has access to the files. <strong>The</strong> integrity of all the attributes set for<br />

UNIX user files and directories should be verified at regular intervals, e.g.<br />

using Tripwire or USE<strong>IT</strong> (see also S 4.26 Regular security checks of the UNIX<br />

system).<br />

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

<strong>IT</strong>-<strong>Baseline</strong> <strong>Protection</strong> <strong>Manual</strong>: Oktober 2000<br />

Prevent access from<br />

unauthorised outsiders<br />

Avoid s bit<br />

Check integrity

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!