• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login

    Forensic Image Analysis with FOG

    Scheduled Pinned Locked Moved
    General Problems
    4
    4
    537
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • I
      icescout27
      last edited by

      Hello everyone,

      I just had a sort of general question as to whether or not it is possible to use a captured raw dd image in FTK. I would like to use the image to perform a forensic analysis on the contents of the drive and need to use raw dd since it is a sector by sector copy.

      I have a one terabyte image captured but the resulting image is only ~92 GB, I’m assuming due to compression? But I also thought you couldn’t compress a raw dd image. The image extension is also .000 when typically raw images start at .001.

      When I try to load the image into FTK it only displays “GZIP” in the evidence tree but has no content. I’ve tried capturing the image many different times with the same results. Not sure if anyone will know, just thought I would ask

      Tom ElliottT 1 Reply Last reply Reply Quote 0
      • Tom ElliottT
        Tom Elliott @icescout27
        last edited by

        @icescout27 you can disable the compression in 1.5.7.

        That said it isn’t quite a dd raw image per say as it’s not using dd in its native form. It’s using partclones imager format which is still a raw copy, just not from dd. The reasoning for this is then our scripts would simply call partclone.restore to place that image on disk regardless of type (raw, btrfs, ntfs, ext, etc…)

        If you really need a true sector by sector you can manually run a dd instance if you know how.

        Typically, though, fog isn’t really intended for forensic usage.as we typically are capturing images to be used for mass on other systems. This of course is not to say fog couldn’t be used for this, just it’s not something we are familiar with as part of our product.

        If you need any help I’m sure we can provide some assistance.

        Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG! Get in contact with me (chat bubble in the top right corner) if you want to join in.

        Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

        Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

        1 Reply Last reply Reply Quote 0
        • S
          Sebastian Roth Moderator
          last edited by Sebastian Roth

          @icescout27 Just to add to what Tom said: You can manually extract the image if you don’t want to recapture it (with compression disabled).

          mv file.000 file.gz
          zcat fiel.gz | partclone.restore --restore_raw_file -C -s - -O hda.img
          

          Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

          Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

          1 Reply Last reply Reply Quote 1
          • george1421G
            george1421 Moderator
            last edited by

            If you are imaging for Forensic Analysis for legal reasons you should not use FOG. You need to use something like “Arsenal Recon” or “SANS SIFT” (which could be delivered by PXE booting in FOG). This software needs to be nationally recognized that exports its information in AFF format. If you don’t use a legally approved method the image collection will be discarded as tainted evidence.

            Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

            1 Reply Last reply Reply Quote 1
            • 1 / 1
            • First post
              Last post

            179

            Online

            12.0k

            Users

            17.3k

            Topics

            155.2k

            Posts
            Copyright © 2012-2024 FOG Project