Week 21 Homework: Digital Forensics In this week's assignment, you will continue to work with your group to continue the final report you began in class. The instructions are included here again for...

1 answer below »

Week 21 Homework: Digital Forensics


In this week's assignment, you will continue to work with your group to continue the final report you began in class. The instructions are included here again for reference. There is also a bonus activity aimed to sharpen your skills in locating and identifying data in a forensic image.



Scenario


Just as in a real-world scenario, you will complete a final report to present your findings. You will work with your team to fill out the report.




  • The final report should be submitted as the homework deliverable for this week. Everything your group has completed in class should be included. What you do not finish today can be continued at home.




  • Use the
    Final Case Report
    Google Doc template to complete your report. Make a copy and be sure that each student has editing access. This will allow everyone in the group to access and work on the document at the same time.




  • Each group will turn in one completed report to be graded.




  • Use the following resource to help guide your work:






Lab Environnement




  • This homework will use the Digital Forensics - Autopsy lab in Kali Linux.




  • You will find the
    tracy-phone-2012-07-15.final.E01
    file located in the
    /corpus
    directory in Autopsy.





Instructions


You've examined and documented quite a bit of information from the iPhone image file. Now you will use that documentation to build a final report.




  1. First, fill out the following evidence worksheet to document the case's WiFi and GPS locations. You will add this, along with the Correspondence Worksheet, to the final report.



    Your group can look for WiFi and GPS info the following directories:




    • Find information about WiFi locations in
      root/Library/Caches/locationd/consolidated.db.





      • Note:
        Input GPS coordinates into Google Maps to see the locations.




      • Refer to the image below as an example:








    • Find information related to WiFi and cell tower location information in
      consolidated.db.








  2. Working in your group's copy of the report template, add content and details as indicated in each section.




    • You will rely on the Locations Information and Correspondence Evidence Worksheets you've completed so far. Additionally, you can use the
      iPhone Forensics - Important Files and Databases
      resource to analyze and find more information to support your case, such as Voicemails and notes from the Notepad iPhone application.




    • Be sure to add to the report the equipment and tools you used to gather and analyze the evidence.



      • For example, Autopsy, the operating system (Kali Linux), text editors (Nano), etc.




    • When including pictures from the iPhone, please use the time stamp of the
      Created time
      from autopsy.







Submission Guidelines



  • Each group should submit one version of the completed Final Case Report document.





Bonus Assignment: Russian Tea Room


The goal of this assignment is to sharpen your skills in locating and identifying data in a forensic image.



  • These skills are important for tasks related to locating and decoding data, such as executable code or malicious documents embedded in images or network logs.



Scenario: The Case of the Little Russian Tea Room




  • There was a fire at the Little Russian Tea Room restaurant last week, and the only thing recovered was a hard drive. To start rebuilding the business, the restaurant hired you as a forensics investigator to look at the disk image and reconstruct the menu.




  • You'll be working with an EnCase image of the hard drive.




  • Luckily, the English and Russian menu are both in the hard drive image. However, only the English menu and two sections of the Russian menu are readable. Your must decode several sections of the Russian menu.





Resources:


The strings in the EnCase image are hex and represent the UTF-16 format. You'll need to be familiar with hex and UTF-16 encoding and decoding for this activity.



  • Review this Unicode Tutorial and the practice exercises. This review will help you locate the menus on the hard drive image.


Below are the files required to complete the assignment:




  • RussianTeaRoom.zip (560 KB): The Autopsy case file and Encase image file.




  • menu.pdf (56.0 KB): The Little Russian Tea Room menu.





  • Google Sheets: Russian Team Room




  • Unicode-Tutorial.md: Short Unicode tutorial.




The files can also be found in the
/root/autopsy-files/homework
directory in Autopsy.



Instructions


Your task is to find, decode, and document six of the menus from the hard drive image using the Unicode Cyrillic and Latin character (cipher) set.




  1. Launch Autopsy and select
    Open Case.




    • Open the
      RussianTeaRoom
      folder and select
      RussianTeaRoom.aut.




    • Add the
      Russian-TeamRoom.E01
      EnCase image file to the case.




    • This is a sample of the hex data in the Autopsy
      RussianTeaRoom
      case file:








  2. Use
    Google Sheets: Russian Team Room
    to document the remaining information from the EnCase image for the investigation.




  3. Find and document the complete file locations for the six menu sections in the image.




    • Hint:
      There may be multiple locations for the same file.




  4. Document the menu items in Cyrillic (e.g., бифштеке) and English (e.g., steak) for the two following menu sections:




    • Pancakes (Menu #3)




    • Meat and Fish (Menu #5)




      • Hint:
        Use the
        Hex
        and
        String
        tabs in
        Data Content
        window in Autopsy to view the data.






    Include in your documentation:




    • Starting location in the hex dump.



      • For example:
        0x00000010




    • Hex string for menu name or menu item.



      • For example:
        00 42 00 65 00 76 00 65 00 72 00 61 00 67 00 65 00 73




    • UTF-16 escape sequence for a menu name or menu item.



      • For example:
        \u0042\u0065\u0076\u0065\u0072\u0061\u0067\u0065\u0073







Submission Guidelines




Important Note for Certification Prep Week




  • In Certification Prep Week, Day 1 you will be using CertMaster Practice in class.




  • Make sure you have access to the tool and should be ready to use it during this unit.





Important Note for Career Prep Week




  • After Certification Prep Week, we will move on to Career Prep. You will take a closer look at the cyber career landscape and will learn practical tips on how to prepare for the job hunt, hone their resume, craft their LinkedIn profile, and ace the behavioral and technical interviews.




  • Please come to class with a digital copy of your resume which you will be working on and sharing with your fellow peers.




  • You must also have a LinkedIn profile set up as well. If you did not set up a LinkedIn account during pre-work, please make sure you do so prior to Career Prep week.



Answered 5 days AfterJul 31, 2021

Answer To: Week 21 Homework: Digital Forensics In this week's assignment, you will continue to work with your...

Swapnil answered on Aug 06 2021
138 Votes
88923/Digital Forensics/RussianTeaRoom/RussianTeaRoom/autopsy.db
88923/Digital Forensics/RussianTeaRoom/RussianTeaRoom/Config/CasePreferences.properties
#
#Mon Mar 25 14:35:32 EDT 2019
88923/Digital Forensics/RussianTeaRoom/RussianTeaRoom/Log/autopsy.log.0
2019-03-25 14:34:50.551 org.sleuthkit.autopsy.keywordsearch.Server isRunning
INFO: Solr server is running
2019-03-25 14:34:51.911 org.sleuthkit.autopsy.casemodule.Case openAsCurrentCase
INFO: Opened 556677 (556677_20190323_161143) in /root/casedata/RussianTeaRoom as the current case
2019-03-25 14:34:52.204 org.sleuthkit.autopsy.corecomponents.DataContentTopComponent findInstance
WARNING: Cannot find DataContentTopComponent component. It will not be located properly in the window system.
2019-03-25 14:34:52.377 org.sleuthkit.autopsy.imagegallery.datamodel.DrawableDB setPragmas
INFO: sqlite-jdbc version 3.7.8 loaded in native mode
2019-03-25 14:35:32.753 org.sleuthkit.autopsy.imagegallery.ImageGalleryController shutDown
INFO: Shutting down image gallery controller for case 556677 (556677_20190323_161143)
2019-03-25 14:35:32.763 org.sleuthkit.autopsy.imagegallery.datamodel.DrawableDB cl
ose
INFO: Closing the drawable.db
2019-03-25 14:35:32.764 org.sleuthkit.autopsy.imagegallery.ImageGalleryController shutDown
INFO: Completed shut down of image gallery controller for case 556677 (556677_20190323_161143)
2019-03-25 14:35:32.784 org.sleuthkit.autopsy.casemodule.Case closeCurrentCase
INFO: Closing current case 556677 (556677_20190323_161143) in /root/casedata/RussianTeaRoom
88923/Digital Forensics/RussianTeaRoom/RussianTeaRoom/Log/autopsy.log.1
2019-03-25 13:40:44.383 org.sleuthkit.autopsy.keywordsearch.Server isRunning
INFO: Solr server is running
2019-03-25 13:40:45.688 org.sleuthkit.autopsy.casemodule.Case openAsCurrentCase
INFO: Opened 556677 (556677_20190323_161143) in /root/casedata/556677 as the current case
2019-03-25 13:40:45.931 org.sleuthkit.autopsy.imagegallery.datamodel.DrawableDB setPragmas
INFO: sqlite-jdbc version 3.7.8 loaded in native mode
2019-03-25 13:40:46.005 org.sleuthkit.autopsy.corecomponents.DataContentTopComponent findInstance
WARNING: Cannot find DataContentTopComponent component. It will not be located properly in the window system.
2019-03-25 14:32:41.755 org.sleuthkit.autopsy.imagegallery.ImageGalleryController shutDown
INFO: Shutting down image gallery controller for case 556677 (556677_20190323_161143)
2019-03-25 14:32:41.763 org.sleuthkit.autopsy.imagegallery.datamodel.DrawableDB close
INFO: Closing the drawable.db
2019-03-25 14:32:41.764 org.sleuthkit.autopsy.imagegallery.ImageGalleryController shutDown
INFO: Completed shut down of image gallery controller for case 556677 (556677_20190323_161143)
2019-03-25 14:32:41.778 org.sleuthkit.autopsy.casemodule.Case closeCurrentCase
INFO: Closing current case 556677 (556677_20190323_161143) in /root/casedata/556677
88923/Digital Forensics/RussianTeaRoom/RussianTeaRoom/Log/autopsy.log.2
2019-03-25 10:14:46.825 org.sleuthkit.autopsy.keywordsearch.Server isRunning
INFO: Solr server is running
2019-03-25 10:14:50.6 org.sleuthkit.autopsy.casemodule.Case openAsCurrentCase
INFO: Opened 556677 (556677_20190323_161143) in /root/casedata/556677 as the current case
2019-03-25 10:14:51.196 org.sleuthkit.autopsy.corecomponents.DataContentTopComponent findInstance
WARNING: Cannot find DataContentTopComponent component. It will not be located properly in the window system.
2019-03-25 10:14:51.202 org.sleuthkit.autopsy.imagegallery.datamodel.DrawableDB setPragmas
INFO: sqlite-jdbc version 3.7.8 loaded in native mode
2019-03-25 10:15:14.449 org.sleuthkit.autopsy.centralrepository.datamodel.EamArtifactUtil getInstanceFromContent
WARNING: Correlation attribute could not be retrieved for 'app.txt' (id=12): Data was null.
2019-03-25 10:34:51.347 org.sleuthkit.autopsy.centralrepository.datamodel.EamArtifactUtil getInstanceFromContent
WARNING: Correlation attribute could not be retrieved for '$FAT1' (id=15): Data was null.
2019-03-25 10:34:51.353 org.sleuthkit.autopsy.centralrepository.datamodel.EamArtifactUtil getInstanceFromContent
WARNING: Correlation attribute could not be retrieved for '$FAT2' (id=16): Data was null.
2019-03-25 10:34:51.361 org.sleuthkit.autopsy.centralrepository.datamodel.EamArtifactUtil getInstanceFromContent
WARNING: Correlation attribute could not be retrieved for '$MBR' (id=14): Data was null.
2019-03-25 10:34:51.38 org.sleuthkit.autopsy.centralrepository.datamodel.EamArtifactUtil getInstanceFromContent
WARNING: Correlation attribute could not be retrieved for 'app.txt' (id=12): Data was null.
2019-03-25 10:34:51.391 org.sleuthkit.autopsy.centralrepository.datamodel.EamArtifactUtil getInstanceFromContent
WARNING: Correlation attribute could not be retrieved for 'CFREDS001 (Volume Label Entry)' (id=7): Data was null.
2019-03-25 10:36:22.684 org.sleuthkit.autopsy.centralrepository.datamodel.EamArtifactUtil getInstanceFromContent
WARNING: Correlation attribute could not be retrieved for 'app.txt' (id=12): Data was null.
2019-03-25 10:55:09.695 org.sleuthkit.autopsy.centralrepository.datamodel.EamArtifactUtil getInstanceFromContent
WARNING: Correlation attribute could not be retrieved for 'app.txt' (id=12): Data was null.
88923/Digital Forensics/RussianTeaRoom/RussianTeaRoom/Log/autopsy.log.3
2019-03-24 18:34:57.546 org.sleuthkit.autopsy.keywordsearch.Server isRunning
INFO: Solr server is running
2019-03-24 18:34:58.871 org.sleuthkit.autopsy.casemodule.Case openAsCurrentCase
INFO: Opened 556677 (556677_20190323_161143) in /root/casedata/556677 as the current case
2019-03-24 18:34:59.209 org.sleuthkit.autopsy.corecomponents.DataContentTopComponent findInstance
WARNING: Cannot find DataContentTopComponent component. It will not be located properly in the window system.
2019-03-24 18:34:59.47 org.sleuthkit.autopsy.imagegallery.datamodel.DrawableDB setPragmas
INFO: sqlite-jdbc version 3.7.8 loaded in native mode
2019-03-24 18:36:18.602 org.sleuthkit.autopsy.centralrepository.datamodel.EamArtifactUtil getInstanceFromContent
WARNING: Correlation attribute could not be retrieved for 'app.txt' (id=12): Data was null.
2019-03-24 18:39:49.405 org.sleuthkit.autopsy.centralrepository.datamodel.EamArtifactUtil getInstanceFromContent
WARNING: Correlation attribute could not be retrieved for 'app.txt' (id=12): Data was null.
2019-03-24 18:40:33.471 org.sleuthkit.autopsy.centralrepository.datamodel.EamArtifactUtil getInstanceFromContent
WARNING: Correlation attribute could not be retrieved for 'CFREDS001 (Volume Label Entry)' (id=7): Data was null.
2019-03-24 18:42:38.557 org.sleuthkit.autopsy.centralrepository.datamodel.EamArtifactUtil getInstanceFromContent
WARNING: Correlation attribute could not be retrieved for 'app.txt' (id=12): Data was null.
2019-03-24 18:43:42.655 org.sleuthkit.autopsy.centralrepository.datamodel.EamArtifactUtil getInstanceFromContent
WARNING: Correlation attribute could not be retrieved for 'CFREDS001 (Volume Label Entry)' (id=7): Data was null.
2019-03-24 18:43:54.017 org.sleuthkit.autopsy.centralrepository.datamodel.EamArtifactUtil getInstanceFromContent
WARNING: Correlation attribute could not be retrieved for 'app.txt' (id=12): Data was null.
2019-03-24 18:44:38.476 org.sleuthkit.autopsy.centralrepository.datamodel.EamArtifactUtil getInstanceFromContent
WARNING: Correlation attribute could not be retrieved for 'app.txt' (id=12): Data was null.
2019-03-24 18:45:26.921 org.sleuthkit.autopsy.centralrepository.datamodel.EamArtifactUtil getInstanceFromContent
WARNING: Correlation attribute could not be retrieved for '$FAT1' (id=15): Data was null.
2019-03-24 18:45:26.922 org.sleuthkit.autopsy.centralrepository.datamodel.EamArtifactUtil getInstanceFromContent
WARNING: Correlation attribute could not be retrieved for '$FAT2' (id=16): Data was null.
2019-03-24 18:45:26.929 org.sleuthkit.autopsy.centralrepository.datamodel.EamArtifactUtil getInstanceFromContent
WARNING: Correlation attribute could not be retrieved for '$MBR' (id=14): Data was null.
2019-03-24 18:45:26.964 org.sleuthkit.autopsy.centralrepository.datamodel.EamArtifactUtil getInstanceFromContent
WARNING: Correlation attribute could not be retrieved for 'app.txt' (id=12): Data was null.
2019-03-24 18:45:26.969 org.sleuthkit.autopsy.centralrepository.datamodel.EamArtifactUtil getInstanceFromContent
WARNING: Correlation attribute could not be retrieved for 'CFREDS001 (Volume Label Entry)' (id=7): Data was null.
2019-03-24 18:48:15.24 org.sleuthkit.autopsy.centralrepository.datamodel.EamArtifactUtil getInstanceFromContent
WARNING: Correlation attribute could not be retrieved for 'app.txt' (id=12): Data was null.
2019-03-24 20:33:38.576 org.sleuthkit.autopsy.centralrepository.datamodel.EamArtifactUtil getInstanceFromContent
WARNING: Correlation attribute could not be retrieved for 'app.txt' (id=12): Data was null.
2019-03-24 20:34:10.519 org.sleuthkit.autopsy.centralrepository.datamodel.EamArtifactUtil getInstanceFromContent
WARNING: Correlation attribute could not be retrieved for 'app.txt' (id=12): Data was null.
2019-03-24 20:38:29.455 org.sleuthkit.autopsy.centralrepository.datamodel.EamArtifactUtil getInstanceFromContent
WARNING: Correlation attribute could not be retrieved for 'app.txt' (id=12): Data was null.
2019-03-24 20:41:01.891 org.sleuthkit.autopsy.centralrepository.datamodel.EamArtifactUtil getInstanceFromContent
WARNING: Correlation attribute could not be retrieved for 'app.txt' (id=12): Data was null.
2019-03-24 20:43:48.542 org.sleuthkit.autopsy.centralrepository.datamodel.EamArtifactUtil getInstanceFromContent
WARNING: Correlation attribute could not be retrieved for 'CFREDS001 (Volume Label Entry)' (id=7): Data was null.
2019-03-24 20:44:00.454 org.sleuthkit.autopsy.centralrepository.datamodel.EamArtifactUtil getInstanceFromContent
WARNING: Correlation attribute could not be retrieved for 'app.txt' (id=12): Data was null.
2019-03-24 20:50:37.55 org.sleuthkit.autopsy.centralrepository.datamodel.EamArtifactUtil getInstanceFromContent
WARNING: Correlation attribute could not be retrieved for 'app.txt' (id=12): Data was null.
2019-03-24 20:51:36.431 org.sleuthkit.autopsy.centralrepository.datamodel.EamArtifactUtil getInstanceFromContent
WARNING: Correlation attribute could not be retrieved for 'CFREDS001 (Volume Label Entry)' (id=7): Data was null.
2019-03-24 20:52:52.002 org.sleuthkit.autopsy.centralrepository.datamodel.EamArtifactUtil getInstanceFromContent
WARNING: Correlation attribute could not be retrieved for 'app.txt' (id=12): Data was null.
2019-03-24 21:01:44.705 org.sleuthkit.autopsy.centralrepository.datamodel.EamArtifactUtil getInstanceFromContent
WARNING: Correlation attribute could not be retrieved for 'app.txt' (id=12): Data was null.
2019-03-24 21:05:11.725 org.sleuthkit.autopsy.centralrepository.datamodel.EamArtifactUtil getInstanceFromContent
WARNING: Correlation attribute could not be retrieved for 'app.txt' (id=12): Data was null.
2019-03-24 22:02:25.543 org.sleuthkit.autopsy.centralrepository.datamodel.EamArtifactUtil getInstanceFromContent
WARNING: Correlation attribute could not be retrieved for 'app.txt' (id=12): Data was null.
2019-03-24 22:16:47.797 org.sleuthkit.autopsy.centralrepository.datamodel.EamArtifactUtil getInstanceFromContent
WARNING: Correlation attribute could not be retrieved for 'app.txt' (id=12): Data was null.
2019-03-24 23:42:01.532 org.sleuthkit.autopsy.keywordsearch.Server stop
INFO: Stopping Solr server from: /root/autopsy-files/autopsy-4.10.0/autopsy/solr
2019-03-24 23:42:01.532...
SOLUTION.PDF

Answer To This Question Is Available To Download

Related Questions & Answers

More Questions »

Submit New Assignment

Copy and Paste Your Assignment Here