4.5.3. Insecure Services

4.5.3. Insecure Services

Potentially, any network service is insecure. This is why turning unused services off is so important. Exploits for services are revealed and patched routinely, making it very important to keep packages associated with any network service updated. Refer to Chapter 3, Security Updates for more information about this issue.

Some network protocols are inherently more insecure than others. These include any services which do the following things:

Examples of inherently insecure services includes the following:

All remote login and shell programs (rlogin, rsh, and telnet) should be avoided in favor of SSH. (refer to Section 4.7, “Security Enhanced Communication Tools” for more information about sshd.)

FTP is not as inherently dangerous to the security of the system as remote shells, but FTP servers must be carefully configured and monitored to avoid problems. Refer to Section 5.6, “Securing FTP” for more information on securing FTP servers.

Services that should be carefully implemented and behind a firewall include:

More information on securing network services is available in Chapter 5, Server Security.

The next section discusses tools available to set up a simple firewall.