<?xml version="1.0" encoding="UTF-8"?><marc:collection xmlns:marc="http://www.loc.gov/MARC21/slim">
  <marc:record>
    <marc:leader>00000nam  2200000za 4500</marc:leader>
    <marc:controlfield tag="001">9.821336</marc:controlfield>
    <marc:controlfield tag="003">CaOODSP</marc:controlfield>
    <marc:controlfield tag="005">20240219183447</marc:controlfield>
    <marc:controlfield tag="007">cr |||||||||||</marc:controlfield>
    <marc:controlfield tag="008">160719s2013    onc|||||o    f000 0 eng d</marc:controlfield>
    <marc:datafield tag="040" ind1=" " ind2=" ">
      <marc:subfield code="a">CaOODSP</marc:subfield>
      <marc:subfield code="b">eng</marc:subfield>
    </marc:datafield>
    <marc:datafield tag="041" ind1=" " ind2=" ">
      <marc:subfield code="a">eng</marc:subfield>
      <marc:subfield code="b">fre</marc:subfield>
    </marc:datafield>
    <marc:datafield tag="043" ind1=" " ind2=" ">
      <marc:subfield code="a">n-cn---</marc:subfield>
    </marc:datafield>
    <marc:datafield tag="086" ind1="1" ind2=" ">
      <marc:subfield code="a">D68-6/161-2009E-PDF</marc:subfield>
    </marc:datafield>
    <marc:datafield tag="100" ind1="1" ind2=" ">
      <marc:subfield code="a">Carbone, Richard.</marc:subfield>
    </marc:datafield>
    <marc:datafield tag="245" ind1="1" ind2="0">
      <marc:subfield code="a">File recovery and data extraction using automated data recovery tools </marc:subfield>
      <marc:subfield code="h">[electronic resource] : </marc:subfield>
      <marc:subfield code="b">a balanced approach using Windows and Linux when working with an unknown disk image and filesystem / </marc:subfield>
      <marc:subfield code="c">by Richard Carbone.</marc:subfield>
    </marc:datafield>
    <marc:datafield tag="260" ind1=" " ind2=" ">
      <marc:subfield code="a">[Ottawa] : </marc:subfield>
      <marc:subfield code="b">Defence Research and Development Canada, </marc:subfield>
      <marc:subfield code="c">c2013.</marc:subfield>
    </marc:datafield>
    <marc:datafield tag="300" ind1=" " ind2=" ">
      <marc:subfield code="a">x, 52 p. : </marc:subfield>
      <marc:subfield code="b">tables, graphs.</marc:subfield>
    </marc:datafield>
    <marc:datafield tag="490" ind1="1" ind2=" ">
      <marc:subfield code="a">Technical Memorandum ; </marc:subfield>
      <marc:subfield code="v">2009-161</marc:subfield>
    </marc:datafield>
    <marc:datafield tag="500" ind1=" " ind2=" ">
      <marc:subfield code="a">"January 2013."</marc:subfield>
    </marc:datafield>
    <marc:datafield tag="504" ind1=" " ind2=" ">
      <marc:subfield code="a">Includes bibliographical references.</marc:subfield>
    </marc:datafield>
    <marc:datafield tag="520" ind1=" " ind2=" ">
      <marc:subfield code="a">This memorandum is the direct result of the analysis of an unknown disk containing unknown data, files and filesystem. The disk was brought to an analysis team at DRDC Valcartier by an agency that desired to ascertain the research centre’s capabilities for extracting and recovering unknown forensic data from an unknown disk and, if possible, automate the process. However, a thorough analysis using various Windows and Linux-based automated data and file recovery tools has led the author to determine that automated tools, regardless of the underlying system, are not yet up to this specific challenge. In addition, the author is of the opinion that fully automated disk recovery tools will never be entirely successful. Instead, the author has determined that a manual approach to data and file extraction will be necessary in order to recover any meaningful data or files from this disk’s unknown filesystem. However, this memorandum will only examine the automated approach used by the various Windows and Linux tools. An additional follow-up study will specifically examine the required manual approach necessary for data recovery from an unknown disk using data pattern matching techniques and sector-by-sector analysis using known file signatures.</marc:subfield>
    </marc:datafield>
    <marc:datafield tag="692" ind1="0" ind2="7">
      <marc:subfield code="2">gccst</marc:subfield>
      <marc:subfield code="a">Technical reports</marc:subfield>
    </marc:datafield>
    <marc:datafield tag="693" ind1="0" ind2="7">
      <marc:subfield code="a">Computer forensics</marc:subfield>
    </marc:datafield>
    <marc:datafield tag="693" ind1="0" ind2="7">
      <marc:subfield code="a">Data extraction</marc:subfield>
    </marc:datafield>
    <marc:datafield tag="693" ind1="0" ind2="7">
      <marc:subfield code="a">Data recovery</marc:subfield>
    </marc:datafield>
    <marc:datafield tag="710" ind1="2" ind2=" ">
      <marc:subfield code="a">Defence R&amp;D Canada.</marc:subfield>
    </marc:datafield>
    <marc:datafield tag="830" ind1="#" ind2="0">
      <marc:subfield code="a">Technical memorandum (Defence R&amp;D Canada)</marc:subfield>
      <marc:subfield code="v">2009-161</marc:subfield>
      <marc:subfield code="w">(CaOODSP)9.820564</marc:subfield>
    </marc:datafield>
    <marc:datafield tag="856" ind1="4" ind2="0">
      <marc:subfield code="q">PDF</marc:subfield>
      <marc:subfield code="s">9.54 MB</marc:subfield>
      <marc:subfield code="u">https://publications.gc.ca/collections/collection_2016/rddc-drdc/D68-6-161-2009-eng.pdf</marc:subfield>
    </marc:datafield>
  </marc:record>
</marc:collection>
