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.

3.2.1 Review of Similar Works Lead<strong>in</strong>g towards the Research Methodology<br />

Seven reviews of similar works were described <strong>in</strong> Section 3.1. The study conducted<br />

by Cerrudo (2003) did was not only to make the security professionals aware that a<br />

potential SQL <strong>in</strong>jection attack could have a critical effect on a bus<strong>in</strong>ess organization,<br />

but also to give recommendations on how to prevent the malicious attacker‟s<br />

manipulations of data <strong>in</strong> the backend databases and other applications on the network.<br />

Likewise, the research performed by Rieback et al., (2006b) was to warn the<br />

middleware designers that a <strong>RFID</strong> tag could be used as an attack vector to exploit<br />

backend database servers <strong>in</strong> order to change the contents of the databases.<br />

Hence, the articles written by Cerrudo (2003) <strong>in</strong> Section 3.1.1 and Rieback et<br />

al., (2006b) <strong>in</strong> Section 3.1.2 give an idea of the type of data manipulation attack by<br />

us<strong>in</strong>g <strong>RFID</strong> tag towards the backend database server of a <strong>RFID</strong> stock management<br />

system (Section 2.3) of a Bus<strong>in</strong>ess System (BS). Therefore, the case of a BS be<strong>in</strong>g<br />

violated by a SQL <strong>in</strong>jection attack through the Read/Write <strong>RFID</strong> <strong>Tag</strong> (Section 3.3.2)<br />

will be replicated (Rieback et al., 2006b). Even though the attack case scenario of the<br />

research will be replicated, the data requirement <strong>in</strong> this attack scenario (Section 3.3)<br />

will be completely different from previous literature. For <strong>in</strong>stance, the system design<br />

(Section 3.3.1) of the research is not the same as that of the system mentioned <strong>in</strong><br />

previous literature and the middleware software has to be developed (accord<strong>in</strong>g to the<br />

research requirement) by us<strong>in</strong>g Software Development Kit (SDK) provided by the<br />

company that manufactures the <strong>RFID</strong> scanner. Furthermore, it is important to<br />

acknowledge that none of the researchers (Cerrudo, 2003; Rieback et al., 2006b)<br />

discussed that the potential for a breach of asset protection could be high and hence<br />

would <strong>in</strong>crease the requirement for forensic read<strong>in</strong>ess <strong>in</strong> any <strong>RFID</strong> BS. Most<br />

importantly, there was no forensic analysis of the <strong>RFID</strong> BS <strong>in</strong> the previous literature.<br />

One of the objectives of the research phases (Figure 3.8 <strong>in</strong> Section 3.2.5) is to<br />

create a prototype of a commercial retail environment us<strong>in</strong>g a <strong>RFID</strong> stock<br />

management system with<strong>in</strong> the laboratory (see Section 3.3.1, <strong>in</strong> which a Microsoft<br />

SQL Server 2005 will be utilized as a backend database server). Subsequently, the<br />

BS will be stressed by a SQL <strong>in</strong>jection attack <strong>in</strong> order to change/manipulate the data<br />

from the backend server and then each entity <strong>in</strong> the BS (Table 2.5 <strong>in</strong> Section 2.3) will<br />

57

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

Saved successfully!

Ooh no, something went wrong!