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

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

S 5.38 Secure integration of DOS PC's into a UNIX<br />

network<br />

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

Administrators<br />

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

DOS PC’s can be integrated into UNIX networks in various ways. In general,<br />

PCs have weaker security mechanisms than UNIX systems. Everyone with<br />

access to a PC can administrate it, thus being able, for example, to change<br />

settings or install software.<br />

By installing the appropriate software, a networked PC can be used to<br />

eavesdrop the network. <strong>The</strong>refore only authorised users may have access to a<br />

PC (see also S 1.23 Locked doors and S 2.6 Granting of site access<br />

authorisations). Moreover, measures must be taken to ensure and regularly<br />

monitor that software cannot be loaded without supervision (see also S 2.9<br />

Ban on Using Non-Released Software and S 2.10 Survey of the software held).<br />

In addition, it is easily possible by changing the configuration of a PC, to fake<br />

any computer ID and thus carry out a masquerade. This means that when<br />

using RPC on the UNIX server no trusted hosts must be defined. Trusted hosts<br />

are systems which are regarded as trustworthy and from which you can log in<br />

(using rlogin) or perform a command (using rsh) without giving a password.<br />

This is set in the $HOME/.rhosts and /etc/hosts.equiv files on the UNIX<br />

server. It must be ensured that the $HOME/.rhosts and /etc/hosts.equiv files<br />

are not available or are empty and that the user does not have access<br />

permission to them (see also S 5.20 Use of the security mechanisms of rlogin,<br />

rsh and rcp).<br />

If PC’s are connected to a UNIX network via NFS, the following points<br />

should be noted:<br />

- On an NFS server every file system or directory which can be mounted by<br />

other computers must be entered in a file (e.g. /etc/exports or<br />

/etc/dfs/dfstab). <strong>The</strong> access rights of the NFS clients to the released file<br />

systems are also set in this file. When using NFS, care must be taken on the<br />

UNIX server that directories are only released for mounting where<br />

absolutely necessary.<br />

- In order to avoid root rights being acquired through NFS, no root access<br />

must be granted for exported file systems on the UNIX server as would be<br />

possible using the ”root=” option. Under no circumstances may root<br />

access be given to a PC in this way.<br />

- When copying files from a PC to a UNIX system via NFS or ftp it can<br />

happen that the attributes are set too freely. You must always check<br />

whether this is the case and change the umask if necessary.<br />

Computer viruses occur mainly on DOS PC’s. When PC’s are networked with<br />

UNIX systems, viruses can spread by infected programmes passing from PC<br />

to PC. <strong>The</strong> same measures should therefore be taken here as when exchanging<br />

programmes using data media or remote data transfer (see also S 4.3 Periodic<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!