15.2. Introduction
Prev | Chapter 15. Security | Next

## 15.2. Introduction

Security is a function that begins and ends with the system administrator. While FreeBSD provides some inherent security, the job of configuring and maintaining additional security mechanisms is probably one of the single largest undertakings of the sysadmin.

System security also pertains to dealing with various forms of attack, including attacks that attempt to crash, or otherwise make a system unusable, but do not attempt to compromise the `root` account. Security concerns can be split up into several categories:

1. Denial of service attacks.

2. User account compromises.

3. Root compromise through accessible services.

4. Root compromise via user accounts.

5. Backdoor creation.

A Denial of Service DoS attack is an action that deprives the machine of needed resources. Typically, DoS attacks are brute-force mechanisms that attempt to crash or otherwise make a machine unusable by overwhelming its services or network stack. Attacks on servers can often be fixed by properly specifying options to limit the load the servers incur on the system under adverse conditions. Brute-force network attacks are harder to deal with. This type of attack may not be able to take the machine down, but it can saturate the Internet connection.

A user account compromise is more common than a DoS attack. Many sysadmins still run unencrypted services, meaning that users logging into the system from a remote location are vulnerable to having their password sniffed. The attentive sysadmin analyzes the remote access logs looking for suspicious source addresses and suspicious logins.

In a well secured and maintained system, access to a user account does not necessarily give the attacker access to `root`. Without `root` access, the attacker cannot generally hide his tracks and may, at best, be able to do nothing more than mess with the user's files or crash the machine. User account compromises are common because users tend not to take the precautions that sysadmins take.

There are potentially many ways to break `root`: the attacker may know the `root` password, the attacker may exploit a bug in a service which runs as `root`, or the attacker may know of a bug in a SUID-root program. An attacker may utilize a program known as a backdoor to search for vulnerable systems, take advantage of unpatched exploits to access a system, and hide traces of illegal activity.

Security remedies should always be implemented with a multi-layered “onion peel” approach and can be categorized as follows:

1. Secure `root` and staff accounts.

2. Secure `root`–run servers and SUID/SGID binaries.

3. Secure user accounts.

4. Secure the password file.

5. Secure the kernel core, raw devices, and filesystems.

6. Quick detection of inappropriate changes made to the system.

7. Paranoia.

The next section covers these items in greater depth.

Prev | Up | Next
Chapter 15. Security | Home | 15.3. Securing FreeBSD

This, and other documents, can be downloaded from http://ftp.FreeBSD.org/pub/FreeBSD/doc/

For questions about FreeBSD, read the documentation before contacting <questions@FreeBSD.org>.
For questions about this documentation, e-mail <doc@FreeBSD.org>.