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.

Unlike SQL Server forensics, the traditional W<strong>in</strong>dows digital forensic <strong>in</strong>vestigation<br />

generally targets on “the volatile and non-volatile operat<strong>in</strong>g system, and selected<br />

application data”, and often ignores the database (Fowler, 2009, p. 50). As the<br />

database is overlooked, the decision on whether a database is compromised or not<br />

dur<strong>in</strong>g an <strong>in</strong>cident is very hard for a forensic <strong>in</strong>vestigator. Nevertheless, the two case<br />

scenarios expla<strong>in</strong>ed <strong>in</strong> this book chapter demonstrate that the application of SQL<br />

Server forensics can discover additional important data beyond the scope of a<br />

traditional W<strong>in</strong>dows forensic <strong>in</strong>vestigation (Fowler, 2009).<br />

Fourthly, the author expla<strong>in</strong>s three different acquisition methods that can be<br />

performed dur<strong>in</strong>g forensic <strong>in</strong>vestigations such as live acquisition, dead acquisition,<br />

and hybrid acquisition. All SQL Server data, volatile and non-volatile, can be<br />

identified and acquired by us<strong>in</strong>g the live acquisition method. On the other hand, the<br />

live acquisition method can solve the problem of tak<strong>in</strong>g a SQL Server offl<strong>in</strong>e for an<br />

<strong>in</strong>vestigation as the bus<strong>in</strong>ess companies may not allow the forensic <strong>in</strong>vestigator to<br />

take the server offl<strong>in</strong>e (Fowler, 2009). Furthermore, the author po<strong>in</strong>ts out some<br />

benefits of live acquisition. For <strong>in</strong>stance, the forensic <strong>in</strong>vestigator can perform<br />

“<strong>in</strong>vestigation on identified data repositories without need<strong>in</strong>g to forensically<br />

duplicate the entire logical or physical disk drives” as live forensics is more and<br />

more realistic due to the ever grow<strong>in</strong>g storage capacity of the computers (Fowler,<br />

2009, p. 54). In fact, the <strong>in</strong>vestigator can save time and easily focus on the database<br />

artifacts that are ma<strong>in</strong>ly related to the <strong>in</strong>vestigation by us<strong>in</strong>g the live acquisition<br />

method. Then, the author mentions two connection methods, <strong>in</strong>teractive and remote<br />

connections, to a SQL Server to perform live acquisition. In an <strong>in</strong>teractive<br />

connection, the <strong>in</strong>vestigator can either access the SQL server onsite or use a remote<br />

desktop protocol (RDP) to log onto the SQL Server and utilize the tools from an<br />

<strong>in</strong>cident response-compact disc (IR-CD) to acquire SQL artifacts. Then, the acquired<br />

output can be transferred to a reliable storage location by us<strong>in</strong>g tools such as Netcat<br />

or Cryptcat. Instead, a universal serial bus (USB) flash or external hard drive can be<br />

connected to the target SQL Server to store the acquired output. Unlike an <strong>in</strong>teraction<br />

connection, Fowler (2009) mentions the <strong>in</strong>vestigator can employ a computer that can<br />

be connected to a compromised network <strong>in</strong> order to remotely connect a target live<br />

44

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

Saved successfully!

Ooh no, something went wrong!