<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Muyiwa F. on Medium]]></title>
        <description><![CDATA[Stories by Muyiwa F. on Medium]]></description>
        <link>https://medium.com/@mxyiwa?source=rss-10101a073228------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*2_sq5WOqVL24x6r1fiLPwQ.jpeg</url>
            <title>Stories by Muyiwa F. on Medium</title>
            <link>https://medium.com/@mxyiwa?source=rss-10101a073228------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 05:05:24 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@mxyiwa/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[How to Create your own Helpdesk Ticketing System]]></title>
            <link>https://medium.com/@mxyiwa/how-to-create-your-own-helpdesk-ticketing-system-91360166ef7e?source=rss-10101a073228------2</link>
            <guid isPermaLink="false">https://medium.com/p/91360166ef7e</guid>
            <dc:creator><![CDATA[Muyiwa F.]]></dc:creator>
            <pubDate>Tue, 25 Mar 2025 15:05:05 GMT</pubDate>
            <atom:updated>2025-03-25T15:05:05.741Z</atom:updated>
            <content:encoded><![CDATA[<p>The ultimate goal of this lab is to provide better customer service while making the support process more efficient and measurable by creating a well-designed ticketing system that helps organisations respond to customer needs more quickly, track performance, and continually improve their support processes.</p><p><strong>Credit:</strong> @<em>NetworkChuck</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/943/1*1dlkizdK4P4Md4LNbL7Olw.png" /></figure><h4>Key Objectives</h4><ul><li>To organise and track customer issues efficiently by creating a structured workflow from submission to resolution</li><li>Prioritise support requests based on urgency, impact, and service level agreements</li><li>Centralise communication between customers and support staff in one system</li><li>Create accountability by assigning clear ownership of issues to specific agents</li><li>Provide visibility into support operations through reporting and analytics</li><li>Maintain a searchable knowledge base of past issues and their resolutions</li><li>Improve customer satisfaction through faster, more consistent problem resolution</li><li>Optimise support team productivity by automating routine tasks</li></ul><h3>Tools / Technologies Used</h3><ul><li>Linode (A cloud hosting provider that offers computing services). <a href="https://ntck.co/linode"><em>Link</em></a></li><li>Peppermint (Ticketing System)</li><li>Docker</li><li>Docker Compose</li><li>macOS terminal</li><li>GitHub repository: <a href="https://github.com/Peppermint-Lab/peppermint"><em>Link</em></a></li></ul><h4>Steps</h4><ol><li>Sign Up and Log Into Linode</li><li>Create a Linode Virtual Machine</li><li>Install Peppermint as the Helpdesk Software</li><li>Launch the LISH Console</li><li>Access the Peppermint System via the URL Found in the LISH Console</li><li>Installing Peppermint Elsewhere I (Docker)</li><li>Installing Peppermint Elsewhere II (Docker Compose)</li><li>Accessing Peppermint as an Admin</li><li>Create a New Ticket/Issue</li><li>Accessing Peppermint as a User/Engineer</li></ol><h4>Step 1: Sign Up and Log Into Linode</h4><ul><li>First, navigate to the Akami website in the link provided above to sign up and log into Linode, which grants you $100 worth of free credit for 60 days.</li></ul><h4>Step 2: Create a Linode Virtual Machine</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gyzfqk6cry2LljALuuQEqw.png" /><figcaption>Create Linode</figcaption></figure><h4>Step 3: Install Peppermint as the Helpdesk Software</h4><ul><li>Navigate to the “<strong>Marketplace</strong>” section and search for Peppermint in the search bar. Select it.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NhDEdxmwwbKWL8ex3_acDg.png" /><figcaption>Linode Marketplace</figcaption></figure><ul><li>Set the limited sudo username and email address.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gj5hquyYOfJiJZjJYLUXZg.png" /><figcaption>Limed Sudo username and email address</figcaption></figure><ul><li>Next, scroll down the page to set up the software.</li><li>Select “<strong>Ubuntu</strong>” as the Image.</li><li>Select the region closest to you in the <strong>Region</strong> Section.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8KENvDENfF1YVdZI5ybfrQ.png" /><figcaption>Region and Image</figcaption></figure><ul><li>Next, navigate to the “<strong>Shared CPU</strong>” sub-section in the <strong>Linode</strong> Plan section.</li><li>Select the <strong>Nanode 1GB</strong> option to minimise computing costs.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jlWbcq8-4UhRNt2Ksxpqvg.png" /><figcaption>Linode Plan</figcaption></figure><ul><li>Next, label the VM in the <strong>Linode Label</strong> section.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KgK_QpGoi5FbQV_VDFDzFA.png" /><figcaption>Linode Label</figcaption></figure><ul><li>Then, set a password in the <strong>Root Password</strong> section. Scroll down to the end of the page and Click “<strong>Create Linode</strong>”. Ignore all other settings.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WX_cofmEXgiKcHrbtxSWfQ.png" /></figure><h4>Step 4: Launch the LISH Console</h4><ul><li>Select the <strong>Launch LISH Console</strong> to see the VM being spun up</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bkirnDaiL0Ak9-HewiR3Gw.png" /><figcaption>Launch LISH Console</figcaption></figure><ul><li>In the console, type “<strong>root</strong>” as the login username and the password you set.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dF_cY95z18oFiZR8dPjEyw.png" /></figure><ul><li>Next, type docker to confirm a docker container (indicated in blue) is being run. Also, when the ticketing system is being accessed, it will be on the port highlighted in red.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UwPIxCFmqKp6THKBzYHEtQ.png" /></figure><h4>Step 5: Access the Peppermint System directly via the URL found in the LISH Console</h4><ul><li>Copy the URL from the <strong>LISH</strong> Console and paste it into a new web browser tab to access the Peppermint ticketing system.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jbFeg8bPdKhfbBF5J9LacA.png" /><figcaption>URL to Access the Peppermint Ticketing System directly</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vBsFr48RJF-97VH8DIKKtg.png" /><figcaption>Peppermint Ticketing System</figcaption></figure><h4>Step 6: Installing Peppermint Elsewhere I (Docker Installation)</h4><p>If you intend to install Peppermint somewhere else, you can use this open-source GitHub repo (link below), courtesy of Peppermint Labs, with guides on how to install Peppermint with Docker.</p><p><strong><em>Link:</em></strong> <a href="https://github.com/Peppermint-Lab/peppermint">https://github.com/Peppermint-Lab/peppermint</a></p><ul><li>To do this, click the link above and then scroll down to the section labelled “<strong>Installation with docker</strong>”. This code will be copied for later.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7RdbgvE9F4Hpb65UdZ5JdQ.png" /><figcaption>Installation with Docker</figcaption></figure><ul><li>Next, open your host machine terminal (<em>in this lab, the Mac Terminal is being used</em>). If Docker has not already been installed on your host machine, it will be installed using Homebrew.</li><li>In case Homebrew has not been installed on your macOS-based host machine, type and run the following command in your terminal: s /bin/bash -c &quot;$(curl -fsSL <a href="https://raw.githubusercontent/">https://raw.githubuserconten</a>t.com/Homebrew/install/HEAD/install.sh)&quot;</li><li>Run brew install --cask docker to install docker.</li><li>After installation, you can launch Docker from the Applications folder.</li><li>Alternatively, you can run the command to start Docker from the terminal: Run open /Applications/Docker.app</li><li>Next, check if Docker is installed by running: docker --version</li></ul><h4>Step 7: Installing Peppermint Elsewhere II (Docker Compose)</h4><ul><li>After launching Docker, go back to the terminal and run mkdir peppermint to make a new directory. Run cd peppermint to navigate to that new directory.</li><li>Next, run nano docker-compose.yml to create a file in the directory.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TqZNLm6TC2Fm3sc_0xm4xA.png" /></figure><ul><li>Copy and paste the code from the “<strong>Installation with docker</strong>” code from <strong>Step 6 into the terminal</strong>. Press <strong>Control + X</strong> and then <strong>Y</strong> then <strong>Enter</strong> to save.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-H9S9oTq3A9tT7xbwz2MAA.png" /></figure><ul><li>In the terminal, run brew install docker-compose to install <strong>Docker Compose</strong>.</li><li>Next, run docker-compose up -d to start the peppermint ticketing system</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Unng4mO9vio5gZxu9Kr4dA.png" /></figure><ul><li>Run docker ps to confirm it’s running.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BRLOGWbDbmNl6OFwI2yqUg.png" /><figcaption>Docker is running successfully</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wmh_EpLJdRsBlohRXdfVsw.png" /><figcaption>Peppermint in a docker container</figcaption></figure><ul><li>Next, copy and paste the IP address from the <strong>Linode Admin Portal</strong> and the port number from the terminal to a new tab on your web browser.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AVFRj9KjnEkT4hmrn2xMxw.png" /><figcaption>Linode Admin Portal</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qIGbH2UxDig8EnO6w6gm6Q.png" /><figcaption>Port Number on from the host machine terminal.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aIHkjjzLA-aJ7oybe-ciBQ.png" /><figcaption>IP Address + Port number (with a Column in between) in the web browser</figcaption></figure><h4>Step 8: Accessing Peppermint as an Admin</h4><ul><li>Here, security doesn’t matter for this lab. The email address is “<strong><em>admin@admin.com” </em></strong>and the password is<strong><em> “1234”.</em></strong></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JcQPCpr5PHnG7TI1f_rtzg.png" /></figure><ul><li>Next, Click “<strong>To Dashboard</strong>” to navigate to the dashboard.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*s4U7hccN4oF6vhYr0IKzHQ.png" /></figure><h4>Step 9: Create a New Ticket / Issue</h4><p><strong>Issue Title:</strong> <em>“Unable to print from office printer”</em></p><p><strong>Description:</strong> <em>A user is unable to print documents from their computer to the office printer. The printer shows as “offline” in the system, despite being physically powered on and connected to the network. The user has tried restarting the printer and their computer, but the issue persists.</em></p><ul><li>First, Create the user: Select the Admin Icon on the left side menu &gt; Select “<strong>User</strong>” and then select the “<strong>New User</strong>” button.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/850/1*J5z7uLOp7qoU1krR7Ox0mw.png" /><figcaption>Admin Icon</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GVzwLAGda8RAF-UsUVi6gA.png" /><figcaption>New User Button</figcaption></figure><ul><li>Next, fill in the details of the user and make sure not to toggle the option to assign them admin privileges. Then select “<strong>Create User</strong>”.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TvD2Vz1eizhtnqFMq_QPvw.png" /><figcaption>Create User</figcaption></figure><ul><li>In the dashboard, select “<strong>New Issue</strong>”. Fill in your details (not the user details created before). Assign to the User previously created who is the engineer and then select “<strong>Create Ticket</strong>”.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DzBG_h1TRSkp2QfPDocj9w.png" /><figcaption>New Ticket</figcaption></figure><ul><li>To change the urgency level of the ticket, select the newly created ticket and select the option on the right side of the side menu.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BtQ6h3H8HBy3ghz2SCgQgA.png" /><figcaption>Urgency Level Option for Tickets</figcaption></figure><p><strong>Step 10: Accessing Peppermint as a User/Engineer</strong></p><ul><li>Go to the login page and type the email and password of the new user/engineer to log into Peppermint.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UtUtBv0jf_H4uJ8d3PQBow.png" /><figcaption>New User login details</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IY47ocECtyGokwY_EAkGiA.png" /></figure><ul><li>Next, open the ticket and take whatever action you are capable of taking. If you cannot rectify the issue, reassign the ticket to the admin and select the “<strong>Close Issue</strong>” button to mark the ticket as complete.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5xTyA6mmbq-m_4hknmxnXA.png" /></figure><p>In conclusion, by following these steps, you will have successfully set up a Linode virtual machine, installed Peppermint as a helpdesk ticketing system, and tested its functionality by creating and managing tickets. This process not only demonstrates how to deploy and manage a cloud-based ticketing system but also gives you hands-on experience with key tools like Docker and Docker Compose. By completing these tasks, you’ll be well-equipped to troubleshoot issues, create tickets, and manage workflows using the Peppermint system, ensuring efficient and organised IT support.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=91360166ef7e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[TryHackMe: SOC Level 1 (Summit) Walkthrough]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@mxyiwa/tryhackme-soc-level-1-summit-walkthrough-61656fab58b4?source=rss-10101a073228------2"><img src="https://cdn-images-1.medium.com/max/1640/1*gfiVw6UGH1-G17XdolgC8w.png" width="1640"></a></p><p class="medium-feed-snippet">Hello friends, this is my walkthrough of how I chased a simulated adversary up the Pyramid of Pain until they gave up.</p><p class="medium-feed-link"><a href="https://medium.com/@mxyiwa/tryhackme-soc-level-1-summit-walkthrough-61656fab58b4?source=rss-10101a073228------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@mxyiwa/tryhackme-soc-level-1-summit-walkthrough-61656fab58b4?source=rss-10101a073228------2</link>
            <guid isPermaLink="false">https://medium.com/p/61656fab58b4</guid>
            <dc:creator><![CDATA[Muyiwa F.]]></dc:creator>
            <pubDate>Fri, 20 Sep 2024 22:23:11 GMT</pubDate>
            <atom:updated>2024-09-20T22:23:11.133Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Active Directory Corporate Network Home Lab]]></title>
            <link>https://medium.com/@mxyiwa/how-to-setup-an-active-directory-corporate-network-home-lab-3fcc0326bef1?source=rss-10101a073228------2</link>
            <guid isPermaLink="false">https://medium.com/p/3fcc0326bef1</guid>
            <dc:creator><![CDATA[Muyiwa F.]]></dc:creator>
            <pubDate>Wed, 11 Sep 2024 17:47:45 GMT</pubDate>
            <atom:updated>2024-09-20T22:24:21.347Z</atom:updated>
            <content:encoded><![CDATA[<p>Hello, my fellow IT/cyber enthusiast! This home lab will be a walkthrough of how to set up an Active Directory corporate network home lab using Oracle’s VirtualBox. The goal here is to create a mini corporate network in an organisation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/791/1*7i1njvChHDAXJVT6enMNQg.jpeg" /><figcaption>Active Directory Corporate Network</figcaption></figure><h3>Lab Objectives</h3><p>The lab is my walkthrough approach to setting up a mini corporate network in my home lab by designing a simple network architecture with a subnet layout, including a Domain Controller (DC) and client machine, assigning static IPs to the DC and configuring DHCP for clients. Install Windows Server on the DC, promote it to a Domain Controller by installing the AD DS role, and set up a new forest with a domain name. Next, we will configure the internal DNS settings on the DC, set clients to use it as their DNS server, and configure the NAT. We will then use Active Directory Users and Computers to create and manage user accounts and organisational units (OUs), setting permissions and updating attributes as needed. Finally, we will prepare a Windows client machine, join it to the domain by configuring system properties, and verify that it integrates properly with domain resources and policies.</p><h3>Tools / Technologies Used</h3><ul><li>Oracle’s VirtualBox <a href="https://www.virtualbox.org/wiki/Downloads"><em>Link</em></a></li><li>Windows 10 ISO Image <a href="https://www.microsoft.com/en-us/evalcenter/evaluate-windows-10-enterprise?msockid=39080e851d656bce1afd1ac21c426ae5"><em>Link</em></a></li><li>Windows Server 2022 ISO <a href="https://www.microsoft.com/en-gb/evalcenter/download-windows-server-2022"><em>Link</em></a></li><li>Draw.io (<em>for the network diagram</em>) <a href="https://www.bing.com/ck/a?!&amp;&amp;p=7262cb220d0af9c07f710e4497e717f0e9fb007b0793cbf2c4436920025daa0dJmltdHM9MTcyNjAxMjgwMCZpbnNpZD01MTk5&amp;ptn=3&amp;ver=2&amp;hsh=4&amp;fclid=39080e85-1d65-6bce-1afd-1ac21c426ae5&amp;psq=draw%2cio&amp;u=a1aHR0cHM6Ly93d3cuZHJhd2lvLmNvbS8&amp;ntb=1"><em>Link</em></a></li></ul><h3>Steps</h3><ol><li>Download VirtualBox and its Extension Pack</li><li>Create a Domain Controller Virtual Machine</li><li>Configure the DC Virtual Machine</li><li>Server Installation on the DC VM</li><li>Windows Server Launch &amp; VM Guest Edition Setup Installation</li><li>Set Up an IP Address for the Internal Network</li><li>Install Active Directory Domain Services (AD DS)</li><li>Create a Dedicated Domain Admin Account</li><li>Sign in to the Dedicated Domain Admin Account</li><li>Install RAS / NAT</li><li>Set Up a DHCP Server on the DC VM</li><li>Set up the DHCP Scope</li><li>Create Users with a Custom PowerShell Script</li><li>Create the Client’s (Windows 10) VM</li><li>Change the Client’s VM and Join the Domain</li><li>Log into the Client’s VM with any of the Created Users</li></ol><h4>Step 1: Download VirtualBox and its Extension Pack</h4><ul><li>First, we will download and install <a href="https://www.virtualbox.org/wiki/Downloads"><strong>VirtualBox</strong></a> and then its Extension Pack</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8u28Gu0a2-DiNlQJhMPAAg.jpeg" /><figcaption>VirtualBox Website</figcaption></figure><ul><li>Next, we will navigate to the <a href="https://www.microsoft.com/en-us/evalcenter/evaluate-windows-10-enterprise?msockid=39080e851d656bce1afd1ac21c426ae5"><strong>Windows 10 ISO Image</strong></a> link. Select whatever language we prefer and download it.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*E8V2BBS83tvj5riWXVXFUw.png" /><figcaption>Windows 10 Iso Image</figcaption></figure><ul><li>After downloading the Windows 10 ISO, we will install the <a href="https://www.microsoft.com/en-gb/evalcenter/download-windows-server-2022">Windows Server 2022 ISO</a>. Select “<strong>ISO</strong>” and then fill in the details requested to download.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-OQqR8fYFQ8biRVoPTPzSQ.png" /><figcaption>Windows Server 2022 website</figcaption></figure><h4>Step 2: Create a Domain Controller Virtual Machine</h4><ul><li>First, we open VirtualBox &gt; Select “<strong>New</strong>” to create the Windows Server 2022 &gt; Name the VM &gt; Change version to “<strong>Other Windows (64-bit)</strong>” &gt; Select “<strong>Next</strong>”.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/887/1*dHif2t3-jKoP8xST10oxNg.jpeg" /></figure><ul><li>Next, we configure the memory size to “<strong>2048 mb</strong>” of RAM. Select “<strong>Next</strong>”.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/836/1*Sbcs9KGttaW8o7CVF8W_JA.png" /></figure><ul><li>Then, we leave the default selection as is in the “<strong>Virtual Hard disk</strong>” section and select “<strong>Next</strong>” then “<strong>Finish</strong>”.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/844/1*FKSRseHujLFRdKBWbkGyWQ.png" /></figure><h4>Step 3: Configure the DC Virtual Machine</h4><p>After the machine has been created, we will configure the machine settings before installing the server.</p><ul><li>Select the virtual machine and go to “<strong>Settings</strong>” &gt; In the “<strong>General</strong>” settings, select “<strong>Advanced</strong>” &gt; Change the “<strong>Shared Clipboard</strong>” &amp; “<strong>Drag ’n’ Drop</strong>” to “<strong>Bidirectional</strong>” (<em>These settings will enable us to copy and paste and also drag and drop files between the VM and host machine</em>).</li><li>Next, we go to the “<strong>System</strong>” settings and select “<strong>Processor</strong>” to increase the number of CPUs allocated to our machine. The higher the number of CPUs, the faster our VM. The recommended number is <strong>4 CPUs</strong>.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/812/1*Y42_6ukGz28Ofcl6h7hoAg.png" /><figcaption>System Settings &gt; Processor</figcaption></figure><ul><li>Then, we go to the “<strong>Network</strong>” settings to create two networks, one dedicated to the Internet and one to the VM Internal Network.</li><li>Since “<strong>Adapter 1</strong>&quot; already has NAT and is connected to the host internet, we go to “<strong>Adapter 2</strong><em>” </em>to create one more adapter &gt; Select “<strong>Enable Network Adapter</strong>” &gt; Go to the drop-down menu in “<strong>Attached to:</strong>” and select “<strong>Internal Network</strong>” and then select “<strong>OK</strong>”.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/661/1*SppLN00qq8gvdYfG46-iaQ.png" /></figure><h4>Step 4: Server Installation on the DC VM</h4><p>To install the server:</p><ul><li>First, we will start the virtual machine, a prompt will be displayed indicating that the VM failed to boot because of a missing operating system.</li><li>We will then go to the drop-down menu named “<strong>DVD:</strong>” &gt; Select “<strong>Other</strong>” and browse to where the Windows Server 2022 ISO was downloaded and select it &gt; Then select “<strong>Mount and Retry Boot</strong>”.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/453/1*s0-EG60oF8BkGzQNrvtP0A.png" /></figure><ul><li>Wait a while for the VM to boot. Once it has finished booting, we will configure the settings prompted to our preference. Then click “<strong>Install now</strong>”.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/997/1*cGrwhKV3x3_sJ1oAUbea8Q.png" /></figure><ul><li>Next, we select the “<strong>Windows Server 2022 Standard Evaluation (Desktop Experience)</strong>” Windows Experience.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GpPEXZg43aQBo11dNAtZew.png" /></figure><ul><li>Next, we check the box to accept the terms and conditions of the license agreement &gt; Select “<strong>Custom: Install Windows only (advanced)</strong>” &gt; Select the drive to install the operating system then “<strong>Next</strong>”. Then wait for the installation to be completed.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1020/1*EUVVjSg0XfnwmtvAJ0Z4bw.png" /><figcaption>Microsoft Server Operating System Setup</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1016/1*aVM1Lv85FV850ZuEmpoGPw.png" /><figcaption>Server installing</figcaption></figure><ul><li>After installing, it would either auto restart or we can click “<strong>Restart Now</strong>” to restart the machine manually.</li><li>After the machine has successfully restarted, an administrative prompt will be displayed instructing to input a password with the default username set as “<strong>Administrator</strong>”.</li><li>Then we input our preferred password and then select “<strong>Finish</strong>”.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1022/1*wwZ6hmpxWI13gVoxIFEwwQ.png" /></figure><p><strong>NOTE: <em>DO NOT USE THE SAME PASSWORD FOR YOUR VMs IN REAL LIFE!!!</em></strong></p><h4>Step 5: Windows Server Launch &amp; VM Guest Edition Setup Installation</h4><ul><li>The Windows will boot up at this stage. To access the machine, the Windows will need to be unlocked first. To do this, we will select “<strong>Input</strong>” &gt; “<strong>Keyboard</strong>” &gt; “<strong>Insert Ctrl-Alt-Del</strong>”. Then input the password in the prompt.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AgtE8TFrIjmZmr6Cbdivng.png" /></figure><ul><li>Next, we navigate to the “<strong>Devices</strong>” menu&gt; Select “<strong>Insert Guest Additions CD image</strong>” to insert guest additions disk file into the virtual optical drive.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/689/1*YMywjoZU-k_DgVa9N91W2w.png" /></figure><ul><li>After inserting the guest additions CD image, we then proceed to the File Explorer on the VM &gt; Select “<strong>This PC</strong>” &gt; Double Click the “<strong>CD Drive (D:) VirtualBox Guest Additions</strong>” &gt; Double click “<strong>VBoxWindowsAdditions-amd64</strong>” exe file &gt; Then, select “<strong>Next</strong>” to install the setup.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1007/1*TYVYCGtRrAURGTEnbjsHsA.png" /><figcaption><em>CD Drive (D:) VirtualBox Guest Additions Driver</em></figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1014/1*GjNvT9mKtaB6ztJkoQy-ZA.png" /><figcaption><em>VBoxWindowsAdditions-amd64 exe file</em></figcaption></figure><ul><li>After installation, we will then select the “<strong>I want to manually reboot later</strong>” option and then select “<strong>Finish</strong>”.</li><li>Next, we shut down the VM and relaunch the VM.</li></ul><p><strong>NOTE:</strong><em> </em><strong><em>The main purpose for installing the guest additions is to prevent the lag experienced with the mouse and also to help resize the VM window.</em></strong></p><h4>Step 6: Set Up an IP Address for the Internal Network</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/791/1*7i1njvChHDAXJVT6enMNQg.jpeg" /></figure><p>According to the networking diagram above, we have two NICs (<em>Network Interface Cards</em>), one for the<strong> Internet</strong> and one for the <strong>Internal Network</strong>. The one for the internet automatically has an IP address assigned to it and the one for the Internal Network does not have an IP address assigned. The goal is to set up an IP address for the Internal Network.</p><p>To do this:</p><ul><li>We will navigate to the “<strong>Network</strong>” settings at the bottom right of the DC VM screen &gt; Then click “<strong>Network &amp; Internet settings</strong>” &gt; “<strong>Change adapter options</strong>”.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/472/1*m7PE8i-fKiwGQSqrqpPB7g.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/844/1*plY1YxWwRuGWLs4gUBeHRw.png" /></figure><ul><li>Two NICs would be displayed. We then right-click either one to go to “<strong>Status</strong>” &gt; then “<strong>Details</strong>” to investigate the IPv4 Address. If there is an IPv4 Address, that particular NIC is connected directly to the internet. If not, then an IP address will be automatically assigned and that would be the NIC <strong>not</strong> connected to the internet aka the “<strong>Internal Network</strong>”.</li><li>Next, we rename the NICs. The one connected to the internet is “<strong>_INTERNET_</strong>” and the second NIC connected to the internal network is “<strong>X_Internal_X</strong>”.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*doSEXDb_lKXk0jCLb3YvjQ.png" /><figcaption>NIC connected to the Internet</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*e2dU7l2wLsnmwwk6DkvxQQ.png" /><figcaption>NIC connected to the Internal network</figcaption></figure><ul><li>After renaming, we will assign an IP address to the <strong>Internal network </strong>by navigating to and selecting the “<strong>Network</strong>” settings at the bottom right of the DC VM screen &gt; Then click “<strong>Network &amp; Internet settings</strong>” &gt; “<strong>Change adapter options</strong>”.</li><li>Then, right-click on the internal network NIC labelled “<strong>X_INTERNAL<em>”</em></strong> and select “<strong>Properties</strong><em>” &gt; </em>Double click “<strong>Internet Protocol Version 4 (TCP/IPv4)</strong>”.</li><li>We then select “<strong>Use the following IP address</strong>” and type in “<strong>172.16.0.1</strong>” as the IP address from the network diagram above and “<strong>255.255.255.0</strong>” as the subnet mask. We will ignore the “<strong>Default gateway</strong>” input because the DC will be the default gateway.</li><li>Next, select “<strong>Use the following DNS server address</strong>” and type either the IP address from the network diagram, “<strong>172.16.0.1</strong>”, or the default loopback address, “<strong>127.0.0.1</strong>”, so the computer can ping itself.</li><li>Select “<strong>OK</strong>” to close the settings.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kJ9pXCBCu2OAvo6_CQcFGw.png" /><figcaption>Assigning IP Address to the Internal Network</figcaption></figure><h4>Step 7: Install Active Directory Domain Services (AD DS)</h4><p>After setting up the IP address, we will install the Active Directory Domain Services (AD DS). To do this:</p><ul><li>First, we open the “<strong>Server Manager</strong>” &gt; Select “<strong>Add roles and features</strong>” &gt; Click “<strong>Next</strong>” while leaving the default selections until we reach the “<strong>Server Selection</strong>” section to select the destination server.</li><li>Select the server previously created then click “<strong>Next</strong><em>”.</em></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*05Z4KHRAoBMWfwR1xmvB6w.png" /><figcaption>Server Manager Dashboard</figcaption></figure><ul><li>After clicking “<strong>Next</strong><em>” </em>to the “<strong>Server Roles</strong>” section, we then select “<strong>Active Directory Domain Services</strong>” and then click “<strong>Add Features</strong>”.</li><li>Click “<strong>Next</strong>” up until the “<strong>Confirmation</strong>” section and select “<strong>Install</strong>” to install this role.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/782/1*Bg_sEvQgcJPiWqoxtX0EEg.png" /><figcaption>Confirmation Section</figcaption></figure><ul><li>Select “<strong>Close</strong>” after the installation has been completed.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/789/1*nwSyEMdNMx9k6EP0qR-wUg.png" /><figcaption>Installation Succeeded on DC</figcaption></figure><ul><li>To enable the post-deployment configuration (<strong>Creating the domain</strong>), we will select the “<strong>Caution Flag Icon</strong>” on the top right of the Server Manager and select “<strong>Promote this server to a domain controller</strong>”.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nRy1FOxEwGF275keFtCgjw.png" /><figcaption>Post-deployment configuration</figcaption></figure><ul><li>In the <strong>“Deployment configuration” </strong>section, we will select “<strong>Add a new forest</strong>” and then input a root domain name ending with “<strong>.com</strong>”.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/758/1*v9YtqwGuQ7gtaooKnEBZNA.png" /><figcaption>Deployment Configuration Section</figcaption></figure><ul><li>Select “<strong>Next</strong>” to move to the “<strong>Domain Controller Options”</strong> section and input a password (<em>I recommend using a consistent password all through the lab</em>).</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/757/1*oLLp6KR5ANZ8PsDggqHyqw.png" /><figcaption>Domain Controller Options Section</figcaption></figure><ul><li>We then select “<strong>Next</strong>” and skip to the <strong>“Prerequisite Check” </strong>section then select “<strong>Install</strong>”. After installation, the VM will be restarted automatically.</li></ul><p>Once we try to sign back in, the domain created will be displayed on the login screen. We then input your password to log back in.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Gttm0wbD-M8bVJEmCLSFzA.png" /></figure><h4>Step 8: Create a Dedicated Domain Admin Account</h4><p>Instead of using the built-in administrator account, we can create a dedicated domain administrative account to use in the DC VM.</p><ul><li>First, we go to the “<strong>Start</strong>” menu and search for “<strong>Active Directory Users and Computers</strong>”, then click to select it.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hVPp0kxT2pcUwmzJpMASwA.png" /><figcaption>Start &gt; Active Directory Users and Computers</figcaption></figure><ul><li>Next, we create a new organisational unit to put the admin account in.</li><li>We then navigate to the newly created domain &gt; Right-click to open the menu &gt; Select “<strong>New</strong>” &gt; Select “<strong>Organizational Unit</strong>”.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PGhxVGW_b4U_HJ6mloorqQ.png" /></figure><ul><li>Next, we name the folder, in this lab, “<strong>_ADMINS</strong>” and uncheck the “<strong>Protect container from accidental deletion</strong>” box to enable deletion when done with the lab. Then, select “<strong>OK</strong>” to create.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/745/1*dwPc_JK8TZJunA2hi6pT5Q.png" /></figure><ul><li>Next, right-click on the newly created folder &gt; Select “<strong>New</strong>” &gt; Select “<strong>User</strong><em>” </em>to create a new user.</li><li>We then input the new user details in the text box, i.e. the <strong>First name</strong>, <strong>Last name</strong>, and <strong>User logon name </strong>(<em>You can use “</em><strong><em>a-</em></strong><em>” in front of your user logon name of choice to identify that user as an admin user</em>). Then select “<strong>Next</strong>”.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/846/1*gm2QE8bd3DQjlgedf2AZkA.png" /><figcaption>Setting Up an Admin User Account</figcaption></figure><ul><li>Next, we set our password and select the “<strong>Password never expires box</strong>” to prevent the password from expiring since this is a lab environment. Then select <em>“</em><strong>Finish</strong><em>”.</em></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/436/1*J70LXVSgLg5yPb_KyFmLUw.png" /><figcaption>User Login Password Setup</figcaption></figure><p>Although an admin user has been created, it is yet to be set up as a domain admin. To do this:</p><ul><li>Right-click on the admin user account created &gt; Select “<strong>Properties</strong>” &gt; Select “<strong>Member Of</strong>” &gt; Select “<strong>Add</strong>” &gt; Type “<strong>domain admins</strong>” in the input section displayed and then select “<strong>Check Names</strong>” to find the object name. Select “<strong>OK</strong>” and then select “<strong>Apply</strong>”.</li><li>Next, we log out of our VM and sign back in to apply changes.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ic_ibR9rFq9zuSRZ8fQkcg.png" /><figcaption>Setting Up New User to Domain Admin</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/406/1*kB6UOSn0l-F1xIjIxUWbSw.png" /></figure><h4>Step 9: Sign in to the Dedicated Domain Admin Account</h4><ul><li>We then sign back in by selecting “<strong>Input</strong>” on the top left of the DC VM screen &gt; “<strong>Keyboard</strong>” &gt; “<strong>Insert Ctrl-Alt-Delet<em>e</em></strong>” to unlock the DC VM.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/992/1*QLPS0tlS1XFKcvN9tSzLaw.png" /></figure><ul><li>Select “<strong><em>Other User</em></strong>” and input the newly created domain admin account username and password to log in.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BZqnqMBH22V1LZ3bBYTJaQ.png" /><figcaption>Logging into the Domain Admin Account</figcaption></figure><h4>Step 10: Install RAS / NAT</h4><p>Next, we install RAS/NAT {<strong>Remote Access Server / Network Address Translation</strong>}. This allows the Windows Client to be on a private virtual network but still access the internet through the DC.</p><p>To do this:</p><ul><li>We navigate to the <strong>Server Manager</strong> and select “<strong>Add roles and features</strong>”.</li><li>We then select “<strong>Next</strong>” more than once to skip to the<strong> Server Roles</strong> section and tick the “<strong>Remote Access</strong>” box.</li><li>Select “<strong>Next</strong>” more than once to skip to the <strong>Role Services</strong> section under the <strong>Remote Access</strong> section and tick the “<strong>Routing</strong>” box. The “<strong>Direct Access and VPN (RAS)</strong>” box automatically gets selected.</li><li>Select “<strong>Next</strong>” to skip to the <strong>Confirmation</strong> section and then select “<strong>Install</strong>”.</li><li>Wait a few minutes for the installation to complete.</li><li>After installation, select “<strong>Close</strong>” to close the “<strong>Add Roles and Features Wizard</strong>” Window.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/781/1*CmJzwfrC6lCYJgoueqRang.png" /><figcaption>RAS/NAT Installation</figcaption></figure><ul><li>Next, we configure the <strong>Routing and Access Server Setup</strong> by selecting “<strong>Tools</strong>” at the upper right corner of the <strong>Server Manager</strong> Page &gt; then, select “<strong><em>Routing and Remote Access</em></strong>”.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/806/1*rxx9QnQcyfaxq6jn9S0Hpg.png" /><figcaption>Routing and Remote Access</figcaption></figure><ul><li>Next, we right-click on “<strong>DC (local)</strong>” &gt; Select “<strong>Configure and Enable Routing and Remote Access</strong>”.</li><li>Click “<strong>Next</strong>” &gt; Select “<strong>Network address translation (NAT)</strong>”, which is the service that is being configured.</li><li>We then click “<strong>Next</strong>” to select “<strong>Use this public interface to connect to the Internet.</strong>” as the <strong>NAT Internet Connection</strong> interface.</li></ul><p><strong>NOTE: <em>A problem usually encountered at this stage is that the public interfaces must be automatically selected or displayed. The solution is to close the configuration setup and run it back again.</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/633/1*iBvveAj8YlB5Rs-54KNIQQ.png" /><figcaption>Routing and Remote Access Server Setup Wizard</figcaption></figure><ul><li>Next, we select the public internet interface labelled “<strong>_INTERNET_</strong>” &gt; Select “<strong>Next</strong>” &gt; Select “<strong>Finish</strong>” to complete the Routing and Remote Access Server Setup Wizard. Then close the setup interface.</li></ul><h4>Step 11: Set Up a DHCP Server on the DC VM</h4><p>Doing this will allow the Windows client to get an IP address to access the internet. To set this up:</p><ul><li>Navigate to the <strong>Server Manager</strong> and select “<strong>Add roles and features</strong>”.</li><li>Select “<strong>Next</strong>” more than once to skip to the<strong> Server Roles</strong> section, tick the “<strong>DHCP Server</strong>” box and Select “<strong>Add Features</strong>”.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/782/1*xMNzPWDI3Jx5W-jFOMct4g.png" /></figure><ul><li>Then, select “<strong>Next</strong>” more than once to skip to the <strong>Confirmation</strong> section and then select “<strong>Install</strong>”.</li><li>We then wait a few minutes for the installation to complete.</li><li>After installation, select “<strong>Close</strong>” to close.</li></ul><h4>Step 12: Set up the DHCP Scope</h4><ul><li>To do this, we select “<strong>Tools</strong>” at the upper right corner of the <strong>Server Manager</strong> Page &gt; Select “<strong>DHCP</strong>”.</li></ul><p><strong>NOTE: <em>DHCP allows client computers on the network to automatically get their IP addresses.</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/686/1*4coVJOjV1eRT1EzILgk5Vw.png" /></figure><ul><li>Next, we go to the DHCP server (<strong>dc.domainexpansion.com</strong>) &gt; We right-click “<strong>IPv4</strong>” &gt; and select “<strong>New Scope</strong>”.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/337/1*4dRtVXW12MuL2vQ1SCMLPg.png" /></figure><ul><li>We then select “<strong>Next</strong>” and name the scope.</li></ul><p><strong>NOTE: <em>It is best practice, especially in labs, to name the scope after the IP range that will be used.</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/512/1*Quuyay0vGqgN1-bZ4B3Qdg.png" /><figcaption>New Scope Wizard</figcaption></figure><ul><li>After naming the scope, we select “<strong>Next</strong>” to go to the <strong>IP Address Range</strong> section.</li><li>In the <strong>Configuration settings for the DHCP Server </strong>section, we input the “<strong>Start IP address</strong>” as [<strong>172.16.0.100</strong>] and the “<strong>End IP address</strong>” as [<strong>172.16.0.200</strong>].</li><li>In the <strong>Configuration settings that propagate to the DHCP Client </strong>section, we set the “<strong>Length</strong>” as [24] and the “<strong>Subnet Mask</strong>” as [<strong>255.255.255.0</strong>].</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/516/1*l-Rvq-b5ySOG54WPnYKRgQ.png" /><figcaption>IP Address Range</figcaption></figure><ul><li>We then select “<strong>Next</strong>” twice to skip the <strong>Add Exclusions and Delay</strong> section straight to the <strong>Lease Duration</strong> section.</li><li>We set the “<strong>Days</strong>” to <strong>8</strong> days or however long we need to lease the IP address for. Within this period, the IP address will not be assigned to any computer except ours, then it will automatically reset after 8 days.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/516/1*rQWwmkwTX6yxYNn-xbXbJw.png" /><figcaption>Lease Duration</figcaption></figure><ul><li>We then select “<strong>Next</strong>” to go to the <strong>Configure DHCP Options </strong>section. This configuration tells our client what servers to use for their DNS, gateway, etc. configurations, so they can access the internet.</li><li>Select “<strong>Yes, I want to configure these options now</strong>” and “<strong>Next</strong>”.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/518/1*ufqZzS3PRuhmFtqAIJALDw.png" /><figcaption>Configure DHCP Options</figcaption></figure><ul><li>Next, in the <strong>Router (Default Gateway)</strong> section, input the IP address of the<strong> DC/Internal NIC</strong> and click “<strong>Add</strong>”.</li></ul><p><strong>NOTE:</strong> You must select<em> “</em><strong><em>Add</em></strong><em>” as not doing this will cause complications.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/515/1*Ko7vTj4z-Bl5WXQSwE2Izw.png" /><figcaption>Router (Default Gateway)</figcaption></figure><ul><li>In the <strong>Domain Name and DNS Servers </strong>section, we will remove any other IP address automatically added, input the IP address of the <strong>DC/Internal NIC </strong>and click “<strong>Add</strong>”.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/513/1*gnbVEwFMcEh8gJ63v6petg.png" /><figcaption>Domain Name and DNS Servers</figcaption></figure><ul><li>Next, we select “<strong>Next</strong>” twice to skip the <strong>WINS Server</strong> section as it is already deprecated.</li><li>In the <strong>Activate Scope </strong>section, we select “<strong>Yes, I want to activate this scope now</strong>” &gt; Select “<strong>Next</strong>” and then “<strong>Finish</strong>” to activate the scope.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/515/1*ovOZTSO1A7qXxA0W7ct99g.png" /><figcaption>Activate Scope</figcaption></figure><p><strong>NOTE:</strong> <em>Sometimes, the scope does not activate. To fix this, right-click the DC [</em><strong><em>dc.domainexpansion.com</em></strong><em>] &gt; Select “</em><strong><em>Authorize</em></strong><em>” &gt; Right-click the DC one more time and select “</em><strong><em>Refresh</em></strong><em>”.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/732/1*-3Mx3327xaH2FjDn4hVZ5A.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/696/1*I6wBMls4q8eEd799s4QcoA.png" /></figure><h4>After fixing the scope activation process, the IPv4 and IPv6 icons will show a green tick to confirm the authorisation of the scope.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/333/1*8k76tG7f3HufmJEA7D0Fmg.png" /></figure><h4>Step 13: Create Users with a Custom PowerShell Script</h4><p>First, the DC needs to be configured so that it can browse the internet. To do this:</p><ul><li>We go to the <strong>Server Manager</strong> and then select “<strong>Configure this local server</strong>”.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Bw3Fr7TjB4YZwF3GQu9qgg.png" /></figure><ul><li>At the “<strong>IE Enhanced Security Configuration</strong>”, we select “<strong>On</strong>” &gt; Select “<strong>Off</strong>” for both the <strong>Administrators</strong> and <strong>Users</strong> options.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/737/1*srjqZs41xmQOA6LoqJ6qag.png" /><figcaption>IE Enhanced Security Configuration</figcaption></figure><ul><li>Next, we open this <a href="https://www.youtube.com/redirect?event=video_description&amp;redir_token=QUFFLUhqazBPVzY1bDQwVDlZZzdmd3RNWEJjZlBITzRQQXxBQ3Jtc0ttUnFuX2N6ajJUVGdETXZQMVltSm9GUVpiSjRFelFrcTBGMV9hNUpQZW9hVi1kZWZWck5seXkwZ0F3bW5OS3lTelJsN05HcGx6cW5PRFB6Tkpvd3UySnk4Y2xSd0RrRVl4ZlhuVmNRVENsTFdKbklSRQ&amp;q=https%3A%2F%2Fgithub.com%2Fjoshmadakor1%2FAD_PS%2Farchive%2Frefs%2Fheads%2Fmaster.zip&amp;v=MHsI8hJmggI">link</a> in our DC VM, to navigate to the source code for the PowerShell script that will be used to create all the users configured by <em>Josh Madakor</em>.</li><li>A zip folder containing the script will be downloaded. We will extract it and save it to an easily accessible location on our DC VM.</li><li>Next, we minimise all windows opened and navigate to the start menu. Search and right click “<strong>Windows PowerShell ISE</strong>” &gt; Select “<strong>More</strong>” &gt; Select “<strong>Run as Administrator</strong>” &gt; And then select “<strong>Yes</strong>”.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/883/1*JAMXgywXbpltpVLTXDIPsA.png" /><figcaption>Windows PowerShell ISE</figcaption></figure><ul><li>Once the Windows PowerShell ISE has been opened, we click the “<strong>Open Script</strong>” icon at the top left of the window to navigate to the location of the PowerShell script folder extracted earlier and select the PowerShell script to open it.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1006/1*znjtvryntlnDmVnjXE1ICw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*I5wnNuVnbP_i-rC58h4U7g.png" /><figcaption>Opened PowerShell Script</figcaption></figure><p>Before anything is run, we need to enable the execution of all scripts on this server. To do this:</p><ul><li>We will type and run the command Set-ExecutionPolicy Unrestrictedin the PowerShell terminal. Then select “<strong>Yes To All</strong>” when the prompt shows to confirm the decision.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KaBzhPzIdoPrh8181S8HAg.png" /><figcaption>Enabling the execution of all scripts</figcaption></figure><ul><li>Next, we navigate to the directory of the PowerShell script by typing, cd C:\Users\&lt;our username&gt;\Desktop\AD_PS-master.</li><li>Type and run lsto reveal the contents of the folder.</li><li>Next, we click on the run icon at the top of the PowerShell window and select “<strong>Run once</strong>” when prompted with a confirmation question.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Fn9AiC4_CfL-SeG9Jd7vHg.png" /></figure><ul><li>The user accounts will begin creating.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/866/1*0lvJHxaJF8yEwo3RhbJhVA.png" /><figcaption>User Accounts being Created</figcaption></figure><p>To search for a particular user created on Active Directory, we will:</p><ul><li>Click “<strong>Start</strong>” &gt; Click the “<strong>Windows Administrative Tools</strong>” folder &gt; Click “<strong>Active Directory Users and Computers</strong>” &gt; Right-click the domain and Select “<strong>Find</strong>” &gt; In the “<strong>Name</strong>” section, we input the name we want to search for &gt; Then click “<strong>Find Now</strong>”.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/747/1*fGqobkREK2qaedxQ-Yn6iA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*1o-egZKvENr8q_dzNJS1rg.png" /></figure><h4>Step 14: Create the Client’s (Windows 10) VM</h4><p>Our next step will be to create the Client’s (Windows 10) VM which will be connected to our private VirtualBox network. We will name our client and join it to the domian. We will then log into it using one of our domain accounts created. To do this, we will:</p><ul><li>Navigate to VirtualBox &gt; Select “<strong>New</strong>” &gt; In the “<strong>Name</strong>” section, we will type in the name of our client’s (Windows 10) VM.</li><li>In the “<strong>Version</strong>”, we will locate our Windows 10 ISO Image ) &gt; Then click “<strong>Next</strong>”.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/858/1*Yef-ESYUb4y7_Gtw_tQHMw.png" /><figcaption>Virtual Machine Name and Operating System Configuration</figcaption></figure><ul><li>Next#, we set the “<strong>Base Memory</strong>” and “<strong>Processors</strong>” to our preferred memory capacity (<strong>4096</strong> <strong>MB</strong> is recommended for the Base Memory and <strong>4 CPU</strong> is recommended for the Processors).</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/821/1*Jh9N4Ql6TFBlQijQfBV7NQ.png" /></figure><ul><li>We then select “<strong>Next</strong>” more than once to skip to the “<strong>Summary</strong>” section and select “<strong>Finish</strong>”.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/817/1*5uNZAymhTZ-IjHgl11XzNQ.png" /></figure><ul><li>After our client’s VM has been created, right-click the client’s VM and select “<strong>Settings</strong>” to go to the VM configurations.</li><li>Next, we go to “<strong>General</strong>” &gt; Click “<strong>Advanced</strong>” &gt; Change the “<strong>Shared Clipboard</strong>” &amp; “<strong>Drag ‘n’ Drop</strong>” to “<strong>Bidirectional</strong>”.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/682/1*Ovg7Z9aWexeylBTJjmQ0Hg.png" /><figcaption>General Configuration for the Client’s VM</figcaption></figure><ul><li>Next, we go to “<strong>Network</strong>” &gt; Select “<strong>Adapter 1</strong>” &gt; Click the dropdown menu for “<strong>Attached to:</strong>” and select “<strong>Internal Network</strong>” &gt; Select “<strong>OK</strong>” to save the changes.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/687/1*pXOdX8G1r5eTGHroak-A1w.png" /><figcaption>Network Configuration for the Client’s VM</figcaption></figure><ul><li>Next, we spin up our newly created client’s VM by double-clicking on it.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/868/1*ZWJ3O9TvMHkvcqspyRnY9A.png" /></figure><ul><li>We then navigate to the Windows ISO Image location via the dropdown menu in the “<strong>DVD:</strong>” section, when prompted to mount it &gt; We select the Windows ISO Image &gt; And then select “<strong>Mount and Retry Boot</strong>”.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*ARZZOk_DbdjX1zOWORFQxg.png" /></figure><ul><li>We wait for the VM to boot then configure our settings in the image below.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1023/1*9rcU-7nfVuEmAPcvsBOxIw.png" /></figure><ul><li>Next, we select “<strong>Install now</strong>” and wait for the setup to start</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1023/1*JW6pU831n7S2FCQsRiUPoQ.png" /></figure><ul><li>Tick the box to accept the licence terms and select “<strong>Next</strong>”.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dQ76y-SwEZDed9_bsdevrg.png" /></figure><ul><li>Select “<strong>Custom: Install Windows only (advanced)</strong>”.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1015/1*xd-iOHzrh1-QesznAsOZ0w.png" /></figure><ul><li>Select “<strong>Next</strong>” when prompted with the question, “<strong>Where do you want to install Windows?</strong>” and we wait for the Windows to install (this may take a while).</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/635/1*lNto2SGTUQhZl6YTz46jIA.png" /></figure><ul><li>We then select our preferred region.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1021/1*ms7DnuviK8ibb7MzFiTSdA.png" /></figure><ul><li>Select our preferred keyboard layout.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1017/1*-biDOGfhbed-yc82ruv9rw.png" /></figure><ul><li>Next, we select “<strong>Domain join instead</strong>” when prompted with the question “<strong>What account should I use?</strong>” and select “<strong>Next</strong>”.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VwHlsw5vpB986MJGBP-Y1w.png" /></figure><ul><li>We will input our preferred username that can be remembered when prompted with the question “<strong>Who’s going to use this PC?</strong>” and then select “<strong>Next.</strong></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1019/1*orzQpp4XHbExWNk2snkd7Q.png" /></figure><ul><li>Next, we input a memorable password (<em>we can also proceed without creating a password</em>) that can remembered when prompted to “<strong>Create a really memorable password</strong>” and select “<strong>Next.</strong></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1021/1*UfkwQUmfEcKPZE0RevXEVQ.png" /></figure><ul><li>Next, we type our password again to confirm it when prompted.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1022/1*ZO9luONr0O-Pa9rZ--azpQ.png" /></figure><ul><li>We then select three security questions and provide an answer when prompted to “<strong>Create security questions for this account</strong>”.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1020/1*TKvJP3HjzouzQTB3_DTf_Q.png" /></figure><ul><li>Next, we set the remaining configurations to our preferred settings and wait for the Windows machine to load.</li></ul><p>After loading has been completed, we proceed to make sure the internet is working:</p><ul><li>Click “<strong>Start</strong>” &gt; Type “<strong>cmd</strong>” in the search bar to navigate to the command line and type cmd.</li><li>Next, we type ipconfigto confirm there is a default gateway and there is connectivity.</li><li>After confirmation, we will ping the internet to confirm the DNS server is working by typing ping &lt;domain name&gt;.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/976/1*oqNBJP7x7ZWp59KGnMH5NA.png" /></figure><h4>Step 15: Change the Client’s VM and Join the Domain</h4><p>The next step is to change the name of the client’s VM and join the domain. To do this, we will:</p><ul><li>Right-click the “<strong>Start</strong>” menu &gt; Select “<strong>System</strong>” &gt; Scroll down and select “<strong>Rename this PC (advanced)</strong>”.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/798/1*ajHiho6MJvA7olKIV4u3NQ.png" /></figure><ul><li>Next, we select “<strong>Change</strong>” in the “<strong>System Properties settings</strong>”</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/410/1*3EhbBRRv2L1jp1pJk2-sXA.png" /></figure><ul><li>In the “<strong>Computer Name/Domain Changes</strong>” settings, we will change the “<strong>Computer Name</strong>” to the name of our Client’s VM and join the domain of the DC VM by selecting the “<strong>Domain</strong>” section and typing the name of the domain. Then select “<strong>OK</strong>”.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/325/1*N2YpnFjAx-6K52Cc4oBjhQ.png" /></figure><ul><li>Next, we will enter the name and password of our domain admin account (<em>the normal account can also be used</em>) in the prompt. Then, select “<strong>OK</strong>”.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/459/1*06Sw4XBjzq1KKBCXJyUmDQ.png" /></figure><ul><li>We then select “<strong>OK</strong>” after the prompt containing the confirmation message of our Client’s VM joining the domain has been displayed.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/334/1*nF6UOpAIJE_34TuNU4TeIg.png" /></figure><ul><li>Next, we make sure all changes made are saved before restarting our Client’s VM.</li></ul><p>While our client’s VM is being restarted, we will navigate to the DC VM to verify if the client VM has joined the DC VM. To do this, we will:</p><ul><li>Click the “<strong>Start</strong>” menu on the DC VM &gt; Select and Open “<strong>Active Directory Users and Computers</strong>”.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/492/1*U3EH-4yZMqyYsI7egwMkbg.png" /><figcaption>Active Directory Users and Computers</figcaption></figure><ul><li>Next, we will select the domain &gt; Select “<strong>Computers</strong>” and we should see the Client’s VM connected to the domain, indicating that it is now a member of the domain.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/758/1*1zONSstf_zbwlgwZMlii4w.png" /></figure><h4>Step 16: Log into the Client’s VM with any of the Created Users</h4><p>The purpose of the Client’s VM being a member of the domain is to give the created users in <strong>Step 13</strong>, access to log into our Client’s VM. To do this:</p><ul><li>First, we select a user’s username from the list of users created in the PowerShell script in Step 13.</li><li>Next, we sign out of our Client’s VM from the current user account and select “<strong>Other User</strong>” to sign back in using the user’s username selected.</li><li>We then type the username and password created and click “<strong>Enter</strong>” to log in and wait for the user profile to be created since this is the first time that this user will be signing into the domain.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1022/1*OGWRzRgaCip5bAEjARlM3A.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1022/1*1mIE6ze0oRVjY59dj_9gEg.png" /><figcaption>User Profile created</figcaption></figure><h3>Conclusion</h3><p>This lab was designed to simulate how an Active Directory network is created and managed to serve as a centralised system that allows the administrator to manage users, devices, and resources across an organisation’s network and also make sure its IT infrastructure is secured.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3fcc0326bef1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Elastic SIEM Configuration and Management Lab using the ELK Stack]]></title>
            <link>https://medium.com/@mxyiwa/how-to-build-an-elastic-siem-lab-8ebd0bd74f28?source=rss-10101a073228------2</link>
            <guid isPermaLink="false">https://medium.com/p/8ebd0bd74f28</guid>
            <dc:creator><![CDATA[Muyiwa F.]]></dc:creator>
            <pubDate>Mon, 26 Aug 2024 02:43:30 GMT</pubDate>
            <atom:updated>2024-09-12T01:32:13.756Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iRfRpLA0VM9Q_tq_pzRdpQ.png" /></figure><h3>What is an Elastic SIEM?</h3><p>Elastic SIEM (Security Information and Event Management) is a comprehensive security solution built using the ELK Stack, which includes Elasticsearch, Logstash, and Kibana. These three technologies provide a powerful solution when working with large data sets which enables us defenders to set up SIEM rules to alert us of attacks on our organisation. It is a key component of Elastic Security designed to help organisations detect, prevent, and respond to security threats in real time by collecting and analysing data from various sources across an IT environment.</p><h3>Key Features</h3><ul><li>Monitors network traffic and endpoint behaviour for signs of intrusion and suspicious activities.</li><li>Protects endpoints (servers, desktops, and cloud instances) from malware, ransomware, and other threats.</li><li>Provides real-time monitoring and behavioural protection to detect suspicious activity.</li><li>Uses machine learning and behavioural analytics to identify and prevent threats.</li><li>Leverages prebuilt detection rules and allows for custom rule creation to fit specific security needs.</li><li>Seamlessly integrates with Elasticsearch for data storage and analysis.</li></ul><h3>Lab Objectives</h3><p>This lab is the walkthrough of my approach to building an Elastic SIEM lab set up in a home lab environment using Elastic SIEM within a Kali Linux VM, where data is forwarded from the VM to the SIEM through the Elastic Defend agent. In this lab, security events are generated on the Kali Linux VM using Nmap, and these logs are then queried and analysed within the Elastic web interface. To enhance visibility and monitoring, a dashboard is created to visualise the security events, and an alert system to notify when specific security events are detected.</p><h3>Tools / Technologies Used</h3><ul><li>Parallels VM</li><li>Kali Linux</li><li>Elastic SIEM</li><li>Elastic Defend Agent</li></ul><h3>Steps</h3><ol><li>Set up a free Elastic Cloud Account and Create a New Deployment.</li><li>Set up a Kali Linux VM.</li><li>Install Elastic Defend as the Software Agent to Collect Logs and Forward the Audit logs and Telemetry from the Kali Linux VM to the Elastic SIEM.</li><li>Generate Security Events on the Kali Linux VM using Nmap.</li><li>Query and analyse the Security Event logs generated in the Elastic SIEM using the Elastic web interface.</li><li>Create dashboards to visualise the Security Events.</li><li>Create alerts to notify the security events that are detected.</li></ol><h4>Step 1: Set up a free Elastic Cloud Account and Create a New Deployment</h4><ul><li>First, we sign up and create a free Elastic cloud account to set up a cloud Elastic instance at <a href="https://cloud.elastic.co/registration">https://cloud.elastic.co/registration</a>.</li><li>After creating the account, we arrive at the “<strong>Create your first deployment</strong>” section &gt; In the “<strong>Name</strong>” section, we input the name of our deployment &gt; Then we click “<strong>Create deployment</strong>”.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8ON9Gxe54iwkUichL3fGoQ.png" /></figure><ul><li>Next, we wait about five minutes for the deployment to be complete and click “<strong>Download</strong>” to <strong>Save the deployment credentials</strong>.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/774/1*4pL7mCrkaX2AO3Kobl20aQ.png" /></figure><ul><li>Click “<strong>Continue</strong>” once the deployment is ready.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vJJTA5AT2cBWMVI4QjdD9g.png" /></figure><h4>Step 2: Set up Kali Linux VM</h4><p>Watch the following YouTube videos to learn how to set up Kali Linux VM in different virtualisation platforms:</p><ul><li>VirtualBox — <a href="https://youtu.be/sAMnXte56yY?si=fJA77ww-IyAvbv9y">https://youtu.be/sAMnXte56yY?si=fJA77ww-IyAvbv9y</a></li><li>Parallels — <a href="https://youtu.be/sAMnXte56yY?si=fJA77ww-IyAvbv9y">https://youtu.be/sAMnXte56yY?si=fJA77ww-IyAvbv9y</a></li><li>VMWare — <a href="https://youtu.be/U0AMu3rznc4?si=Z0CY5O8FhXea-Uvg">https://youtu.be/U0AMu3rznc4?si=Z0CY5O8FhXea-Uvg</a></li></ul><h4>Step 3: Install Elastic Defend as the Software Agent to Collect Logs and Forward the Audit logs and Telemetry from the Kali Linux VM to the Elastic SIEM</h4><p>An Agent is a small, lightweight software program installed on the server, endpoint, or device. This agent collects data such as logs, metrics, or security-related events and then sends this information to a centralised SIEM system for analysis, monitoring, and alerting. In this lab, <strong>Elastic Defend</strong> will be used as the agent.</p><p>Elastic Defend is a unified, lightweight software agent developed by Elastic to simplify the collection and monitoring of data across various environments. It provides organisations with prevention, detection, and response capabilities with deep visibility for EPP, EDR, SIEM, and Security Analytics use cases across Windows, macOS, and Linux operating systems running on traditional endpoints and public cloud environments. ​​</p><p>To set up this agent on our Kali Linux VM, we will follow these steps:</p><ul><li>First, we select the hamburger menu icon on the top left corner of the page and select “<strong>Add integrations</strong>” at the bottom of the menu page.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XzxWaCfEuHBUsgM35ATpXg.png" /></figure><ul><li>Next, we will search for “<strong>Elastic Defend</strong>” in the search bar and select the Elastic Defend integration.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*isgNyLMJD3llsjRc1LgJgw.png" /><figcaption>Elastic Defend integration</figcaption></figure><ul><li>Select “<strong>Add Elastic Defend</strong>” on the top right corner of the page.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sC4V0dLr1zWjiaKOHES1RA.png" /></figure><ul><li>Then, select “<strong>Install Elastic Agent</strong>” and copy the command for <strong><em>Linux Tar</em></strong><em>.</em></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1JEkuzGKq8d6gSgNdgyhjw.png" /><figcaption>Install Elastic Agent</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KUjJzFlZ7clqxiLv_hevIw.png" /></figure><ul><li>Next, we will paste the command into our Kali Linux VM terminal and click enter to run the command.</li></ul><p><strong>NOTE: The installation command has been modified due to an error encountered. Details will be found in the “<em>Issues Encountered</em>” section below.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*p5jWYbuAbzu0IkqICKVPGg.png" /><figcaption>Modified installation command for Elastic Defend</figcaption></figure><ul><li>Once the agent has been installed, a message will be displayed on the terminal confirming this installation. Logs will automatically be collected and forwarded to our Elastic SIEM instance.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kTfA3pWDXBj3fkxupzRLUA.png" /><figcaption>Successful Installation Confirmation</figcaption></figure><ul><li>To verify the agent installation has been successful, we will run the command, sudo systemctl status elastic-agent.service, in the Kali Linux VM terminal. The command in the image below will confirm the agent has been successfully installed.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3wWvqcZ0On6w04mM_qxloQ.png" /><figcaption>Verified Agent Installation</figcaption></figure><h4>Step 4: Generate Security Events on the Kali Linux VM using Nmap</h4><p>To test if the agent is working effectively, we generate some security events on the Kali Linux VM. To achieve this, Nmap will be utilised.</p><p>Nmap (Network Mapper) is a powerful open-source tool used for network discovery, security auditing, and vulnerability scanning. It is widely used by network administrators, security professionals, and hackers to explore networks, discover hosts and services, and assess security vulnerabilities.</p><p>We will follow these steps to run a Nmap scan:</p><ul><li>To install Nmap on other Linux VMs, open a new terminal and run the following command, sudo apt-get install nmap, to install it.</li><li>Since Nmap is already installed on Kali Linux, we will open a new terminal and scan the local host (Kali Linux VM) using Nmap by running the following command, command, sudo nmap -p- localhost. A couple of listening services would be found.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-drLb53HzTs-7kw8_dxpPA.png" /><figcaption>A Nmap scan using the command “sudo nmap -p- localhost”</figcaption></figure><ul><li>The local host can also be scanned by running the command, sudo nmap -sS localhost or sudo nmap -sT localhost.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZFhTUsKXNW6JjpNGNvpoVA.png" /><figcaption>A Nmap scan using the command “sudo nmap -sS localhost”</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HsIlZGznVslTzDfaZvSlww.png" /><figcaption>A Nmap scan using the command “sudo nmap -sT localhost”</figcaption></figure><p>The purpose of these scans is to generate multiple security events, such as detecting open ports and identifying the services running on those ports.</p><h4>Step 5: Query and analyse the Security Event logs generated in the Elastic SIEM using the Elastic web interface.</h4><p>After data has been forwarded from the Kali Linux VM to the Elastic SIEM, querying and analysing the logs can begin.</p><p>Follow these steps to begin:</p><ul><li>First, we navigate to our deployed Elastic SIEM Instance. Select the hamburger menu icon on the top left corner of the page and select “<strong>Logs</strong>” under the “<strong>Observability</strong>” section.</li><li>Next, we will select “<strong>Stream</strong>” under “<strong>Logs</strong>”.</li><li>Click on the search bar and type process.args: &quot;nmap&quot; to search for the security log events related to Nmap. Then click Enter.</li></ul><p><strong>NOTE: It may take time for the events to populate and display in the SIEM. Be patient.</strong></p><ul><li>The result of the search will look like the image below. You can navigate to one of the logs and click the blue menu icon on the right side to view more details.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ypW0yelsSNAOteVi7InwFQ.png" /><figcaption>Search results</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/980/1*9p0Q-p0IPCEh_vM7VK89jg.png" /><figcaption>More details of the search results (IP address has been redacted for security purposes)</figcaption></figure><h4>Step 6: Create dashboards to visualise the Security Events</h4><p>Creating dashboards is essential for transforming raw data into visual representations, such as charts, graphs, maps, and tables. This approach simplifies the understanding of complex data, making it easier to identify patterns, trends, and anomalies at a glance.</p><p>The following are the steps to creating dashboards:</p><ul><li>First, we navigate to the Elastic web portal at <a href="https://cloud.elastic.co/">https://cloud.elastic.co/</a>.</li><li>Then, click the hamburger menu icon on the top left corner of the page and select “<strong>Dashboards</strong>” under the “<strong>Analytics</strong>” section.</li><li>Click the “<strong>Create dashboard</strong>” button on the top right side of the page.</li><li>Click the “<strong>Create visualisation</strong>” button on the top left side of the page to add some fields to be visualised on the dashboard.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*u7hIK7G-bM7DQj8RdmZFxQ.png" /><figcaption>“Create visualisation” page</figcaption></figure><ul><li>Next, we navigate to the right side of the screen to select “<strong>Bar vertical stacked</strong>” as the visualisation type and change the “<strong>Data View</strong>” section beneath the visualisation type to “<strong>*metrics</strong>”.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vMQQWXRcd3d66hshySXRWw.png" /><figcaption>Visualisation Type and Data View Sections</figcaption></figure><ul><li>Then, we will select the “<strong>@timestamp</strong>” field in the “<strong>Horizontal Axis</strong>” section and the “<strong>Count</strong>” function in the “<strong>Vertical Axis</strong>” section. Then, click “<strong>Close</strong>”.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/718/1*MDAV9nQIkKW-ioQaGZrA3w.png" /><figcaption>Horizontal Axis Section</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/590/1*1uXtPo6psL4MnITImGpT3Q.png" /><figcaption>Vertical Axis Section</figcaption></figure><ul><li>Next, we will click the “<strong>Save and return</strong>” button in the top right corner of the page to save the dashboard.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*o9Z4pTdLOHkW4W1fqsSUhw.png" /><figcaption>“Edit Visualisation” Page</figcaption></figure><ul><li>We then input the title of our dashboard and description and then click “<strong>Save</strong>”.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JwbI9zzVtt3VsdI2r_urBQ.png" /></figure><h4>Step 7: Create alerts to notify the security events that are detected</h4><p>Alerts enable real-time notification of suspicious activities or security breaches. This proactive detection allows security teams to respond quickly to potential threats before they escalate. It also automates the monitoring process by continuously evaluating data against predefined conditions or thresholds. This reduces the need for constant manual oversight and ensures critical events are not missed.</p><p>To create an alert, we will take the following steps:</p><ul><li>First, we will click the hamburger menu icon on the top left corner of the page and select “<strong>Alerts</strong>” under the “<strong>Security</strong>” section.</li><li>Then, select the “<strong>Manage rules</strong>” button on the top right area of the page.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iKItY7vyK93eA9GVeyRFtg.png" /><figcaption>“Manage rules”</figcaption></figure><ul><li>Next, we will click the “<strong>Create new rule</strong>” button on the top right to create a new rule for our alert.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tpwxqijPXoyo63XNbuxjHg.png" /></figure><ul><li>Under the “<strong>Define rule</strong>” section, select “<strong>Custom query</strong>”.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*U8_32grgkF09dPKgSKnIvQ.png" /></figure><ul><li>After selecting, we will scroll down to the Custom query field and set event.action: &quot;nmap_scan&quot; as the condition for the rule. Scroll down, then click “<strong>Continue</strong>” to save the changes.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/822/1*DsuhBHcIaRkqd6xrnL5DRw.png" /></figure><ul><li>Next, we will navigate to the “<strong>About rule</strong>” section and input the name and description of the rule set &gt; Set the severity level of the alert, scroll down and click “<strong>Continue</strong>” to save the changes.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/940/1*HbOhTEOUF1ltkuJWQSpSzg.png" /></figure><ul><li>Next, we leave the “<strong>Schedule rule</strong>” section as is and click “<strong>Continue</strong>” to save the changes.</li><li>In the “<strong>Rule actions</strong>” section, we will select the connector type. In this case, the “<strong>Email</strong>” connector will be selected.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/916/1*H0w7sDUaVOH73sVAOHhSjg.png" /><figcaption>Connector type</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/766/1*_x_sbdYu3GQrxHbYTEDktA.png" /><figcaption>Information has been redacted for security reasons</figcaption></figure><ul><li>Finally, we will select the “<strong>Create &amp; enable rule</strong>” button to create the alert.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/920/1*C-6AJzd6qybwRrKZzBO_Ow.png" /></figure><p>The alert has been set to monitor Nmap scans. If detected, an alert will be triggered, and the actions set will be taken. Alerts can be viewed and managed in the “<strong>Alerts</strong>” section under the “<strong>Security</strong>”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XLvTUXD0VH_OHdDd499WTA.png" /><figcaption>Changes displayed on the dashboard after running a Nmap scan within 30 minutes of deployment</figcaption></figure><h4>Next Steps</h4><ul><li>We can add more agents to the Elastic SIEM so a couple of endpoints can push more telemetry to the dashboards.</li><li>We can also create more robust dashboards and alerts.</li><li>Generate more security events on the Kali Linux VM and query them in the Elastic SIEM.</li><li>Finally, we can test the alerts that have been created by generating more Nmap scans on our Kali Linux VM.</li></ul><h4>Issues Encountered</h4><p>In <strong>Step 4</strong>, when trying to install the Elastic Agent, an error was encountered, check below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*h5BS9PAvBsi5kfR57hhi8w.png" /><figcaption>Syntax error: Unterminated quoted string</figcaption></figure><p>After googling for a solution for the error, I came across a GitHub post about this issue and its solution. The solution was to change the command line to a different arch, “<strong>arm64</strong>”, instead of “<strong>x86_64</strong>”. (<em>Click the </em><a href="https://github.com/elastic/fleet-server/issues/2537#issuecomment-1526651915"><em>link</em></a><em> to the solution</em>). The image below contains the new command line code:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QcAhQDanHFHZ--pAdkOgMA.png" /><figcaption>Arch Change from “x86_64” to “arm64”</figcaption></figure><h4>Conclusion</h4><p>In this lab, I learned to build an Elastic SIEM lab that involved setting up a free Elastic account and configuring a Kali Linux VM for data collection using the Elastic Defend agent. This lab was designed to generate security events with Nmap, which were queried and analysed through the Elastic web interface. A dashboard was created to visualise these security events, and an alert system was implemented to provide real-time notifications for detected threats. This lab aimed to gain practical experience in deploying and managing an Elastic SIEM environment, which will enhance my ability to monitor and respond to security incidents effectively.</p><p>Thank you for taking the time to go through this walkthrough. Hopefully, it was helpful to you. Happy building!!</p><p><strong>NOTE: It is important that when done with the lab, you delete all the Elastic SIEM instances that have been deployed to prevent further charges.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8ebd0bd74f28" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[EscapeRoom Blue Team Challenge — Analyzing PCAPs with Wireshark]]></title>
            <link>https://medium.com/@mxyiwa/escaperoom-blue-team-challenge-analyzing-pcaps-with-wireshark-648d6b57a0c4?source=rss-10101a073228------2</link>
            <guid isPermaLink="false">https://medium.com/p/648d6b57a0c4</guid>
            <dc:creator><![CDATA[Muyiwa F.]]></dc:creator>
            <pubDate>Sat, 17 Feb 2024 02:32:51 GMT</pubDate>
            <atom:updated>2024-02-18T17:18:06.712Z</atom:updated>
            <content:encoded><![CDATA[<h3>EscapeRoom Blue Team Challenge — Analyzing PCAPs with Wireshark</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7hXAGpiCAfYDWyvcD_VB9w.jpeg" /></figure><p>This lab is the walkthrough of my approach to solving the “<strong><em>EscapeRoom</em></strong>” CTF by The Honeynet Project on the Cyberdefenders website. The goal is to perform a series of analyses of the PCAP files provided by the Cyberdefenders platform and answer a series of questions about my analysis.</p><h4><strong>Challenge Scenario</strong></h4><p><em>As a SOC Analyst, you are part of a company that specialises in hosting web applications through KVM-based Virtual Machines. Over the weekend, one of the Virtual Machines went down, and the site administrators began to panic as they feared this might be the result of malicious activity. They were able to extract a few logs from the compromised environment in hopes that you could investigate and determine what happened.</em></p><h4><strong>Tools / Technologies Used</strong></h4><ol><li>Parallels Hypervisor</li><li>Kali Linux</li><li>Wireshark</li><li>Ghidra</li><li>ZUI {Brim Security}</li><li>UPX (Ultimate Packer for eXecutables)</li></ol><h4>Disclaimer</h4><p><em>Because I do not know how infected the malicious PCAP files might be, the best practice for me was to run a VM and download the PCAP files there. Also, I downloaded Wireshark to analyse the malicious files.</em></p><h4>Steps</h4><ol><li>I started by launching my hypervisor (<strong>Parallels</strong>).</li><li>Next, I opened Kali Linux which had been pre-installed.</li><li>I proceeded to launch the Mozilla Firefox default web browser on my Kali Linux VM to navigate to the CTF challenge on the <a href="https://cyberdefenders.org/blueteam-ctf-challenges/18#nav-questions"><em>Cyberdefenders.com</em></a> website.</li><li>Next, I downloaded and extracted the files from the ZIP archive. This Zip archive is password protected so I was prompted to input the password before the extraction could take place.</li><li>Then, I proceeded to install Wireshark via the terminal on Kali Linux {<em>Following the steps in this post: </em><a href="https://medium.com/@fauziamutalib/installing-and-configuring-wireshark-on-kali-linux-as-a-newbie-e86cde3b9ee3"><em>Installing and Configuring Wireshark on Kali Linux for Newbies</em></a><em> by <br></em><strong><em>Fauzia Mutalib</em></strong>}.</li><li>Once Wireshark was launched, I proceeded to upload the pcap file to Wireshark by selecting “<strong><em>File &gt; Open &gt; Download &gt; EscapeRoom</em></strong> folder <strong><em>&gt; hp_challenge.pcap &gt; </em></strong><em>Select</em><strong><em> ‘Open’ </em></strong>” to upload<em>.</em></li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/603/1*QRd9s4t4J-kEpotBkwqDZw.png" /><figcaption>Image of the extracted pcap and log files</figcaption></figure><p>7. Next, I began analysing!</p><h4><strong>Challenge Questions</strong></h4><ol><li><strong>What service did the attacker use to gain access to the system?</strong></li></ol><p>ANS: <strong><em>SSH</em></strong></p><p>I was able to get this answer after analysing the Pcap file for the ports opened by navigating to “<strong><em>Statistics</em> &gt; <em>Endpoints</em> &gt; <em>TCP.71</em> &gt; <em>Port</em></strong><em>”. </em>I proceeded to click on<em> “</em><strong><em>Port</em></strong><em>” </em>to arrange the data in the column in a hierarchical format from less than to greater than.</p><p>There were three types of ports open, ports 22(<strong>SSH</strong>), 80(<strong>HTTP</strong>) &amp; ports ranging from 33677–60670 (<strong>Ephemeral Ports [</strong><em>1024–65535</em><strong>]</strong>).</p><p>Since the VM was remotely accessed, port 22 (<strong>Secure Shell</strong>) which<strong> </strong>is a well-known port number used for secure remote administration and file transfer over an unsecured network, is what the attacker used to gain access to the system.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*VVal-PHhRhCth4E0iIg5Aw.png" /><figcaption>Statistics menu in Wireshark</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/844/1*G3Sl5bSyPtKO_LLkDbmpgg.png" /><figcaption>Open ports in the <em>Endpoints menu (SSH Highlighted)</em></figcaption></figure><p>2. <strong>What attack type was used to gain access to the system? (one word)</strong></p><p>ANS: <strong><em>Brute-force Attack</em></strong></p><p>According to Wikipedia, in cryptography, a <strong>brute-force attack</strong> consists of an attacker submitting many passwords or passphrases with the hope of eventually guessing correctly. The attacker systematically checks all possible passwords and passphrases until the correct one is found.</p><p>From the network packet home page, I could see that the attacker tried to log into the system several times via SSH which is a great indicator of a <strong>brute-force attack.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/958/1*V-li_v8ydTA4vfWOol34jw.png" /><figcaption>Protocol showing several attempts to log in via SSH signifying a <strong>brute-force attack.</strong></figcaption></figure><p><strong>3. What was the tool the attacker possibly used to perform this attack?</strong></p><p>ANS:<strong> <em>Hydra</em></strong></p><p>Since I was able to identify that the attack performed was a brute force attack. I was able to conduct a quick Google search to identify the tool that most likely fits the effects of the attack identified. The tool discovered was “<strong><em>Hydra</em></strong>”.</p><p><strong>4. How many failed attempts were there?</strong></p><p>ANS: <em>There were</em><strong><em> 52 failed </em></strong><em>attempts.</em></p><p>To identify the number of failed attempts.</p><ul><li>First, I filtered the search to <strong>“<em>ssh</em>”</strong>.</li><li>Next, I navigated to “<strong><em>Statistics</em> &gt; <em>Endpoints</em> &gt; <em>TCP.54</em></strong><em>”. (</em><strong><em>TCP.54</em></strong><em> meaning there were 54 attempts to establish an SSH session</em>)</li><li>Next, I scrolled to the right of the screen to the column that identified bytes being sent from server (B) to client (A) {<strong>Packets B -&gt; A</strong>}.</li><li>From the {<strong>Packets B -&gt; A</strong>} column, I could identify that from the 54 attempts to establish an SSH session, there were only 2 successful attempts based on the bytes sent from server (B) to client (A).</li></ul><p>Therefore, there were 52 failed attempts to establish an SSH session.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BcSvqj0R7-OXr6Oaov3DzQ.png" /><figcaption>The two successful attempts to establish an SSH session.</figcaption></figure><p><strong>5. What credentials (username: password) were used to gain access? Refer to shadow.log and sudoers.log.</strong></p><p>ANS: <strong><em>manager: forgot</em></strong></p><ul><li>First, I started by navigating to the “<strong>EscapeRoom</strong>” folder extracted in the command terminal by typing cd Downloads &gt; ls &gt; cd EscapeRoom &gt; ls .</li><li>Next, I expanded both the “<em>shadow.log</em>” and “<em>sudoers.log</em>” files by typing, cd cat shadow.log and cat sudoers.log files respectively. The user and the hash of the passwords will be contained in the shadow.log file.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*slrl0ZIJrPsTJU3oY4nXBQ.png" /><figcaption>Navigating to the shadow.log file</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bFry_YHCIBWLpzx7BntGqw.png" /><figcaption>The hash of the password</figcaption></figure><ul><li>Then, I proceeded to figure out the hash of the password by using the “<a href="https://hashcat.net/wiki/doku.php?id=example_hashes"><strong>Hashcat</strong></a>” tool via the website by typing ctrl + F to open the search bar and then typing “<strong>$6$</strong>” from the first three characters of the hash.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-pN1h-F9pKGD6bW7v_esuw.png" /><figcaption>Standard Hash Format for Linux Machine (Hash Mode: 1800)</figcaption></figure><ul><li>I then identified the admin usernames in the “<em>sudoers.log</em>” file, copied their hashes from the “<em>shadow.log</em>” file enumerated on the terminal into a text editor by typing gedit “FILE_NAME.txt”and saved the file in my “<strong>EscapeRoom</strong>” folder.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fj-L5PNKgVtDnX4hJ-0O3w.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yh-TqfltxmjYt3BefbgCFw.png" /></figure><ul><li>Next, I put the file into a Hashcat command by typing hash cat -m 1800 rawdata.txt /usr/share/wordlists/rockyou.txt.gz, using both the hash node (1800) and the “<strong><em>rockyou.txt</em></strong>” free password list found on Kali Linux. I waited for about a minute for the command to be executed.</li><li>Two passwords were displayed with their respective hashes. I proceeded to compare the hashes to the ones on the “<strong>shadow.log</strong>” file to identify the usernames.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/992/1*9D4nxx6zDo8UEE6yIyPeoA.png" /><figcaption>Passwords extracted from the rockyou.txt password list.</figcaption></figure><p><strong>6. What other credentials (username: password) could have been used to gain access and also have SUDO privileges? Refer to shadow.log and sudoers.log.</strong></p><p>ANS:<strong> <em>sean: spectre</em></strong></p><p><em>*Refer to the answer obtained from Question №5.</em></p><p><strong>7. What tool is used to download malicious files on the system?</strong></p><p>ANS:<strong> <em>Wget</em></strong></p><ul><li>I got this answer by identifying the other protocol apart from SSH, observed from my initial findings on Wireshark which was HTTP.</li><li>I then typed “HTTP” in the search bar to list all the HTTP traffic.</li><li>I clicked on any traffic on the list. Then I right-clicked to follow the HTTP Stream and was able to identify that the User-Agent used was “<strong>Wget</strong>”, which is a free software package for retrieving files using HTTP, HTTPS, FTP and FTPS, the most widely used Internet protocols.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KwVybyIyerPEToYDnvA6zA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PEiR38DL4wZoUteYRKLzDA.png" /><figcaption>HTTP Stream</figcaption></figure><p>Another way the answer can be found is by using ZUI.</p><ul><li>I went to the search bar and typed {<strong><em>_path==“http”</em></strong>}.</li><li>Then I scrolled towards the right side of the screen.</li><li>I then analysed the “<em>user_agent</em>” column and identified that “<em>wget</em>” was used.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*baCyARkNJl4Q6Du-GJrQ5w.png" /></figure><p><strong>8. How many files did the attacker download to perform malware installation?</strong></p><p>ANS:<strong> <em>3</em></strong></p><p>I got this answer by navigating to “<em>File &gt; Export Objects &gt; HTTP</em>” on Wireshark and was able to identify three suspicious-looking files with filenames “1,2,3”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/744/1*VeUg_y7qBpQKabaFJo7DOg.png" /><figcaption>Wireshark HTTP Object List</figcaption></figure><p><strong>9. What is the main malware MD5 hash?</strong></p><p>ANS: <strong><em>772b620736b760c1d736b1e6ba2f885b</em></strong></p><ul><li>Using ZUI, I was able to locate the MD5 hash by identifying the actual malware which I did by typing {<strong><em>_path ==“http” | sort ts</em></strong>} in the search bar to navigate to the three files the attacker downloaded to perform the malware installation.</li><li>Next, I scrolled to the far right of the page to the “<strong><em>resp_mime_types</em></strong>” column and was able to identify the actual malware file which was labelled “<strong><em>application/x-executable</em></strong>” which was in file 1.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SXbkKbjXFdLCfHafF3C7ow.png" /></figure><ul><li>I then proceeded to derive the MD5 hash by typing {<strong><em>_path ==“files” | sort ts</em></strong>} in the search bar and then used the malware file labelled “<strong><em>application/x-executable</em></strong>” under the “<strong><em>mime_type</em></strong>” column to trace the data displayed to the “<strong><em>md5</em></strong>” column where the hash was displayed.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qyYOD9KxkvRQB1Dvm4XkyA.png" /></figure><p><strong>10. What file has the script modified so the malware will start upon reboot?</strong></p><p>ANS:<strong> <em>/etc/rc.local</em></strong></p><ul><li>After a quick Google search to identify what script was modified so that the malware can run upon reboot, I came across an article on Superuser that identified that one simple place where to put your script to be run at system boot time is <strong><em>/etc/rc.local</em></strong>.</li></ul><p><strong>Article:</strong> <a href="https://superuser.com/questions/294967/where-and-how-are-custom-startup-commands-configured-in-linux">Where and how are custom startup commands configured in Linux?</a></p><ul><li>To confirm this, I searched for “<strong><em>rc.local</em></strong>” on the “<strong>Find a packet</strong>” search tool. I then configured the search to “<strong>Packet details &gt; Narrow &amp; Wide &gt; String</strong>”. I got one hit. Check below.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*12xf9_l1Im6TZ6ZZDKO69A.png" /></figure><ul><li>Next, I followed the TCP stream of that packet. Here, I was able to confirm that the script was indeed a malware script by the indication of suspicious activities (a bunch of “<em>/var/mail/mail</em>” in the script).</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_Nv05_NSu69PTQ_FN_L40Q.png" /><figcaption>TCP Stream of the packet with the malware script</figcaption></figure><p><strong>11. Where did the malware keep local files?</strong></p><p>ANS:<strong> <em>/var/mail</em></strong></p><p>I got this answer by analysing the bash script from the previous question which indicated where the malware kept local files.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/938/1*36sctPQxrhVZhlDy2aBxvA.png" /><figcaption>Bash Script in the TCP Stream indicating where the malware kept local files.</figcaption></figure><p><strong>12. What is missing from ps.log?</strong></p><p>ANS:<strong> <em>/var/mail/mail</em></strong></p><p>After analysing the bash script from the TCP Stream again, I was able to identify two commands in a line of code indicating what was missing from ps.log. The two commands are nohup and /dev/null.</p><p>a. nohup: <em>is short for “No Hangups.” It’s not a command that you run by itself. </em><em>nohupis a supplemental command that tells the Linux system not to stop a command once it has started.</em></p><p>b. /dev/null: <em>It is a virtual device, which has a special property: Any data written to /dev/null vanishes or disappears. Because of this characteristic, it is also called bitbucket or blackhole.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/868/1*gwP4D2W431QsrQrhYAbAWw.png" /><figcaption>Bash script in the TCP Stream indicating the commands used to discard the information from ps.log.</figcaption></figure><p>In this instance, these two commands completely discarded all the information in “<strong><em>var/mail/mail</em></strong><em>”. </em>To confirm this, I expanded the contents of ps.log and investigated to make sure <em>“</em><strong><em>var/mail/mail</em></strong><em>” </em>was missing from the contents of ps.log because it was being discarded by the malware itself.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HrqQFYATfQ_pg-7bXO_VRw.png" /><figcaption>Image 1 of the contents of ps.log.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8G05DPOXJ4kYvgn7I3On7w.png" /><figcaption>Image 2 of the contents of ps.log.</figcaption></figure><p>The mage above displays the contents of ps.log indicating “<strong><em>var/mail/mail</em></strong><em>” is what is missing from </em>ps.log<em>.</em></p><p><strong>13. What is the main file that was used to remove this information from ps.log?</strong></p><p>ANS:<strong> <em>sysmod.ko</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/896/1*XCLXzWujeWsrToWCzS1JqA.png" /></figure><p>After I analysed the bash shell script, it revealed the presence of malware labelled “<strong>2</strong>,” stored in the etc/modules directory as <strong><em>sysmod.ko</em></strong>. This directory typically holds kernel module names to load at boot time. In the context of the malware, “<strong>1</strong>” serves as the primary malware file, while “<strong>3</strong>” represents the shell script. Consequently, “<strong>2</strong>” functions as the file responsible for clearing data from the ps.log file.</p><p><strong>14. Inside the Main function, what is the function that causes requests to those servers?</strong></p><p>ANS:<em> </em><strong><em>requestFile</em></strong></p><ul><li>First, I downloaded the main malware (“<strong>1</strong>”) file from the PCAP file on Wireshark. Started by clearing all open searches then navigated to <em>File &gt; Export Objects &gt; HTTP</em>. Clicked filename “<strong>1</strong>” and saved to the <em>EscapeRoom </em>folder.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WPewJmOx1QeQgFFj92xovw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/864/1*zuIICG_4O4U6EwgwzglNyg.png" /><figcaption>Malware “1” file saved in the EscapeRoom Folder</figcaption></figure><ul><li>Next, I proceeded to install <strong><em>Ghidra</em></strong>, a software reverse engineering (SRE) framework created and maintained by the National Security Agency Research Directorate {<a href="https://youtu.be/Hiu6OZXtK-A?si=61wSKQVWLdgLPSXj"><em>How-to-install-Ghidra</em></a><em>}.</em></li><li>After launching Ghidra, I then created a new project by navigating to <em>File &gt; New Project &gt; Selected “Non-Shared Project” &gt; Next &gt; Navigated to my EscapeRoom project directory &gt; Set my custom project Name &gt; Clicked “Finish</em>”.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/850/1*TTfbWk5A-E3YebU35uU43g.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/856/1*qBPOnDh53LqvwJ7KKsThVQ.png" /></figure><ul><li>Next, I proceed to decompress malware “<strong>1</strong>” initially downloaded by using <strong>UPX</strong> {<em>Ultimate Packer for eXecutables</em>} which is a free, open-source, advanced executable file compressor, which means it compresses executable files and reduces their size. It achieves this by employing a variety of compression algorithms. To achieve this, I ran the command, upx -d &lt;Compressed_Malware_Name&gt; -o &lt;New_Decompressed_Malware_Name&gt;.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/818/1*bVXYBGTF82GKnPhDC_2Z0w.png" /><figcaption>Decompressing the executable file with UPX</figcaption></figure><ul><li>After decompression, I dragged the decompressed malware file into <em>Ghidra</em> to be reverse-engineered and then clicked “<strong>OK</strong>” to run.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/860/1*dhnholDkJik6I0RHlHMlIw.png" /><figcaption>Imported decompressed executable file requesting permission to run.</figcaption></figure><ul><li>I opened the imported executable file (<strong><em>DecompressedMalware</em></strong>). I was prompted with an option to analyse because I had not done that. I selected “<strong>Yes</strong>” and then “<strong>Analyze</strong>”.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IfdZD2EEsD-f2wfD2wlAEA.png" /></figure><ul><li>After analysing, I searched for “<strong>request</strong>” in the filter bar on the left side of the page because the question was to investigate what caused <strong><em>requests</em> </strong>to those servers<strong>. requestFile </strong>was the function inside the main function that gets files from the server.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IxArJ2H2X-Vv3L9EKqtsaQ.png" /></figure><p><strong>15. One of the IPs the malware contacted starts with 17. Provide the full IP.</strong></p><p>ANS: <strong><em>174.129.57.253</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1fOsbcuBYfjg2UZdHurIzw.png" /></figure><ul><li>Got this answer by navigating to <em>File &gt; Export Objects &gt; HTTP and then identified the IP that started with 17 which is highlighted above.</em></li></ul><p><strong>16. How many files did the malware request from external servers?</strong></p><p>ANS: 9</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IjdIzSIqXsdyn64Ehm4TIw.png" /><figcaption>PCAP File from ZUI</figcaption></figure><p>I got this answer by counting the number of requests highlighted above that are not malware files on ZUI / Brim Security.</p><p><strong>17. What are the commands that the malware was receiving from attacker servers? Format: comma-separated in alphabetical order</strong></p><p>ANS: <strong><em>NOP, RUN</em></strong></p><p>I got this answer by using Ghidra to reverse-engineer the main malware file.</p><ul><li>First, I navigated to the <strong>Symbol tree</strong> on the left side of the page. Clicked the “<strong>Functions” </strong>folder and then navigated to <strong><em>processMessage</em></strong> (<em>Instead of spending hours analysing each function, I was able to get information on the internet from people who have attempted this project on which particular function to investigate</em>).</li><li>Next, I was able to identify two different hex codes (<em>highlighted in blue in the image below</em>) on the right side of the Ghidra page which would eventually be translated to ASCII using <a href="https://onlinetools.com/hex/convert-hex-to-ascii#examples">Online Tools</a>.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sJDqZ7lA-q0aXUjYJJMq1g.png" /><figcaption>“processMessage” from the Functions folder in the Symbol Tree.</figcaption></figure><ul><li>I then proceeded to convert the hex codes to ASCII on Online Tools. The ASCII conversion was <strong>NOP, RUN</strong>.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ycPb1QqZrDMdQ4h3bO1_1g.png" /></figure><p>According to Wikipedia, NOP means “No Operation” and is a machine language instruction and its assembly language mnemonic, programming language statement, or computer protocol command that does nothing. RUN means both “to run” and “to execute” which refers to the specific action of a user starting (or <em>launching</em> or <em>invoking</em>) a program, as in “Please run the application.”</p><h4>Issues Encountered</h4><p>I ran into an issue in <strong>Question №5</strong>.<strong> </strong>The problem was simply a permission error encountered when trying to unzip the “<strong>rockyou.tx.gz</strong>” password list file. So, I took the steps highlighted.</p><ul><li>First, I typed cdto navigate to the root folder on the command terminal.</li><li>Next, I typed cd /usr/share/wordlists/ to navigate to the wordlists folder.</li><li>Typed ls to enumerate the content of the folder and then ls -l rockyou.txt.gz to identify the permission on the zipped “<strong>rockyou.txt</strong>” file.</li><li>Then I typed gzip -d rockyou.txt to try to unzip the file but I ran into a permission error. I remediated this by adding the sudo command to the previous command, sudo gzip -d rockyou.txt.</li><li>After, extracting the files from the zip folder, I used cat rockyou.txt to display the contents of the unzipped file.</li></ul><h4>Closing Remarks</h4><p>This CTF was most definitely challenging and brain-tasking, but I enjoyed it and I was able to learn a lot. It exposed me to a wide range of tools such as Ghidra, which taught me house to reverse engineer malware, Wireshark for analysing captured traffic and ZUI. I hope this write-up can be useful to anyone who wants to attempt this challenge. Thanks for reading!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=648d6b57a0c4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Azure Sentinel SIEM Lab: Mapping Live Cyber Attacks on World Map]]></title>
            <link>https://medium.com/@mxyiwa/azure-sentinel-siem-lab-to-map-live-cyber-attacks-d74c2426d59b?source=rss-10101a073228------2</link>
            <guid isPermaLink="false">https://medium.com/p/d74c2426d59b</guid>
            <dc:creator><![CDATA[Muyiwa F.]]></dc:creator>
            <pubDate>Tue, 03 Oct 2023 03:12:39 GMT</pubDate>
            <atom:updated>2024-09-21T14:55:15.621Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CYLdPeSCwduGAyZgUsx7ZA.png" /><figcaption>A map created in Microsoft Sentinel displaying real-time cyber attacks from all over the world.</figcaption></figure><h3>What is Azure Sentinel?</h3><p>Azure Sentinel is a cloud-native security information and event management (SIEM) solution offered by Microsoft as part of its Azure cloud platform. It is designed to help organisations detect, investigate, and respond to security threats and incidents across their entire enterprise, including on-premises and multi-cloud environments.</p><h4>Lab Objectives</h4><p>The goal of this lab is to create a virtual machine in the cloud to map out live cyber-attacks on a world map using a vulnerable Azure Virtual VM (Honeypot) on the internet and then monitor and log attacks from different IP addresses from various countries all over the world and display the data on a world map to visualise where all the attacks are coming from.</p><h4><strong>Technologies and OS used</strong></h4><ol><li>Parallels Virtual Machine</li><li>Windows 11</li><li>Microsoft Azure Sentinel (SIEM)</li><li>PowerShell</li><li>IP Geolocation</li></ol><h3>Steps:</h3><ul><li>Create an Azure subscription account (It’s free. You get $200 worth of free credits).</li><li>Create a Virtual Machine in Azure (Turn the external firewall off and the Windows firewall too).</li><li>Create a log repository called a <strong>Log Analytics Workspace</strong> in Azure, which will be used to ingest logs into the virtual machine.</li><li>Next, set up Microsoft Sentinel within Azure to map all the different attackers’ data.</li><li>Use PowerShell to extract the IP Address from the Windows logs and send it to a third-party API.</li><li>The third-party API will then derive the latitude, longitude, state/province, etc., and send it back to the VM.</li><li>Create a custom log in the Log Analytics Workspace with the geographic data in it.</li></ul><h3>Create an Azure subscription account</h3><ol><li>Go to <a href="https://azure.microsoft.com/en-gb/free">Create Your Azure Free Account Today | Microsoft Azure</a> . To create an Azure Free Subscription Account.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bC9hB7-Z6MeUWaNT-OMFtg.png" /></figure><p>2. Once the subscription has been created, go to https://portal.azure.com</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DfprtAaGaL8JoIRHOeoOBA.png" /></figure><p><strong>N.B: <em>Make sure to delete your resources when you’re done with the lab (or they will eat up the free $200 and start deducting funds from your account as long as they keep running).</em></strong></p><h3>Create A Virtual Machine</h3><ul><li>Search for the <strong><em>Virtual Machine</em></strong> service in the search bar and select it.</li><li>Go to Create &gt; Select Azure Virtual Machine &gt; Go to <strong><em>Resource group</em></strong> and select “<strong><em>Create new</em></strong>” &gt; Name it.</li><li>Go to the “<strong><em>Virtual machine name</em></strong><em>” </em>field and name it to your preference.</li><li>Leave all other settings as default. Change the “<strong><em>Security Type</em></strong>” to Standard.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mJv6SzV72z2TLnHGECsP2g.png" /></figure><ul><li>Input a username and password you will remember (<strong><em>don’t use your actual password or username for any real account</em></strong>)</li><li>Scroll to the bottom and tick the agreement box.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XG_pr53l1V3_ujZ_v3_V4w.png" /></figure><ul><li>Select “<strong><em>Next:Disks</em>” </strong>(skip this settings all the way to <strong><em>Next:Networking</em></strong>)</li><li>Go to “<strong><em>NIC network security group”. </em></strong><em>Select “</em><strong><em>Advanced</em></strong><em>”.</em></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Y2nAqhNO8WZKPaThv2RbOw.png" /></figure><ul><li>Go to the “<strong><em>Configure network security group” &gt;</em></strong><em> Click </em><strong><em>“Create new” </em></strong><em>to create a new network security group</em></li><li>Delete the inbound rule already there.</li><li>Select “<strong><em>Add an inbound rule” </em></strong>to create a new inbound rule that allows everything into the VM.</li><li>Leave all settings as default except;<br>- <strong>Destination port ranges</strong> = “*”<br>- <strong>Priority</strong> = “100&quot;<br>- <strong>Name </strong>= “PREFERED_NAME”</li><li>Then select “<strong><em>Add” </em></strong><em>at the bottom.</em></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5HGteMXIt3d0CjgZncqvXg.png" /></figure><ul><li>Select “<strong>OK</strong>” then “<strong>Review + Create</strong>”. Further settings are not required for this section.</li><li>Wait for validation to be passed and select “<strong>Create</strong>”.</li></ul><h3>Create a Log Analytics Workspace</h3><p>While the VM is in the process of deployment, proceed to create a log analytics workspace.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*S_nYcoVbsLcqw7CO_bq7-w.png" /></figure><ul><li>Go to the search bar above and search for “<strong><em>Log Analytics workspace</em></strong>” service and select it.</li><li>Select “<strong><em>Create Log Analytics Workspace</em></strong>”.</li><li>Set the project details as;<br>- <strong>Subscription</strong> = “DEFAULT_SUBSCRIPTION”<br>- <strong>Resource Group </strong>= “RESOURCE_GROUP_CREATED”<br>- <strong>Name </strong>= “PREFERED_NAME”<br>- <strong>Region</strong> = “West US 2”</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JiDj6Snj6Vdj2YJQs3vAEQ.png" /></figure><ul><li>Select “<strong><em>Review + Create</em></strong>”.</li><li>Wait for validation to be passed and select “<strong><em>Create</em></strong>”.</li><li>Next, go to the search bar and search for “<strong>M<em>icrosoft Defender for Cloud</em></strong>” formerly “<strong><em>Security Center</em></strong>”, to enable the ability to gather logs from the VM into the Log Analytics Workspace.</li><li>On the left side of the screen, go to Management &gt; Environment settings &gt; Select the dropdown menu for the subscription &gt; Select the Log Analytics Workspace that was just created.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pZh1zPfMFqiOSFvAEHVGqg.png" /></figure><ul><li>Under the <em>Defender Plans</em> menu, Turn on Servers and turn off the SQL servers.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Zkw1qwcVHmFHfW0wSjVs_A.png" /></figure><ul><li>Click “<strong><em>Save</em></strong>”</li><li>Next, click the <em>Data Collection </em>menu and select “<strong><em>All Events</em></strong>”. Then save it.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OAXpRpoMZgBCrvk2jSem_A.png" /></figure><ul><li>Next, go back to the Log Analytics Workspace &gt; Click your workspace &gt; Click “<strong><em>Virtual Machine</em></strong>” &gt; Click the VM created early and select “<strong><em>Connect</em></strong>”.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*olTbnbwtHcgTArUrie3lrg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ndSDp7arjzLMDawgyTODXA.png" /></figure><h3><strong>Set up Microsoft Sentinel with Azure</strong></h3><ul><li>While the VM tries to connect, open Azure in a new tab in the browser and set up Sentinel</li><li>Search for “<strong><em>Microsoft Sentinel</em></strong>” in the search bar and click to open</li><li>Click “<strong><em>Create Microsoft Sentinel</em></strong>” &gt; Click the workspace created and click the “<strong><em>Add</em></strong>” option below</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ckigiv6flpCQBc7RuKeJdA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*f8kkE3k3zD5N7X-8vYVMKA.png" /></figure><ul><li>Next, go back to the previous tab. Go to the VM and click to open.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_o_FOa-uTL9U0vwSPdqMnw.png" /></figure><ul><li>Copy the Public IP Address to log into the VM via a Remote Desktop</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*V-sJv3ZNUdqintvgzQXX7g.png" /></figure><ul><li>Next, open the start menu on your Windows computer and search and open the “<strong><em>Remote Desktop Connection</em></strong>”</li><li>Paste the Public IP Address. Click the “<strong><em>Show Options</em></strong>” button to configure the display settings &gt; Select the “<strong><em>Display</em></strong>” tab and drag the cursor indicating the size of the remote desktop away from the maximum (large) size.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/904/1*3BwiRnWBmTCSD1VR-mdARQ.png" /></figure><ul><li>Then click “<strong><em>Connect</em></strong>”.</li><li>Credentials used to create the VM will be required to connect to the Public IP Address. Type the VM username and password &gt; Click OK &gt; Tick the box prompting to accept certificate errors and click “<strong><em>Yes</em></strong>”.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1008/1*o1kj3SOTkIOBtxO6SB8hOw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Xwtamsy7YyoCjY8H6_LPcA.png" /></figure><ul><li>Now, the VM is remotely logged into</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9zhNgjsnPxh5MsgUcoTySw.png" /></figure><p><strong><em>N.B: It is recommended you open the Remote Desktop Connection on a Windows Virtual machine, preferably VMware or Parallels</em></strong></p><ul><li>Next, proceed to set up the Microsoft Edge browser on the remote desktop.</li><li>Inside, the remote desktop, click on Start and navigate to “<strong><em>Event Viewer</em></strong>”</li><li>On the left side of the screen, click “<strong><em>Windows Logs</em></strong>” &gt; Security &gt; and select one of the audit logs, <strong><em>Audit Failure </em>with Event ID: <em>4625</em></strong></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dt2dSmMqgqyU9FxxHMHohg.png" /></figure><ul><li>After opening one of the failed audit logs, navigate to the “<strong><em>Network Information</em></strong>” section. The IP Address from there is from the VM trying to log into the remote desktop.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/830/1*_cdgZXoYQv_-vQKgsMFeqw.png" /></figure><p><strong><em>N.B: The Remote Desktop is what attackers are going to try to log into. After discovering the VM on the internet, their IP Addresses are going to be displayed in the “Network Information” section as displayed in the picture above, when they fail or succeed in logging into the Remote Desktop.</em></strong></p><h3>Using PowerShell to extract the IP Address from the Windows logs and send it to a third-party API (IP GEOLOCATION)</h3><p>Since the information in the previous step only provides their IP Addresses and not their location, what is going to be done next is to programmatically, with PowerShell, take their IP Addresses and use an IP Geolocation API to find their locations.</p><p>From the information obtained from one of the IP Addresses, proceed to use the information to create a custom log and then send that log to the Log Analytics Workspace. Then use Microsoft Sentinel to plot out the attackers on the map. with the information obtained.</p><ul><li>First, copy the IP Address from the “<strong><em>Network Information</em></strong>” on the Remote Desktop &gt; Navigate to the IP geolocation website on the web browser (<a href="https://ipgeolocation.io/">Free IP Geolocation API and Accurate IP Geolocation Database</a>) &gt; Paste the IP Address obtained from the Remote Desktop and information such as the Country name, Latitude, Longitude, etc, will be displayed.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ce9xkJ9u8y3VLuZM_v3uIA.png" /></figure><ul><li>Next, navigate to the Windows VM and turn off the firewall so that the VM can be more susceptible or respond to ICMP echo requests and be discovered on the internet much faster.<br>- Go to Start on your Windows VM &gt; Search for “<strong><em>wf.msc</em></strong>” to navigate to the firewall &gt; Click “<strong><em>Open</em></strong>” &gt; Select “<strong><em>Windows Defender Firewall Properties</em></strong>” &gt; Turn off the “<strong><em>Firewall state</em></strong>” in the Domain Profile, Private Profile, and Public Profile. &gt; Click “<strong><em>Apply</em></strong>” then “<strong><em>OK</em></strong>” &gt; Exit the mscfirewall window.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/772/1*wAzIKLGT9LSABoN48pZhJQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/995/1*JvFkUehHhTLzF0zflaQE5A.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/397/1*LCZgvileYabYW8MM-KVO_g.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/394/1*Y3sBNxDqG9IdM-BkM_X6jg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/391/1*vkIxxxmJUSk1CTWxwtYwig.png" /></figure><ul><li>Next, proceed to your host machine &gt; open the command line and ping the VM<br>- Type “ ping VM_IP_ADDRESS -t”. To confirm it’s accessible through the internet.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*V4rrxMA67l2WpWcUK-8XIg.png" /></figure><ul><li>Close the Command Line in the host machine and the Event Viewer in the VM/Remote Desktop.</li><li>Next, download/copy a custom PowerShell script from the GitHub repository (<a href="https://github.com/Mxyiwa/SIEM-AzureSentinelLab/blob/main/Log%20Exporter.ps1"><strong>PowerShell Script</strong></a>)</li><li>Next, on the Windows VM/Remote Desktop, Go to Start &gt; Search for “<strong><em>Windows PowerShell ISE”</em></strong>, and open it.</li><li>Click on File &gt; New &gt; Paste the copied PowerShell script and save to the Desktop.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5a9H9LJEOT5KqE6kSDyJgA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ordo_douCDSN97Ebn3yCDA.png" /></figure><p><strong><em>N.B: The PowerShell script has been custom-created so there is no need to care too much about it. What is important is obtaining the API Keys for the IP Address to be converted to the data needed such as the longitude, latitude, country, etc.</em></strong></p><ul><li>To obtain the API Key, go to the website, <a href="https://ipgeolocation.io/">Free IP Geolocation API and“ Accurate IP Geolocation Database</a>. Click the hamburger menu &gt; Select “<strong><em>Sign Up</em></strong>” &gt; Sign up and get the free API key (<strong><em>The free version can only accommodate 1000 API calls per day</em></strong>)</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0Zmgn1IFSj7s1ZQ68iCXXw.png" /></figure><ul><li>Go to the Windows PowerShell ISE custom log script and paste the API Key obtained in the “<strong><em>API KEY</em></strong>” section</li><li>Press Ctrl + S to save the changes.</li></ul><p>The PowerShell Script looks through the event logs and extracts all the events of people who failed to log in, extracts their IP addresses/geo-data, and creates a new log file. This log file output is located in the “<strong><em>ProgramData</em></strong>” directory on the VM/Remote Desktop (<strong><em>The file path is highlighted in the picture below</em></strong>).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9hfF3p0Vgb7WodVjTap7Lg.png" /></figure><ul><li>Next, click the run icon on the top of the Windows PowerShell ISE to run the script</li><li>The “purple” output displayed is a representation of failed log-ons <br> <strong><em>N.B: The failed log-ons displayed are sample ones</em></strong>.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Qnoy1PbKnUjzbnQrGYm1Gg.png" /></figure><p>A log file will be created in the directory as well, which will be used to configure Log Analytics Workspace to be able to detect real-life failed log ons.</p><h3>Create a custom log in the Log Analytics Workspace with the geographic data in it</h3><ul><li>Next, create a custom log in the Log Analytics Workspace on Azure</li><li>Navigate to Log Analytics Workspace &gt; Select the workspace created&gt; Tables&gt; Select Create &gt; Select New custom log (MMA-based) &gt; Click the file icon to add a log file</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cG8hs0tt-J0jFa_e_hHxjw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3pg5QhYdDkoxTmMRRDcH8w.png" /></figure><ul><li>Since the log file is on the VM/Remote Desktop, Go to the VM/Remote Desktop &gt; Select Windows Key + R&gt; Type in the search prompt “<strong><em>C:\ProgramData\</em></strong>”. The custom log file will be titled “<strong><em>failed_rdp</em></strong>”.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/435/1*_MphBk_B5wfizybGWhgvmw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/831/1*tQ1Qg3LAcgcIjqxm-z-60Q.png" /></figure><ul><li>Open and copy the contents of the log file.</li><li>Open “<strong><em>Notepad</em></strong>” on the host PC and paste the contents there.</li><li>Save on the desktop of the host PC as “<strong><em>failed_rdp.log</em></strong>”.</li><li>Next, go back to the “<strong><em>Create Custom Log</em></strong>” step in your browser, select the file icon to navigate to the “<strong><em>failed_rdp.log</em></strong>” location and select it.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hoD6Zg48uz-2TdHPQoOygQ.png" /></figure><ul><li>Click “<strong><em>Next</em></strong>” to Record Delimiter (<strong><em>look through the data to confirm the failed logins</em></strong>).</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bn7_iZAlV9Jz5bjxElEGlA.png" /></figure><ul><li>Click “<strong><em>Next</em></strong>” to Collection Paths which is the location of the log on the VM/Remote Desktop, select Windows as the type and “<strong><em>C:\ProgramData\NAME_OF_THE_LOG_FILE</em></strong>” as the path (Make sure the path is correct).</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*H5uJRwrPCyfOF9TGlPNopg.png" /></figure><ul><li>Click “<strong><em>Next</em></strong>” and rename the custom log name to any name preferable.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*l5Zg_XuH3mNQwAxy7Yc7Ng.png" /></figure><ul><li>Click “<strong><em>Next</em></strong>” and Create to create the custom log.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FWfNYCB0U5BrFCgslOMV2w.png" /><figcaption><strong><em>N.B: It will take a few minutes for the Log Analytics Workspace and Virtual machine to sync after creating the custom log</em></strong></figcaption></figure><ul><li>Next, go to Log Analytics Workspace on Azure &gt; Select the workspace created &gt; Select “<strong><em>Logs</em></strong>” &gt; Type the custom log name in the search &gt; Click on “<strong><em>Run”</em></strong> to display the geodata from the log file.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qUtlDOPsivSL6NGUqKgWvQ.png" /></figure><p>Unfortunately, Microsoft has deprecated the feature to extract fields from the data so a solution discovered on the internet is to plot the custom script below into the workbook</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/904/1*EZinqE9Au_g_3Karuz0HLg.png" /></figure><ul><li>Then run it. The result is displayed below.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_GkJ3W1AOdfHhgO59otDZw.png" /></figure><p>The section highlighted is the failed login geodata of some attackers.</p><h3>Setting Up the Attack Map On Sentinel</h3><ul><li>Open a new tab on the browser and navigate to the Azure portal</li><li>Search for Microsoft Sentinel &gt; Select your workspace &gt; Click on “<strong><em>Workbooks</em></strong>” under Threat Management &gt; Select “<strong><em>Add Workbook</em></strong>” to add a new one &gt; Click “<strong><em>Edit</em></strong>” to remove the default widgets</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*i9xozqwXdyH-MlW_lCs8Jw.png" /></figure><ul><li>Next, Select “<strong><em>Add</em></strong>” &gt; Add Query</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Okww790od9v6zQPJgenz-g.png" /></figure><ul><li>Copy and paste the query from the GitHub repository (<a href="https://github.com/Mxyiwa/SIEM-AzureSentinelLab/blob/main/Log%20Analytics%20workspace%20Logs%20Query.txt"><em>Log Analytics workspace Logs Query</em></a><em>) </em>into the workspace query field.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/928/1*97p4D-D_ZUa3CAUfoYwExQ.png" /></figure><ul><li>Select “<strong><em>Run Query</em></strong>” &gt; Change Visualisation to “<strong><em>Map</em></strong>” and Size to “<strong><em>Full</em></strong>”</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9auSXocUCobG_ekw0uGy-A.png" /></figure><ul><li>Open Map Settings and make sure the fields are set to pull information from each of its specific data sources. Make sure the “<strong>Metric Label = label” &amp; “Metric Value = “event_count</strong>”</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/413/1*bQFOQw60EHl4Qj2OxkG8qg.png" /></figure><ul><li>The attacks would then be displayed on the map.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PvSW40u1IiYWlGwlvE-PMQ.png" /></figure><ul><li>Next, Save the Workbook.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mW-Np0iqmR69JmXtPl5E9Q.png" /></figure><p>After a period of time, a couple of minutes or hours later, attackers all over the world with their failed log-ons will be displayed on the map.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CYLdPeSCwduGAyZgUsx7ZA.png" /><figcaption><strong>After 30 minutes, the majority of the attackers were from Martinique</strong></figcaption></figure><h3>Closing Remarks</h3><p>This lab emphasises the need for cybersecurity. Once you can access the internet through any platform, it is important to know that you can be cyber-attacked from anywhere in the world which is why it is important for internet users to take cybersecurity very seriously. Some best practices include installing security updates, using strong passwords, enabling MFA, etc.</p><p><strong><em>N.B: It is very important that when done with the lab, you delete all the resources or else they’ll eat up your free $200 and roll over the frier tier to paid.</em></strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d74c2426d59b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Exploiting AWS 1 {FLAWS Challenge}]]></title>
            <link>https://medium.com/@mxyiwa/exploiting-aws-flaws-challenge-342e45efe76e?source=rss-10101a073228------2</link>
            <guid isPermaLink="false">https://medium.com/p/342e45efe76e</guid>
            <dc:creator><![CDATA[Muyiwa F.]]></dc:creator>
            <pubDate>Wed, 06 Sep 2023 18:35:28 GMT</pubDate>
            <atom:updated>2023-12-30T23:38:43.960Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RBo36hSryK-gyaidAcqmSw.jpeg" /></figure><p>This article provides a detailed approach to navigating successfully through this challenge. This challenge, <a href="http://flaws.cloud/"><strong>flaws.cloud</strong></a>, was created by Scott Piper of Summit Route.</p><p><strong>Challenge Overview</strong></p><p>This challenge comprises a series of levels, six levels to be exact, designed to teach some common mistakes made when using Amazon Web Services (AWS) including IAM, EC2, S3, and more, and how to exploit them. A series of hints are provided to assist in teaching how to discover the information needed to pass each challenge.</p><p><strong>Technologies and OS used</strong></p><ol><li>Parallels Virtual Machine</li><li>Kali Linux OS</li><li>AWS Console</li></ol><p><strong>Disclaimer: </strong>I recommend everyone attempt this challenge themselves before reading through this article to test their own skills and capabilities.</p><p><strong>Table of Contents</strong></p><p>Level 1: Buckets of Fun<br>Level 2: Misconfigured Bucket Permissions<br>Level 3: Leaked Secrets<br>Level 4: Unencrypted Snapshots<br>Level 5: Metadata Exposure<br>Level 6: IAM Misconfigurations</p><h3><strong>Level 1: Buckets of Fun</strong></h3><p><a href="http://flaws.cloud/hint1.html">Link</a></p><p>Since the site, <a href="http://flaws.cloud/">flaws.cloud</a>, is hosted on a S3 bucket. The challenge here is to find the first sub-domain.</p><ol><li>First, start with the domain enumeration;</li></ol><ul><li>Open the CLI terminal on your VM.</li><li>Type<em>“</em>nslookup flaws.cloud<em>” </em>or <em>“</em>host flaws.cloud<em>” </em>to display certain information about the domain such as the IP Address, etc.</li><li>Next, proceed to do a reverse lookup of the first IP Address displayed. Type<em>“</em>host FIRST_IP_ADDRESS<em>”.</em></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Xtmv2dwf1PZqII8Pk5bH5Q.png" /></figure><ul><li>The result shows that the S3 website is hosted in us-west-2.</li></ul><p>2. Next, navigate to the sub domain of the S3 website, “<a href="http://flaws.cloud.s3.amazonaws.com/">flaws.cloud.s3.amazonaws.com</a>”, on your web browser.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Osv1xY3ctG1dFen6n1cdEg.png" /></figure><p>3. Next, enumerate the bucket by typing &quot;aws s3 ls://flaws.cloud/ --region us-west-2”.</p><p><strong>N.B: </strong><em>You are most likely to run into the error in the image below indicating you not being authenticated and unable to access without any credentials. Don’t fret!</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bzDS8tvipgfHY3Koj9wvrg.png" /></figure><p>4. The solution is to specify a “<strong><em>no-sign-request</em></strong>”, which basically means that you are telling the CLI not to sign for a request or look for credentials which will give you anonymous access to the content of the S3 bucket;</p><ul><li>Type “aws s3 ls s3://flaws.cloud/ --region us-west-2 --no-sign-request”.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JbOB3yJG7f62LyesDho6TA.png" /></figure><p><strong>N.B: </strong><em>The same thing displayed on the S3 website will be displayed in the CLI.</em></p><p>5. Next, proceed to copy the secret file from the CLI and add it as a suffix to the S3 website on your web browser to complete the challenge by finding the secret file.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Mi5uf3bomwggCJqufBsAlQ.png" /></figure><p>6. <strong>Lessons Learned</strong>: Because the Bucket’s listing has its access permission set to “Everyone”, it was easy to access. So as best practice when setting up a bucket, is to make sure to grant the least privilege to only essential users.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/955/1*_rM5vjHggkeTDsBL7Y_VVQ.png" /></figure><h3><strong>Level 2: Unauthorised Authenticated Access</strong></h3><p><a href="http://level2-c8b217a33fcf1f839f6f1f73a00a9ae7.flaws.cloud/hint1.html">Link</a></p><p>An AWS account is going to be required for this next level. Don’t worry, all that is required is the free tier. You will need to create an IAM user account and use the Access Key ID AND Secret Access Key from the AWS IAM user account you created. The goal here is to do some authenticated access by an authenticated AWS user.</p><ol><li>First, type “aws configure --profile USER_ACCOUNT” to configure a profile using credentials from an existing user account. “USER_ACCOUNT” is the unique name of the IAM user account/profile going to be created. You can set the region to whatever region you want or just proceed without inputting any region. You can also set the default output format to “<strong>json</strong>” or leave it as is.</li><li>Once the credentials have been configured, an AWS profile will be created that can be used to access specific resources using the CLI.</li><li>Next, access the Level 2 bucket from the website through the CLI with the newly created credentials by typing “aws s3 --profile USER_ACCOUNT ls s3://level2-c8b217a33fcf1f839f6f1f73a00a9ae7.flaws.cloud”.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*K2jYJ0jfOTnIOyOqFz0Vyw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FjWlx5U6hp5yxzW4kjzYrg.png" /></figure><p>4. Next, copy the secret file from the CLI (<strong><em>secret-e4443fc.html</em></strong>) and add it as a suffix to the S3 website to complete the challenge by finding the secret file.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1018/1*engUihdmA5vr_2DdQQcjPg.png" /></figure><p>5. <strong>Lessons Learned</strong>: Similar to lessons learned in Level 1, the Bucket’s listing has its access permission set to “<strong>Any Authenticated AWS User</strong>”, it was easy to access. So the best practice once again would be to make sure to not violate the principles of least privilege.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/982/1*eKJ3rJ4hBZbaIIQ8g4INFQ.png" /></figure><h3><strong>Level 3: Leaked Secrets</strong></h3><p><a href="http://level3-9afd3927f195e10225021a578e6f78df.flaws.cloud/hint1.html">Link</a></p><p>The goal here is to find the AWS Access key and Secret Access Key.</p><ol><li>Start with a domain enumeration;<br>- Using the credentials configured in the previous levels, proceed to access and list the Level 3 S3 bucket from the website through the CLI with the credentials by typing, “aws s3 --profile USER_ACCOUNT ls s3://level3-9afd3927f195e10225021a578e6f78df.flaws.cloud/”.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/963/1*h6Z5qjXmKl-BAWXxImvkZw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BGHhWc28ttdMBWSpsZTe7w.png" /></figure><p>2. Next, there’s a git file in the data displayed, which is an indication of code activity in what was just enumerated. Proceed to use the “<strong><em>git log</em></strong>” command to investigate the repository. But before doing that, the content of the bucket needs to be dumped and then proceed to create a new folder on the desktop where the content of the S3 bucket would be synced/ downloaded to the local computer;</p><ul><li>First, type “ls” to list the folders on the local computer.</li><li>Navigate to the “Desktop” folder by typing “cd Desktop”.</li><li>Create a new directory where to download/sync the contents of the S3 bucket by typing “mkdir DIRECTORY_NAME”.</li><li>Type “cd Desktop” to navigate to the new directory.</li><li>Next, use the sync command to download the content of the S3 bucket. Type “aws s3 --profile USER_ACCOUNT sync s3://level3-9afd3927f195e10225021a578e6f78df.flaws.cloud/ .<br>ls -al”.</li><li>Next, type “git log” command to look at the history of the repository.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*d4FNlI2rGa7Up3NuH9yBvg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*v6iXVTFdiw0WjoVyoTiFfA.png" /></figure><p>3. Next, investigate both hash tokens of the commit displayed by typing “git checkout HASH_TOKEN”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vmK_O7VsVLskv8PCqlck3w.png" /></figure><p>4. The first hash token investigated did not provide any information needed but the second hash token had more information. Type “ls” to list the content of the second hash token. The second hash token contains the access keys.</p><p>5. Next, type “cat access_keys.txt” to investigate the contents of the access keys. The access key file contains the access key and secret access key to this vulnerable user.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*R4HSK64Lils9lLwQYa6dSw.png" /></figure><p>6. Next, use the credentials obtained to create your own profile;</p><ul><li>Type “aws configure --profile NEW_ACCOUNT”</li><li>Copy and paste the credentials obtained where prompted. Leave the default region name or default output format as is or input your preferential details.</li><li>Next, type “aws configure --profile NEW_ACCOUNT s3 ls” to list the contents of the S3 bucket the credentials had access to.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_E3L-DD3Lo6_tRru3S1E_Q.png" /></figure><p>7. <strong>Lessons Learned</strong>: Because the bucket listing had granted access to “Everyone”, the AWS access keys were accidentally leaked. A solution to this is to revoke them when discovered that the access keys have leaked. Also, roll the secrets early and often if they have been compromised because access keys are not meant to be used long-term to prevent vulnerabilities and eventually, exploitation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/867/1*RBqp7kCxER2ypZKyhcHrUQ.png" /></figure><h3>Level 4: Unencrypted Snapshots</h3><p><a href="http://level4-1156739cfb264ced6de514971a4bef68.flaws.cloud/">Link</a></p><p>The goal is to obtain credentials to log into this EC2 instance.</p><ol><li>First, start with a domain enumeration. Type “host 4d0cf09b9b2d761a7d87be99d17507bce8b86f3b.flaws.cloud” in the CLI.</li><li>Next, find the Account ID using the credentials from the previous challenge/level. Type “ aws --profile NEW_ACCOUNT sts get-caller-identity”.</li><li>Next, use the information obtained to see all the snapshots, as indicated in the challenge, associated with the user. Type “aws --profile NEW_ACCOUNT ec2 describe-snapshots --owner-id ID_NUMBER --region us_west_2”.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8QpXNCrb-lOroB-xGlvkgw.png" /></figure><p>4. Next, investigate further by taking out the Owner ID. Type “aws --profile NEW_ACCOUNT ec2 describe-snapshots --region us_west_2”. Wait for it to load. Access will then be granted to all the snapshots that were saved on the user’s credentials.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BaQklZDRBnYiQ0qqgT3Pjw.png" /></figure><p>5. Next, mount the snapshot from step 3 from this user credentials in your own AWS account. Type “aws --profile NEW_ACCOUNT ec2 create-volume --availability-zone us-west-2a --region us-west-2 --snapshot-id SNAPSHOT_ID_NUMBER”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*g1zSC0uqqdZ-RcWBdMJMdQ.png" /></figure><p><strong>N.B: </strong><em>The availability zone needs to be specified and the Snapshot ID from Step 3 is to be used.</em></p><p>6. Next, log into your AWS account console. Set the region to “<strong>us-west-2</strong>”. Navigate to EC2 &gt; Elastic Block Store&gt; Volumes. Then locate the Volume ID of the instance you just mounted. Rename it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*q7--oNeqFbPP_rdb2J2UoQ.png" /></figure><p>7. Next, create an instance from the Volume ID.</p><ul><li>Go to the EC2 Dashboard &gt; Select “<em>Launch an Instance</em>”.</li><li>Name your instance.</li><li>Select your AMI (I selected Ubuntu).</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1GRHrggWpMdKJlmBx67Etw.png" /></figure><ul><li>Leave the default instance type (t2.micro) as it is.</li><li>Create a new key pair, name it and, save it.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*r8WNivvekzRFyFgS11U8Fg.png" /></figure><ul><li>Move the saved key pair to the directory on your local computer through the CLI. Type “mv ~/Download/KEY_PAIR ~/Desktop/DIRECTORY_NAME”</li><li>Type “cd DESKTOP/DIRECTORY_NAME” to navigate to the directory containing the key pair. Type “ls” to list the contents of the directory.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nVE09o9Qil-5bgNyvNfLJg.png" /></figure><ul><li>Now go back to the AWS console and complete the instance you were creating. Leave the <strong>Network Settings</strong> as is.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*W0XddHRUePMdDv-EvcNc3w.png" /></figure><ul><li>Add a new volume in the <strong>EBS Volume</strong> section. Set the Snapshot field with the Snapshot ID (Might take a few minutes to find). Make sure it’s set to “<em>Not Encrypted</em>”.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*W0XddHRUePMdDv-EvcNc3w.png" /></figure><ul><li>Leave the remaining settings as default and select “<em>Launch Instance</em>” to create your instance.</li><li>After a successful launch, go back to the instance page and wait a few minutes for the instance to be provisioned.</li></ul><p>8. Now that it’s running, go back to the CLI and use the SSH key to change the permissions for the key to be used to ssh into the instance.</p><ul><li>Type “chmod 400 KEY_PAIR”. Now you can ssh into the instance.</li><li>First, copy the public address from the instance. Then go to the CLI and type “ssh -i KEY_PAIR AMI@PUBLIC_IPV4_ADDRESS”</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*s6sQqu7bE1Tm4sc2lX6dxg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eWUelBd0xkRiAvzcmd1-tQ.png" /></figure><ul><li>Next, we list information about all the available blocks. Type “lsblk”.</li><li>Next, we mount the “<strong>xvde1</strong>” disk. Type “sudo mount/dev/xvde1 /mnt”.</li><li>Now type “lsblk” again to see that the “<strong>xvde1</strong>” disk has been mounted.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QbG26oQASycS0hyXW4GRNg.png" /></figure><ul><li>Type “ls-al” then “cd /mnt” to navigate to the mount directory.</li><li>Then type “ls” to list the contents of the mount directory. Then type “cd home”, and “ls” to list the contents of the home directory. Then type “cd AMI_NAME”.</li><li>Type “ls” to list the contents of the AMI directory and type “cat setupNgnix.sh” to enumerate the contents of the directory.</li><li>The contents of the directory displayed will be the username and password for this level’s EC2 instance challenge.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IVeI1BtY_11NN5kav3xPSw.png" /></figure><p>9. Now, use these EC2 credentials to log into the EC2 instance from the link in the challenge.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/907/1*ppz3Mm26OYWSLEN92YQ16w.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/844/1*fv1BX8Y4c5jPxHbyAX7kRw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/984/1*Mi95kMPSeUbnz_5zIB9Duw.png" /></figure><p>10. <strong>Lessons Learned:</strong> Be conscious about protecting the snapshots because attackers can use unencrypted snapshots to log into your EC2 instance. Ensure the security of the EC2 instance by making sure the snapshots cannot be accessed publicly and also ensure the principles of least privilege.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/907/1*zw3esj1SWqlVFHxkec4MIA.png" /></figure><h3><strong>Level 5: Metadata Exposure</strong></h3><p><a href="http://level5-d2891f604d2061b6977c2481b0c8333e.flaws.cloud/243f422c/hint1.html">Link</a></p><p>The goal is to see how you can use the proxies from the challenge to list the contents of Level S3 buckets.</p><ol><li>First, type “curl <a href="http://4d0cf09b9b2d761a7d87be99d17507bce8b86f3b.flaws.cloud/proxy/169.254.169.254/">http://4d0cf09b9b2d761a7d87be99d17507bce8b86f3b.flaws.cloud/proxy/169.254.169.254/</a>”, to display the contents from the S3 bucket. The IP address used in the command is gotten from the Level 5: Hint 1 page.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/849/1*QFbp-mawEePl8BKw_vZZIg.png" /></figure><p>2. Next, dig deeper by filtering the search to the latest data. From latest &gt; meta-data&gt;iam&gt;security-credentials&gt;flaws. Type “curl <a href="http://4d0cf09b9b2d761a7d87be99d17507bce8b86f3b.flaws.cloud/proxy/169.254.169.254/latest/meta-data/iam/security-credentials/flaws">http://4d0cf09b9b2d761a7d87be99d17507bce8b86f3b.flaws.cloud/proxy/169.254.169.254/latest/meta-data/iam/security-credentials/flaws</a><strong>&quot;</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aRVQsj1b-DMnGkZUtpHOJw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YzCdYQzQK7NTRCNZM7Jn3A.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dThH9Bzue99pZJiO7TNk5g.png" /></figure><p>3. After digging deeper, some unencrypted credentials were discovered which would be used to create a new profile. Type “ aws configure --profile YOUR_NEW_PROFILE&quot;. Copy and paste the credentials and leave the defaults as is.</p><p>4. Next, use the token from the credentials to create a new profile but first there is a need to edit the AWS credentials in the home directory.</p><ul><li>Minimise the current terminal and open a new terminal &gt; Navigate to home directory. Type “cd”. Navigate to the <strong>AWS</strong> directory. Type “cd .aws” &gt; List content of the directory. Type “ls”. Enumerate the <strong>Credentials</strong> directory. Type “nano credentials”</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*fZqQwy18PY0yNGc90Au7lA.png" /></figure><p>5. Next, go to the previous terminal and copy the token. Go to the new terminal and paste the token to the latest profile we just created. Type “aws_session_token = TOKEN”. Select “<strong>ctrl + x</strong>” then “<strong>y</strong>” for “<strong>yes</strong>” to save and exit.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*42VAYrqlj13bGouV3S883w.png" /></figure><p>6. Now that the session token has been added to the profile, go back to the previous terminal to list the contents of the Level 6 S3 bucket with the newly created profile because it has the credentials that will grant access to the bucket.</p><ul><li>Type “ aws --profile YOUR_NEW_PROFILE s3 ls s3://level6-cc4c404a8a8b876167f5e70a7d8c9880.flaws.cloud”</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oZMQyTk4nmyIaQvJxKULEA.png" /></figure><p>7. Next, enumerate the first file listed to see if this the S3 bucket that contains the hidden link to Level 6</p><ul><li>Type “aws --profile YOUR_NEW_PROFILE s3 ls s3://level6-cc4c404a8a8b876167f5e70a7d8c9880.flaws.cloud/ddcc78ff/”</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oweNWSG5mcb-YjfjaFmn4Q.png" /></figure><p>8. It is! Now, proceed to copying the link from the terminal and inputting it in the web browser with the prefix “<em>http</em>”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/840/1*TpeNITmY7SZ5f2YB_Hwihg.png" /></figure><p>10. <strong>Lessons Learned:</strong> Due to the easy accessibility of the credentials, it was possible to exploit the credentials to gain access to the AWS environment. To avoid this, only provision access to with the least privilege that the user needs and also make sure to prevent your applications from having access to the exposed IP Address.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/995/1*ecRS3nykoUO7hE-DQEHLvQ.png" /></figure><h3>Level 6: IAM Misconfigurations</h3><p><a href="http://level6-cc4c404a8a8b876167f5e70a7d8c9880.flaws.cloud/ddcc78ff/hint1.html">Link</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/794/1*soLBUxIHJYndL3Q8vGFG9Q.png" /></figure><ol><li>First, use the credentials provided in this level to create a profile;</li></ol><ul><li>Type “aws configure --profile NEW_PROFILE”. Input credentials and leave defaults as is.</li></ul><p>2. Next, enumerate this iam user;</p><ul><li>Type “aws --profile NEW_PROFILE iam get-user”</li></ul><p>3. Next, investigate what policies are attached to this user;</p><ul><li>Type “aws --profile NEW_PROFILE iam list-attached-user-policies --user-name Level6”</li><li>From the information displayed, copy the ARNs {Amazon Resource Number} to discover the Version ID of the both policies displayed.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jriWz9gUzxVpkE61-uJOWA.png" /></figure><ul><li>Type “aws --profile NEW_PROFILE iam get-policy --policy-arn arn:aws:iam::975426262029:policy/MySecurityAudit” and “aws --profile NEW_PROFILE iam get-policy --policy-arn arn:aws:iam::975426262029:policy/list_apigateways” right after, to get both Version IDs.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zhZWEzYjZVL9GHQWffOW0Q.png" /></figure><p>4. Next, use the Version IDs to look at the permissions that the policies actually provide;</p><ul><li>Type “aws --profile NEW_PROFILE iam get-policy-version --policy-arn arn:aws:iam::975426262029:policy/MySecurityAudit --version-id v1”</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KGFk9lcW2aVTImC6JTGJ6g.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iDXrA4yJ6E-iR2Kg9gtB-A.png" /></figure><ul><li>Type “aws --profile NEW_PROFILE iam get-policy-version --policy-arn arn:aws:iam::975426262029:policy/list_apigateways --version-id v4”</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rh-_E8DPKYgOB_HcCZ3sSg.png" /></figure><ul><li>The difference between both policies is that the “<strong>MySecurityAudit</strong>” policy is extremely permissive while the “<strong>list_apigateways</strong>” policy is more specific.</li></ul><p>5. Next, use the permissions allowed by the “MySecurityAudit” policy to list the Lambda function in the policy;</p><ul><li>Type “ aws --region us-west-2 --profile NEW_PROFILE lambda list-functions”.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zpLgr-hI7RwFbcXvaEwqeA.png" /></figure><p>6. Next, proceed to get the policy for the “Level6” lambda function to extract the REST API ID;</p><ul><li>Type “aws --region us-west-2 --profile NEW_PROFILE lambda get-policy --function-name Level6”.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wP0ps7K81Oxg7FikIsiTvA.png" /></figure><p>7. Next, execute (invoke function) this specified resource;</p><ul><li>Type “aws --region us-west-2 --profile NEW_PROFILE apigateway get-stages --rest-api-id &quot;s33ppypa75&quot;”.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*B3VEeEglHSDhNXUkFkl44A.png" /></figure><p>8. Use information from the parameters obtained to call the lambda function. In this case, the parameter is the Stage Name, “<strong>Prod</strong>”;</p><ul><li>Type “curl https://s33ppypa75.execute-api.us-west-2.amazonaws.com/Prod/level6”.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5VDReeGuWOX7s4rZLuXPzQ.png" /></figure><ul><li>Click the website link to take you to the end of the challenge.</li></ul><p>9. <strong>Lessons Learned: </strong>As a result of the <strong>SecurityAudit</strong> policy being extremely permissive to the IAM policies, the AWS environment. An attacker with malicious intent can do the same. Which is why the principle of least privilege is extremely important. Practice only granting essential permissions for the jobs the users need to do.</p><h3>Closing Remarks</h3><p>I enjoyed navigating through this challenge and learning more about AWS services and how to access them, especially through the CLI. The challenge provides opportunities to learn about different AWS services (e.g. S3 Buckets, EC2 Instances, EBS Volume, etc.), and other services such as navigating through the Parallels Virtual Machine, Kali Linux, etc. Thank you for reading till the end and remember to always grant the least privilege when dealing in the cyber world😄!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=342e45efe76e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Vulnerability Management Lab with Nessus Tenable]]></title>
            <link>https://medium.com/@mxyiwa/nessus-essentials-vulnerability-management-lab-55a80d26185a?source=rss-10101a073228------2</link>
            <guid isPermaLink="false">https://medium.com/p/55a80d26185a</guid>
            <dc:creator><![CDATA[Muyiwa F.]]></dc:creator>
            <pubDate>Tue, 02 May 2023 15:04:32 GMT</pubDate>
            <atom:updated>2024-08-27T01:55:45.053Z</atom:updated>
            <content:encoded><![CDATA[<h4><strong>What is Vulnerability Management in Cybersecurity?</strong></h4><p>According to Microsoft, Vulnerability Management is a continuous, proactive, and often automated process that keeps your computer systems, networks, and enterprise applications safe from cyberattacks and data breaches. As such, it is an important part of an overall security program. By identifying, assessing, and addressing potential security weaknesses, organisations can help prevent attacks and minimise damage if one does occur.</p><p>The goal of this lab is to install and configure Nessus Tenable to run credentialed and uncredentialed scans of an old, deprecated software on a Windows Host platform in a controlled virtual home lab environment.</p><h4>Task Objectives</h4><ul><li>Download and install your preferred hypervisor (VMware Workstation Player)</li><li>Download Windows 11 ISO</li><li>Download and Install Nessus Tenable</li><li>Configure the virtual machine in the hypervisor</li><li>Install the Windows ISO in the VM</li><li>Create a Basic scan in Nessus</li><li>Inspect the first scan (non-credentialed)</li><li>Configure the VM for credentialed scans</li><li>Inspect and compare the first scan with credentialed results</li><li>Download and install a deprecated software</li><li>Remediate the vulnerabilities detected</li><li>Inspect scanned results after remediation of some vulnerabilities</li></ul><p><strong>To begin this lab, follow these steps:</strong></p><h4><strong><em>Step 1: Download and install your preferred hypervisor</em></strong></h4><p>We will download and install the VM Workstation Player.</p><p><strong>Download Here: </strong><a href="https://www.vmware.com/products/workstation-player/workstation-player-evaluation.html"><strong>https://www.vmware.com/products/workstation-player/workstation-player-evaluation.html</strong></a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LGu3M0ghTYvO5wggU5je4Q.png" /></figure><h4><strong><em>Step 2: Download Windows 11 ISO</em></strong></h4><p><strong>Download Here: </strong><a href="https://www.microsoft.com/en-gb/software-download/windows11"><strong>https://www.microsoft.com/en-gb/software-download/windows11</strong></a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SPlIaNTAZ_LQAA8suiYcPg.png" /></figure><h4><strong><em>Step 3: Download and Install Nessus Tenable</em></strong></h4><p>Nessus Essentials is a vulnerability scanner tool that we’re going to use for this lab.</p><p><strong>Download Here: </strong><a href="https://www.tenable.com/products/nessus/nessus-essentials"><strong>https://www.tenable.com/products/nessus/nessus-essentials</strong></a></p><ul><li>When you navigate to the website, you’ll be asked to fill in your details in order to obtain an activation key that will be sent to your email.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-p5ddvXL2FX3pjTcNe1t4Q.png" /></figure><ul><li>After you’ve registered, you’ll be prompted to download Nessus. Click “<strong>Download</strong>”</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HKoSfTv-lR88-bL2TsPKXA.png" /></figure><ul><li>Select the Nessus file that is compatible with your computer/virtual machine</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*R3CK-rqjHk0nFEZc9riDSw.png" /></figure><ul><li>Install it and configure your setup. You will be navigated to a webpage when you’re done installing</li><li>Click on “Connect via SSL”</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*84wsTCzuR8NoBaUQMMolEw.png" /></figure><p><strong><em>NOTE: Your web browser would indicate that the connection might not be secure. Ignore it and proceed to the website</em></strong></p><ul><li>Click on “Nessus Essentials” after it has finished initialising</li><li>Then click “<strong>Continue</strong>” and then click <strong>“Skip”</strong> when asked to fill in your details. You will then be prompted to input your activation code. You can find this in your email.</li><li>Then check the box; “Register Offline” and then click “Continue”</li><li>Then set up your username and password (try to make them memorable as forgetting them could be a hassle). It’s going to start initialising after you click “<strong>Continue</strong>” which is going to take a while.</li></ul><h4><strong><em>Step 4: Configure the virtual machine in the hypervisor</em></strong></h4><ul><li>Open VM workstation Player</li><li>Go to player &gt; File &gt; New Virtual Machine</li><li>Click on “<strong>Browse</strong>” to find the location when your Windows 11 ISO is downloaded and select it</li><li>Click “<strong>Next</strong>” and set the location you want to install it (default location is preferable), then click “Next” again</li><li>Leave the disk size as it is and set your memory to “<strong>4096 MB</strong>”. You can leave your memory as well if you don’t know how much RAM you have</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oFOoePU12EjGyBqgtpZg8g.png" /></figure><ul><li>You can leave your number of processor cores as well if you don’t know about your CPU</li><li>Change your Network Adapter to “<strong>Bridged</strong>” — this puts your virtual machine on the same network as your actual physical computer so your Nessus implementation can talk to your virtual machine more easily</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kExpfttrOAeMBCfj0XnQlA.png" /></figure><ul><li>Then click close and then check the “<strong>Power on after creation</strong>” box and click “<strong>Finish</strong>”</li></ul><h4><strong><em>Step 5: Install Windows 11</em></strong></h4><p>After the VM finishes getting created, It’s going to launch and we install Windows 11</p><ul><li>Set up your Windows 11 OS to your preference</li></ul><h4><strong><em>Step 6: Create a basic scan in Nessus</em></strong></h4><ul><li>To get the IP Address: Go to your VM &gt; Click Start &gt; Open Command Line &gt; Type “ipconfig”</li><li>Copy the IPv4 Address and open the command line on your local machine and ping the IP Address just to make sure you can reach it</li><li>Type “<strong>ping {Your IP Address} -t</strong>”. You may run into the error “<strong>Request timed out</strong>”. Don’t worry</li><li>Go to your VM to disable the firewall</li><li>Click Start &gt; Type “<strong>wf.msc</strong>” &gt; Click Open &gt; Click “<strong> Windows Defender Firewall Properties</strong>” &gt; Turn off the Domain Profile, Private Profile, and Public Profile&gt; Then Click “OK”</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AVOb4LTX3QByzywp2M2rDw.png" /></figure><ul><li>The ping on your local machine should go through now. Click Control C to cancel the ping</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*X1CCuNuKfLq8TLbKSRNKVA.png" /></figure><ul><li>Close the command line and open Nessus</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yhzFtSrMlruP22WZ9Xg_7Q.png" /></figure><ul><li>Click Create a New Scan</li><li>Select Basic Network Scan</li><li>Name it (e.g, Windows 11 Single Host)</li><li>Type your VM IP Address in the “<strong>Targets</strong>” box</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VaTJj1DsFSdok8uC1YMrew.png" /></figure><ul><li>Click Save</li></ul><h4><strong><em>Step 7: Inspect the first scan (non-credentialed)</em></strong></h4><ul><li>Click the “Play Button” on the right-hand side of the screen to launch the scan</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*s7RVtQq5ibF-widnt9y12Q.png" /></figure><ul><li>After it has launched, click the network scanned to inspect the results from the non-credentialed scan</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*P4MEKc5R8J3xXlG8LH_FHw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NUB4RNS99hXv0lh3NkNgSQ.png" /></figure><h4><strong><em>Step 8: Configure the VM for credentialed scans</em></strong></h4><ul><li>Go back to the VM</li><li>Click Start &gt; Type “<strong>Services.msc</strong>” &gt; Click “<strong>Remote Registry</strong>” &gt; Click “ <strong>Automatic</strong>” to enable Remote Registry &gt; Click “Start” &gt; Click “OK” &gt; Then Close</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*S11MB3NX71na2JoHEBKVTg.png" /></figure><ul><li>Click Start &gt; Type “ <strong>Share across devices”</strong> &gt; Turn on File and printer sharing &gt; Then Close</li><li>Next, click Start &gt; Type “<strong>User Account Control</strong>” &gt; Drag the button to the extreme bottom where it says “<strong>Never notify</strong>” to disable it &gt; Then Close</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HsGvmfzFtksT9q_Rgijbpg.png" /></figure><ul><li>Click Start &gt; Type “<strong>regedit</strong>” to go to the Registry Editor &gt; HKEY_LOCAL_MACHINE &gt; SOFTWARE &gt; Microsoft &gt; Windows &gt; CurrentVersion &gt; Policies &gt; System &gt; Create a DWORD called “<strong>LocalAccountTokenFilterPolicy</strong>”&gt; Click enter&gt; Double click the DWORD Created and set Value to 1 &gt; Then Close</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UWBTKmxxhDpQqfIOSbwksw.png" /></figure><ul><li>Restart the Virtual Machine and Sign in</li><li>Go back to Nessus</li><li>Check the box to select the network &gt; Go to More &gt; and then Configure &gt; Click “<strong>Credentials</strong>” to add a set of credentials &gt; Click “Windows” &gt; Authentication method is Password &gt; Username is what you used for your VM (Open command line on your VM and type “<strong>whoami</strong>” to get the username if you are unsure &gt; Type your Password &gt; Then Click Save &gt; Then go back to the main network dashboard</li></ul><p><strong><em>Step 9: Inspect and Compare the first scan with credentialed results</em></strong></p><ul><li>Click the “<strong>Play Button</strong>” on the right-hand side of the screen to run the scan one more time</li><li>Wait for a few minutes for the scan to complete and then compare the results with the first non-credentialed scan by clicking on the network and inspecting the history of the two scans</li><li>You can click the “<strong>Vulnerabilities</strong>” tab to see where the scan has indicated to be the most vulnerable parts of the VM</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8kALusJltTB32fhxjH0WHw.png" /></figure><ul><li>You can also click the “<strong>Remediations</strong>” tab to see high-level instructions on how to remediate these vulnerabilities</li></ul><h4><strong><em>Step 10: Installing a deprecated software {an outdated/vulnerable older version of Firefox}</em></strong></h4><p>Download Here: <a href="https://ftp.mozilla.org/pub/firefox/releases/3.6.12/win32/en-US/">https://ftp.mozilla.org/pub/firefox/releases/3.6.12/win32/en-US/</a></p><p><strong><em>NOTE: MAKE SURE YOU DOWNLOAD AND INSTALL ON YOUR VIRTUAL MACHINE FOR SECURITY REASONS</em></strong></p><h4><strong><em>Step 11: Remediating some vulnerabilities</em></strong></h4><ul><li>Go back to Nessus</li><li>Click the “<strong>Play Button</strong>” on the right-hand side of the screen to run another scan</li><li>Wait for the scan to complete and then click on the network. You’ll notice the vulnerabilities&#39; critical level will increase</li><li>Click “<strong>Remediations</strong>” to see what is recommended for you to be able to remediate these vulnerabilities</li><li>Some of the remediation instructions suggested are to update the Firefox software to the latest version or to just uninstall the software</li><li>To uninstall the software, go to the VM &gt; Click Start &gt; Type “<strong>appwiz.cpl</strong>” &gt; Click Firefox &gt; Click Uninstall</li><li>Then go to Start &gt; Type “<strong>Windows Updates</strong>” &gt; Click “<strong>Check for Updates</strong>” to manually check for updates. Then update all outdated software.</li><li>Then restart your VM after updates have been installed</li><li>Sign in &gt; Click Start &gt; Type “<strong>Windows Updates</strong>” &gt; Click “<strong>Check for Updates</strong>” again to make sure all updates are done</li></ul><h4><strong><em>Step 12: Inspecting scanned results after remediation of some vulnerabilities</em></strong></h4><ul><li>Go back to Nessus &gt; My Scans</li><li>Click the “<strong>Play Button</strong>” on the right-hand side of the screen to run another scan</li><li>Go to the “<strong>History</strong>” tab to inspect and compare scans after remediation</li><li>Check the “<strong>Vulnerabilities</strong>” tab for any more vulnerabilities and also the “Remediations” tab for instructions on how to remediate any more vulnerabilities that may pop up</li></ul><h4>Conclusion</h4><p>It is important to make sure that your organisation&#39;s security system is constantly being scanned for vulnerabilities and that patches are deployed periodically to help remediate these vulnerabilities.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=55a80d26185a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My name is Muyiwa Fadare. I am a front-end developer. My goals for HNG internship 8.0 are;]]></title>
            <link>https://medium.com/@mxyiwa/my-name-is-kingsley-fadare-i-am-a-frontend-developer-my-goals-for-hng-internship-8-0-are-33835b1bd102?source=rss-10101a073228------2</link>
            <guid isPermaLink="false">https://medium.com/p/33835b1bd102</guid>
            <dc:creator><![CDATA[Muyiwa F.]]></dc:creator>
            <pubDate>Mon, 16 Aug 2021 18:25:46 GMT</pubDate>
            <atom:updated>2023-04-20T15:03:22.234Z</atom:updated>
            <content:encoded><![CDATA[<p>My name is Muyiwa Fadare. I am a front-end developer. My goals for HNG internship 8.0 are;</p><ol><li>Improving my skills as a developer</li><li>Gaining knowledge and experience</li><li>Networking with experts who can help guide me</li><li>Getting acquainted with difficult tasks and finishing them successfully</li><li>Helping my fellow developers/teammates when they’re stuck</li><li>Hopefully, getting a full-time job after completing this internship</li><li>And most importantly, having fun while doing what I love.</li></ol><p>You can join this amazing internship program if you feel you have what it takes to be an amazing developer, regardless of your stack. You can use this link, https://internship.zuri.team, to join me and a large community of amazing developers to hone your skills and create something amazing.</p><p>The links I’m going to post below are tutorial links for different tools developers use when creating “magic!”.</p><p>If you want to learn how to navigate Figma, click this link https://youtu.be/3q3FV65ZrUs</p><p>To learn GIT, click this link https://youtu.be/PQsJR8ci3J0</p><p>Now, if you want to learn how to program using python, click this link https://youtu.be/WvhQhj4n6b8.</p><p>Happy learning!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=33835b1bd102" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>