An Ontology for Digital Forensics in IT Security Incidents - OPUS

An Ontology for Digital Forensics in IT Security Incidents - OPUS An Ontology for Digital Forensics in IT Security Incidents - OPUS

opus.bibliothek.uni.augsburg.de
from opus.bibliothek.uni.augsburg.de More from this publisher
15.01.2014 Views

70 CHAPTER 9. SUMMARY after some issue occurred. Using the ontology to investigate the cases made it easier because only queries had to be issued. For example, for the Autorun query the printkey module of volatility needs to be run multiple times to get the data from the registry in the memory. For the registry on the hard disk it is rst needed to know where the relevant les are located and then extract them with icat from The Sleuth Kit if the source is an image and then run reglookup for each of them. All this is simplied to only issuing one query because all other commands have been run automatically during the extraction process. In my opinion the ontological approach has great potential because it makes forensic analysis easier. An additional aspect is that after the database is lled, multiple investigators can use this data and do not need to run the same tools again. The creation of the ontology is not that easy as the tools do not create satisfying RDFS les or are uncomfortable to use. If the forensic ontology is to be developed further, it may be useful to create a tool that allows an easier creation of RDFS les of similar structure. Additionally, a program should be developed that makes it easier to parse the output of a forensic tool and map it to the correct part of the ontology.

Appendix A Extraction tool listings < properties > < comment > ExtractInformation - Config - File < entry key =" samdump2 " >/ usr / bin / samdump2 < entry key =" started " >1353417866724 < entry key =" sesamerepo "> case1 < entry key =" ramimage " >../ cases / case1 / zeus . vmem < entry key =" fsstat " >../ TSK / fsstat < entry key =" hddimage " >../ cases / case1 / zeus . raw < entry key =" threadcount " >10 < entry key =" skipregistry "> true < entry key =" reglookup " >../ reglookup / reglookup < entry key =" ontology " >../ ONTO < entry key =" database "> sesame < entry key =" datadir " >../ cases / case1 / extracted < entry key =" bkhive " >/ usr / bin / bkhive < entry key =" python " >/ usr / bin / python < entry key =" fls " >../ TSK / fls < entry key =" hddimageoffset " >63 < entry key =" baseuri "> http :// www .0 x221b . org / < entry key =" mmls " >../ TSK / mmls < entry key =" sesameserver "> http ://..:8080/ openrdf - sesame / < entry key =" volatility " >../ volatility -2.1/ vol .py < entry key =" icat " >../ TSK / icat < entry key =" skipprocesses "> true Listing A.1: Conguration of the tool(shortened) Start Start loading Ontology Start writing User . rdfs (2.0 KB ) Finished writing User . rdfs Start writing Filesystem . rdfs (8.0 KB ) Finished writing Filesystem . rdfs Start writing Forensic . rdfs (1.0 KB ) Finished writing Forensic . rdfs Start writing Registry . rdfs (4.0 KB ) Finished writing Registry . rdfs Start writing Process . rdfs (2.0 KB ) Finished writing Process . rdfs Start writing Hardware . rdfs (1.0 KB ) 71

Appendix A<br />

Extraction tool list<strong>in</strong>gs<br />

<br />

<br />

< properties ><br />

< comment > ExtractIn<strong>for</strong>mation - Config - File <br />

< entry key =" samdump2 " >/ usr / b<strong>in</strong> / samdump2 <br />

< entry key =" started " >1353417866724 <br />

< entry key =" sesamerepo "> case1 <br />

< entry key =" ramimage " >../ cases / case1 / zeus . vmem <br />

< entry key =" fsstat " >../ TSK / fsstat <br />

< entry key =" hddimage " >../ cases / case1 / zeus . raw <br />

< entry key =" threadcount " >10 <br />

< entry key =" skipregistry "> true <br />

< entry key =" reglookup " >../ reglookup / reglookup <br />

< entry key =" ontology " >../ ONTO <br />

< entry key =" database "> sesame <br />

< entry key =" datadir " >../ cases / case1 / extracted <br />

< entry key =" bkhive " >/ usr / b<strong>in</strong> / bkhive <br />

< entry key =" python " >/ usr / b<strong>in</strong> / python <br />

< entry key =" fls " >../ TSK / fls <br />

< entry key =" hddimageoffset " >63 <br />

< entry key =" baseuri "> http :// www .0 x221b . org / <br />

< entry key =" mmls " >../ TSK / mmls <br />

< entry key =" sesameserver "> http ://..:8080/ openrdf - sesame / <br />

< entry key =" volatility " >../ volatility -2.1/ vol .py <br />

< entry key =" icat " >../ TSK / icat <br />

< entry key =" skipprocesses "> true <br />

<br />

List<strong>in</strong>g A.1: Conguration of the tool(shortened)<br />

Start<br />

Start load<strong>in</strong>g <strong>Ontology</strong><br />

Start writ<strong>in</strong>g User . rdfs (2.0 KB )<br />

F<strong>in</strong>ished writ<strong>in</strong>g User . rdfs<br />

Start writ<strong>in</strong>g Filesystem . rdfs (8.0 KB )<br />

F<strong>in</strong>ished writ<strong>in</strong>g Filesystem . rdfs<br />

Start writ<strong>in</strong>g Forensic . rdfs (1.0 KB )<br />

F<strong>in</strong>ished writ<strong>in</strong>g Forensic . rdfs<br />

Start writ<strong>in</strong>g Registry . rdfs (4.0 KB )<br />

F<strong>in</strong>ished writ<strong>in</strong>g Registry . rdfs<br />

Start writ<strong>in</strong>g Process . rdfs (2.0 KB )<br />

F<strong>in</strong>ished writ<strong>in</strong>g Process . rdfs<br />

Start writ<strong>in</strong>g Hardware . rdfs (1.0 KB )<br />

71

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

Saved successfully!

Ooh no, something went wrong!