Today, only minutes pass between plugging into the Internet and being attacked by some other machine - and that's only the background noise level of non-targeted attacks. There was a time when a computer could tick away year after year without coming under attack. For examples of Internet background radiation studies, see [CAIDA, 2003], [Cymru, 2004] or [IMS, 2004].

With this book we summarize experiences in post-mortem intrusion analysis that we accumulated over a decade of time. During this episode the Internet grew explosively, from less than a hundred thousand connected hosts to more than a hundred million [ISC, 2004]. This increase in the number of connected hosts led to an even more dramatic - if less surprising - increase in the frequency of computer and network intrusions. As the network changed character and scope, so did the character and scope of the intrusions that we were faced with. We're pleased to share some of the learning opportunities with the reader.

In that same decade, however, little if anything changed in the way that computer systems handle information. In fact, we feel that it is safe to claim that computer systems haven't changed fundamentally in the last 35 years - the entire lifetime of the Internet and of many operating systems that are in use today, including Linux, Windows and many others. Although our observations are derived from today's systems, we optimistically expect that at least some of our insights will remain valid for another decade.

What you can expect to learn from this book

The premise of the book is that forensic information can be found everywhere you look. With this guiding principle in mind we develop tools to collect information from obvious and not so obvious sources, we walk through analyses of real intrusions in detail, and we discuss the limitations of our approach.

Although we illustrate our approach with specific forensic tools in specific system environments, we do not provide cookbooks for how to use those tools, nor do we provide checklists for step-by-step investigation. Instead, we provide a background on how information persists, how information about past events may be recovered, and how trustworthiness of that information may be affected by deliberate or accidental processes.

In our case studies and examples we deviate from traditional computer forensics and head towards the study of system dynamics. Volatility and persistence of file systems and memory are pervasive topics in our book. And while the majority of our examples are from Solaris, FreeBSD and Linux systems, Microsoft's Windows shows up on occasion as well. Our emphasis is on the underlying principles that these systems have in common: we look for inherent properties of computer systems, rather than accidental differences or superficial features.

Our global themes are problem solving, analysis and discovery, with a focus on reconstruction of past events. This may help you to discover why events transpired, but that is generally outside the scope of this work. Knowing what happened will leave you better prepared the next time something bad is about to happen, even when it is not sufficient to prevent future problems. We should note up-front, however, that we do not cover the detection or prevention of intrusions. We do show that traces from one intrusion can lead to the discovery of other intrusions, and we point out how forensic information may be affected by system protection mechanisms, and by their failures.

Intended audience

The target audience of the book is anyone who wants to deepen their understanding of how computer systems work, as well as anyone who is likely to become involved with the technical aspects of computer intrusion or system analysis. These are not only system administrators, incident responders, other computer security professionals, or forensic analysts, but also anyone who is concerned about the impact of computer forensics on privacy.

While we have worked hard to make the material accessible to non-expert readers, we definitely do not target the novice computer user. As a minimal requirement, we assume strong familiarity with the basic concepts of UNIX or Windows file systems, networking, and processes.

Organization of this book

The book has three parts: we present foundations first, proceed with analysis of processes, systems and files, and end the book with discovery. We do not expect you to read everything in the order presented. Nevertheless, we suggest that you start with the first chapter, as it introduces all the major themes that return throughout the book.

In Part 1, "Basic Concepts", we introduce general high-level concepts, as well as basic techniques that we rely on in later chapters.

In Part 2, "Exploring System Abstractions", we explore the abstractions of file systems, processes, and operating systems. The focus of these chapters is on analysis: making sense of information found on a computer system and judging the trustworthiness of our findings.

In Part 3, "Beyond the Abstractions", we look beyond the constraints of the file, process and operating system abstractions. The focus of this part is on discovery, as we study the effects of system architecture on the decay of information.

The appendices present background material: Appendix A is an introduction to the Coroner's Toolkit and related software, and Appendix B presents our current insights with respect to the order of volatility and its ramifications when capturing forensic information from a computer system.

Conventions used in this book

In the examples we use constant width font for program code, command names, and command input/output. User input is shown in bold constant width font. We use $ as the shell command prompt for unprivileged users, and reserve # for super-user shells. Capitalized names, such as Argus, are used when we write about a system instead of individual commands.

Whenever we write UNIX, we implicitly refer to Solaris, FreeBSD, and Linux. In some examples we include the operating system name in the command prompt. For example, we use solaris$ to indicate that an example is specific to Solaris systems.

As hinted at earlier, many examples in this book are taken from real-life intrusions. In order to protect privacy we anonymize information about systems that are not our own. For example, we replace real network addresses by private network addresses such as or, and replace hostnames or user names. Where appropriate we even replace the time and time zone.


The examples in this book feature several small programs that were written for the purpose of discovery and analysis. Often we were unable to include the entire code listing because the additional detail would only detract from the purpose of the book. The complete source code for these and other programs is made available online at:

On the same websites you will also find bonus material, such as case studies that were not included in the book and pointers to other resources.


We owe a great deal of gratitude to Karen Gettman, Brian Kernighan, and the rest of Addison-Wesley for their patience and support over the many years that this book has been under construction.

While we take full responsibility for any mistakes, this book would not be what it is without our review team. In particular we would like to thank (in alphabetical order): Aleph1, Brad Powell, Brian Carrier, Douglas Schales, Elizabeth Zwicky, Eoghan Casey, Fred Cohen, Gary McGraw, Muffy Barkocy, Rik Farrow, and Steve Romig. Ben Pfaff and Jim Chow helped with a chapter, and Dalya Sachs provided valuable assistance with editing an early version of the text. Tsutomu Shimumura inspired us to do things that we thought were beyond our skills. Wietse would like to thank the FIRST community for the opportunity to use them as a sounding board for many of the ideas that were developed for this book. And contrary to current practice, the manuscript was produced as HTML draft with the vi text editor plus a host of little custom scripts and standard UNIX tools that helped us finish the book.

Dan Farmer
Wietse Venema


[CAIDA, 2003] The CAIDA network telescope project.

[Cymru, 2004] Team Cymru Darknet project.

[IMS, 2004] The University of Michigan Internet Motion Sensor project.

[ISC, 2004] Internet Systems Consortium, ISC Domain Survey: Number of Internet Hosts.