Red Hat ENTERPRISE LINUX 3 - SECURITY GUIDE User manual

Red Hat Enterprise Linux 3
Security Guide

Red Hat Enterprise Linux 3: Security Guide
Copyright © 2003 by Red Hat, Inc.
Red Hat, Inc.
1801 Varsity Drive
Raleigh NC 27606-2072 USA
Phone: [phone]
Phone: [phone]
Fax: [phone]
PO Box 13588
Research Triangle Park NC 27709 USA
rhel-sg(EN)-3-Print-RHI (2003-07-25T17:12)
Copyright © 2003 by Red Hat, Inc. This material may be distributed only subject to the terms and conditions set forth in the
Open Publication License, V1.0 or later (the latest version is presently available at http://www.opencontent.org/openpub/).
Distribution of substantively modified versions of this document is prohibited without the explicit permission of the copyright
holder.
Distribution of the work or derivative of the work in any standard (paper) book form for commercial purposes is prohibited
unless prior permission is obtained from the copyright holder.
Red Hat, Red Hat Network, the Red Hat "Shadow Man" logo, RPM, Maximum RPM, the RPM logo, Linux Library,
PowerTools, Linux Undercover, RHmember, RHmember More, Rough Cuts, Rawhide and all Red Hat-based trademarks and
logos are trademarks or registered trademarks of Red Hat, Inc. in the United States and other countries.
Linux is a registered trademark of Linus Torvalds.
Motif and UNIX are registered trademarks of The Open Group.
XFree86 is a trademark of The XFree86 Project, Inc, and is pending registration.
Intel and Pentium are registered trademarks of Intel Corporation. Itanium and Celeron are trademarks of Intel Corporation.
AMD, Opteron, Athlon, Duron, and K6 are registered trademarks of Advanced Micro Devices, Inc.
Netscape is a registered trademark of Netscape Communications Corporation in the United States and other countries.
Java and Swing are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. or other countries.
Oracle is a registered trademark, and Oracle8i, Oracle9i, and interMedia are trademarks or registered trademarks of Oracle
Corporation.
Microsoft and Windows are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or
other countries.
SSH and Secure Shell are trademarks of SSH Communications Security, Inc.
FireWire is a trademark of Apple Computer Corporation.
IBM, AS/400, OS/400, RS/6000, S/390, and zSeries are registered trademarks of International Business Machines
Corporation. eServer, iSeries, and pSeries are trademarks of International Business Machines Corporation.
All other trademarks and copyrights referred to are the property of their respective owners.
The GPG fingerprint of the [email protected] key is:
CA 20 86 86 2B D6 9D FC 65 F6 EC C4 21 91 80 CD DB 42 A6 0E

Table of Contents
Introduction.......................................................................................................................................... i
1. Document Conventions.........................................................................................................ii
2. More to Come ...................................................................................................................... iv
2.1. Send in Your Feedback ......................................................................................... iv
I. A General Introduction to Security ................................................................................................ i
1. Security Overview................................................................................................................. 1
1.1. What is Computer Security? .................................................................................. 1
1.2. Security Controls ................................................................................................... 5
1.3. Conclusion ............................................................................................................. 6
2. Attackers and Vulnerabilities ................................................................................................ 7
2.1. A Quick History of Hackers .................................................................................. 7
2.2. Threats to Network Security .................................................................................. 7
2.3. Threats to Server Security...................................................................................... 8
2.4. Threats to Workstation and Home PC Security ................................................... 10
II. Configuring Red Hat Enterprise Linux for Security................................................................ 11
3. Security Updates ................................................................................................................. 13
3.1. Updating Packages............................................................................................... 13
4. Workstation Security........................................................................................................... 19
4.1. Evaluating Workstation Security ......................................................................... 19
4.2. BIOS and Boot Loader Security .......................................................................... 19
4.3. Password Security................................................................................................ 22
4.4. Administrative Controls....................................................................................... 27
4.5. Available Network Services................................................................................. 33
4.6. Personal Firewalls ................................................................................................ 35
4.7. Security Enhanced Communication Tools........................................................... 36
5. Server Security.................................................................................................................... 37
5.1. Securing Services With TCP Wrappers and xinetd .......................................... 37
5.2. Securing Portmap................................................................................................. 40
5.3. Securing NIS........................................................................................................ 40
5.4. Securing NFS ....................................................................................................... 42
5.5. Securing the Apache HTTP Server...................................................................... 43
5.6. Securing FTP ....................................................................................................... 44
5.7. Securing Sendmail ............................................................................................... 47
5.8. Verifying Which Ports Are Listening .................................................................. 48
6. Virtual Private Networks..................................................................................................... 51
6.1. VPNs and Red Hat Enterprise Linux ................................................................... 51
6.2. Crypto IP Encapsulation (CIPE).......................................................................... 51
6.3. Why Use CIPE? ................................................................................................... 52
6.4. CIPE Installation.................................................................................................. 53
6.5. CIPE Server Configuration .................................................................................. 53
6.6. Configuring Clients for CIPE .............................................................................. 54
6.7. Customizing CIPE ............................................................................................... 56
6.8. CIPE Key Management ....................................................................................... 57
6.9. IPsec..................................................................................................................... 57
6.10. IPsec Installation................................................................................................ 58
6.11. IPsec Host-to-Host Configuration...................................................................... 58
6.12. IPsec Network-to-Network configuration.......................................................... 60
7. Firewalls.............................................................................................................................. 65
7.1. Netfilter and IPTables .......................................................................................... 66
7.2. Using IPTables ..................................................................................................... 66
7.3. Common iptables Filtering.............................................................................. 68
7.4. FORWARD and NAT Rules..................................................................................... 69
7.5. DMZs and iptables .......................................................................................... 70

7.6. Viruses and Spoofed IP Addresses ...................................................................... 70
7.7. IP6Tables.............................................................................................................. 70
7.8. Additional Resources........................................................................................... 71
III. Assessing Your Security............................................................................................................. 73
8. Vulnerability Assessment.................................................................................................... 75
8.1. Thinking Like the Enemy .................................................................................... 75
8.2. Defining Assessment and Testing ........................................................................ 75
8.3. Evaluating the Tools............................................................................................. 77
IV. Intrusions and Incident Response............................................................................................. 81
9. Intrusion Detection.............................................................................................................. 83
9.1. Defining Intrusion Detection Systems ................................................................. 83
9.2. Host-based IDS .................................................................................................... 83
9.3. Network-based IDS.............................................................................................. 86
10. Incident Response ............................................................................................................. 89
10.1. Defining Incident Response ............................................................................... 89
10.2. Creating an Incident Response Plan .................................................................. 89
10.3. Implementing the Incident Response Plan......................................................... 90
10.4. Investigating the Incident................................................................................... 91
10.5. Restoring and Recovering Resources ................................................................ 93
10.6. Reporting the Incident........................................................................................ 94
V. Appendixes.................................................................................................................................... 95
A. Hardware and Network Protection..................................................................................... 97
A.1. Secure Network Topologies ................................................................................ 97
A.2. Hardware Security............................................................................................. 100
B. Common Exploits and Attacks......................................................................................... 101
C. Common Ports.................................................................................................................. 105
Index................................................................................................................................................. 117
Colophon.......................................................................................................................................... 123

Introduction
Welcome to the Red Hat Enterprise Linux Security Guide!
The Red Hat Enterprise Linux Security Guide is designed to assist users of Red Hat Enterprise Linux
in learning the processes and practices of securing workstations and servers against local and remote
intrusion, exploitation, and malicious activity. The Red Hat Enterprise Linux Security Guide details
the planning and the tools involved in creating a secured computing environment for the data center,
workplace, and home. With proper administrative knowledge, vigilance, and tools, systems running
Red Hat Enterprise Linux can be both fully functional and secured from most common intrusion and
exploit methods.
This guide discusses several security-related topics in great detail, including:
•Firewalls
•Encryption
•Securing Critical Services
•Virtual Private Networks
•Intrusion Detection
The manual is divided into the following parts:
•General Introduction to Security
•Configuring Red Hat Enterprise Linux for Security
•Assessing Your Security
•Intrusions and Incident Response
•Appendix
We would like to thank Thomas Rude for his generous contributions to this manual. He wrote the
Vulnerability Assessments and Incident Response chapters. Thanks, "farmerdude."
This manual assumes that you have an advanced knowledge of Red Hat Enterprise Linux. If you are
a new user or only have basic to intermediate knowledge of Red Hat Enterprise Linux and need more
information on using the system, refer to the following guides which discuss the fundamental aspects
of Red Hat Enterprise Linux in greater detail than the Red Hat Enterprise Linux Security Guide:
•The Red Hat Enterprise Linux Installation Guide provides information regarding installation.
•The Red Hat Enterprise Linux Introduction to System Administration contains introductory infor-
mation for new Red Hat Enterprise Linux system administrators.
•The Red Hat Enterprise Linux System Administration Guide offers detailed information about con-
figuring Red Hat Enterprise Linux to suit your particular needs as a user. This guide includes some
services that are discussed (from a security standpoint) in the Red Hat Enterprise Linux Security
Guide.
•Red Hat Enterprise Linux Reference Guide provides detailed information suited for more experi-
enced users to refer to when needed, as opposed to step-by-step instructions.
HTML, PDF, and RPM versions of the manuals are available on the Red Hat Enterprise Linux Docu-
mentation CD and online at http://www.redhat.com/docs/.

ii Introduction
Note
Although this manual reflects the most current information possible, read the Red Hat Enterprise
Linux Release Notes for information that may not have been available prior to our documenta-
tion being finalized. They can be found on the Red Hat Enterprise Linux CD #1 and online at
http://www.redhat.com/docs/.
1. Document Conventions
When you read this manual, certain words are represented in different fonts, typefaces, sizes, and
weights. This highlighting is systematic; different words are represented in the same style to indicate
their inclusion in a specific category. The types of words that are represented this way include the
following:
command
Linux commands (and other operating system commands, when used) are represented this way.
This style should indicate to you that you can type the word or phrase on the command line
and press [Enter] to invoke a command. Sometimes a command contains words that would be
displayed in a different style on their own (such as file names). In these cases, they are considered
to be part of the command, so the entire phrase is displayed as a command. For example:
Use the cat testfile command to view the contents of a file, named testfile, in the current
working directory.
file name
File names, directory names, paths, and RPM package names are represented this way. This style
should indicate that a particular file or directory exists by that name on your system. Examples:
The .bashrc file in your home directory contains bash shell definitions and aliases for your own
use.
The /etc/fstab file contains information about different system devices and file systems.
Install the webalizer RPM if you want to use a Web server log file analysis program.
application
This style indicates that the program is an end-user application (as opposed to system software).
For example:
Use Mozilla to browse the Web.
[key]
A key on the keyboard is shown in this style. For example:
To use [Tab] completion, type in a character and then press the [Tab] key. Your terminal displays
the list of files in the directory that start with that letter.
[key]-[combination]
A combination of keystrokes is represented in this way. For example:
The [Ctrl]-[Alt]-[Backspace] key combination exits your graphical session and return you to the
graphical login screen or the console.

Introduction iii
text found on a GUI interface
A title, word, or phrase found on a GUI interface screen or window is shown in this style. Text
shown in this style is being used to identify a particular GUI screen or an element on a GUI
screen (such as text associated with a checkbox or field). Example:
Select the Require Password checkbox if you would like your screensaver to require a password
before stopping.
top level of a menu on a GUI screen or window
A word in this style indicates that the word is the top level of a pulldown menu. If you click on
the word on the GUI screen, the rest of the menu should appear. For example:
Under File on a GNOME terminal, the New Tab option allows you to open multiple shell
prompts in the same window.
If you need to type in a sequence of commands from a GUI menu, they are shown like the
following example:
Go to Main Menu Button (on the Panel) => Programming => Emacs to start the Emacs text
editor.
button on a GUI screen or window
This style indicates that the text can be found on a clickable button on a GUI screen. For example:
Click on the Back button to return to the webpage you last viewed.
computer output
Text in this style indicates text displayed to a shell prompt such as error messages and responses
to commands. For example:
The ls command displays the contents of a directory. For example:
Desktop about.html logs paulwesterberg.png
Mail backupfiles mail reports
The output returned in response to the command (in this case, the contents of the directory) is
shown in this style.
prompt
A prompt, which is a computer’s way of signifying that it is ready for you to input something, is
shown in this style. Examples:
$
#
[stephen@maturin stephen]$
leopard login:
user input
Text that the user has to type, either on the command line, or into a text box on a GUI screen, is
displayed in this style. In the following example, text is displayed in this style:
To boot your system into the text based installation program, you must type in the text com-
mand at the boot: prompt.
replaceable
Text used for examples which is meant to be replaced with data provided by the user is displayed
in this style. In the following example,

version-number

is displayed in this style:

iv Introduction
The directory for the kernel source is /usr/src/

version-number

/, where

version-number

is the version of the kernel installed on this system.
Additionally, we use several different strategies to draw your attention to certain pieces of informa-
tion. In order of how critical the information is to your system, these items are marked as note, tip,
important, caution, or a warning. For example:
Note
Remember that Linux is case sensitive. In other words, a rose is not a ROSE is not a rOsE.
Tip
The directory /usr/share/doc/ contains additional documentation for packages installed on your
system.
Important
If you modify the DHCP configuration file, the changes will not take effect until you restart the DHCP
daemon.
Caution
Do not perform routine tasks as root — use a regular user account unless you need to use the root
account for system administration tasks.
Warning
Be careful to remove only the necessary Red Hat Enterprise Linux partitions. Removing other parti-
tions could result in data loss or a corrupted system environment.
2. More to Come
The Red Hat Enterprise Linux Security Guide is part of Red Hat’s growing commitment to provide
useful and timely support and information to Red Hat Enterprise Linux users. As new tools and secu-
rity methodologies are released, this guide will be expanded to include them.

Introduction v
2.1. Send in Your Feedback
If you spot a typo in the Red Hat Enterprise Linux Security Guide, or if you have thought of a
way to make this manual better, we would love to hear from you! Submit a report in Bugzilla
(http://bugzilla.redhat.com/bugzilla/) against the component rhel-sg.
Be sure to mention the manual’s identifier:
rhel-sg(EN)-3-Print-RHI (2003-07-25T17:12)
By mentioning the identifier, we know exactly which version of the guide you have.
If you have a suggestion for improving the documentation, try to be as specific as possible. If you
have found an error, include the section number and some of the surrounding text so we can find it
easily.

vi Introduction

I. A General Introduction to Security
This part defines information security, its history, and the industry that has developed to address it. It
also discusses some of the risks that computer users or administrators face.
Table of Contents
1. Security Overview........................................................................................................................... 1
2. Attackers and Vulnerabilities ........................................................................................................ 7

Chapter 1.
Security Overview
Because of the increased reliance on powerful, networked computers to help run businesses and keep
track of our personal information, industries have been formed around the practice of network and
computer security. Enterprises have solicited the knowledge and skills of security experts to prop-
erly audit systems and tailor solutions to fit the operating requirements of the organization. Because
most organizations are dynamic in nature, with workers accessing company IT resources locally and
remotely, the need for secure computing environments has become more pronounced.
Unfortunately, most organizations (as well as individual users) regard security as an afterthought, a
process that is overlooked in favor of increased power, productivity, and budgetary concerns. Proper
security implementation is often enacted postmortem — after an unauthorized intrusion has already
occurred. Security experts agree that the right measures taken prior to connecting a site to an untrusted
network such as the Internet is an effective means of thwarting most attempts at intrusion.
1.1. What is Computer Security?
Computer security is a general term that covers a wide area of computing and information process-
ing. Industries that depend on computer systems and networks to conduct daily business transactions
and access crucial information regard their data as an important part of their overall assets. Several
terms and metrics have entered our daily business vocabulary, such as total cost of ownership (TCO)
and quality of service (QoS). In these metrics, industries calculate aspects such as data integrity and
high-availability as part of their planning and process management costs. In some industries, such
as electronic commerce, the availability and trustworthiness of data can be the difference between
success and failure.
1.1.1. How did Computer Security Come about?
Many readers may recall the movie "Wargames," starring Matthew Broderick in his portrayal of a
high school student who breaks into the United States Department of Defense (DoD) supercomputer
and inadvertently causes a nuclear war threat. In this movie, Broderick uses his modem to dial into the
DoD computer (called WOPR) and plays games with the artificially intelligent software controlling
all of the nuclear missile silos. The movie was released during the "cold war" between the former
Soviet Union and the United States and was considered a success in its theatrical release in 1983.
The popularity of the movie inspired many individuals and groups to begin implementing some of
the methods that the young protagonist used to crack restricted systems, including what is known as
war dialing — a method of searching phone numbers for analog modem connections in a defined area
code and phone prefix combination.
More than 10 years later, after a four-year, multi-jurisdictional pursuit involving the Federal Bureau
of Investigation (FBI) and the aid of computer professionals across the country, infamous computer
cracker Kevin Mitnick was arrested and charged with 25 counts of computer and access device fraud
that resulted in an estimated US$80 Million in losses of intellectual property and source code from
Nokia, NEC, Sun Microsystems, Novell, Fujitsu, and Motorola. At the time, the FBI considered it the
largest computer-related criminal offense in U.S. history. He was convicted and sentenced to a com-
bined 68 months in prison for his crimes, of which he served 60 months before his parole on January
21, 2000. He was further barred from using computers or doing any computer-related consulting until
2003. Investigators say that Mitnick was an expert in social engineering — using human beings to
gain access to passwords and systems using falsified credentials.
Information security has evolved over the years due to the increasing reliance on public networks
to disclose personal, financial, and other restricted information. There are numerous instances such
as the Mitnick and the Vladimir Levin case (refer to Section 1.1.2 Computer Security Timeline for

2 Chapter 1. Security Overview
more information) that prompted organizations across all industries to rethink the way they handle
information transmission and disclosure. The popularity of the Internet was one of the most important
developments that prompted an intensified effort in data security.
An ever-growing number of people are using their personal computers to gain access to the resources
that the Internet has to offer. From research and information retrieval to electronic mail and commerce
transaction, the Internet has been regarded as one of the most important developments of the 20th
century.
The Internet and its earlier protocols, however, were developed as a trust-based system. That is, the
Internet Protocol was not designed to be secure in itself. There are no approved security standards built
into the TCP/IP communications stack, leaving it open to potentially malicious users and processes
across the network. Modern developments have made Internet communication more secure, but there
are still several incidents that gain national attention and alert us to the fact that nothing is completely
safe.
1.1.2. Computer Security Timeline
Several key events contributed to the birth and rise of computer security. The following lists some of
the most important events that brought attention to computer and information security and its impor-
tance today.
1.1.2.1. The 1960s
•Students at the Massachusetts Institute of Technology (MIT) form the Tech Model Railroad Club
(TMRC) begin exploring and programming the school’s PDP-1 mainframe computer system. The
group eventually use the term "hacker" in the context it is known today.
•The DoD creates the Advanced Research Projects Agency Network (ARPANet), which gains pop-
ularity in research and academic circles as a conduit for the electronic exchange of data and infor-
mation. This paves the way for the creation of the carrier network known today as the Internet.
•Ken Thompson develops the UNIX operating system, widely hailed as the most "hacker-friendly"
OS because of its accessible developer tools and compilers, and its supportive user community.
Around the same time, Dennis Ritchie develops the C programming language, arguably the most
popular hacking language in computer history.
1.1.2.2. The 1970s
•Bolt, Beranek, and Newman, a computing research and development contractor for government
and industry, develops the Telnet protocol, a public extension of the ARPANet. This opens doors
to public use of data networks once restricted to government contractors and academic researchers.
Telnet, though, is also arguably the most insecure protocol for public networks, according to several
security researchers.
•Steve Jobs and Steve Wozniak found Apple Computer and begin marketing the Personal Computer
(PC). The PC is the springboard for several malicious users to learn the craft of cracking systems
remotely using common PC communication hardware such as analog modems and war dialers.
•Jim Ellis and Tom Truscott create USENET, a bulletin-board style system for electronic commu-
nication between disparate users. USENET quickly becomes one the most popular forums for the
exchange of ideas in computing, networking, and, of course, cracking.

Chapter 1. Security Overview 3
1.1.2.3. The 1980s
•IBM develops and markets PCs based on the Intel 8086 microprocessor, a relatively inexpensive
architecture that brought computing from the office to the home. This serves to commodify the PC
as a common and accessible tool that was fairly powerful and easy to use, aiding in the proliferation
of such hardware in the homes and offices of malicious users.
•The Transmission Control Protocol, developed by Vint Cerf, is split into two separate parts. The
Internet Protocol is born from this split, and the combined TCP/IP protocol becomes the standard
for all Internet communication today.
•Based on developments in the area of phreaking, or exploring and hacking the telephone system, the
magazine 2600: The Hacker Quarterly is created and begins discussion on topics such as cracking
computers and computer networks to a broad audience.
•The 414 gang (named after the area code where they lived and hacked from) are raided by author-
ities after a nine-day cracking spree where they break into systems from such top-secret locations
as the Los Alamos National Laboratory, a nuclear weapons research facility.
•The Legion of Doom and the Chaos Computer Club are two pioneering cracker groups that begin
exploiting vulnerabilities in computers and electronic data networks.
•The Computer Fraud and Abuse Act of 1986 was voted into law by congress based on the exploits of
Ian Murphy, also known as Captain Zap, who broke into military computers, stole information from
company merchandise order databases, and used restricted government telephone switchboards to
make phone calls.
•Based on the Computer Fraud and Abuse Act, the courts were able to convict Robert Morris, a
graduate student, for unleashing the Morris Worm to over 6,000 vulnerable computers connected
to the Internet. The next most prominent case ruled under this act was Herbert Zinn, a high-school
dropout who cracked and misused systems belonging to AT&T and the DoD.
•Based on concerns that the Morris Worm ordeal could be replicated, the Computer Emergency
Response Team (CERT) is created to alert computer users of network security issues.
•Clifford Stoll writes The Cuckoo’s Egg, Stoll’s account of investigating crackers who exploit his
system.
1.1.2.4. The 1990s
•ARPANet is decommissioned. Traffic from that network is transferred to the Internet.
•Linus Torvalds develops the Linux kernel for use with the GNU operating system; the widespread
development and adoption of Linux is largely due to the collaboration of users and developers com-
municating via the Internet. Because of its roots in UNIX, Linux is most popular among hackers and
administrators who found it quite useful for building secure alternatives to legacy servers running
proprietary (closed-source) operating systems.
•The graphical Web browser is created and sparks an exponentially higher demand for public Internet
access.
•Vladimir Levin and accomplices illegally transfer US$10 Million in funds to several accounts by
cracking into the CitiBank central database. Levin is arrested by Interpol and almost all of the
money is recovered.
•Possibly the most heralded of all crackers is Kevin Mitnick, who hacked into several corporate sys-
tems, stealing everything from personal information of celebrities to over 20,000 credit card num-
bers and source code for proprietary software. He is arrested and convicted of wire fraud charges
and serves 5 years in prison.

4 Chapter 1. Security Overview
•Kevin Poulsen and an unknown accomplice rig radio station phone systems to win cars and cash
prizes. He is convicted for computer and wire fraud and is sentenced to 5 years in prison.
•The stories of cracking and phreaking become legend, and several prospective crackers convene at
the annual DefCon convention to celebrate cracking and exchange ideas between peers.
•A 19-year-old Israeli student is arrested and convicted for coordinating numerous break-ins to US
government systems during the Persian-Gulf conflict. Military officials call it "the most organized
and systematic attack" on government systems in US history.
•US Attorney General Janet Reno, in response to escalated security breaches in government systems,
establishes the National Infrastructure Protection Center.
•British communications satellites are taken over and ransomed by unknown offenders. The British
government eventually seizes control of the satellites.
1.1.3. Security Today
In February of 2000, a Distributed Denial of Service (DDoS) attack was unleashed on several of the
most heavily-trafficked sites on the Internet. The attack rendered yahoo.com, cnn.com, amazon.com,
fbi.gov, and several other sites completely unreachable to normal users, as it tied up routers for several
hours with large-byte ICMP packet transfers, also called a ping flood. The attack was brought on
by unknown assailants using specially created, widely available programs that scanned vulnerable
network servers, installed client applications called trojans on the servers, and timed an attack with
every infected server flooding the victim sites and rendering them unavailable. Many blame the attack
on fundamental flaws in the way routers and the protocols used are structured to accept all incoming
data, no matter where or for what purpose the packets are sent.
This brings us to the new millennium, a time where an estimated 400 Million people use or have used
the Internet worldwide. At the same time:
•On any given day, there are approximately 225 major incidences of security breach reported to the
CERT Coordination Center at Carnegie Mellon University. [source: http://www.cert.org]
•In 2002, the number of CERT reported incidences jumped to 82,094 from 52,658 in 2001. As of
this writing, the number of incidences reported in only the first quarter of 2003 is 42,586. [source:
http://www.cert.org]
•The worldwide economic impact of the three most dangerous Internet Viruses of the last two years
was estimated at US$13.2 Billion. [source: http://www.newsfactor.com/perl/story/16407.html]
Computer security has become a quantifiable and justifiable expense for all IT budgets. Organizations
that require data integrity and high availability elicit the skills of system administrators, developers,
and engineers to ensure 24x7 reliability of their systems, services, and information. To fall victim to
malicious users, processes, or coordinated attacks is a direct threat to the success of the organization.
Unfortunately, system and network security can be a difficult proposition, requiring an intricate knowl-
edge of how an organization regards, uses, manipulates, and transmits its information. Understanding
the way an organization (and the people that make up the organization) conducts business is paramount
to implementing a proper security plan.
1.1.4. Standardizing Security
Enterprises in every industry rely on regulations and rules that are set by standards making bodies such
as the American Medical Association (AMA) or the Institute of Electrical and Electronics Engineers
(IEEE). The same ideals hold true for information security. Many security consultants and vendors
agree upon the standard security model known as CIA, or Confidentiality, Integrity, and Availability.

Chapter 1. Security Overview 5
This three-tiered model is a generally accepted component to assessing risks of sensitive information
and establishing security policy. The following describes the CIA model in further detail:
•Confidentiality — Sensitive information must be available only to a set of pre-defined individuals.
Unauthorized transmission and usage of information should be restricted. For example, confiden-
tiality of information ensures that a customer’s personal or financial information is not obtained by
an unauthorized individual for malicious purposes such as identity theft or credit fraud.
•Integrity — Information should not be altered in ways that render it incomplete or incorrect. Unau-
thorized users should be restricted from the ability to modify or destroy sensitive information.
•Availability — Information should be accessible to authorized users any time that it is needed.
Availability is a warranty that information can be obtained with an agreed-upon frequency and
timeliness. This is often measured in terms of percentages and agreed to formally in Service Level
Agreements (SLAs) used by network service providers and their enterprise clients.
1.2. Security Controls
Computer security is often divided into three distinct master categories, commonly referred to as
controls:
•Physical
•Technical
•Administrative
These three broad categories define the main objectives of proper security implementation. Within
these controls are sub-categories that further detail the controls and how to implement them.
1.2.1. Physical Controls
The Physical control is the implementation of security measures in a defined structure used to deter
or prevent unauthorized access to sensitive material. Examples of physical controls are:
•Closed-circuit surveillance cameras
•Motion or thermal alarm systems
•Security guards
•Picture IDs
•Locked and dead-bolted steel doors
1.2.2. Technical Controls
The Technical control uses technology as a basis for controlling the access and usage of sensitive data
throughout a physical structure and over a network. Technical controls are far-reaching in scope and
encompass such technologies as:
•Encryption
•Smart cards
•Network authentication
•Access control lists (ACLs)

6 Chapter 1. Security Overview
•File integrity auditing software
1.2.3. Administrative Controls
Administrative controls define the human factors of security. It involves all levels of personnel within
an organization and determines which users have access to what resources and information by such
means as:
•Training and awareness
•Disaster preparedness and recovery plans
•Personnel recruitment and separation strategies
•Personnel registration and accounting
1.3. Conclusion
Now that you have learned about the origins, reasons, and aspects of security, you can determine the
appropriate course of action with regards to Red Hat Enterprise Linux. It is important to know what
factors and conditions make up security in order to plan and implement a proper strategy. With this
information in mind, the process can be formalized and the path becomes clearer as you delve deeper
into the specifics of the security process.

Chapter 2.
Attackers and Vulnerabilities
To plan and implement a good security strategy, first be aware of some of the issues which determined,
motivated attackers exploit to compromise systems. But before detailing these issues, the terminology
used when identifying an attacker must be defined.
2.1. A Quick History of Hackers
The modern meaning of the term hacker has origins dating back to the 1960s and the Massachusetts
Institute of Technology (MIT) Tech Model Railroad Club, which designed train sets of large scale
and intricate detail. Hacker was a name used for club members who discovered a clever trick or
workaround for a problem.
The term hacker has since come to describe everything from computer buffs to gifted programmers.
A common trait among most hackers is a willingness to explore in detail how computer systems and
networks function with little or no outside motivation. Open source software developers often consider
themselves and their colleagues to be hackers, and use the word as a term of respect.
Typically, hackers follow a form of the hacker ethic which dictates that the quest for information and
expertise is essential, and that sharing this knowledge is the hackers duty to the community. During
this quest for knowledge, some hackers enjoy the academic challenges of circumventing security
controls on computer systems. For this reason, the press often uses the term hacker to describe those
who illicitly access systems and networks with unscrupulous, malicious, or criminal intent. The more
accurate term for this type of computer hacker is cracker — a term created by hackers in the mid-
1980s to differentiate the two communities.
2.1.1. Shades of Grey
Within the community of individuals who find and exploit vulnerabilities in systems and networks are
several distinct groups. These groups are often described by the shade of hat that they "wear" when
performing their security investigations and this shade is indicative of their intent.
The white hat hacker is one who tests networks and systems to examine their performance and de-
termine how vulnerable they are to intrusion. Usually, white hat hackers crack their own systems or
the systems of a client who has specifically employed them for the purposes of security auditing.
Academic researchers and professional security consultants are two examples of white hat hackers.
Ablack hat hacker is synonymous with a cracker. In general, crackers are less focused on program-
ming and the academic side of breaking into systems. They often rely on available cracking programs
and exploit well known vulnerabilities in systems to uncover sensitive information for personal gain
or to inflict damage on the target system or network.
The grey hat hacker, on the other hand, has the skills and intent of a white hat hacker in most situations
but uses his knowledge for less than noble purposes on occasion. A grey hat hacker can be thought of
as a white hat hacker who wears a black hat at times to accomplish his own agenda.
Grey hat hackers typically subscribe to another form of the hacker ethic, which says it is acceptable to
break into systems as long as the hacker does not commit theft or breach confidentiality. Some would
argue, however that the act of breaking into a system is in itself unethical.
Regardless of the intent of the intruder, it is important to know the weaknesses a cracker may likely
attempt to exploit. The remainder of the chapter focuses on these issues.

8 Chapter 2. Attackers and Vulnerabilities
2.2. Threats to Network Security
Bad practices when configuring the following aspects of a network can increase the risk of attack.
2.2.1. Insecure Architectures
A misconfigured network is a primary entry point for unauthorized users. Leaving a trust-based, open
local network vulnerable to the highly-insecure Internet is much like leaving a door ajar in a crime-
ridden neighborhood — nothing may happen for an arbitrary amount of time, but eventually someone
will exploit the opportunity.
2.2.1.1. Broadcast Networks
System administrators often fail to realize the importance of networking hardware in their security
schemes. Simple hardware such as hubs and routers rely on the broadcast or non-switched principle;
that is, whenever a node transmits data across the network to a recipient node, the hub or router sends
a broadcast of the data packets until the recipient node receives and processes the data. This method
is the most vulnerable to address resolution protocol (arp) or media access control (MAC) address
spoofing by both outside intruders and unauthorized users on local nodes.
2.2.1.2. Centralized Servers
Another potential networking pitfall is the use of centralized computing. A common cost-cutting
measure for many businesses is to consolidate all services to a single powerful machine. This can be
convenient as it is easier to manage and costs considerably less than multiple-server configurations.
However, a centralized server introduces a single point of failure on the network. If the central server
is compromised, it may render the network completely useless or worse, prone to data manipulation or
theft. In these situations a central server becomes an open door, allowing access to the entire network.
2.3. Threats to Server Security
Server security is as important as network security because servers often hold a great deal of an
organization’s vital information. If a server is compromised, all of its contents may become available
for the cracker to steal or manipulate at will. The following sections detail some of the main issues.
2.3.1. Unused Services and Open Ports
A full installation of Red Hat Enterprise Linux contains up to 1200 application and library packages.
However, most server administrators do not opt to install every single package in the distribution,
preferring instead to install a base installation of packages, including several server applications.
A common occurrence among system administrators is to install the operating system without paying
attention to what programs are actually being installed. This can be problematic because unneeded
services may be installed, configured with the default settings, and possibly turned on. This can cause
unwanted services, such as Telnet, DHCP, or DNS, to run on a server or workstation without the
administrator realizing it, which in turn can cause unwanted traffic to the server, or even, a potential
pathway into the system for crackers. Refer To Chapter 5 Server Security for information on closing
ports and disabling unused services.