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

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

- For every <strong>IT</strong> system which needs to log into the local <strong>IT</strong> system via UUCP,<br />

a separate user ID and password must be entered in /etc/passwd. <strong>The</strong> uucp<br />

user's UID must not be selected for this; instead, each remote <strong>IT</strong> system<br />

must have its own, individual UID.<br />

- UUCP passwords are transferred in the uncoded form during<br />

communication requests, and stored uncoded in the corresponding UUCP<br />

configuration file for requests to remote computers. Depending on the<br />

application and environment (particularly in the case of long-distance<br />

networks), appropriate safeguards must be taken, e.g. use of one-time<br />

passwords.<br />

Various configuration files must be set up to allow the use of UUCP. All<br />

settings must be documented, and deviations from the settings recommended<br />

in the following must be explained to allow an understanding of these<br />

modifications at a later stage.<br />

<strong>The</strong> following files must be administered very carefully as they contain<br />

critical information for security. <strong>The</strong> files are located in the /usr/lib/uucp and<br />

/etc/uucp directories. Only the uucp user must have write access to these<br />

directories.<br />

- Systems: This file contains information required for establishing<br />

connections with remote <strong>IT</strong> systems. <strong>The</strong> time periods over which UUCP<br />

transmission is allowed can be specified here for every <strong>IT</strong> system. <strong>The</strong>se<br />

time periods must be as short as possible. This file also contains the<br />

telephone numbers and log-in sequences for the <strong>IT</strong> systems with which<br />

UUCP connections can be established. Only the uucp owner must have<br />

read access to Systems, as passwords for remote <strong>IT</strong> systems are also<br />

entered here.<br />

- Permissions: Access rights for remote systems are specified here. No <strong>IT</strong><br />

systems are listed in Permissions on its delivery, i.e. no access is possible<br />

via UUCP. For every computer that can call and log-in, and for every<br />

computer that can be called, settings must be made to specify the<br />

respective access rights and other conditions. <strong>The</strong> access rights for <strong>IT</strong><br />

systems called by the local one are specified in the entries listed under<br />

MACHINE, and under LOGNAME for the calling <strong>IT</strong> system. Security can<br />

be increased considerably through the use of these configuration<br />

possibilities.<br />

<strong>The</strong> uucheck -v command should be regularly used to check the options set<br />

in the Permissions file. <strong>The</strong>se options should be set as follows:<br />

REQUEST<br />

This option should be set to NO (default setting) to prevent<br />

remote systems from reading local data.<br />

COMMANDS<br />

On no account should ALL be entered here; only required<br />

commands like rnews or rmail should be allowed. <strong>The</strong><br />

commands should be stated with the full path name.<br />

WR<strong>IT</strong>E/READ<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!