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.

The acquisition result of r<strong>in</strong>g buffer security error was as shown <strong>in</strong> the figure<br />

below.<br />

Figure 4.24: R<strong>in</strong>g Buffer security error results from sys.dm_os_r<strong>in</strong>g_buffers<br />

After acquir<strong>in</strong>g all the volatile SQL Server evidence, the forensic <strong>in</strong>vestigator<br />

must perform the acquisition of non-volatile server evidence.<br />

4.2.3.4 Non-volatile SQL Server Evidence<br />

As stated <strong>in</strong> Section 3.1.3, the traditional digital forensic <strong>in</strong>vestigation approach<br />

of acquir<strong>in</strong>g the evidence is firstly to collect the volatile data while the system<br />

is runn<strong>in</strong>g and then unplug or disconnect the power cable to collect non-volatile<br />

data. However, Fowler (2009) mentions that the traditional <strong>in</strong>vestigation<br />

approach cannot be applied to the acquisition of non-volatile SQL Server<br />

artefact as the artefacts such as server log<strong>in</strong>s, database users and the like cannot<br />

be collected when the Server is down. Hence, the non-volatile SQL Server<br />

artefacts were also acquired and preserved by us<strong>in</strong>g different collection<br />

methods for different purposes <strong>in</strong> order to help the <strong>in</strong>vestigation (see Table A1.<br />

2 <strong>in</strong> Appendix 1). For <strong>in</strong>stance, the different non-volatile server collection<br />

methods <strong>in</strong>cluded us<strong>in</strong>g the extended WFT tool, which was <strong>in</strong>tegrated <strong>in</strong><br />

Helix_<strong>RFID</strong>_IR toolkit (see Appendix 2), and ad hoc acquisition method. The<br />

f<strong>in</strong>d<strong>in</strong>gs of these artefacts are presented <strong>in</strong> the follow<strong>in</strong>g.<br />

4.2.3.4.1 Authentication Sett<strong>in</strong>gs of the Backend Database Server<br />

Bra<strong>in</strong>ard et al., (2006) has mentioned that the user authentication <strong>in</strong> a<br />

comput<strong>in</strong>g system can be accomplished through three factors such as what you<br />

do know (e.g., a password), what you do have (e.g., an ID badge) and who you<br />

really are (e.g., a f<strong>in</strong>gerpr<strong>in</strong>t). Hence, the SQL Server authentication is a<br />

process <strong>in</strong> which the server verifies and manages log<strong>in</strong> requests and the<br />

authentication mode (e.g., W<strong>in</strong>dows, or SQL Server and W<strong>in</strong>dows<br />

98

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

Saved successfully!

Ooh no, something went wrong!