22.12.2012 Views

Front cover - IBM Redbooks

Front cover - IBM Redbooks

Front cover - IBM Redbooks

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.

390 Lotus Security Handbook<br />

change; therefore – as an added security measure – it can be mounted as<br />

read-only.<br />

► /var partition: This partition stores system logs and data services such as<br />

mail, Web, databases, printing, running services, package management, and<br />

so forth. If only one separate partition is created from /, /var is the one that<br />

should be created separately.<br />

► /usr/local directory (the /opt directory in Solaris): These directories often<br />

contain locally-installed optional software, configuration files, and data. The<br />

/usr/local directory is normally not affected by operating system upgrades.<br />

Depending on how these directories are used by the UNIX system, they too<br />

can be mounted as read-only.<br />

The details vary in different UNIX versions (and GNU/Linux distributions) so we<br />

recommend that you read the installation notes that come with the version of<br />

UNIX to be installed to determine the best manner to install them with proper<br />

security in mind.<br />

9.4.3 Disabling the extraneous inetd service<br />

The inetd service is the UNIX “Super Internet Server.” It is basically a daemon<br />

process that is invoked at boot time and reads in a flat configuration file that is<br />

normally found at /etc/inetd.conf.<br />

The inetd service listens for incoming connections on the defined IP ports. When<br />

a connection is initiated on a defined port, it invokes a pre-configured program to<br />

service the request. After the connection is finished, the process invoked to<br />

service that request terminates. The original reason for designing this service in<br />

this manner was to lighten the load and resources required on the IT system.<br />

There are a number of services enabled through inetd, and almost all of them<br />

should be disabled as part of a properly hardened server. Besides normally<br />

disabling FTP, TFTP, Telnet, and the Berkeley r* commands, the following<br />

should be disabled:<br />

► The in.named service: This is the BIND name services daemon. Except for<br />

servers that are specifically defined as being the DNS servers of the<br />

organizations, DNS should not be running on a hardened UNIX server.<br />

► The in.fingerd service: This is the finger daemon that can be used to show<br />

user information and lists of users who are logged in. On a properly hardened<br />

UNIX server, there is no reason to advertise that information that could be of<br />

help to would-be attackers.<br />

► The daytime service: This is the service that displays the date and time on the<br />

system in a string format. Do not permit would-be attackers to get the date<br />

and time of the system, as it is useful for them to implement replay attacks.

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

Saved successfully!

Ooh no, something went wrong!