File System Forensic Analysis by Brian Carrier

BUY IT NEW

  • $59.99 List price
    $44.99 Online price
    $40.49 Member price
    (Save 32%)
    Limited Time Offer! Everyone receives the Member Price on books.
    See Details
  • skip to cart
  • Add To List uiAction=GetAllLists&page=List&pageType=list&ean=9780321268174&productCode=BK&maxCount=100&threshold=3

GET FREE SHIPPING ON ORDERS OF $25 OR MORE

DELIVERY & GIFT DETAILS:

Usually ships within 24 hours

Delivery Time and Shipping Rates

Eligible for gift wrap & gift message.

BUY IT USED

14 copies from $32.95

See All Available

Pick Me Up

Reserve it at BN.com & pick it up in 60 minutes at your local store.

Enter a zip code

(Paperback)

  • Pub. Date: March 2005
  • 600pp
  • Sales Rank: 54,270
    Buy it Used: 14 copies from $32.95 See All Available

    Customers who bought this also bought

     
    • Overview
    • Editorial Reviews
    • Customer Reviews
    • Features

    Product Details

    • Pub. Date: March 2005
    • Publisher: Addison-Wesley
    • Format: Paperback, 600pp
    • Sales Rank: 54,270

    Synopsis

    This book explains how to analyze data structures that partition and assemble storage volumes as well as the data structures in a volume that are used to store and retrieve files. After examining PC-based and server-based partitions, the author describes file allocation table (FAT), NTFS, and Unix file systems, and illustrates the manual analysis of example disk images. The information will help security experts identify where a file existed on disk and the various data structures that need to be in sync to view it. Annotation ©2004 Book News, Inc., Portland, OR

    More Reviews and Recommendations

    Biography

    Brian Carrier has authored several leading computer forensic tools, including The Sleuth Kit (formerly The @stake Sleuth Kit) and the Autopsy Forensic Browser. He has authored several peer-reviewed conference and journal papers and has created publicly available testing images for forensic tools. Currently pursuing a Ph.D. in Computer Science and Digital Forensics at Purdue University, he is also a research assistant at the Center for Education and Research in Information Assurance and Security (CERIAS) there. He formerly served as a research scientist at @stake and as the lead for the @stake Response Team and Digital Forensic Labs. Carrier has taught forensics, incident response, and file systems at SANS, FIRST, the @stake Academy, and SEARCH.

    Brian Carrier's contains book updates and up-to-date URLs from the book's references.

    © Copyright Pearson Education. All rights reserved.

    Customer Reviews

    • Reader Rating:
    • Ratings: 2Reviews: 2

    File System Forensic Analysisby Anonymous

    Reader Rating:
    See Detailed Ratings

    May 05, 2005: Brian Carrier has written a solid book that should be on the reference shelf of anyone in the Digital Forensics field that conducts analysis of file systems. The book is well organized into three parts, each with multiple chapters. The first part discusses the foundations necessary to understand digital evidence, computer functions and acquiring data for analysis. This part is intentionally at a higher level, yet still provides the necessary foundations for the subsequent parts. A good explanation of host protected area (HPA) and device configuration overlays (DCO) is included, as well as methods by which one can test for such areas on volumes. The second part discusses volume analysis. Brian takes this topic and divides it into four chapters addressing basic volumes, personal computer volumes, server volumes and finally multiple disk volumes. He provides detailed information on a variety of common partition types, even including both SPARC and i386 partition information for Sun Solaris. Finally the third part discusses file system analysis, and the last 10 chapters are dedicated to covering general information, and then detailed descriptions of concepts, analysis and data structures for FAT, NTFS, Ext2, Ext3, UFS1 and UFS2 file systems. The detailed information provided well-documented explanations and included analysis scenarios. For instance, in his discussion of NTFS analysis, an image of a damaged disk is evaluated, and he provides meaningful explanations of reconstructing the damaged tables to allow analysis of the data. He provides many such examples throughout. An additional positive attribute to this work is the thorough bibliography placed after each chapter, which quickly provides the reader with other data sources, should they be needed. Overall, this is an excellent reference for anyone that must conduct analysis of file systems for investigative purposes. He provides clear information that is valuable, regardless of what tools an examiner may use to conduct analysis. This is definitely worth having on your bookshelf.

    File System Forensic Analysisby Anonymous

    Reader Rating:
    See Detailed Ratings

    April 11, 2005: Carrier's book is rare in its comprehensive coverage of how computers actually store data on disks. Other books might give lesser amounts of detail. And then, a particular book usually describes only how a given operating system does its storage. Carrier goes further on both counts. He describes how Microsoft, Apple, BSD, linux and Sun do their disks. Though Microsoft's FAT and NTFS get the most extensive coverage, due to the prevalence of disks using these formats. Hierarchies of disks are also covered, like the RAID levels. Plus logical volumes of disks, which span actual sets of disks. The cutting edge topic is forensics. It is to this end that he explains throughout the book how knowing certain details might aid you in recovering data. Consider his discussion of slack space as one example. He shows how if an operating system does not overwrite this, then a post mortem can reveal fragments of an earlier, supposedly deleted file. (Gosh!) Similar to how an operating system might delete a file by erasing the pointer to the file, but not the actual contents. I'm simplifying here. But perhaps you can see the utility in knowing exactly how files are kept and removed.