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.105 Initial measures after a Unix standard<br />

installation<br />

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

Implementation responsibility: Administrator<br />

Most Unix systems do not satisfy the system security requirements after a<br />

standard installation. Often too many sensitive services and configurations are<br />

activated by the vendors or else these are provided with access rights which<br />

are not sufficiently restrictive.<br />

This section is intended to show by way of example how to make the system<br />

secure following a standard installation.<br />

- Prior to installation the administrator should be given appropriate training,<br />

especially as regards the security aspects. This should include informing<br />

him of all the potential security weaknesses of the <strong>IT</strong> system (see also<br />

S 2.35 Obtaining information on security weaknesses of the system).<br />

Subscribing to appropriate mailing lists should also be covered.<br />

- After the installation has been completed, the System Administrator's<br />

account should be assigned a good password (see S 2.11 Provisions<br />

governing the use of passwords).<br />

- A review should be made of which services are running on the <strong>IT</strong> system.<br />

It is possible to check this e.g. by entering the command netstat -a | grep<br />

listen. Services which are not needed should be disabled or removed (see<br />

S 5.72 Deactivation of unnecessary network services).<br />

- If the system does not function as a mail server, the mail daemon should be<br />

deactivated as a network service. If mail is to be delivered locally on the<br />

system, sendmail can be started with the option -q15 or as a cron process:<br />

1 * * * * /usr/sbin/sendmail -q 2>&1 >/dev/null<br />

<strong>The</strong> mail queue is emptied at regular intervals and the mail is delivered<br />

locally.<br />

- <strong>The</strong> latest version of the vendor's sendmail should be installed (see also<br />

S 4.107 Use of vendor resources and S 5.19 Use of the sendmail security<br />

mechanisms). Alternatively, public domain mail programs such as a qmail<br />

can be used. <strong>The</strong> version number of the installed version of sendmail can<br />

be identified with the command telnet localhost 25.<br />

- After the standard installation, the security patches provided by the vendor<br />

should be installed (see also S 4.107 Use of vendor resources). It is<br />

extremely important then to check that no unnecessary services have been<br />

activated as a result of the patch installation.<br />

- <strong>The</strong> file systems should be imported or exported only to the necessary<br />

extent. Care must be taken to ensure that file systems are not exported in<br />

such a way that anyone can write to them.<br />

- If there is no alternative to using NIS, then NIS+ should be used as<br />

additional security mechanisms are incorporated into this.<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!