Network intrusion detection : an analyst's handbook / Stephen Northcutt, Judy Novak and Donald McLachlan.

By: Northcutt, Stephen .

Contributor(s): Novak, Judy | McLachlan, Donald .

Material type: materialTypeLabel

BookPublisher: Indianapolis : New Riders, 2001Description: xxxii, 430 p. : ill. ; 23 cm.ISBN: 0735710082.Subject(s): Computer networks -- Security measures

| Internet -- Security measures

| Computer security

DDC classification: 005.8

Contents:

IP Concepts -- Introduction to TCPdump and Transmission Control Protocol (TCP) -- Fragmentation -- ICMP -- Stimulus and Response -- DNS -- Mitnick Attack -- Introduction to Filters and Signatures -- Architectural Issues -- Interoperability and Correlation -- Network-Based Intrusion-Detection Solutions -- Future Directions -- Exploits and Scans to Apply Exploits -- Denial of Service -- Detection of Intelligence Gathering -- The Trouble with RPCs -- Filters to Detect, Filters to Protect -- System Compromise -- The Hunt for Timex -- Organizational Issues -- Automated and Manual Response -- Business Case for Intrusion Detection.

Holdings
Item type	Current library	Call number	Copy number	Status	Date due	Barcode	Item holds
General Lending	MTU Bishopstown Library Lending	005.8 (Browse shelf(Opens below))	1	Available		00083108

Total holds: 0

Enhanced descriptions from Syndetics:

A training aid and reference for intrusion detection analysts. The authors have been through the trenches and give you access to unusual and unique data.

Includes index.

Table of contents provided by Syndetics

Introduction (p. xviii)
1 IP Concepts (p. 1)
The TCP/IP Internet Model (p. 2)
Packaging (Beyond Paper or Plastic) (p. 4)
Addresses (p. 9)
Service Ports (p. 12)
IP Protocols (p. 13)
Domain Name System (p. 15)
Routing: How You Get There From Here (p. 16)
Summary (p. 18)
2 Introduction to TCP dump and Transmission Control Protocol (TCP) (p. 19)
TCP dump (p. 20)
Introduction to TCP (p. 25)
TCP Gone Awry (p. 31)
Summary (p. 34)
3 Fragmentation (p. 35)
Theory of Fragmentation (p. 36)
Malicious Fragmentation (p. 44)
Summary (p. 46)
4 ICMP (p. 49)
ICMP Theory (p. 49)
Mapping Techniques (p. 52)
Normal ICMP Activity (p. 57)
Malicious ICMP Activity (p. 60)
To Block or Not To Block (p. 66)
Summary (p. 67)
Hardware-Based ID (p. 214)
Defense in Depth (p. 214)
Program-Based ID (p. 215)
Smart Auditors (p. 216)
Summary (p. 216)
13 Exploits and Scans to Apply Exploits (p. 217)
False Positives (p. 217)
IMAP Exploits (p. 225)
Scans to Apply Exploits (p. 228)
Single Exploit, Portmap (p. 233)
Summary (p. 240)
14 Denial of Service (p. 241)
Brute-Force Denial-of-Service Traces (p. 242)
Elegant Kills (p. 246)
nmap 2.53 (p. 250)
Distributed Denial-of-Service Attacks (p. 251)
Summary (p. 254)
15 Detection of Intelligence Gathering (p. 255)
Network and Host Mapping (p. 256)
NetBIOS-Specific Traces (p. 265)
Stealth Attacks (p. 267)
Measuring Response Time (p. 272)
Viruses as Information Gatherers (p. 274)
Summary (p. 278)
16 The Trouble with RPCs (p. 279)
portmapper (p. 279)
dump Is a Core Component of rpcinfo (p. 282)
Attacks That Directly Access an RPC Service (p. 284)
The Big Three (p. 287)
Analysis Under Fire (p. 287)
Oh nmap! (p. 291)
Summary (p. 294)
17 Filters to Detect, Filters to Protect (p. 295)
The Mechanics of Writing TCPdump Filters (p. 296)
Bit Masking (p. 297)
TCPdump IP Filters (p. 300)
TCPdump UDP Filters (p. 302)
TCPdump TCP Filters (p. 304)
Summary (p. 308)
18 System Compromise (p. 309)
Christmas Eve 1998 (p. 310)
Where Attackers Shop (p. 323)
Communications Network (p. 325)
Anonymity (p. 328)
Summary (p. 328)
19 The Hunt for Timex (p. 329)
The Traces (p. 329)
The Hunt Begins (p. 331)
Y2K (p. 339)
Sources Found (p. 343)
Miscellaneous Findings (p. 343)
Summary Checklist (p. 347)
Epilogue and Purpose (p. 347)
Summary (p. 348)
20 Organizational Issues (p. 349)
Organizational Security Model (p. 349)
Defining Risk (p. 353)
Risk (p. 354)
Defining the Threat (p. 359)
Risk Management Is Dollar Driven (p. 363)
How Risky Is a Risk? (p. 363)
Summary (p. 365)
21 Automated and Manual Response (p. 367)
Automated Response (p. 368)
Honeypot (p. 373)
Manual Response (p. 375)
Summary (p. 383)
22 Business Case for Intrusion Detection (p. 385)
Part 1 Management Issues (p. 387)
Part 2 Threats and Vulnerabilities (p. 391)
Part 3 Tradeoffs and Recommended Solution (p. 395)
Repeat the Executive Summary (p. 400)
Summary (p. 400)
Index (p. 403)

Excerpt provided by Syndetics

Introduction Our goal in writing Network Intrusion Detection, Third Edition has been toempower you as an analyst. We believe that if you read this book cover to cover,and put the material into practice as you go, you will be ready to enter theworld of intrusion analysis. Many people have read our books, or attended ourlive class offered by SANS, and the lights have gone on; then, they are off tothe races. We will cover the technical material, the workings of TCP/IP, andalso make every effort to help you understand how an analyst thinks throughdozens of examples. Network Intrusion Detection, Third Edition is offered in five parts. Part I,"TCP/IP," begins with Chapter 1, ranging from an introduction to thefundamental concepts of the Internet protocol to a discussion of RemoteProcedure Calls (RPCs). We realize that it has become stylish to begin a booksaying a few words about TCP/IP, but the system Judy and I have developed hasnot only taught more people IP but a lot more about IP as well--more thanany other system ever developed. We call it "real TCP" because thematerial is based on how packets actually perform on the network, not theory.Even if you are familiar with IP, give the first part of the book a look. We areconfident you will be pleasantly surprised. Perhaps the most important chapterin Part I is Chapter 5, "Stimulus and Response." Whenever you look ata network trace, the first thing you need to determine is if it is a stimulus ora response. This helps you to properly analyze the traffic. Please take the timeto make sure you master this material; it will prevent analysis errors as youmove forward. Tip Whenever you look at a network trace, thefirst thing you need to determine is if it is a stimulus or a response. The book continues in Part II, "Traffic Analysis" with a discussionof traffic analysis. By this, we mean analyzing the network traffic byconsideration of the header fields of the IP and higher protocol fields.Although ASCII and hex signatures are a critical part of intrusion detection,they are only tools in the analyst's tool belt. Also in Part II, we beginto show you the importance of each field, how they are rich treasures tounderstanding. Every field has meaning, and fields provide information bothabout the sender of the packet and its intended purpose. As this part of thebook comes to a close, we tell you stories from the perspective of an analystseeing network patterns for the first time. The goal is to help you prepare forthe day when you will face an unknown pattern. Although there are times a network pattern is so obvious it almost screamsits message, more often you have to search for events of interest. Sometimes,you can do this with a well-known signature, but equally often, you must searchfor it. Whenever attackers write software for denial of service, or exploits,the software tends to leave a signature that is the result of crafting thepacket. This is similar to the way that a bullet bears the marks of the barrelof the gun that fired it, and experts can positively identify the gun by thebullet. In Part III of the book, "Filters/Rules for NetworkMonitoring" we build the skills to examine any field in the packet and theknowledge to determine what is normal and what is anomalous. In this section, wepractice these skills both with TCPdump and also Snort. In Part IV, we consider the larger framework of intrusion detection. Wediscuss where you should place sensors, what a console needs to support for dataanalysis, and automated and manual response issues to intrusion detection. Inaddition, this section helps arm the analyst with information about how theintrusion detection capability fits in with the business model of theorganization. Finally, this book provides three appendixes that reference common signaturesof well-known reconnaissance, denial of service, and exploit scans. We believeyou will find this to be no fluff, packed with data from the first to the lastpage. Network Intrusion Detection, Third Edition has not been developed byprofessional technical writers. Judy and I have been working as analysts since1996 and have faced a number of new patterns. We are thankful for thisopportunity to share our experiences and insights with you and hope this bookwill be of service to you in your journey as an intrusion analyst. (c) Copyright Pearson Education. All rights reserved. Excerpted from Network Intrusion Detection: An Analyst's Handbook by Stephen Northcutt, Judy Novak All rights reserved by the original copyright owners. Excerpts are provided for display purposes only and may not be reproduced, reprinted or distributed without the written permission of the publisher.

Author notes provided by Syndetics

Stephen Northcutt is a graduate of Mary Washington College. He is the author of Incident Handling: Step-by-Step and Intrusion Detection: Shadow Style, both published by the SANS Institute. He was the original developer of the Shadow intrusion detection system and served as the leader of the Department of Defense's Shadow Intrusion Detection Team for two years. Formerly the Director of the U.S. Navy's Information System Security Office at the Naval Security Warfare Center, he is currently the Chief Information Warfare Officer for the U.S. Ballistic Missile Defense Organization. Stephen is a featured lecturer and co-chair of the SANS Conference and is the program chair of the first Intrustion Detection Conference.