workshop 2 revised

44
Workshops on Born-Digital Materials Workflow Peter Chan, Digital Archivist Oct. 20, 2011

Post on 19-Oct-2014

338 views

Category:

Technology


2 download

DESCRIPTION

 

TRANSCRIPT

Page 1: Workshop 2 revised

Workshops on

Born-Digital Materials Workflow

Peter Chan, Digital Archivist

Oct. 20, 2011

Page 2: Workshop 2 revised

Week 2 Agenda

• Accessioning

– virus check;

–disk imaging;

– create FTK case;

– collection summary

–AT accession record

Page 3: Workshop 2 revised

Virus Check

• Quarantine for 30 days (count from the day the media arrive at Stanford)

• Run Sophos

• Remove virus, if any, before creating disk/logical image (unless you are capturing the disk for a researcher in computer virus!)

Page 4: Workshop 2 revised

Disk / Forensic image

• A complete bit-by-bit copy of a storage medium or device, such as a hard drive, SSD (solid state drive), tape drive, floppy disk, CD/DVD/BD, or flash memory device.

• The image can be stored in one or more files.

• Deleted files, if any, may be copied in this process.

Page 5: Workshop 2 revised

Logical image

• A copy of the files in the directory(folder) / directories(folders) specified in the copy process.

• The full path of each file is recorded and the files are embedded in

one or more files in AD1 format.

• Since deleted files and unpartitioned space are not represented in a directory, they are not copied in the process.

• The host operating system has to recognize the target directory (folder) for the operation. (You cannot perform a logical copy of an Apple disk using FTK Imager under Windows perform).

Page 6: Workshop 2 revised
Page 7: Workshop 2 revised
Page 8: Workshop 2 revised

Disk Partition

• Disk partitioning is the act of dividing a physical hard disk drive into multiple logical storage units.

• The logical units can have different file systems so that we can set the same physical machine as a Window based PC and/or a Linux based PC and/or a Mac PC.

Page 9: Workshop 2 revised

GParted

Page 10: Workshop 2 revised

File System

• Microsoft: FAT12 (File Allocation Table), FAT16, FAT32, exFAT (FAT64), NTFS (New Technology File System)

• Apple: Apple ProDOS, HFS (Hierarchical File System), HFS+

• CPM file system

• Linux: ext (extended filesystem), ext2, ext3, ext4

• Optical Discs: ISO 9660, UDF (Universal Disk Format)

Page 11: Workshop 2 revised

Computer Management

Page 12: Workshop 2 revised
Page 13: Workshop 2 revised

Capture 5.25 Floppy Diskette

Page 15: Workshop 2 revised

Hard Disk Interface

• SCSI

• IDE

• Firewire 1394

• SATA

• USB

Page 16: Workshop 2 revised

Internal Write Blocker

Page 17: Workshop 2 revised

Image Log Spreadsheet

• Use the following columns – Box# – CM# – Media Details (3.5, 5.25, single/double sided,

single/double/high density, etc.) – Image Result (successful / unreadable) – Note (bad sector, etc.) – Manufacturer – Earliest modification/creation year of files – Folder title (if removed from collection folder)

• Use “Call No. Imaging Log” as file name

Page 18: Workshop 2 revised

FTK Imager

Page 19: Workshop 2 revised

Create Disk Image

• Physical Drive – hard / flash memory drive

• Logical Drive – floppy / CD / DVD drive

• Contents of a Folder – logical image

• Fernico Device – a device which backs up forensic data from network locations or from locally attached hard drives, automatically spanning the content over a series of discs.

Page 20: Workshop 2 revised

Fernico Device

Page 21: Workshop 2 revised

Create Image

Tick “Verify images after they are created” Tick “Create directory listings of all files in the image after they are created” if you need one.

Page 22: Workshop 2 revised

Image Type

Page 23: Workshop 2 revised

Image Type

• Raw (dd) – commonly used disk image format created by the UNIX command dd

• SMART – proprietary disk image format created by ASR Data.

• E01 – proprietary disk image format created by EnCase.

• AFF – an open source disk image format, allow encryption of disk image

• AD1 - proprietary logical disk image format created by AccessData.

Page 24: Workshop 2 revised

Evidence Item Information

Page 25: Workshop 2 revised

Evidence Item Information

• Use “Raw (dd)” as image type

• Use call no. as “Case Number”

• Use CMxxx as “Evidence Number”

• Put your name as “Examiner”

• Use the following in the “Notes” field:

– 3.5 inch floppy disk; 5.25 inch floppy disk; Zip disk;

– External hard disk; Internal hard disk;

– Optical Disk

Page 26: Workshop 2 revised

Select Image Destination

Page 27: Workshop 2 revised

Select Image Destination

• Store all files under “Disk Image” folder in Desktop

• Use “Case No.” + CMxxx as Image Filename for disk image

• Default Image Fragment Size = 1500 MB

• To save images segments that can be burned to a CD, specify 650 MB.

• To save image segments that can be burned to a DVD, specify 4000 MB.

• Selecting 0 (zero) produces the largest file, with no compression.

Page 28: Workshop 2 revised

Storage Locations for Files

Page 29: Workshop 2 revised
Page 30: Workshop 2 revised

Create New Case in AccessData FTK

• Copy image files to network before creating new case.

• Use call no. as Case Name

• Store case in Drive:\FTK\FTK Case

• Field Mode: bypasses file signature analysis and detailed options in order to vastly speed the processing. (for people to analysis the case in the field)

Page 31: Workshop 2 revised
Page 32: Workshop 2 revised

Evidence Processing

• Detailed Options

– Evidence Processing - "√" Flag Duplicate Files; "√" MD-5 Hash, SHA-1 Hash; "√" Expand Compound Files; under “Expansion Options” "√" BZIP2, GZIP, RAR, TAR, ZIP; "√“ dtSearch Text Index; "√“ Create Thumbnails for Graphics (save as default)

– Evidence Refinement (Advanced) - remove "√" Include File Slack, Include Free Space (save as default)

Page 33: Workshop 2 revised

Evidence Processing

• KFF - Using a database of hashes from known files, this option flags insignificant files as ignorable files and flags known illicit or dangerous files as alert files, alerting the examiner to their presence in the case.

• Fuzzy hashing - A tool which provides the ability to compare two distinctly different files and determine a fundamental level of similarity. This similarity is expressed as score from 0-100. The higher the score reported the more similar the two pieces of data. A score of 100 would indicate that the files are close to identical. Alternatively a score of 0 would indicate no meaningful common sequence of data between the two files.

Page 34: Workshop 2 revised

Evidence – Add/Remove

Page 35: Workshop 2 revised

Use “All Images of a Directory” at the Network Forensic Lab Folder

35

Page 36: Workshop 2 revised

Images Files Identified

36

Page 37: Workshop 2 revised

Choose Appropriate Time Zone

37

Page 38: Workshop 2 revised

Processing Status of Each Image File

38

Page 39: Workshop 2 revised

File - Report

Page 40: Workshop 2 revised

Report Output

• Report Folder – Drive:\FTK\FTK Report\Call#

• Formats – PDF

• Don’t check “Use object identification number for filename” and “Append extension to filename if bad/absent”

• Rename “Report” to Call# FTK Collection Summary

• Copy the report to \\sul-wallaby\Special Collections\Manuscripts\Collections\Call#\

Page 41: Workshop 2 revised

AT Accession Record Alternate Extent

Page 42: Workshop 2 revised

AT Accession Record Alternate Extent

Page 43: Workshop 2 revised

AT Accession Record External Documents

Page 44: Workshop 2 revised

External Documents Location

• \\sul-wallaby\Special Collections\Manuscripts\Collections\M1437 Gould

• M1437 FTK Accession Report

• M1437 Computer Media Imaging Log