23.12.2012 Views

Digital Forensics in Small Devices: RFID Tag Investigation

Digital Forensics in Small Devices: RFID Tag Investigation

Digital Forensics in Small Devices: RFID Tag Investigation

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

server and use IR tools to collect the artifacts. But, these connections depend on the<br />

“system and database libraries, and dynamic management objects (DMOs) on the<br />

SQL Server” (Fowler, 2009, p. 57).<br />

The dead acquisition method is the way <strong>in</strong> which the power connection of the<br />

SQL Server is forcefully shutdown. However, the potential evidence from the volatile<br />

data will be lost when the server‟s power is down even though the analysis results can<br />

easily be repeated for later verification. But, the actual SQL data alterations have<br />

normally happened <strong>in</strong> the memory and are recorded <strong>in</strong> the database transaction log.<br />

Likewise, on-disk data pages are only updated “dur<strong>in</strong>g the start-up and shutdown of<br />

the SQL Server service”, and when “the regularly scheduled checkpo<strong>in</strong>t process runs<br />

which then flushes the modified data pages to disk” (Fowler, 2009, pp. 58-59). Thus,<br />

the author does not recommend dead acquisition as the SQL Server utilizes as much<br />

system memory as possible.<br />

In hybrid acquisition, the live acquisition of volatile data from a target system<br />

is <strong>in</strong>itially performed and then followed by dead acquisition. Hence, the hybrid<br />

acquisition allows the forensic <strong>in</strong>vestigator to manage the relative proportions of live<br />

and dead acquisitions accord<strong>in</strong>g to his or her needs (Fowler, 2009).<br />

Figure 3.4).<br />

F<strong>in</strong>ally, the author expla<strong>in</strong>s a methodology of SQL Server forensics (see<br />

<strong>Investigation</strong><br />

Preparedness<br />

Incident<br />

Verification<br />

Figure 3.4: SQL Server forensic methodology (Fowler, 2009, p. 60)<br />

Despite the fact that there are many different forensic methodologies which can be<br />

found <strong>in</strong> literature, every phase of any methodology must be performed correctly by<br />

the forensic <strong>in</strong>vestigator. Otherwise, the results of the <strong>in</strong>vestigation as evidence may<br />

not be possibly accepted by the court (Fowler, 2009). For <strong>in</strong>stance, the <strong>in</strong>tegrity of the<br />

digital evidence must be ma<strong>in</strong>ta<strong>in</strong>ed by produc<strong>in</strong>g digital hashes on all the acquired<br />

artifacts dur<strong>in</strong>g the <strong>in</strong>vestigation.<br />

For <strong>Investigation</strong> Preparedness (IP), the first phase of the SQL Server<br />

forensic methodology, the author mentions that the IR toolkit must be created, a<br />

45<br />

Artifact<br />

Collection<br />

Artifact<br />

Analysis

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!