{
    "id": "674ba4a3-d32c-402a-9daa-d4f2e1914560",
    "name": "Windows Registry Analysis",
    "slug": "windows-registry-analysis",
    "status": "published",
    "lab_type": "pta",
    "is_sample": false,
    "duration_in_seconds": 1800,
    "metadata": {
        "courses": [
            "cd60ce4a-1b83-48c4-8d38-7e6bfeab4a1e",
            "f6ac45c3-fa73-49e5-a56a-0be38f64aee5"
        ],
        "pta_sdn": "62",
        "pta_namespace": "my.ine",
        "learning_paths": [],
        "has_published_parent": true
    },
    "session": null,
    "company": "a491bc32-c056-4946-9169-cc053387bada",
    "created": "2022-03-30T02:57:31.767485Z",
    "modified": "2024-04-30T14:32:23.617075Z",
    "is_beta": false,
    "lab_objectives": [],
    "main_learning_area": "3e1aa06f-2e9f-4789-b50d-aa027ad8dcfa",
    "learning_areas": [
        {
            "id": "3e1aa06f-2e9f-4789-b50d-aa027ad8dcfa",
            "name": "Cyber Security",
            "slug": "cyber-security"
        }
    ],
    "categories": [],
    "tags": [],
    "difficulty": null,
    "is_web_access": false,
    "is_lab_experience": false,
    "is_featured": false,
    "cve": null,
    "severity": null,
    "year": null,
    "classification": null,
    "external_url": "",
    "solution_video": null,
    "explanation_video": null,
    "description": "# Scenario\n\nCompany XYZ's IT department got a tip regarding employee misconduct. One of the users might have violated the company's policy by installing different illegal applications and wasting official working hours by doing personal communication (chatting) and other stuff. The IR team managed to respond immediately and take a full forensic image of the user's system.\n\nYou have been called to perform a series of forensic analysis and investigation, in order to either prove that the tip was true, and the user was really behaving in an improper or unprofessional manner; or prove that the tip was just an accusation with no solid evidence.\n\n**[Note:]**\n\nThis case will not end with analyzing the Windows Registry only! In this lab, you will be profiling the user's activity based on the information found in Windows registry only, but further user profiling will be done in other labs to cover topics such as Shell Bags and LNK files.\n\nEvidence given are:\n\n1.  **WindowsRegisty folder** [located at **C:\\\\DFP\\\\Labs\\\\Module6\\\\Lab14\\\\WindowsRegistry**] includes: SYSTEM, SOFTWARE, SAM, and NTUSER.DAT registry files.\n\n|**File** |    **Hash** |\n|------------ |--------------------|\n|NTUSER.DAT |  c70ee7615b5c27ab9fee91681da8f4e2|\n|SAM     |     190697abebc5496f9b4eb6adc66d2834  |\n|SOFTWARE    | 5b6a904d2e37fe3de2ab98cdc3c46291|\n|SYSTEM  |     e4571e43d4d4b62db9c4dc4f96ab629a|\n\n2.  **HunterProfileImage folder** includes:\n\n-   Hunter-ProfileImage.ad1 which is the user hunter's whole home directory\n\n-   Hunter-ProfileImage.ad1.csv\n\n-   Hunter-ProfileImage.ad1.txt\n\n|**File** |    **Hash** |\n|------------ |--------------------|\n|Hunter-ProfileImage.ad1 |  a9a6a075b9deb8d70dca1ddf313fe055|\n|Hunter-ProfileImage.ad1.csv     |     c02392553aab92362ec9f7f0b05e21cb  |\n|Hunter-ProfileImage.ad1.txt    | 23a057157f5d69bed322390ab131aff4|\n\n# Goals\n\n-   Use different registry analysis tools to perform Windows Registry investigations\n\n-   Analyze user activity from the registry\n\n-   Check system configurations found in the registry\n\n-   Analyze system time zone information\n\n-   Analyze recently used documents, applications, mounted devices, etc.\n\n-   Gain the ability to analyze the Windows SAM file\n\n-   Gain the ability to analyze UserAssist keys\n\n# What you will learn\n\n-   How to use Windows Registry Explorer and RegRipper to Analyze Windows Registry files\n\n-   How to search and locate different artifacts in the Windows Registry\n\n-   How to analyze time zone information and understand the true timezone being used\n\n-   How to analyze network IP Address configurations used by the system\n\n-   How to check for firewall settings and RDP related configurations\n\n-   How to analyze the Windows SAM file to locate users, their SIDs and  RID also groups and other configurations related to user and group management\n\n-   Locate and analyze UserAssist keys to understand what applications and files were used by the user\n\n# Recommended tools\n\n-   **Windows Registry Explorer**\n\n-   **DCode**\n\n-   **Regripper**\n\n-   **Notepad++**",
    "description_html": "<h1>Scenario</h1>\n<p>Company XYZ's IT department got a tip regarding employee misconduct. One of the users might have violated the company's policy by installing different illegal applications and wasting official working hours by doing personal communication (chatting) and other stuff. The IR team managed to respond immediately and take a full forensic image of the user's system.</p>\n<p>You have been called to perform a series of forensic analysis and investigation, in order to either prove that the tip was true, and the user was really behaving in an improper or unprofessional manner; or prove that the tip was just an accusation with no solid evidence.</p>\n<p><strong>[Note:]</strong></p>\n<p>This case will not end with analyzing the Windows Registry only! In this lab, you will be profiling the user's activity based on the information found in Windows registry only, but further user profiling will be done in other labs to cover topics such as Shell Bags and LNK files.</p>\n<p>Evidence given are:</p>\n<ol>\n<li><strong>WindowsRegisty folder</strong> [located at <strong>C:\\DFP\\Labs\\Module6\\Lab14\\WindowsRegistry</strong>] includes: SYSTEM, SOFTWARE, SAM, and NTUSER.DAT registry files.</li>\n</ol>\n<table>\n<thead>\n<tr>\n<th><strong>File</strong></th>\n<th><strong>Hash</strong></th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>NTUSER.DAT</td>\n<td>c70ee7615b5c27ab9fee91681da8f4e2</td>\n</tr>\n<tr>\n<td>SAM</td>\n<td>190697abebc5496f9b4eb6adc66d2834</td>\n</tr>\n<tr>\n<td>SOFTWARE</td>\n<td>5b6a904d2e37fe3de2ab98cdc3c46291</td>\n</tr>\n<tr>\n<td>SYSTEM</td>\n<td>e4571e43d4d4b62db9c4dc4f96ab629a</td>\n</tr>\n</tbody>\n</table>\n<ol>\n<li>\n<p><strong>HunterProfileImage folder</strong> includes:</p>\n</li>\n<li>\n<p>Hunter-ProfileImage.ad1 which is the user hunter's whole home directory</p>\n</li>\n<li>\n<p>Hunter-ProfileImage.ad1.csv</p>\n</li>\n<li>\n<p>Hunter-ProfileImage.ad1.txt</p>\n</li>\n</ol>\n<table>\n<thead>\n<tr>\n<th><strong>File</strong></th>\n<th><strong>Hash</strong></th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>Hunter-ProfileImage.ad1</td>\n<td>a9a6a075b9deb8d70dca1ddf313fe055</td>\n</tr>\n<tr>\n<td>Hunter-ProfileImage.ad1.csv</td>\n<td>c02392553aab92362ec9f7f0b05e21cb</td>\n</tr>\n<tr>\n<td>Hunter-ProfileImage.ad1.txt</td>\n<td>23a057157f5d69bed322390ab131aff4</td>\n</tr>\n</tbody>\n</table>\n<h1>Goals</h1>\n<ul>\n<li>\n<p>Use different registry analysis tools to perform Windows Registry investigations</p>\n</li>\n<li>\n<p>Analyze user activity from the registry</p>\n</li>\n<li>\n<p>Check system configurations found in the registry</p>\n</li>\n<li>\n<p>Analyze system time zone information</p>\n</li>\n<li>\n<p>Analyze recently used documents, applications, mounted devices, etc.</p>\n</li>\n<li>\n<p>Gain the ability to analyze the Windows SAM file</p>\n</li>\n<li>\n<p>Gain the ability to analyze UserAssist keys</p>\n</li>\n</ul>\n<h1>What you will learn</h1>\n<ul>\n<li>\n<p>How to use Windows Registry Explorer and RegRipper to Analyze Windows Registry files</p>\n</li>\n<li>\n<p>How to search and locate different artifacts in the Windows Registry</p>\n</li>\n<li>\n<p>How to analyze time zone information and understand the true timezone being used</p>\n</li>\n<li>\n<p>How to analyze network IP Address configurations used by the system</p>\n</li>\n<li>\n<p>How to check for firewall settings and RDP related configurations</p>\n</li>\n<li>\n<p>How to analyze the Windows SAM file to locate users, their SIDs and  RID also groups and other configurations related to user and group management</p>\n</li>\n<li>\n<p>Locate and analyze UserAssist keys to understand what applications and files were used by the user</p>\n</li>\n</ul>\n<h1>Recommended tools</h1>\n<ul>\n<li>\n<p><strong>Windows Registry Explorer</strong></p>\n</li>\n<li>\n<p><strong>DCode</strong></p>\n</li>\n<li>\n<p><strong>Regripper</strong></p>\n</li>\n<li>\n<p><strong>Notepad++</strong></p>\n</li>\n</ul>",
    "tasks": "# Tasks\n\n## TASK 1 - PROFILING THE SYSTEM USED\n\nIn this task, you are required to gather as many footprints as possible that can clearly identify the system and configuration used. You need to identify the system based on the Windows Registry, so you are required to check different registry locations that can help you with your investigation.\n\nAll registry-related evidence can be found at **C:\\\\DFP\\\\Labs\\\\Module6\\\\Lab14\\\\WindowsRegistry**\n\nTo make sure you gathered enough information, you need to answer some questions:\n\n1.  What is the name of the computer?\n\n2.  The forensic image was handed to you with no label about what operating system was running, so make sure you check that.\n\n3.  What is the time zone used by this system and is daylight saving DST active or not? (check your slide notes for help or online resources).\n\n4.  What is the installation date for this system? (hint: use DCode.exe to figure it out).\n\n5.  To whom was this system registered, and what was the system's root directory?\n\n6.  When was this system last shutdown?\n\n7.  Check the system's firewall and see if RDP was enabled or not.\n\n8.  What was the name of the last user that logged into the system?\n\nWe also need information regarding the network, so:\n\n9.  What was the GUID of the active network interface and what is the IP address given to this machine?\n\n10. What was the DHCP Name Server's IP address, and default gateway?\n\n11. When was the leased time obtained, and when will it end?\n\n## TASK 2 - EXPORTING REGISTRY HIVES AND CREATING BOOKMARKS\n\nOne very useful feature of Registry Explorer is the capability of exporting registry hives and even values. Registry hives could be exported into various formats for referencing or analysis using another tool. Bookmarks is another great feature provided by Registry Explorer. This feature can be very useful for future analysis, or if you want to go back to a specific location and check for a key or value.\n\nSo, in this task, all you need to do is get familiar with how to export Windows registry values and how to create Windows Registry Explorer bookmarks for future use.\n\n## TASK 3 - ANALYZING THE WINDOWS REGISTRY: SAM HIVE\n\nIn this task, we need you to start profiling the user based on Registry footprints or artifacts found in the Windows Registry hive named SAM only. To help you organize your analysis, you are required to answer the following questions:\n\n1.  Check how many users this machine has and who are they?\n\n2.  What is the SID and RID of our user of interest?\n\n3.  When was the user's profile created?\n\n4.  Is there any other evidence you can use to validate your answer?\n\n5.  When did he/she last logged into the system?\n\n6.  How many times has he/she logged into the system?\n\n7.  Where could we find his/her password user hint and what is it?\n\n## TASK 4 - PROFILING USER ACTIVITY USING NTUSER.DAT\n\nIn this task, we need you to start profiling the user based on different Windows Registry footprints or artifacts found in different Windows Registry hives, especially the user's profile hive NTUSER.DAT.\n\nTo help you do that, the task has been divided into a couple of sections, each with a different number of questions. Part one will be:\n\n1.  What applications are installed on this machine? (hint: check the location: **SOFTWARE\\\\Microsoft\\\\Windows\\\\CurrentVersion\\\\App Paths**)\n\n2.  While doing the interviewing, one employee mentioned that there could be a remote administration tool (RAT) being used. Do some searching to find that, as they had no idea of the specific application, so try to figure out yourself. Use the Registry Explorer's searching capability to build a list of the most     commonly used RATs. Did you find anything suspicious?\n\n3.  Check the applications that have been set to run at system startup. (hint: this could be done by searching for \"Run\" or \"Runonce\" registry values). How many applications did you find and what are     they?\n\n4.  Is there any suspicious application among them? What is it, and why do you think so?\n\nThe second part would be to check both LastVisitedPidlMRU and OpenSavePidlMRU to understand some of the user's activity related to applications and files. These keys could be found in the NTUSER.DAT hive file. Then answer the questions below. Check the following location inside **NTUDER.DAT**. **\\\\SOFTWARE\\\\Mircosoft\\\\Windows\\\\CurrentVersion\\\\Explorer\\\\ComDlg32\\\\OpenSavePidlMRU**\n\n5.  How many documents did you find and what are they?\n\n6.  Could you identify their locations?\n\n7.  Can you check their content, and is there anything suspicious about them?\n\n8.  Which was the last opened file, and how did you prove that?\n\n9.  Let us check the last opened applications. How many applications did you find, and what are they?\n\n10. Check the RecentDocs that hold subkeys and values for LNK files. What did you find?\n\nThe third part requires you to move on to other questions related to the drives this user accessed or the network shares, etc. So, make sure to check what drives have been mounted on the system. Currently, you are only interested in listing the mounted devices; you will be doing further analysis later on when you get to the USB forensics lab. So go to the location: **SYSTEM\\\\MountedDevices** and then, answer the following questions:\n\n11. How many devices did you find, and do you know what are they?\n\n12. Could you identify their drive letters?\n\nThe final part of this task will be to check the **UserAssist** keys and answer the questions below. These keys can be found in the location: **NTUSER.DAT\\\\SOFTWARE\\\\Microsoft\\\\Windows\\\\CurrentVersion\\\\Explorer\\\\UserAssist**\n\n13. Now, check the UserAssist keys that start with \"CEBFF5CD\" in their GUID and end with \"49EA\". How many entries did you find in the Count subkey?\n\n14. What is the value name of any of the keys found? What encoding (some call it encryption) are they using?\n\n15. What is the software application that was executed the most?\n\n16. Check the software type. What type of software did you find (the nature of their usage)?\n\n17. Now, we want you just to check the entries in the UserAssist subkey that start with \"F4E57C4B\" and end with \"3D9F\". This subkey contains LNK files (shortcuts), more on them in our next lab. For now, just     answer the questions. How many times was the Google Chrome shortcut used?\n\n18. What was the last time he/she used Google Chrome?",
    "tasks_html": "<h1>Tasks</h1>\n<h2>TASK 1 - PROFILING THE SYSTEM USED</h2>\n<p>In this task, you are required to gather as many footprints as possible that can clearly identify the system and configuration used. You need to identify the system based on the Windows Registry, so you are required to check different registry locations that can help you with your investigation.</p>\n<p>All registry-related evidence can be found at <strong>C:\\DFP\\Labs\\Module6\\Lab14\\WindowsRegistry</strong></p>\n<p>To make sure you gathered enough information, you need to answer some questions:</p>\n<ol>\n<li>\n<p>What is the name of the computer?</p>\n</li>\n<li>\n<p>The forensic image was handed to you with no label about what operating system was running, so make sure you check that.</p>\n</li>\n<li>\n<p>What is the time zone used by this system and is daylight saving DST active or not? (check your slide notes for help or online resources).</p>\n</li>\n<li>\n<p>What is the installation date for this system? (hint: use DCode.exe to figure it out).</p>\n</li>\n<li>\n<p>To whom was this system registered, and what was the system's root directory?</p>\n</li>\n<li>\n<p>When was this system last shutdown?</p>\n</li>\n<li>\n<p>Check the system's firewall and see if RDP was enabled or not.</p>\n</li>\n<li>\n<p>What was the name of the last user that logged into the system?</p>\n</li>\n</ol>\n<p>We also need information regarding the network, so:</p>\n<ol>\n<li>\n<p>What was the GUID of the active network interface and what is the IP address given to this machine?</p>\n</li>\n<li>\n<p>What was the DHCP Name Server's IP address, and default gateway?</p>\n</li>\n<li>\n<p>When was the leased time obtained, and when will it end?</p>\n</li>\n</ol>\n<h2>TASK 2 - EXPORTING REGISTRY HIVES AND CREATING BOOKMARKS</h2>\n<p>One very useful feature of Registry Explorer is the capability of exporting registry hives and even values. Registry hives could be exported into various formats for referencing or analysis using another tool. Bookmarks is another great feature provided by Registry Explorer. This feature can be very useful for future analysis, or if you want to go back to a specific location and check for a key or value.</p>\n<p>So, in this task, all you need to do is get familiar with how to export Windows registry values and how to create Windows Registry Explorer bookmarks for future use.</p>\n<h2>TASK 3 - ANALYZING THE WINDOWS REGISTRY: SAM HIVE</h2>\n<p>In this task, we need you to start profiling the user based on Registry footprints or artifacts found in the Windows Registry hive named SAM only. To help you organize your analysis, you are required to answer the following questions:</p>\n<ol>\n<li>\n<p>Check how many users this machine has and who are they?</p>\n</li>\n<li>\n<p>What is the SID and RID of our user of interest?</p>\n</li>\n<li>\n<p>When was the user's profile created?</p>\n</li>\n<li>\n<p>Is there any other evidence you can use to validate your answer?</p>\n</li>\n<li>\n<p>When did he/she last logged into the system?</p>\n</li>\n<li>\n<p>How many times has he/she logged into the system?</p>\n</li>\n<li>\n<p>Where could we find his/her password user hint and what is it?</p>\n</li>\n</ol>\n<h2>TASK 4 - PROFILING USER ACTIVITY USING NTUSER.DAT</h2>\n<p>In this task, we need you to start profiling the user based on different Windows Registry footprints or artifacts found in different Windows Registry hives, especially the user's profile hive NTUSER.DAT.</p>\n<p>To help you do that, the task has been divided into a couple of sections, each with a different number of questions. Part one will be:</p>\n<ol>\n<li>\n<p>What applications are installed on this machine? (hint: check the location: <strong>SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\App Paths</strong>)</p>\n</li>\n<li>\n<p>While doing the interviewing, one employee mentioned that there could be a remote administration tool (RAT) being used. Do some searching to find that, as they had no idea of the specific application, so try to figure out yourself. Use the Registry Explorer's searching capability to build a list of the most     commonly used RATs. Did you find anything suspicious?</p>\n</li>\n<li>\n<p>Check the applications that have been set to run at system startup. (hint: this could be done by searching for \"Run\" or \"Runonce\" registry values). How many applications did you find and what are     they?</p>\n</li>\n<li>\n<p>Is there any suspicious application among them? What is it, and why do you think so?</p>\n</li>\n</ol>\n<p>The second part would be to check both LastVisitedPidlMRU and OpenSavePidlMRU to understand some of the user's activity related to applications and files. These keys could be found in the NTUSER.DAT hive file. Then answer the questions below. Check the following location inside <strong>NTUDER.DAT</strong>. <strong>\\SOFTWARE\\Mircosoft\\Windows\\CurrentVersion\\Explorer\\ComDlg32\\OpenSavePidlMRU</strong></p>\n<ol>\n<li>\n<p>How many documents did you find and what are they?</p>\n</li>\n<li>\n<p>Could you identify their locations?</p>\n</li>\n<li>\n<p>Can you check their content, and is there anything suspicious about them?</p>\n</li>\n<li>\n<p>Which was the last opened file, and how did you prove that?</p>\n</li>\n<li>\n<p>Let us check the last opened applications. How many applications did you find, and what are they?</p>\n</li>\n<li>\n<p>Check the RecentDocs that hold subkeys and values for LNK files. What did you find?</p>\n</li>\n</ol>\n<p>The third part requires you to move on to other questions related to the drives this user accessed or the network shares, etc. So, make sure to check what drives have been mounted on the system. Currently, you are only interested in listing the mounted devices; you will be doing further analysis later on when you get to the USB forensics lab. So go to the location: <strong>SYSTEM\\MountedDevices</strong> and then, answer the following questions:</p>\n<ol>\n<li>\n<p>How many devices did you find, and do you know what are they?</p>\n</li>\n<li>\n<p>Could you identify their drive letters?</p>\n</li>\n</ol>\n<p>The final part of this task will be to check the <strong>UserAssist</strong> keys and answer the questions below. These keys can be found in the location: <strong>NTUSER.DAT\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Explorer\\UserAssist</strong></p>\n<ol>\n<li>\n<p>Now, check the UserAssist keys that start with \"CEBFF5CD\" in their GUID and end with \"49EA\". How many entries did you find in the Count subkey?</p>\n</li>\n<li>\n<p>What is the value name of any of the keys found? What encoding (some call it encryption) are they using?</p>\n</li>\n<li>\n<p>What is the software application that was executed the most?</p>\n</li>\n<li>\n<p>Check the software type. What type of software did you find (the nature of their usage)?</p>\n</li>\n<li>\n<p>Now, we want you just to check the entries in the UserAssist subkey that start with \"F4E57C4B\" and end with \"3D9F\". This subkey contains LNK files (shortcuts), more on them in our next lab. For now, just     answer the questions. How many times was the Google Chrome shortcut used?</p>\n</li>\n<li>\n<p>What was the last time he/she used Google Chrome?</p>\n</li>\n</ol>",
    "published_date": "2020-10-20T15:32:26Z",
    "solutions": "# SOLUTIONS\n\n## TASK 1 - PROFILING THE SYSTEM USED\n\nBefore we start answering the questions, one of the important things to do, if you recall the Windows Registry part of the course, is check the ControlSet. So, in order to analyze the Windows registry correctly, our first check should be to identify what was the active ControlSet.\n\nTo do that, let us first open Windows Registry Explorer, which is the tool that we will use to solve this task. You can find it inside \"**C:\\\\DFP\\\\Tools\\\\Windows\\\\RegistryExplorer_RECmd**\", and then double-click on \"RegistryExplorer.exe.\" After doing that, I assume you got the following:\n\n![1](https://assets.ine.com/content/ptp/lab_14_windows_registry_analysis/1.png)\n\nNow, since we need to know the ControlSet, this key can be found within the Windows SYSTEM registry hive, so we need to load it. Do that by going to **File** **-> Load offline hive** and navigate to the location of the SYSTEM hive (**C:\\\\DFP\\\\Labs\\\\Module6\\\\Lab14\\\\WindowsRegistry**) and press the **Open** button.\n\nAfter doing that, you will get something like the following:\n\n![2](https://assets.ine.com/content/ptp/lab_14_windows_registry_analysis/2.png)\n\nNow you need to expand the first row, and then you need to navigate all the way through **SYSTEM** until you reach the \"**Select**\" key, as seen in the snapshot below.\n\n![3](https://assets.ine.com/content/ptp/lab_14_windows_registry_analysis/3.png)\n\n**Now if we** check the content of the ***Current*** value, we see it holding the value **1**. Now, since we have the ControlSet, we know which direction to steer our investigation wheel inside the SYSTEM keys. Let's move on and start answering some questions.\n\n**[Important note:]** Since we only have one here it's easy, but you if you have more than one, this is a really important step to check before proceeding.\n\n1.  **What is the name of the computer?**\n\n**[Answer:]** \n\nNow, in order to answer that, we need to check for the **ComputerName** value to find the answer. This is easily done by going to **Bookmarks** **-> Common** **-> ComputerName**. If you check the right pane as seen in the snapshot below, you will notice that it is \"4ORENSICS\". \n![4](https://assets.ine.com/content/ptp/lab_14_windows_registry_analysis/4.png)\n\n2.  **The forensic image was handed to you with no label about what operating system was running, so make sure you check that.**\n\n**[Answer:]** This information is very important for us to continue our investigation. Let us check the Operating system version used and other important information. Before we can find this answer, I need you to add the Windows **SOFTWARE** registry to Windows Registry Explorer. After doing that, I need you to navigate to:  \n\n**SOFTWARE\\\\Microsoft\\\\Windows NT\\\\CurrentVersion** \n\nThe table below could help you:\n\n|**Operating System**  |  **Version number**  |\n|-----------------  |---------------------  |\n|Windows 10 and Windows Server 2016  |       10.0   |\n|Windows 8.1 and Windows Server 2012 R2  |   6.3   |\n|Windows 8 and Windows Server 2012   |       6.2   |\n|Windows 7 and Windows Server 2008 R2    |   6.1  |\n|Windows Server 2008 and Windows Vista   |   6.0  |\n\nNow from the **CurrentVersion** value found and based on the table above, we can say that the system we are investigating is a Windows 8.1 or Windows Server 2012 R2, but if you check the value **ProductName**, you will find that we are dealing with a Windows 8.1 Enterprise. All this can be seen in the snapshot below:\n\n![5](https://assets.ine.com/content/ptp/lab_14_windows_registry_analysis/5.png)\n\n**[Note:]** I have removed one of the \"Value Type\" column from the output to make it easier to understand.\n\n3.  **What is the time zone used by this system and is daylight saving DST active or not?**\n\n**[Answer:]** Now, you need to pay attention to what will be done. First, the time zone information could be found by navigating to the location below:\n\n**SYSTEM\\\\ControlSet\\#\\#\\#\\\\Control\\\\TimeZoneInfromation**\n\nAnd since our ControlSet is 1, then the exact location would be:\n\n**SYSTEM\\\\ControlSet001\\\\Control\\\\TimeZoneInfromation**\n\nThe results we found were the following:\n\n![6](https://assets.ine.com/content/ptp/lab_14_windows_registry_analysis/6.png)\n\nThis is the most important value to be used to establish time-related to UTC, and it is the one you need to use to determine whether daylight saving is active or not. Check this reference: <http://kb.digital-detective.net/display/BF/Identification+of+Time+Zone+Settings+on+Suspect+Computer>\n\nSo, based on the ActiveTimeBias value found (420) and the StandardName value (@tzres.dll,-211), we can determine we have a PST8PDT or Pacific Daylight Time or just PDT time zone. If you're wondering where I managed to resolve @tzres.dll,-211 to PDT, then check this:\n\n<https://github.com/log2timeline/plaso/blob/master/plaso/winnt/time_zones.py>\n\nOr\n\n<http://www.nirsoft.net/dll_information/windows8/tzres_dll.html>\n\nNow, is DST active or not? Well, it sure is, and that's because ActiveTimeBias is 420 which when divided by 60 leads to 7 hours. And this means we have a **UTC-7**.\n\n4.  **What is the installation date for this system? (hint: use DCode.exe to figure it out).**\n**[Answer:]** This is found in the snapshot we saw before, let's add it again below:\n\n![7](https://assets.ine.com/content/ptp/lab_14_windows_registry_analysis/7.png)\n\nSo, we have the value 1466498265!\n\nEasy; we can use the DCode.exe tool here present at [C:\\DFP\\Tools\\Time] to convert this number into a timestamp. You can find the tool inside the tools directory. BUT wait a minute! We need to adjust the time using the time zone we just found. So, make sure in the \"Add Bias\" field you select UTC-7 because this is the time zone this computer was working in. Before pressing the Decode button, please keep in mind that Windows uses **Unix 32** bit here for the **InstallDate** value, so make sure you select the \"**Unix: Numeric Value**.\" Finally, enter the value we want to decode, and with that done, we have the following after pressing Decode:\n\n![8](https://assets.ine.com/content/ptp/lab_14_windows_registry_analysis/8.png)\n\nThe answer is:\n\n**Tue, 21 June 2016 01:37:45 -07:00**\n\nThat was easy, right?\n\n5.  **To whom was this system registered, and what was the system's root directory?**\n\n**[Answer:]** This system was registered to a person named \"**Hunter,**\" and the system root directory is **C:\\\\Windows** which could be found from the path below:\n\n**Microsoft\\\\Windows NT\\\\CurrentVersion** \n\nCheck the snapshot below:\n![8.1](https://assets.ine.com/content/ptp/lab_14_windows_registry_analysis/8.1.png)\n\n6. **When was this system last shutdown?**\n\n   Shutdown time is found in: **SYSTEM\\ControlSet001\\Control\\Windows\\ShutdownTime**\n\n   It is a Windows FILETIME (64 bit)\n\n   Answer = 2016-06-21 01:34:49 (UTC)\n\n   Answer = Tue Jun 21 01:34:49 2016 (UTC)\n\n   Answer = Tue Jun 21 08:34:49 2016 (UTC-7/Local Time)\n\n   \n\n   **Extra**: To find the Installation date, we need to check the following: **SAM\\Domains\\Account\\F**\n\n   Offset 8-15 holds value\n\n   It is using Windows FILETIME (64 bit)\n\n   Answer = 2013-08-22 14:45:11 (UTC\ufeff)\n\n   \n\n   **Note**: The InstallDate or other registry keys no longer are valid to use as an Installation date, since they only reflect the time of updates/upgrades/etc/long story short\n\n7. **Check the system's firewall and see if RDP was enabled or not.**\n   **[Answer:]** We should always check the Windows Firewall and Remote Desktop, just in case. The Firewall and Remote Desktop settings are found under:\n\n**SYSTEM\\\\ControlSet\\#\\#\\#\\\\Services\\\\SharedAccess\\\\Parameters\\\\FirewallPolicy**\n\n**SYSTEM\\\\ControlSet\\#\\#\\#\\\\Control\\\\TerminalServer**\n\n\n\nAnd since we are working under ControlSet001, then we need to go here:\n\n**SYSTEM\\\\ControlSet001\\\\Services\\\\SharedAccess\\\\Parameters\\\\FirewallPolicy**\n\n**SYSTEM\\\\ControlSet001\\\\Control\\\\TerminalServer**\n\nMake sure you check the firewall for both profiles (domain and public). If you don't know how to reach that, then we could go to Tools -> Find and then write the keyword you are looking for. You can see that in the snapshot below.\n\n![9](https://assets.ine.com/content/ptp/lab_14_windows_registry_analysis/9.png)\n\nAfter that, all you need to do is double-click on the result you want to display under Windows Registry Explorer. Now from the left-hand pane, we can see after expanding the tree and selecting DomainProfile, that we found the following:\n\n![10](https://assets.ine.com/content/ptp/lab_14_windows_registry_analysis/10.png)\n\nThis clearly says that the firewall is enabled. By checking the PublicProfile, we get this:\n\n![11](https://assets.ine.com/content/ptp/lab_14_windows_registry_analysis/11.png)\n\nAnd again, this means that the firewall is enabled (value 1 here represents true which means it is enabled). \n\nNow, by going to the \"**SYSTEM\\\\ControlSet001\\\\Control\\\\TerminalServer**\" location and checking the **fDenyTSConnection** value, we can determine if RDP is enabled or not. From the value found, we can say that it is true, the RDP is not allowed.\n\n![12](https://assets.ine.com/content/ptp/lab_14_windows_registry_analysis/12.png)\n\n8. **What was the name of the last user that logged into the system?**\n   **[Answer:]** This is the final answer related to general system configurations, after that we'll move on network-related stuff. Again, since we don't know where we could find this information, we could use Registry Explorer's find capabilities (Tools Find) to search for the name of the last logged on user. This could be found in the value \"***LastLoggedOnUser***.\" You can see the results after searching below:\n\n![13](https://assets.ine.com/content/ptp/lab_14_windows_registry_analysis/13.png)\n\nSo, the last user who logged into the system was \"**Hunter,**\" and we could even see his SID (**S-1-5-21-2489440558-2754304563-710705792-1001**). \n\nNow, we need to start answering the questions related to networking stuff, so let's get that done too.\n\n9. **What was the GUID of the active network interface, and what is the IP address given to this machine?**\n\n**[Answer:]** To answer this, I need you to navigate to the following location:  **SYSTEM\\\\ControlSet\\#\\#\\#\\\\Services\\\\Tcpip\\\\Parameters\\\\Interfaces\\\\{GUID}\\\\** \n\nWhich means, in our case:\n**SYSTEM\\\\ControlSet001\\\\Services\\\\Tcpip\\\\Parameters\\\\Interfaces\\\\{GUID}\\ ** \n\nAs we can see from the snapshot below, the GUID for the active interface is: 8CB9FBF6-AE23-4E1C-AA0A-EE23CB4FE736. Which means the full path is: **ControlSet001\\\\Services\\\\Tcpip\\\\Parameters\\\\Interfaces\\\\{8CB9FBF6-AE23-4E1C-AA0A-EE23CB4FE736}** \n\n![14](https://assets.ine.com/content/ptp/lab_14_windows_registry_analysis/14.png)\n \nNow, if you check the values found within that key, you can find that the computer was given an IP Address which was 10.0.2.15 from the DHCP Server which had the IP Address 10.0.2.2, as seen in the figure above.\n\n10. **What was the DHCP Server's IP address, and default gateway?**\n\n**[Answer:]** We answered the DHCP server part in the previous question. Now for the default gateway, we can find it be going down a little in the same page under the value named  \"**DhcpDefaultGateway**.\" The result is also 10.0.2.2 as seen in the figure below: \n\n![15](https://assets.ine.com/content/ptp/lab_14_windows_registry_analysis/15.png)\n\n11. **When was the leased time obtained, and when will it end?**\n    **[Answer:]** Now to check this we need you to be focused a little bit more. We need to check the following values:\n\n-   LeaseObtainedTime\n\n-   Lease\n\n-   LeaseTerminatesTime\n\n ![16](https://assets.ine.com/content/ptp/lab_14_windows_registry_analysis/16.png) \n\nThe first value gives us an answer about what was the leased time for this interface. It shows **1466475852**. To convert it using epoch time, we can use the following website: \n\n <https://www.epochconverter.com/> \n\nGo to the first option \"**Convert epoch to human readable date and vice versa**,\" add the value in the field and click \"**Timestamp to Human date**.\" Now, since we found that this computer has a UTC-7 timestamp or PDT, make sure you click on the GMT URL found at the end of the line saying, \"**Your time zone:**\" to adjust the used  timestamp. It will take you to another page, just search for the -07:00 or PDT to get the following final result: Jun 20 2016 19:24:12 \n\nOr you can go to this page directly: <https://www.epochconverter.com/timezones?q=1466475852&tz=UTC> \n\nSo, based on that, the lease was obtained at \"Jun 20 2016 19:24:12\". \n\nTo check when does this lease terminate, we can either use the value in **LeaseTerminatesTime** and follow the same procedure we did for the lease obtained, or just add the value in Lease to **LeaseObtainedTime**. Another way is to divide that number you found in the Lease which is 86400 by 1440 (seconds per day), and that gives us one day. To conclude, the answer is 1-day. \n\n**[Note:]** you can also check that on the epochconverter website.\n\n## Task 2 - EXPORTING REGISTRY HIVES AND CREATING BOOKMARKS\n\nLet's get this task done quickly as it is very easy thanks to Windows Registry Explorer. In order to export the registry hives into other formats for referencing or analysis using another tool, all you need to do is go to File -> Export \"Registry hives\" and then choose the file format you want. That's it! \n\nNow, in order to create a bookmark, follow the steps below:\n\n1.  To add a bookmark, all you need to do is right-click on the key of interest, and then select \"**Add bookmark**\" or press **F4** on your keyboard.\n\n2.  A menu like the one seen in the figure below will pop-up.\n\n![17](https://assets.ine.com/content/ptp/lab_14_windows_registry_analysis/17.png)\n\n3.  Fill in the fields:\n\n    a.  Category: to what category does this registry entry belong to.\n\n    b.  Name: the name of the registry key.\n\n    c.  Key path: the full path to this registry key.\n\n    d.  Short description: give this bookmark a short description.\n\n    e.  Long description: write full details of this bookmark. For example; what it does, why it is important and stuff like that. Anything that will help an analyst understand its benefit.\n\n4.  When you finish, press the \"**Save**\" button.\n\nNow, to use your new bookmark, all you need to do is select the exact hive that this bookmark belongs to (assuming you closed Registry Explorer, or you navigated to another location), then go to **Bookmarks**  **->  User created** and finally select the one you want.\n\n## Task 3 - Analyzing the Windows Registry: SAM Hive\n\nWe will be solving this task using another tool named **RegRipper** present at [C:\\DFP\\Tools\\Others\\RegRipper2.8-master], so that you know that there are different options to be used out there. So, let us start analyzing the Windows SAM file, to extract user information from there. This will help us with checking different stuff based on his/her SID. I assume you already know how to extract the Windows SAM file from a system, as it is given to us this time, so let us proceed with answering the questions.\n\nTo use RegRipper, all we need to do is load the SAM file, specify a location to store the generated report, and then select the profile required, which is **sam** here. After that, all you need to do is press the **Rip it** button. This could be seen in the snapshot below:\n\n![18](https://assets.ine.com/content/ptp/lab_14_windows_registry_analysis/18.png)\n\nI have attached the generated report to the Appendix of this document, so please check it if you didn't manage to generate one for some reason. Now we can move on and start answering the questions.\n\n1.  **Check how many users does this machine have and who are they?**\n\n**[Answer:]** We have the following:\n\na.  Administrator\n\nb.  Guest\n\nc.  Hunter\n\nBut, please note that the account is disabled for both Administrator and Guest\n\n2.  **What is the SID and RID of our user of interest?**\n\n**[Answer:]** Since both Administrator and Guest are disabled accounts, and since we know our suspect is using the user account named \"Hunter,\" the SID is \"S-1-5-21-2489440558-2754304563-710705792-1001\". This means that his/her RID is \"1001\".\n\n3.  **When was the user's profile created?**\n\n**[Answer:]** It was created on Tue Jun 21 08:37:43 2016.\n\n4.  **Is there any other evidence you can use to validate your answer?**\n\n**[Answer:]** This user is a member of the Administrators group, which means he has administrative privileges. Additionally, the Administrators group last update was \"Tue Jun 21 08:37:43 2016\", which is the exact same time the user account was created and added to that group.\n\n5.  **When did he/she last logged into the system?**\n\n**[Answer:]** The last login that for this user was \"Tue Jun 21 01:42:40 2016\".\n\n6.  **How many times has he/she logged into the system?**\n\n**[Answer:]** From the Login count, we can see that he/she logged into the system 3 times.\n\n7.  **Where could we find his/her password user hint and what is it?**\n\n**[Answer:]** We can find it from the \"Password Hint\" settings, and it was \"What do you do?\".\n\n## Task 4 - PROFILING USER ACTIVITY using NTUSER.DAT\n\nWe have a good base of information about the user of interest, so in this task, we will be chasing other Windows artifacts that could be found in different Windows registry files, especially as we said in the NTUSER.DAT file, which is the file that holds most of the user account's configurations and settings.\n\nIn this task, I am going back to using Eric Zimmerman's Windows Registry Explorer, feel free to use whatever Windows Registry tool you want.\n\nLet us begin answering the questions we have:\n\n1.  **What applications are installed on this machine?**\n\n**[Answer:]** To answer that question, we could check the following location: **SOFTWARE\\\\Microsoft\\\\Windows\\\\CurrentVersion\\\\App Paths**\n\nAfter navigating there, I assume you found a lot of keys there, as seen in the snapshot below:\n\n![19](https://assets.ine.com/content/ptp/lab_14_windows_registry_analysis/19.png)\n\nSo, to form a list we will just need to go through them. I'm going to cheat a little here and use RegRipper and then get the list from there (the results of ripping SOFTWARE using RegRipper is attached as an Appendix to the end of this lab manual).\n\nI assume you found a lot of applications; so I am just going to mention those that are suspicious and leave out the applications that are from Microsoft and others like Java, Python, Adobe Acrobat Reader, Notepad++, 7zip, Google Chrome, etc.\n\n\n\n<u>Those that look suspicious are:</u>\n\na.  BCWipe.exe - C:\\\\Program Files (x86)\\\\Jetico\\\\BCWipe\\\\BCWipe.exe\n\nb.  ccleaner.exe - C:\\\\Program Files\\\\CCleaner\\\\CCleaner64.exe\n\nc.  Wireshark.exe - C:\\\\Program Files\\\\Wireshark\\\\Wireshark.exe\n\nAn investigator must not rely on the \"**App Paths**\" subkeys only. There are lots of applications that won't be listed there! That means further investigation is always vital! For this task, we won't do that, as the aim is just to work with the artifacts in the Windows Registry.\n\n2.  **While doing the interviewing, one employee mentioned that there could be a remote administration tool (RAT) being used. Do some search to find that, as they had no idea of the application in specific, so try to figure out yourself. Use the Registry Explorer's searching capability to build a list of the most commonly used  RATs.** **Did you find anything suspicious?**\n\n**[Answer:]** You have to build a list of tools that could be used to remotely administer a system, so what came in mind here was two things: VNC and TeamViewer. If we add the NTUSER.DAT file to Windows Registry Explorer and search around, we will find the following: \n\n![20](https://assets.ine.com/content/ptp/lab_14_windows_registry_analysis/20.png)\n\nAnd if we double click on the first entry (highlighted in red in the previous snapshot), we will get the following:  \n\n![21](https://assets.ine.com/content/ptp/lab_14_windows_registry_analysis/21.png) \n\nSo, it is clear that the user has used TeamViewer, and maybe this was the RAT tool mentioned to us. Anyway, let's wait a little, we should not stop at this point, as we said; the more evidence, the more bricks we have to build a solid case. We do not have enough information yet. So, let us move on and answer other questions.\n\n3.  **Check the applications that have been set to run at system startup. (hint: this could be done by searching for \"Run\" or \"Runonce\" registry values). How many applications did you find and     what are they?**\n\n**[Answer:]** You can easily answer that by pressing ctrl+F to bring up the search screen, and then use both keywords to search for results, as follows.\n\n![22](https://assets.ine.com/content/ptp/lab_14_windows_registry_analysis/22.png) \n\nI double clicked on each of the entries starting from the first, especially since we do not know what exact value we could find the results in. Windows Registry Explorer comes really handy with its search capabilities in such cases. \n\nNow, double-click on the entry that I've highlighted in the snapshot above in red, and proceed to the next step. \n\nAs you see in the snapshot below, we found Skype, GoogleDrive, and CCleaner! \n\n![23](https://assets.ine.com/content/ptp/lab_14_windows_registry_analysis/23.png)\n\nSo, to answer the question, we found three, and they were: Skype, GoogleDrive, and CCleaner.\n\n4.  **Is there any suspicious application among them? What is it, and why do you think so?**\n\n**[Answer:]** If the company's policy allows Skype, which lots of business environments today do, then, that Skype is okay. The same goes for GoogleDrive. But, for CCleaner? Why would you need that? It could be okay, and it could not be okay. So, I'm going with the hypothesis that CCLeaner isn't okay here.\n\nCheck both **LastVisitedPidlMRU** and **OpenSavePidlMRU** to understand some of the user's activity related to applications and files. These Keys could be found in the NTUSER.DAT hive file. Then, answer the questions below. So, navigate inside **NTUDER.DAT** until you reach:\n\n**\\\\SOFTWARE\\\\Mircosoft\\\\Windows\\\\CurrentVersion\\\\Explorer\\\\ComDlg32\\\\OpenSavePidlMRU**\n\n5.  **How many documents did you find and what are they?**\n\n**[Answer:]** I found two, one .docx file and one .jpg file, as seen in the snapshot below: \n\n![24](https://assets.ine.com/content/ptp/lab_14_windows_registry_analysis/24.png)\n\n6.  **Could you identify their locations?**\n\n**[Answer:]** Yes, they are:\n\n-   My Computer\\\\C:\\\\Users\\\\Hunter\\\\Documets\\\\Welcome.docx\n\n-   My Computer\\\\Documets\\\\home-network-design-networking-for-a-single-family-home-case-house-arkko-1433-x-792.jpg\n\n7.  **Can you check their content, and is there anything suspicious about them?**\n\n**[Answer:]** If we were working on the whole forensic image, then we would have to locate them and then check whether they are suspicious or not. Since we are not working on the whole forensic image in this case and we only have some/parts of it to analyze, we will assume they are suspicious and move on with our investigation.\n\n8.  **Which was the last opened file, and how did you prove that?**\n\n[**Answer**:] The last opened file was the \"Welcome.docx\" file. And the proof is from the \"Opened on\" date, which was \"2016-06-21 12:27:37\".\n\n9.  **Let us check the last opened applications. How many applications did you find, and what are they?**\n\n[**Answer**:] We see only one, which was chrome.exe.\n\n10. **Check the RecentDocs that hold subkeys and values for LNK files. What did you find?**\n\n**[Answer:]** To solve this, we need to go to the following location:\n\n**NTUSER.DAT \\Software \\Microsoft \\Windows \\CurrentVersion \\Explorer\\\\RecentDocs\\ **\n\n\n\nThis is another great location to check for recently used documents and files that is stored within the registry as a subkey. The values inside these subkeys are LNK files that we haven't analyzed yet (you will do so later in the course). For now, just let's just check what we found here, which was:\n\n-   Welcome.docx\n\n-   home-network-design-networking-for-a-single-family-home-case-house-arkko-1433-x-792.jpg\n\n-   Exfil (this was a directory)\n\n-   Exfiltration_Diagram.png\n\n-   dns-exfiltration-using-sqlmap-18-728.jpg\n\nThere seems to be a lot going on this computer!!!\n\n\n\nNow we need to move on to other questions related to the drives this user accessed or network shares etc. So, let us check what drives have been mounted on the system. Currently, we are only interested in listing the mounted devices; we will be doing further analysis later on when we get to the USB forensics lab\n\nLet's navigate to **SYSTEM\\\\MountedDevices** as seen below:\n\n![25](https://assets.ine.com/content/ptp/lab_14_windows_registry_analysis/25.png)\n\n11. **How many devices did you find, and do you know what are they?**\n\n**[Answer:]** We actually found four volumes, which are: \n\\\\??\\\\Volume{32138f1e-3788-11e6-8250-806e6f6e6963} \n\\\\??\\\\Volume{32138f1f-3788-11e6-8250-806e6f6e6963} \n\\\\??\\\\Volume{fb7f938e-37a4-11e6-8254-080027d269d7} \n\\\\??\\\\Volume{fb7f93ec-37a4-11e6-8254-080027d269d7} \n\nWe can't say much here, because we need to do further USB forensics, but what I can say, is there is a C: which is usually used for the operating system, a D: which is used to mount DVD drives, and the E: which could most probably be used to mount USB devices to it.\n\n12. **Could you identify their drive letters?**\n\n**[Answer:]** Yes, they are C:, D:, and E:.\n\nOur final step in this task will be to check the **UserAssist** keys and answer the questions given.\n\nLet's start by navigating to the UserAssist location found within the NTUSER.DAT file:\n\n**NTUSER.DAT\\\\SOFTWARE\\\\Microsoft\\\\Windows\\\\CurrentVersion\\\\Explorer\\\\UserAssist**\n\nThe results could be seen below:\n\n![26](https://assets.ine.com/content/ptp/lab_14_windows_registry_analysis/26.png)\n\n13. **Now, check the UserAssist keys that start with \"CEBFF5CD\" in their GUID and end with \"49EA\". How many entries did you find in the Count subkey?**\n\n**[Answer:]** We found a total of 68 rows.\n\n14. **What is the value name of any of the keys found? What encoding (some call it encryption!!!) are they using?**\n\n**[Answer:]** One sample is \"7P5N40RS-N0SO-4OSP-874N-P0S2R0O9SN8R}\\\\Aznc\\\\mraznc.rkr\" which is  actually the \"Program Name{Program Files}\\\\Nmap\\\\zenmap.exe\" value. Thanks to Windows Registry Explorer, it converts it back automatically for you. \n\nThis isn't encryption, it is only ROT13. More about ROT13 can be found here: <https://en.wikipedia.org/wiki/ROT13>\n\n15. **What is the software application that was executed the most?**\n\n**[Answer:]** If we filter based on the \"Run Counter\" we find that Adobe Acrobat Reader was run 5 times. Anyway, we won't depend on this only, as we could check Prefetch files that we will analyze in the next upcoming labs.\n\n16. **Let us check the software type over there. What type of software did you find (the nature of their usage)?**\n\n**[Answer:]** From the entries, we can see that the user was using a couple of different tools. Zenmap|Nmap for network scanning, Putty for remote administration, Dropbox, and GoogleDrive for maybe sharing files, Readers and Cleaners like CCleaner, and finally even Wiping tools. So, there is a lot, but all depends on the policy at the company and what is allowed and what isn't.\n\n17. **Now I want you just to check the entries in the UserAssist subkey  that start with \"F4E57C4B\" and end with \"3D9F\". This subkey contains LNK files (shortcuts), more on them in our next lab. For now, just answer the questions. How many times was the Google Chrome shortcut used?**\n\n**[Answer:]** It was run 3 times, as you can see in the snapshot below: \n![27](https://assets.ine.com/content/ptp/lab_14_windows_registry_analysis/27.png)\n\n18. **What was the last time he used Google Chrome?**\n\n**[Answer:]** It was last executed on 2016-06-21 01:43:24, but I highly recommend that you also check the prefetch files (we will show you how later on in the course).\n\n## APPENDIX - RegRipper SAM Results for Task 3\n\nsamparse v.20160203\n\n(SAM) Parse SAM file for user & group mbrshp info\n\nUser Information\n\n-------------------------\n\nUsername : Administrator [500]\n\nFull Name :\n\nUser Comment : Built-in account for administering the computer/domain\n\nAccount Type : Default Admin User\n\nAccount Created : Tue Jun 21 08:19:47 2016 Z\n\nName :\n\nLast Login Date : Tue Mar 18 10:20:36 2014 Z\n\nPwd Reset Date : Tue Mar 18 10:20:39 2014 Z\n\nPwd Fail Date : Never\n\nLogin Count : 3\n\n--> Password does not expire\n\n--> Account Disabled\n\n--> Normal user account\n\n\n\nUsername : Guest [501]\n\nFull Name :\n\nUser Comment : Built-in account for guest access to the computer/domain\n\nAccount Type : Default Guest Acct\n\nAccount Created : Tue Jun 21 08:19:47 2016 Z\n\nName :\n\nLast Login Date : Never\n\nPwd Reset Date : Never\n\nPwd Fail Date : Never\n\nLogin Count : 0\n\n--> Password does not expire\n\n--> Account Disabled\n\n--> Password not required\n\n--> Normal user account\n\n\n\nUsername : Hunter [1001]\n\nFull Name :\n\nUser Comment :\n\nAccount Type : Default Admin User\n\nAccount Created : Tue Jun 21 08:37:43 2016 Z\n\nName :\n\nPassword Hint : What do you do?\n\nLast Login Date : Tue Jun 21 01:42:40 2016 Z\n\nPwd Reset Date : Tue Jun 21 08:37:43 2016 Z\n\nPwd Fail Date : Tue Jun 21 12:53:04 2016 Z\n\nLogin Count : 3\n\n--> Password does not expire\n\n--> Password not required\n\n--> Normal user account\n\n\n\nUsername : HomeGroupUser$ [1003]\n\nFull Name : HomeGroupUser$\n\nUser Comment : Built-in account for homegroup access to the computer\n\nAccount Type : Custom Limited Acct\n\nAccount Created : Tue Jun 21 08:40:06 2016 Z\n\nName :\n\nLast Login Date : Never\n\nPwd Reset Date : Tue Jun 21 08:40:06 2016 Z\n\nPwd Fail Date : Never\n\nLogin Count : 0\n\n--> Password does not expire\n\n--> Normal user account\n\n-------------------------\n\nGroup Membership Information\n\n-------------------------\n\nGroup Name : Event Log Readers [0]\n\nLastWrite : Thu Aug 22 14:45:11 2013 Z\n\nGroup Comment : Members of this group can read event logs from local machine\n\nUsers : None\n\n\n\nGroup Name : Guests [1]\n\nLastWrite : Tue Jun 21 08:14:47 2016 Z\n\nGroup Comment : Guests have the same access as members of the Users group by default, except for the Guest account which is further restricted\n\nUsers :\n\nS-1-5-21-2489440558-2754304563-710705792-501\n\n\n\nGroup Name : Network Configuration Operators [0]\n\nLastWrite : Tue Mar 18 09:52:38 2014 Z\n\nGroup Comment : Members in this group can have some administrative privileges to manage configuration of networking features\n\nUsers : None\n\n\n\nGroup Name : Performance Log Users [0]\n\nLastWrite : Thu Aug 22 14:45:11 2013 Z\n\nGroup Comment : Members of this group may schedule logging of performance counters, enable trace providers, and collect event traces both locally and via remote access to this computer\n\nUsers : None\n\n\n\nGroup Name : Hyper-V Administrators [0]\n\nLastWrite : Tue Mar 18 09:52:38 2014 Z\n\nGroup Comment : Members of this group have complete and unrestricted access to all features of Hyper-V.\n\nUsers : None\n\n\n\nGroup Name : IIS_IUSRS [1]\n\nLastWrite : Thu Aug 22 14:45:11 2013 Z\n\nGroup Comment : Built-in group used by Internet Information Services.\n\nUsers :\n\nS-1-5-17\n\n\n\nGroup Name : Backup Operators [0]\n\nLastWrite : Tue Mar 18 09:52:38 2014 Z\n\nGroup Comment : Backup Operators can override security restrictions for the sole purpose of backing up or restoring files\n\nUsers : None\n\n\n\nGroup Name : Users [2]\n\nLastWrite : Tue Jun 21 08:37:43 2016 Z\n\nGroup Comment : Users are prevented from making accidental or intentional system-wide changes and can run most applications\n\nUsers :\n\nS-1-5-4\n\nS-1-5-11\n\n\n\nGroup Name : Access Control Assistance Operators [0]\n\nLastWrite : Tue Mar 18 09:52:38 2014 Z\n\nGroup Comment : Members of this group can remotely query authorization attributes and permissions for resources on this computer.\n\nUsers : None\n\n\n\nGroup Name : Distributed COM Users [0]\n\nLastWrite : Thu Aug 22 14:45:11 2013 Z\n\nGroup Comment : Members are allowed to launch, activate and use Distributed COM objects on this machine.\n\nUsers : None\n\n\n\nGroup Name : Administrators [2]\n\nLastWrite : Tue Jun 21 08:37:43 2016 Z\n\nGroup Comment : Administrators have complete and unrestricted access to the computer/domain\n\nUsers :\n\nS-1-5-21-2489440558-2754304563-710705792-1001\n\nS-1-5-21-2489440558-2754304563-710705792-500\n\n\n\nGroup Name : Power Users [0]\n\nLastWrite : Tue Mar 18 09:52:38 2014 Z\n\nGroup Comment : Power Users are included for backwards compatibility and possess limited administrative powers\n\nUsers : None\n\n\n\nGroup Name : Cryptographic Operators [0]\n\nLastWrite : Tue Mar 18 09:52:38 2014 Z\n\nGroup Comment : Members are authorized to perform cryptographic operations.\n\nUsers : None\n\n\n\nGroup Name : Remote Management Users [0]\n\nLastWrite : Thu Aug 22 14:45:11 2013 Z\n\nGroup Comment : Members of this group can access WMI resources over management protocols (such as WS-Management via the Windows Remote Management service). This applies only to WMI namespaces that grant access to the user.\n\nUsers : None\n\n\n\nGroup Name : Replicator [0]\n\nLastWrite : Tue Mar 18 09:52:38 2014 Z\n\nGroup Comment : Supports file replication in a domain\n\nUsers : None\n\n\n\nGroup Name : Performance Monitor Users [0]\n\nLastWrite : Thu Aug 22 14:45:11 2013 Z\n\nGroup Comment : Members of this group can access performance counter data locally and remotely\n\nUsers : None\n\n\n\nGroup Name : Remote Desktop Users [0]\n\nLastWrite : Tue Mar 18 09:52:38 2014 Z\n\nGroup Comment : Members in this group are granted the right to logon remotely\n\nUsers : None\n\nAnalysis Tips:\n\n- For well-known SIDs, see http://support.microsoft.com/kb/243330\n\n- S-1-5-4 = Interactive\n\n- S-1-5-11 = Authenticated Users\n\n- Correlate the user SIDs to the output of the ProfileList plugin\n\n## APPENDIX - RegRipper SOFTWARE Results for Task 4\n\nNot included due to file size.",
    "solutions_html": "<h1>SOLUTIONS</h1>\n<h2>TASK 1 - PROFILING THE SYSTEM USED</h2>\n<p>Before we start answering the questions, one of the important things to do, if you recall the Windows Registry part of the course, is check the ControlSet. So, in order to analyze the Windows registry correctly, our first check should be to identify what was the active ControlSet.</p>\n<p>To do that, let us first open Windows Registry Explorer, which is the tool that we will use to solve this task. You can find it inside \"<strong>C:\\DFP\\Tools\\Windows\\RegistryExplorer_RECmd</strong>\", and then double-click on \"RegistryExplorer.exe.\" After doing that, I assume you got the following:</p>\n<p><img alt=\"1\" src=\"https://assets.ine.com/content/ptp/lab_14_windows_registry_analysis/1.png\" /></p>\n<p>Now, since we need to know the ControlSet, this key can be found within the Windows SYSTEM registry hive, so we need to load it. Do that by going to <strong>File</strong> <strong>-&gt; Load offline hive</strong> and navigate to the location of the SYSTEM hive (<strong>C:\\DFP\\Labs\\Module6\\Lab14\\WindowsRegistry</strong>) and press the <strong>Open</strong> button.</p>\n<p>After doing that, you will get something like the following:</p>\n<p><img alt=\"2\" src=\"https://assets.ine.com/content/ptp/lab_14_windows_registry_analysis/2.png\" /></p>\n<p>Now you need to expand the first row, and then you need to navigate all the way through <strong>SYSTEM</strong> until you reach the \"<strong>Select</strong>\" key, as seen in the snapshot below.</p>\n<p><img alt=\"3\" src=\"https://assets.ine.com/content/ptp/lab_14_windows_registry_analysis/3.png\" /></p>\n<p><strong>Now if we** check the content of the **<em>Current</em></strong> value, we see it holding the value <strong>1</strong>. Now, since we have the ControlSet, we know which direction to steer our investigation wheel inside the SYSTEM keys. Let's move on and start answering some questions.</p>\n<p><strong>[Important note:]</strong> Since we only have one here it's easy, but you if you have more than one, this is a really important step to check before proceeding.</p>\n<ol>\n<li><strong>What is the name of the computer?</strong></li>\n</ol>\n<p><strong>[Answer:]</strong> </p>\n<p>Now, in order to answer that, we need to check for the <strong>ComputerName</strong> value to find the answer. This is easily done by going to <strong>Bookmarks</strong> <strong>-&gt; Common</strong> <strong>-&gt; ComputerName</strong>. If you check the right pane as seen in the snapshot below, you will notice that it is \"4ORENSICS\". \n<img alt=\"4\" src=\"https://assets.ine.com/content/ptp/lab_14_windows_registry_analysis/4.png\" /></p>\n<ol>\n<li><strong>The forensic image was handed to you with no label about what operating system was running, so make sure you check that.</strong></li>\n</ol>\n<p><strong>[Answer:]</strong> This information is very important for us to continue our investigation. Let us check the Operating system version used and other important information. Before we can find this answer, I need you to add the Windows <strong>SOFTWARE</strong> registry to Windows Registry Explorer. After doing that, I need you to navigate to:  </p>\n<p><strong>SOFTWARE\\Microsoft\\Windows NT\\CurrentVersion</strong> </p>\n<p>The table below could help you:</p>\n<table>\n<thead>\n<tr>\n<th><strong>Operating System</strong></th>\n<th><strong>Version number</strong></th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>Windows 10 and Windows Server 2016</td>\n<td>10.0</td>\n</tr>\n<tr>\n<td>Windows 8.1 and Windows Server 2012 R2</td>\n<td>6.3</td>\n</tr>\n<tr>\n<td>Windows 8 and Windows Server 2012</td>\n<td>6.2</td>\n</tr>\n<tr>\n<td>Windows 7 and Windows Server 2008 R2</td>\n<td>6.1</td>\n</tr>\n<tr>\n<td>Windows Server 2008 and Windows Vista</td>\n<td>6.0</td>\n</tr>\n</tbody>\n</table>\n<p>Now from the <strong>CurrentVersion</strong> value found and based on the table above, we can say that the system we are investigating is a Windows 8.1 or Windows Server 2012 R2, but if you check the value <strong>ProductName</strong>, you will find that we are dealing with a Windows 8.1 Enterprise. All this can be seen in the snapshot below:</p>\n<p><img alt=\"5\" src=\"https://assets.ine.com/content/ptp/lab_14_windows_registry_analysis/5.png\" /></p>\n<p><strong>[Note:]</strong> I have removed one of the \"Value Type\" column from the output to make it easier to understand.</p>\n<ol>\n<li><strong>What is the time zone used by this system and is daylight saving DST active or not?</strong></li>\n</ol>\n<p><strong>[Answer:]</strong> Now, you need to pay attention to what will be done. First, the time zone information could be found by navigating to the location below:</p>\n<p><strong>SYSTEM\\ControlSet###\\Control\\TimeZoneInfromation</strong></p>\n<p>And since our ControlSet is 1, then the exact location would be:</p>\n<p><strong>SYSTEM\\ControlSet001\\Control\\TimeZoneInfromation</strong></p>\n<p>The results we found were the following:</p>\n<p><img alt=\"6\" src=\"https://assets.ine.com/content/ptp/lab_14_windows_registry_analysis/6.png\" /></p>\n<p>This is the most important value to be used to establish time-related to UTC, and it is the one you need to use to determine whether daylight saving is active or not. Check this reference: <a href=\"http://kb.digital-detective.net/display/BF/Identification+of+Time+Zone+Settings+on+Suspect+Computer\">http://kb.digital-detective.net/display/BF/Identification+of+Time+Zone+Settings+on+Suspect+Computer</a></p>\n<p>So, based on the ActiveTimeBias value found (420) and the StandardName value (@tzres.dll,-211), we can determine we have a PST8PDT or Pacific Daylight Time or just PDT time zone. If you're wondering where I managed to resolve @tzres.dll,-211 to PDT, then check this:</p>\n<p><a href=\"https://github.com/log2timeline/plaso/blob/master/plaso/winnt/time_zones.py\">https://github.com/log2timeline/plaso/blob/master/plaso/winnt/time_zones.py</a></p>\n<p>Or</p>\n<p><a href=\"http://www.nirsoft.net/dll_information/windows8/tzres_dll.html\">http://www.nirsoft.net/dll_information/windows8/tzres_dll.html</a></p>\n<p>Now, is DST active or not? Well, it sure is, and that's because ActiveTimeBias is 420 which when divided by 60 leads to 7 hours. And this means we have a <strong>UTC-7</strong>.</p>\n<ol>\n<li><strong>What is the installation date for this system? (hint: use DCode.exe to figure it out).</strong>\n<strong>[Answer:]</strong> This is found in the snapshot we saw before, let's add it again below:</li>\n</ol>\n<p><img alt=\"7\" src=\"https://assets.ine.com/content/ptp/lab_14_windows_registry_analysis/7.png\" /></p>\n<p>So, we have the value 1466498265!</p>\n<p>Easy; we can use the DCode.exe tool here present at [C:\\DFP\\Tools\\Time] to convert this number into a timestamp. You can find the tool inside the tools directory. BUT wait a minute! We need to adjust the time using the time zone we just found. So, make sure in the \"Add Bias\" field you select UTC-7 because this is the time zone this computer was working in. Before pressing the Decode button, please keep in mind that Windows uses <strong>Unix 32</strong> bit here for the <strong>InstallDate</strong> value, so make sure you select the \"<strong>Unix: Numeric Value</strong>.\" Finally, enter the value we want to decode, and with that done, we have the following after pressing Decode:</p>\n<p><img alt=\"8\" src=\"https://assets.ine.com/content/ptp/lab_14_windows_registry_analysis/8.png\" /></p>\n<p>The answer is:</p>\n<p><strong>Tue, 21 June 2016 01:37:45 -07:00</strong></p>\n<p>That was easy, right?</p>\n<ol>\n<li><strong>To whom was this system registered, and what was the system's root directory?</strong></li>\n</ol>\n<p><strong>[Answer:]</strong> This system was registered to a person named \"<strong>Hunter,</strong>\" and the system root directory is <strong>C:\\Windows</strong> which could be found from the path below:</p>\n<p><strong>Microsoft\\Windows NT\\CurrentVersion</strong> </p>\n<p>Check the snapshot below:\n<img alt=\"8.1\" src=\"https://assets.ine.com/content/ptp/lab_14_windows_registry_analysis/8.1.png\" /></p>\n<ol>\n<li><strong>When was this system last shutdown?</strong></li>\n</ol>\n<p>Shutdown time is found in: <strong>SYSTEM\\ControlSet001\\Control\\Windows\\ShutdownTime</strong></p>\n<p>It is a Windows FILETIME (64 bit)</p>\n<p>Answer = 2016-06-21 01:34:49 (UTC)</p>\n<p>Answer = Tue Jun 21 01:34:49 2016 (UTC)</p>\n<p>Answer = Tue Jun 21 08:34:49 2016 (UTC-7/Local Time)</p>\n<p><strong>Extra</strong>: To find the Installation date, we need to check the following: <strong>SAM\\Domains\\Account\\F</strong></p>\n<p>Offset 8-15 holds value</p>\n<p>It is using Windows FILETIME (64 bit)</p>\n<p>Answer = 2013-08-22 14:45:11 (UTC\ufeff)</p>\n<p><strong>Note</strong>: The InstallDate or other registry keys no longer are valid to use as an Installation date, since they only reflect the time of updates/upgrades/etc/long story short</p>\n<ol>\n<li><strong>Check the system's firewall and see if RDP was enabled or not.</strong>\n   <strong>[Answer:]</strong> We should always check the Windows Firewall and Remote Desktop, just in case. The Firewall and Remote Desktop settings are found under:</li>\n</ol>\n<p><strong>SYSTEM\\ControlSet###\\Services\\SharedAccess\\Parameters\\FirewallPolicy</strong></p>\n<p><strong>SYSTEM\\ControlSet###\\Control\\TerminalServer</strong></p>\n<p>And since we are working under ControlSet001, then we need to go here:</p>\n<p><strong>SYSTEM\\ControlSet001\\Services\\SharedAccess\\Parameters\\FirewallPolicy</strong></p>\n<p><strong>SYSTEM\\ControlSet001\\Control\\TerminalServer</strong></p>\n<p>Make sure you check the firewall for both profiles (domain and public). If you don't know how to reach that, then we could go to Tools -&gt; Find and then write the keyword you are looking for. You can see that in the snapshot below.</p>\n<p><img alt=\"9\" src=\"https://assets.ine.com/content/ptp/lab_14_windows_registry_analysis/9.png\" /></p>\n<p>After that, all you need to do is double-click on the result you want to display under Windows Registry Explorer. Now from the left-hand pane, we can see after expanding the tree and selecting DomainProfile, that we found the following:</p>\n<p><img alt=\"10\" src=\"https://assets.ine.com/content/ptp/lab_14_windows_registry_analysis/10.png\" /></p>\n<p>This clearly says that the firewall is enabled. By checking the PublicProfile, we get this:</p>\n<p><img alt=\"11\" src=\"https://assets.ine.com/content/ptp/lab_14_windows_registry_analysis/11.png\" /></p>\n<p>And again, this means that the firewall is enabled (value 1 here represents true which means it is enabled). </p>\n<p>Now, by going to the \"<strong>SYSTEM\\ControlSet001\\Control\\TerminalServer</strong>\" location and checking the <strong>fDenyTSConnection</strong> value, we can determine if RDP is enabled or not. From the value found, we can say that it is true, the RDP is not allowed.</p>\n<p><img alt=\"12\" src=\"https://assets.ine.com/content/ptp/lab_14_windows_registry_analysis/12.png\" /></p>\n<ol>\n<li><strong>What was the name of the last user that logged into the system?**\n   <strong>[Answer:]</strong> This is the final answer related to general system configurations, after that we'll move on network-related stuff. Again, since we don't know where we could find this information, we could use Registry Explorer's find capabilities (Tools Find) to search for the name of the last logged on user. This could be found in the value \"**<em>LastLoggedOnUser</em></strong>.\" You can see the results after searching below:</li>\n</ol>\n<p><img alt=\"13\" src=\"https://assets.ine.com/content/ptp/lab_14_windows_registry_analysis/13.png\" /></p>\n<p>So, the last user who logged into the system was \"<strong>Hunter,</strong>\" and we could even see his SID (<strong>S-1-5-21-2489440558-2754304563-710705792-1001</strong>). </p>\n<p>Now, we need to start answering the questions related to networking stuff, so let's get that done too.</p>\n<ol>\n<li><strong>What was the GUID of the active network interface, and what is the IP address given to this machine?</strong></li>\n</ol>\n<p><strong>[Answer:]</strong> To answer this, I need you to navigate to the following location:  <strong>SYSTEM\\ControlSet###\\Services\\Tcpip\\Parameters\\Interfaces\\{GUID}\\</strong> </p>\n<p>Which means, in our case:\n*<em>SYSTEM\\ControlSet001\\Services\\Tcpip\\Parameters\\Interfaces\\{GUID}\\ *</em> </p>\n<p>As we can see from the snapshot below, the GUID for the active interface is: 8CB9FBF6-AE23-4E1C-AA0A-EE23CB4FE736. Which means the full path is: <strong>ControlSet001\\Services\\Tcpip\\Parameters\\Interfaces\\{8CB9FBF6-AE23-4E1C-AA0A-EE23CB4FE736}</strong> </p>\n<p><img alt=\"14\" src=\"https://assets.ine.com/content/ptp/lab_14_windows_registry_analysis/14.png\" /></p>\n<p>Now, if you check the values found within that key, you can find that the computer was given an IP Address which was 10.0.2.15 from the DHCP Server which had the IP Address 10.0.2.2, as seen in the figure above.</p>\n<ol>\n<li><strong>What was the DHCP Server's IP address, and default gateway?</strong></li>\n</ol>\n<p><strong>[Answer:]</strong> We answered the DHCP server part in the previous question. Now for the default gateway, we can find it be going down a little in the same page under the value named  \"<strong>DhcpDefaultGateway</strong>.\" The result is also 10.0.2.2 as seen in the figure below: </p>\n<p><img alt=\"15\" src=\"https://assets.ine.com/content/ptp/lab_14_windows_registry_analysis/15.png\" /></p>\n<ol>\n<li>\n<p><strong>When was the leased time obtained, and when will it end?</strong>\n    <strong>[Answer:]</strong> Now to check this we need you to be focused a little bit more. We need to check the following values:</p>\n</li>\n<li>\n<p>LeaseObtainedTime</p>\n</li>\n<li>\n<p>Lease</p>\n</li>\n<li>\n<p>LeaseTerminatesTime</p>\n</li>\n</ol>\n<p><img alt=\"16\" src=\"https://assets.ine.com/content/ptp/lab_14_windows_registry_analysis/16.png\" /> </p>\n<p>The first value gives us an answer about what was the leased time for this interface. It shows <strong>1466475852</strong>. To convert it using epoch time, we can use the following website: </p>\n<p><a href=\"https://www.epochconverter.com/\">https://www.epochconverter.com/</a> </p>\n<p>Go to the first option \"<strong>Convert epoch to human readable date and vice versa</strong>,\" add the value in the field and click \"<strong>Timestamp to Human date</strong>.\" Now, since we found that this computer has a UTC-7 timestamp or PDT, make sure you click on the GMT URL found at the end of the line saying, \"<strong>Your time zone:</strong>\" to adjust the used  timestamp. It will take you to another page, just search for the -07:00 or PDT to get the following final result: Jun 20 2016 19:24:12 </p>\n<p>Or you can go to this page directly: <a href=\"https://www.epochconverter.com/timezones?q=1466475852&amp;tz=UTC\">https://www.epochconverter.com/timezones?q=1466475852&amp;tz=UTC</a> </p>\n<p>So, based on that, the lease was obtained at \"Jun 20 2016 19:24:12\". </p>\n<p>To check when does this lease terminate, we can either use the value in <strong>LeaseTerminatesTime</strong> and follow the same procedure we did for the lease obtained, or just add the value in Lease to <strong>LeaseObtainedTime</strong>. Another way is to divide that number you found in the Lease which is 86400 by 1440 (seconds per day), and that gives us one day. To conclude, the answer is 1-day. </p>\n<p><strong>[Note:]</strong> you can also check that on the epochconverter website.</p>\n<h2>Task 2 - EXPORTING REGISTRY HIVES AND CREATING BOOKMARKS</h2>\n<p>Let's get this task done quickly as it is very easy thanks to Windows Registry Explorer. In order to export the registry hives into other formats for referencing or analysis using another tool, all you need to do is go to File -&gt; Export \"Registry hives\" and then choose the file format you want. That's it! </p>\n<p>Now, in order to create a bookmark, follow the steps below:</p>\n<ol>\n<li>\n<p>To add a bookmark, all you need to do is right-click on the key of interest, and then select \"<strong>Add bookmark</strong>\" or press <strong>F4</strong> on your keyboard.</p>\n</li>\n<li>\n<p>A menu like the one seen in the figure below will pop-up.</p>\n</li>\n</ol>\n<p><img alt=\"17\" src=\"https://assets.ine.com/content/ptp/lab_14_windows_registry_analysis/17.png\" /></p>\n<ol>\n<li>\n<p>Fill in the fields:</p>\n<p>a.  Category: to what category does this registry entry belong to.</p>\n<p>b.  Name: the name of the registry key.</p>\n<p>c.  Key path: the full path to this registry key.</p>\n<p>d.  Short description: give this bookmark a short description.</p>\n<p>e.  Long description: write full details of this bookmark. For example; what it does, why it is important and stuff like that. Anything that will help an analyst understand its benefit.</p>\n</li>\n<li>\n<p>When you finish, press the \"<strong>Save</strong>\" button.</p>\n</li>\n</ol>\n<p>Now, to use your new bookmark, all you need to do is select the exact hive that this bookmark belongs to (assuming you closed Registry Explorer, or you navigated to another location), then go to <strong>Bookmarks</strong>  <strong>-&gt;  User created</strong> and finally select the one you want.</p>\n<h2>Task 3 - Analyzing the Windows Registry: SAM Hive</h2>\n<p>We will be solving this task using another tool named <strong>RegRipper</strong> present at [C:\\DFP\\Tools\\Others\\RegRipper2.8-master], so that you know that there are different options to be used out there. So, let us start analyzing the Windows SAM file, to extract user information from there. This will help us with checking different stuff based on his/her SID. I assume you already know how to extract the Windows SAM file from a system, as it is given to us this time, so let us proceed with answering the questions.</p>\n<p>To use RegRipper, all we need to do is load the SAM file, specify a location to store the generated report, and then select the profile required, which is <strong>sam</strong> here. After that, all you need to do is press the <strong>Rip it</strong> button. This could be seen in the snapshot below:</p>\n<p><img alt=\"18\" src=\"https://assets.ine.com/content/ptp/lab_14_windows_registry_analysis/18.png\" /></p>\n<p>I have attached the generated report to the Appendix of this document, so please check it if you didn't manage to generate one for some reason. Now we can move on and start answering the questions.</p>\n<ol>\n<li><strong>Check how many users does this machine have and who are they?</strong></li>\n</ol>\n<p><strong>[Answer:]</strong> We have the following:</p>\n<p>a.  Administrator</p>\n<p>b.  Guest</p>\n<p>c.  Hunter</p>\n<p>But, please note that the account is disabled for both Administrator and Guest</p>\n<ol>\n<li><strong>What is the SID and RID of our user of interest?</strong></li>\n</ol>\n<p><strong>[Answer:]</strong> Since both Administrator and Guest are disabled accounts, and since we know our suspect is using the user account named \"Hunter,\" the SID is \"S-1-5-21-2489440558-2754304563-710705792-1001\". This means that his/her RID is \"1001\".</p>\n<ol>\n<li><strong>When was the user's profile created?</strong></li>\n</ol>\n<p><strong>[Answer:]</strong> It was created on Tue Jun 21 08:37:43 2016.</p>\n<ol>\n<li><strong>Is there any other evidence you can use to validate your answer?</strong></li>\n</ol>\n<p><strong>[Answer:]</strong> This user is a member of the Administrators group, which means he has administrative privileges. Additionally, the Administrators group last update was \"Tue Jun 21 08:37:43 2016\", which is the exact same time the user account was created and added to that group.</p>\n<ol>\n<li><strong>When did he/she last logged into the system?</strong></li>\n</ol>\n<p><strong>[Answer:]</strong> The last login that for this user was \"Tue Jun 21 01:42:40 2016\".</p>\n<ol>\n<li><strong>How many times has he/she logged into the system?</strong></li>\n</ol>\n<p><strong>[Answer:]</strong> From the Login count, we can see that he/she logged into the system 3 times.</p>\n<ol>\n<li><strong>Where could we find his/her password user hint and what is it?</strong></li>\n</ol>\n<p><strong>[Answer:]</strong> We can find it from the \"Password Hint\" settings, and it was \"What do you do?\".</p>\n<h2>Task 4 - PROFILING USER ACTIVITY using NTUSER.DAT</h2>\n<p>We have a good base of information about the user of interest, so in this task, we will be chasing other Windows artifacts that could be found in different Windows registry files, especially as we said in the NTUSER.DAT file, which is the file that holds most of the user account's configurations and settings.</p>\n<p>In this task, I am going back to using Eric Zimmerman's Windows Registry Explorer, feel free to use whatever Windows Registry tool you want.</p>\n<p>Let us begin answering the questions we have:</p>\n<ol>\n<li><strong>What applications are installed on this machine?</strong></li>\n</ol>\n<p><strong>[Answer:]</strong> To answer that question, we could check the following location: <strong>SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\App Paths</strong></p>\n<p>After navigating there, I assume you found a lot of keys there, as seen in the snapshot below:</p>\n<p><img alt=\"19\" src=\"https://assets.ine.com/content/ptp/lab_14_windows_registry_analysis/19.png\" /></p>\n<p>So, to form a list we will just need to go through them. I'm going to cheat a little here and use RegRipper and then get the list from there (the results of ripping SOFTWARE using RegRipper is attached as an Appendix to the end of this lab manual).</p>\n<p>I assume you found a lot of applications; so I am just going to mention those that are suspicious and leave out the applications that are from Microsoft and others like Java, Python, Adobe Acrobat Reader, Notepad++, 7zip, Google Chrome, etc.</p>\n<p><u>Those that look suspicious are:</u></p>\n<p>a.  BCWipe.exe - C:\\Program Files (x86)\\Jetico\\BCWipe\\BCWipe.exe</p>\n<p>b.  ccleaner.exe - C:\\Program Files\\CCleaner\\CCleaner64.exe</p>\n<p>c.  Wireshark.exe - C:\\Program Files\\Wireshark\\Wireshark.exe</p>\n<p>An investigator must not rely on the \"<strong>App Paths</strong>\" subkeys only. There are lots of applications that won't be listed there! That means further investigation is always vital! For this task, we won't do that, as the aim is just to work with the artifacts in the Windows Registry.</p>\n<ol>\n<li><strong>While doing the interviewing, one employee mentioned that there could be a remote administration tool (RAT) being used. Do some search to find that, as they had no idea of the application in specific, so try to figure out yourself. Use the Registry Explorer's searching capability to build a list of the most commonly used  RATs.</strong> <strong>Did you find anything suspicious?</strong></li>\n</ol>\n<p><strong>[Answer:]</strong> You have to build a list of tools that could be used to remotely administer a system, so what came in mind here was two things: VNC and TeamViewer. If we add the NTUSER.DAT file to Windows Registry Explorer and search around, we will find the following: </p>\n<p><img alt=\"20\" src=\"https://assets.ine.com/content/ptp/lab_14_windows_registry_analysis/20.png\" /></p>\n<p>And if we double click on the first entry (highlighted in red in the previous snapshot), we will get the following:  </p>\n<p><img alt=\"21\" src=\"https://assets.ine.com/content/ptp/lab_14_windows_registry_analysis/21.png\" /> </p>\n<p>So, it is clear that the user has used TeamViewer, and maybe this was the RAT tool mentioned to us. Anyway, let's wait a little, we should not stop at this point, as we said; the more evidence, the more bricks we have to build a solid case. We do not have enough information yet. So, let us move on and answer other questions.</p>\n<ol>\n<li><strong>Check the applications that have been set to run at system startup. (hint: this could be done by searching for \"Run\" or \"Runonce\" registry values). How many applications did you find and     what are they?</strong></li>\n</ol>\n<p><strong>[Answer:]</strong> You can easily answer that by pressing ctrl+F to bring up the search screen, and then use both keywords to search for results, as follows.</p>\n<p><img alt=\"22\" src=\"https://assets.ine.com/content/ptp/lab_14_windows_registry_analysis/22.png\" /> </p>\n<p>I double clicked on each of the entries starting from the first, especially since we do not know what exact value we could find the results in. Windows Registry Explorer comes really handy with its search capabilities in such cases. </p>\n<p>Now, double-click on the entry that I've highlighted in the snapshot above in red, and proceed to the next step. </p>\n<p>As you see in the snapshot below, we found Skype, GoogleDrive, and CCleaner! </p>\n<p><img alt=\"23\" src=\"https://assets.ine.com/content/ptp/lab_14_windows_registry_analysis/23.png\" /></p>\n<p>So, to answer the question, we found three, and they were: Skype, GoogleDrive, and CCleaner.</p>\n<ol>\n<li><strong>Is there any suspicious application among them? What is it, and why do you think so?</strong></li>\n</ol>\n<p><strong>[Answer:]</strong> If the company's policy allows Skype, which lots of business environments today do, then, that Skype is okay. The same goes for GoogleDrive. But, for CCleaner? Why would you need that? It could be okay, and it could not be okay. So, I'm going with the hypothesis that CCLeaner isn't okay here.</p>\n<p>Check both <strong>LastVisitedPidlMRU</strong> and <strong>OpenSavePidlMRU</strong> to understand some of the user's activity related to applications and files. These Keys could be found in the NTUSER.DAT hive file. Then, answer the questions below. So, navigate inside <strong>NTUDER.DAT</strong> until you reach:</p>\n<p><strong>\\SOFTWARE\\Mircosoft\\Windows\\CurrentVersion\\Explorer\\ComDlg32\\OpenSavePidlMRU</strong></p>\n<ol>\n<li><strong>How many documents did you find and what are they?</strong></li>\n</ol>\n<p><strong>[Answer:]</strong> I found two, one .docx file and one .jpg file, as seen in the snapshot below: </p>\n<p><img alt=\"24\" src=\"https://assets.ine.com/content/ptp/lab_14_windows_registry_analysis/24.png\" /></p>\n<ol>\n<li><strong>Could you identify their locations?</strong></li>\n</ol>\n<p><strong>[Answer:]</strong> Yes, they are:</p>\n<ul>\n<li>\n<p>My Computer\\C:\\Users\\Hunter\\Documets\\Welcome.docx</p>\n</li>\n<li>\n<p>My Computer\\Documets\\home-network-design-networking-for-a-single-family-home-case-house-arkko-1433-x-792.jpg</p>\n</li>\n<li>\n<p><strong>Can you check their content, and is there anything suspicious about them?</strong></p>\n</li>\n</ul>\n<p><strong>[Answer:]</strong> If we were working on the whole forensic image, then we would have to locate them and then check whether they are suspicious or not. Since we are not working on the whole forensic image in this case and we only have some/parts of it to analyze, we will assume they are suspicious and move on with our investigation.</p>\n<ol>\n<li><strong>Which was the last opened file, and how did you prove that?</strong></li>\n</ol>\n<p>[<strong>Answer</strong>:] The last opened file was the \"Welcome.docx\" file. And the proof is from the \"Opened on\" date, which was \"2016-06-21 12:27:37\".</p>\n<ol>\n<li><strong>Let us check the last opened applications. How many applications did you find, and what are they?</strong></li>\n</ol>\n<p>[<strong>Answer</strong>:] We see only one, which was chrome.exe.</p>\n<ol>\n<li><strong>Check the RecentDocs that hold subkeys and values for LNK files. What did you find?</strong></li>\n</ol>\n<p><strong>[Answer:]</strong> To solve this, we need to go to the following location:</p>\n<p>*<em>NTUSER.DAT \\Software \\Microsoft \\Windows \\CurrentVersion \\Explorer\\RecentDocs\\ *</em></p>\n<p>This is another great location to check for recently used documents and files that is stored within the registry as a subkey. The values inside these subkeys are LNK files that we haven't analyzed yet (you will do so later in the course). For now, just let's just check what we found here, which was:</p>\n<ul>\n<li>\n<p>Welcome.docx</p>\n</li>\n<li>\n<p>home-network-design-networking-for-a-single-family-home-case-house-arkko-1433-x-792.jpg</p>\n</li>\n<li>\n<p>Exfil (this was a directory)</p>\n</li>\n<li>\n<p>Exfiltration_Diagram.png</p>\n</li>\n<li>\n<p>dns-exfiltration-using-sqlmap-18-728.jpg</p>\n</li>\n</ul>\n<p>There seems to be a lot going on this computer!!!</p>\n<p>Now we need to move on to other questions related to the drives this user accessed or network shares etc. So, let us check what drives have been mounted on the system. Currently, we are only interested in listing the mounted devices; we will be doing further analysis later on when we get to the USB forensics lab</p>\n<p>Let's navigate to <strong>SYSTEM\\MountedDevices</strong> as seen below:</p>\n<p><img alt=\"25\" src=\"https://assets.ine.com/content/ptp/lab_14_windows_registry_analysis/25.png\" /></p>\n<ol>\n<li><strong>How many devices did you find, and do you know what are they?</strong></li>\n</ol>\n<p><strong>[Answer:]</strong> We actually found four volumes, which are: \n\\??\\Volume{32138f1e-3788-11e6-8250-806e6f6e6963} \n\\??\\Volume{32138f1f-3788-11e6-8250-806e6f6e6963} \n\\??\\Volume{fb7f938e-37a4-11e6-8254-080027d269d7} \n\\??\\Volume{fb7f93ec-37a4-11e6-8254-080027d269d7} </p>\n<p>We can't say much here, because we need to do further USB forensics, but what I can say, is there is a C: which is usually used for the operating system, a D: which is used to mount DVD drives, and the E: which could most probably be used to mount USB devices to it.</p>\n<ol>\n<li><strong>Could you identify their drive letters?</strong></li>\n</ol>\n<p><strong>[Answer:]</strong> Yes, they are C:, D:, and E:.</p>\n<p>Our final step in this task will be to check the <strong>UserAssist</strong> keys and answer the questions given.</p>\n<p>Let's start by navigating to the UserAssist location found within the NTUSER.DAT file:</p>\n<p><strong>NTUSER.DAT\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Explorer\\UserAssist</strong></p>\n<p>The results could be seen below:</p>\n<p><img alt=\"26\" src=\"https://assets.ine.com/content/ptp/lab_14_windows_registry_analysis/26.png\" /></p>\n<ol>\n<li><strong>Now, check the UserAssist keys that start with \"CEBFF5CD\" in their GUID and end with \"49EA\". How many entries did you find in the Count subkey?</strong></li>\n</ol>\n<p><strong>[Answer:]</strong> We found a total of 68 rows.</p>\n<ol>\n<li><strong>What is the value name of any of the keys found? What encoding (some call it encryption!!!) are they using?</strong></li>\n</ol>\n<p><strong>[Answer:]</strong> One sample is \"7P5N40RS-N0SO-4OSP-874N-P0S2R0O9SN8R}\\Aznc\\mraznc.rkr\" which is  actually the \"Program Name{Program Files}\\Nmap\\zenmap.exe\" value. Thanks to Windows Registry Explorer, it converts it back automatically for you. </p>\n<p>This isn't encryption, it is only ROT13. More about ROT13 can be found here: <a href=\"https://en.wikipedia.org/wiki/ROT13\">https://en.wikipedia.org/wiki/ROT13</a></p>\n<ol>\n<li><strong>What is the software application that was executed the most?</strong></li>\n</ol>\n<p><strong>[Answer:]</strong> If we filter based on the \"Run Counter\" we find that Adobe Acrobat Reader was run 5 times. Anyway, we won't depend on this only, as we could check Prefetch files that we will analyze in the next upcoming labs.</p>\n<ol>\n<li><strong>Let us check the software type over there. What type of software did you find (the nature of their usage)?</strong></li>\n</ol>\n<p><strong>[Answer:]</strong> From the entries, we can see that the user was using a couple of different tools. Zenmap|Nmap for network scanning, Putty for remote administration, Dropbox, and GoogleDrive for maybe sharing files, Readers and Cleaners like CCleaner, and finally even Wiping tools. So, there is a lot, but all depends on the policy at the company and what is allowed and what isn't.</p>\n<ol>\n<li><strong>Now I want you just to check the entries in the UserAssist subkey  that start with \"F4E57C4B\" and end with \"3D9F\". This subkey contains LNK files (shortcuts), more on them in our next lab. For now, just answer the questions. How many times was the Google Chrome shortcut used?</strong></li>\n</ol>\n<p><strong>[Answer:]</strong> It was run 3 times, as you can see in the snapshot below: \n<img alt=\"27\" src=\"https://assets.ine.com/content/ptp/lab_14_windows_registry_analysis/27.png\" /></p>\n<ol>\n<li><strong>What was the last time he used Google Chrome?</strong></li>\n</ol>\n<p><strong>[Answer:]</strong> It was last executed on 2016-06-21 01:43:24, but I highly recommend that you also check the prefetch files (we will show you how later on in the course).</p>\n<h2>APPENDIX - RegRipper SAM Results for Task 3</h2>\n<p>samparse v.20160203</p>\n<p>(SAM) Parse SAM file for user &amp; group mbrshp info</p>\n<p>User Information</p>\n<hr />\n<p>Username : Administrator [500]</p>\n<p>Full Name :</p>\n<p>User Comment : Built-in account for administering the computer/domain</p>\n<p>Account Type : Default Admin User</p>\n<p>Account Created : Tue Jun 21 08:19:47 2016 Z</p>\n<p>Name :</p>\n<p>Last Login Date : Tue Mar 18 10:20:36 2014 Z</p>\n<p>Pwd Reset Date : Tue Mar 18 10:20:39 2014 Z</p>\n<p>Pwd Fail Date : Never</p>\n<p>Login Count : 3</p>\n<p>--&gt; Password does not expire</p>\n<p>--&gt; Account Disabled</p>\n<p>--&gt; Normal user account</p>\n<p>Username : Guest [501]</p>\n<p>Full Name :</p>\n<p>User Comment : Built-in account for guest access to the computer/domain</p>\n<p>Account Type : Default Guest Acct</p>\n<p>Account Created : Tue Jun 21 08:19:47 2016 Z</p>\n<p>Name :</p>\n<p>Last Login Date : Never</p>\n<p>Pwd Reset Date : Never</p>\n<p>Pwd Fail Date : Never</p>\n<p>Login Count : 0</p>\n<p>--&gt; Password does not expire</p>\n<p>--&gt; Account Disabled</p>\n<p>--&gt; Password not required</p>\n<p>--&gt; Normal user account</p>\n<p>Username : Hunter [1001]</p>\n<p>Full Name :</p>\n<p>User Comment :</p>\n<p>Account Type : Default Admin User</p>\n<p>Account Created : Tue Jun 21 08:37:43 2016 Z</p>\n<p>Name :</p>\n<p>Password Hint : What do you do?</p>\n<p>Last Login Date : Tue Jun 21 01:42:40 2016 Z</p>\n<p>Pwd Reset Date : Tue Jun 21 08:37:43 2016 Z</p>\n<p>Pwd Fail Date : Tue Jun 21 12:53:04 2016 Z</p>\n<p>Login Count : 3</p>\n<p>--&gt; Password does not expire</p>\n<p>--&gt; Password not required</p>\n<p>--&gt; Normal user account</p>\n<p>Username : HomeGroupUser$ [1003]</p>\n<p>Full Name : HomeGroupUser$</p>\n<p>User Comment : Built-in account for homegroup access to the computer</p>\n<p>Account Type : Custom Limited Acct</p>\n<p>Account Created : Tue Jun 21 08:40:06 2016 Z</p>\n<p>Name :</p>\n<p>Last Login Date : Never</p>\n<p>Pwd Reset Date : Tue Jun 21 08:40:06 2016 Z</p>\n<p>Pwd Fail Date : Never</p>\n<p>Login Count : 0</p>\n<p>--&gt; Password does not expire</p>\n<p>--&gt; Normal user account</p>\n<hr />\n<p>Group Membership Information</p>\n<hr />\n<p>Group Name : Event Log Readers [0]</p>\n<p>LastWrite : Thu Aug 22 14:45:11 2013 Z</p>\n<p>Group Comment : Members of this group can read event logs from local machine</p>\n<p>Users : None</p>\n<p>Group Name : Guests [1]</p>\n<p>LastWrite : Tue Jun 21 08:14:47 2016 Z</p>\n<p>Group Comment : Guests have the same access as members of the Users group by default, except for the Guest account which is further restricted</p>\n<p>Users :</p>\n<p>S-1-5-21-2489440558-2754304563-710705792-501</p>\n<p>Group Name : Network Configuration Operators [0]</p>\n<p>LastWrite : Tue Mar 18 09:52:38 2014 Z</p>\n<p>Group Comment : Members in this group can have some administrative privileges to manage configuration of networking features</p>\n<p>Users : None</p>\n<p>Group Name : Performance Log Users [0]</p>\n<p>LastWrite : Thu Aug 22 14:45:11 2013 Z</p>\n<p>Group Comment : Members of this group may schedule logging of performance counters, enable trace providers, and collect event traces both locally and via remote access to this computer</p>\n<p>Users : None</p>\n<p>Group Name : Hyper-V Administrators [0]</p>\n<p>LastWrite : Tue Mar 18 09:52:38 2014 Z</p>\n<p>Group Comment : Members of this group have complete and unrestricted access to all features of Hyper-V.</p>\n<p>Users : None</p>\n<p>Group Name : IIS_IUSRS [1]</p>\n<p>LastWrite : Thu Aug 22 14:45:11 2013 Z</p>\n<p>Group Comment : Built-in group used by Internet Information Services.</p>\n<p>Users :</p>\n<p>S-1-5-17</p>\n<p>Group Name : Backup Operators [0]</p>\n<p>LastWrite : Tue Mar 18 09:52:38 2014 Z</p>\n<p>Group Comment : Backup Operators can override security restrictions for the sole purpose of backing up or restoring files</p>\n<p>Users : None</p>\n<p>Group Name : Users [2]</p>\n<p>LastWrite : Tue Jun 21 08:37:43 2016 Z</p>\n<p>Group Comment : Users are prevented from making accidental or intentional system-wide changes and can run most applications</p>\n<p>Users :</p>\n<p>S-1-5-4</p>\n<p>S-1-5-11</p>\n<p>Group Name : Access Control Assistance Operators [0]</p>\n<p>LastWrite : Tue Mar 18 09:52:38 2014 Z</p>\n<p>Group Comment : Members of this group can remotely query authorization attributes and permissions for resources on this computer.</p>\n<p>Users : None</p>\n<p>Group Name : Distributed COM Users [0]</p>\n<p>LastWrite : Thu Aug 22 14:45:11 2013 Z</p>\n<p>Group Comment : Members are allowed to launch, activate and use Distributed COM objects on this machine.</p>\n<p>Users : None</p>\n<p>Group Name : Administrators [2]</p>\n<p>LastWrite : Tue Jun 21 08:37:43 2016 Z</p>\n<p>Group Comment : Administrators have complete and unrestricted access to the computer/domain</p>\n<p>Users :</p>\n<p>S-1-5-21-2489440558-2754304563-710705792-1001</p>\n<p>S-1-5-21-2489440558-2754304563-710705792-500</p>\n<p>Group Name : Power Users [0]</p>\n<p>LastWrite : Tue Mar 18 09:52:38 2014 Z</p>\n<p>Group Comment : Power Users are included for backwards compatibility and possess limited administrative powers</p>\n<p>Users : None</p>\n<p>Group Name : Cryptographic Operators [0]</p>\n<p>LastWrite : Tue Mar 18 09:52:38 2014 Z</p>\n<p>Group Comment : Members are authorized to perform cryptographic operations.</p>\n<p>Users : None</p>\n<p>Group Name : Remote Management Users [0]</p>\n<p>LastWrite : Thu Aug 22 14:45:11 2013 Z</p>\n<p>Group Comment : Members of this group can access WMI resources over management protocols (such as WS-Management via the Windows Remote Management service). This applies only to WMI namespaces that grant access to the user.</p>\n<p>Users : None</p>\n<p>Group Name : Replicator [0]</p>\n<p>LastWrite : Tue Mar 18 09:52:38 2014 Z</p>\n<p>Group Comment : Supports file replication in a domain</p>\n<p>Users : None</p>\n<p>Group Name : Performance Monitor Users [0]</p>\n<p>LastWrite : Thu Aug 22 14:45:11 2013 Z</p>\n<p>Group Comment : Members of this group can access performance counter data locally and remotely</p>\n<p>Users : None</p>\n<p>Group Name : Remote Desktop Users [0]</p>\n<p>LastWrite : Tue Mar 18 09:52:38 2014 Z</p>\n<p>Group Comment : Members in this group are granted the right to logon remotely</p>\n<p>Users : None</p>\n<p>Analysis Tips:</p>\n<ul>\n<li>\n<p>For well-known SIDs, see http://support.microsoft.com/kb/243330</p>\n</li>\n<li>\n<p>S-1-5-4 = Interactive</p>\n</li>\n<li>\n<p>S-1-5-11 = Authenticated Users</p>\n</li>\n<li>\n<p>Correlate the user SIDs to the output of the ProfileList plugin</p>\n</li>\n</ul>\n<h2>APPENDIX - RegRipper SOFTWARE Results for Task 4</h2>\n<p>Not included due to file size.</p>",
    "flags": [],
    "min_points_to_pass": null,
    "access_type": "default",
    "user_status": "unstarted",
    "user_lab_status": null,
    "user_status_modified": null,
    "user_flags": [],
    "global_running_session": null
}