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

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

e <strong>in</strong>vestigated for evidence of the theft. Hence, the forensic analysis of the SQL<br />

Server related to previous works (Sections 3.1.3 and 3.1.4) should be revised. As<br />

stated <strong>in</strong> Section 3.1.3, Fowler (2009) discussed the differences among traditional<br />

forensics and the SQL Server forensics by giv<strong>in</strong>g two fictitious scenarios <strong>in</strong> which the<br />

attack of the first scenario was orig<strong>in</strong>ated via the Web and the latter was caused by an<br />

unhappy employee. Then, Fowler (2009) expla<strong>in</strong>ed the ways <strong>in</strong> which the<br />

<strong>in</strong>vestigation should be performed on the SQL Server related <strong>in</strong>cidents <strong>in</strong> a<br />

forensically sound manner. In addition, the ways <strong>in</strong> which the phases of forensic<br />

methodology performed <strong>in</strong> the SQL Server forensics could be utilized to identify a<br />

database security breach. On the other hand <strong>in</strong> Section 3.1.4, the research conducted<br />

by Fowler (2007) described how to perform a forensic analysis of a Microsoft SQL<br />

Server 2005 by us<strong>in</strong>g a real world security <strong>in</strong>cident scenario. The values of the<br />

articles (Fowler, 2007; Fowler 2009) were to highlight malicious attacks on SQL<br />

Servers could come from not only the Web, but also from a malicious employee. In<br />

addition, it is important to note that a live forensic analysis has to be performed on a<br />

SQL Server <strong>in</strong> order to acquire all volatile and non-volatile SQL Server artefacts (see<br />

Appendix 1). With the exception of the ways <strong>in</strong> which a forensics <strong>in</strong>vestigation of a<br />

SQL Server <strong>in</strong>cident is conducted, none of the papers written by Fowler (2007, 2009)<br />

were related to the forensic <strong>in</strong>vestigation of a compromised <strong>RFID</strong> BS as a whole and<br />

the malicious attack compromised the SQL Server from the web. However, the idea<br />

of creat<strong>in</strong>g IRCD (Incident Response CD) and the application of SQL forensic<br />

methodology would be replicated for develop<strong>in</strong>g a customized<br />

Helix_<strong>RFID</strong>_IncidentResponse (Helix_<strong>RFID</strong>_IR) toolkit (see Appendix 2) and<br />

<strong>in</strong>vestigat<strong>in</strong>g the backend database server respectively.<br />

As stated <strong>in</strong> Section 3.1.5, Wang et al., (2009) proposed a live physical<br />

memory forensic method of a target or compromised host (workstation or server). In<br />

fact, important potential evidence can be acquired from the physical memory of a<br />

runn<strong>in</strong>g workstation or server. Otherwise, the evidence of a compromised <strong>RFID</strong> BS<br />

will not be complete and the volatile evidence from the memory will be lost when the<br />

power supply of the target host is turned off. Additionally, most bus<strong>in</strong>ess companies<br />

may not permit a forensic <strong>in</strong>vestigator to take the server offl<strong>in</strong>e (Fowler, 2009). Thus,<br />

58

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

Saved successfully!

Ooh no, something went wrong!