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.

4.2.3.2 Ad Hoc Artefact Collection by us<strong>in</strong>g Trusted SQLCMD<br />

In order to perform <strong>in</strong>teractive ad hoc artefact collection, the trusted SQLCMD<br />

b<strong>in</strong>ary for SQL Server 2005 from HELIX_<strong>RFID</strong>_IR tool was used. However,<br />

the connection establishment to victim‟s SQL server was firstly done by us<strong>in</strong>g<br />

the follow<strong>in</strong>g syntax.<br />

Figure 4.20: Connection to the Victim’s Server for ad hoc data acquisition<br />

Then, all the actions performed on the victim‟s system by us<strong>in</strong>g SQLCMD<br />

b<strong>in</strong>ary was directed to the output file by us<strong>in</strong>g the follow<strong>in</strong>g command.<br />

:out E:\InitialConnection.txt<br />

However, the results of executed Database Console Commands (DBCC) were<br />

required to redirect to the above mentioned output file from the SQL Server log<br />

(Fowler, 2009). The follow<strong>in</strong>g syntax, <strong>in</strong> which the trace flag 3604 was<br />

enabled, was used to direct DBCC results.<br />

DBCC TRACEON(3604)<br />

GO<br />

After enabl<strong>in</strong>g the connection session, the session would rema<strong>in</strong> effective even<br />

the <strong>in</strong>vestigator switch database contexts dur<strong>in</strong>g the <strong>in</strong>vestigation (Fowler,<br />

2009).<br />

4.2.3.3 Volatile SQL Server Evidence<br />

(Fowler, 2009, p. 182)<br />

The potential evidence could be presented <strong>in</strong> the volatile SQL Server artefacts.<br />

The important part of the <strong>in</strong>vestigation was to acquire the volatile SQL Server<br />

data as early as possible due to the volatile data from the on-disk server data<br />

94

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

Saved successfully!

Ooh no, something went wrong!