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

Remarks<br />

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

S 4.23 Secure invocation of executable files<br />

Initiation responsibility: <strong>IT</strong> Security Management, Administrators<br />

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

Steps must be taken to ensure that only approved versions of executable files<br />

and no modified versions that may have been introduced (especially Trojan<br />

horses) are called up.<br />

<strong>The</strong>refore, the current directory (.) should not be included as a path in the<br />

PATH variable. Executable files should only be held in the directories<br />

intended for the purpose. Only the owner should have write access to the<br />

directories contained in a PATH variable. This should be regularly checked. In<br />

UNIX systems with an IFS variable, this should be set to the default value<br />

(space, tab and newline) and, in particular, must not be set to "/".<br />

Additional controls:<br />

- Are the PATH entries checked regularly?<br />

- Are executable files scattered around the system?<br />

- Are the procedures for executable files known to the users?<br />

- Is the integrity of the relevant configuration files verified regularly (e.g.<br />

with Tripwire or USE<strong>IT</strong>)?<br />

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

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

Current directory not in<br />

the search path

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

Saved successfully!

Ooh no, something went wrong!