<?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 Bhumika Sejwal on Medium]]></title>
        <description><![CDATA[Stories by Bhumika Sejwal on Medium]]></description>
        <link>https://medium.com/@bhumika04?source=rss-b3537fa54661------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*QSoQvxgwYCSivJfOu65RpA.jpeg</url>
            <title>Stories by Bhumika Sejwal on Medium</title>
            <link>https://medium.com/@bhumika04?source=rss-b3537fa54661------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 08:04:32 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@bhumika04/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[Getting Started with Wazuh : Setting Up My First Open-Source SIEM Lab]]></title>
            <link>https://medium.com/@bhumika04/getting-started-with-wazuh-setting-up-my-first-open-source-siem-lab-8249897f1085?source=rss-b3537fa54661------2</link>
            <guid isPermaLink="false">https://medium.com/p/8249897f1085</guid>
            <category><![CDATA[wazuh-manager]]></category>
            <category><![CDATA[wazuh]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[soc-analyst]]></category>
            <category><![CDATA[siem]]></category>
            <dc:creator><![CDATA[Bhumika Sejwal]]></dc:creator>
            <pubDate>Fri, 20 Nov 2026 19:25:15 GMT</pubDate>
            <atom:updated>2026-11-21T07:03:50.411Z</atom:updated>
            <content:encoded><![CDATA[<p><em>My hands-on journey of deploying Wazuh, monitoring endpoint activity, and investigating a brute-force attack.</em></p><h3>Introduction</h3><p>As I continue exploring the field of cybersecurity, I wanted to gain more practical experience with security monitoring and threat detection.</p><p>After working with Splunk and understanding how a SIEM (Security Information and Event Management) solution collects and analyzes logs, I decided to explore another popular security monitoring platform: <strong>Wazuh</strong>.</p><p>In this blog, I’ll share my experience setting up Wazuh, understanding its components, connecting an endpoint, and exploring how it helps monitor security events in a system.</p><h4><strong>What is Wazuh ?</strong></h4><p>Wazuh is a free, open-source security platform that unifies Extended Detection and Response (XDR) and Security Information and Event Management (SIEM) capabilities across cloud, virtual, containerized, and on-premises environments.</p><p>It helps security teams monitor endpoints, identify suspicious activities, and detect potential security threats.</p><p><strong>Key features of Wazuh:</strong></p><ul><li>Security log analysis</li><li>File Integrity Monitoring (FIM)</li><li>Vulnerability detection</li><li>Malware detection</li><li>Security Configuration Assessment (SCA)</li><li>Threat detection</li><li>Endpoint monitoring</li><li>Compliance monitoring</li></ul><p><strong>Wazuh Architecture</strong></p><p>The Wazuh architecture is composed of a multi-platform Wazuh agent and three central components: the Wazuh server, Wazuh indexer, and Wazuh dashboard.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*o6aenDDt8axetDcn.png" /></figure><ul><li><strong>Wazuh Agent:</strong> Lightweight software installed on endpoints (Linux, Windows, macOS, AIX, Solaris) to collect telemetry and perform threat prevention, detection, and response.</li><li><strong>Wazuh Server:</strong> Analyzes data received from agents using decoders, rules, and threat intelligence feeds; it also manages and configures agents remotely.</li><li><strong>Wazuh Indexer:</strong> A scalable full-text search and analytics engine that indexes and stores alerts and log data.</li><li><strong>Wazuh Dashboard:</strong> A web-based user interface for data visualization, threat hunting, regulatory compliance reporting, and module configuration.</li></ul><h3>1. <strong>Lab Environment and Requirements</strong></h3><p>The lab consists of four main components :</p><ol><li>Wazuh Manager/Server : Ubuntu 22.10</li><li>Wazuh Agent : Ubuntu 22.10</li><li>Attacker Machine : Kali Linux</li><li>Platform : VirtualBox</li></ol><h3>2. Installing and setting up Wazuh on Ubuntu</h3><p>To begin working with Wazuh, I first visited the official Wazuh website (<a href="https://documentation.wazuh.com/current/quickstart.html">https://documentation.wazuh.com/current/quickstart.html</a>) and followed the installation instructions provided in its documentation.</p><p>I opened the terminal and executed the necessary commands to complete the setup.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1TwcQhXRIUTAe3lSp0eJaQ.png" /></figure><p>After the successful execution of command I got the credentials for wazuh and then, I opened the browser then visited <a href="https://localhost/">https://localhost</a> (port 443) to open wazuh .</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XTxIv_sASmb0WsvE5_2d1w.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4it7wO1-CE15FeVzgwD9ZA.png" /><figcaption>Overview of Wazuh before deploying any agent</figcaption></figure><h3>3.Connecting a Wazuh Agent</h3><p>After successfully setting up the Wazuh environment, the next step was connecting a Wazuh agent to the Wazuh server. The Wazuh agent is installed on the endpoint that needs to be monitored. It collects system logs, security events, and other endpoint-related information and sends them to the Wazuh manager for analysis.</p><p>To establish the connection , I first created a new agent by going to agent summary and then clicking on deploy new agent.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*f77TnvQ_w7sRTuOHZ4ilHA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wYJlBpoLp-8nZ7z7WbrH0A.png" /></figure><p>After that I selected the DEB amd64 under Linux in Select the package to download and install on your system.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*02pBM5mxR8MTzElEpmt7fA.png" /></figure><p>Then, assigned the server address as 10.0.2.4 which was my Wazuh Manager ip address.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/907/1*LsJ8reB7iJ0rvDzSlOal7Q.png" /></figure><p>Also, assigned the agent name as Agent0.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/972/1*Rc-Da5EI-CfEFw9k-jXo2Q.png" /></figure><p>Next ,I ran the command under Run the following commands to download and install the agent in the Wazuh Agent.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rEsssIOSENtCxz3MsWzhfw.png" /></figure><p>After successfully executing the previous command, I ran the commands under Start the agent to start the agent.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/470/1*v9zb8FLChKYsVoFSOOmI5A.png" /></figure><p>Then, to verify the agent connection ,I clicked on Back to agent list.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/525/1*BisCCR8IftP_c_CqyjZUgw.png" /></figure><p>Once connected, the endpoint became visible in the Wazuh Dashboard, allowing me to monitor its activities and investigate security-related events from a centralized interface.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eQmPEmDAkoGbIdE3yZig_g.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0R5rJDjoSJ-4Y8eHYPFgOw.png" /><figcaption>Wazuh agent successfully deployed</figcaption></figure><p>4. <strong>Exploring the Wazuh Dashboard</strong></p><h3>4. Exploring the Wazuh Dashboard</h3><p>After successfully connecting the Wazuh agent, I explored the Wazuh Dashboard to analyze the logs and security events collected from the monitored endpoint. The dashboard provided a centralized view of the agent’s activities, allowing me to examine system events and understand how endpoint data is monitored.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vanqdfmtu5CEFP7c0jN-pA.png" /></figure><p>Along with log analysis, I also explored two important Wazuh features: <strong>Vulnerability Detection</strong> and <strong>Security Configuration Assessment (SCA)</strong>.</p><ul><li><strong>Vulnerability Detection:</strong> This feature helps identify known vulnerabilities in installed software packages by checking them against vulnerability databases. It helps security analysts understand potential weaknesses in monitored systems.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XD6_MWBSoKzhuD3A7vXQCw.png" /><figcaption>Vulnerability Detection for Wazuh Agent</figcaption></figure><ul><li><strong>Security Configuration Assessment (SCA):</strong> This feature evaluates the endpoint’s security configuration against predefined policies and checks. It helps identify security misconfigurations and areas where system security can be improved.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jMEeoTQ4mrxJ2XHSNyDZHA.png" /><figcaption>Security Configuration Assessment for Wazuh Agent</figcaption></figure><p>Exploring these features gave me a better understanding of how Wazuh goes beyond basic log monitoring. It provides useful capabilities for identifying vulnerabilities, assessing system configurations, and supporting continuous security monitoring in a Security Operations Center (SOC).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-JNLnRKZoKVDC5Jvb8gILA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3l1d3w6olYv5CkRRJQwbAg.png" /></figure><h3>5. Simulating and Analyzing a Brute-Force Attack Using Kali Linux</h3><p>After exploring the different security monitoring features of Wazuh, I decided to perform a practical security testing activity to understand how suspicious login attempts can be detected and analyzed.</p><p>For this, I used <strong>Kali Linux</strong> as the attacking machine and the system running the Wazuh agent as the target machine. I simulated a brute-force attack by generating multiple failed login attempts against the target endpoint.</p><p>Firstly ,I installed openssh server in the target machine using following commands:</p><pre>sudo apt update &amp;&amp; sudo apt upgrade -y<br>sudo apt install openssh-server -y</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/863/1*imJVy9z3Rc0qWsDE2-pi8w.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/703/1*dF8JbOouH5xVYAc3rCpI9w.png" /></figure><p>After installing the ssh server I enabled and started it and checked its status using the following commands :</p><pre>sudo systemctl enable ssh<br>sudo systemctl start ssh<br>sudo systemctl status ssh</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/592/1*JcErUN5ahAMtyJEMM5TOAQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/588/1*iZgubqnRnzL8juvbFqnDWQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1008/1*OQKKBAjJb2Ks0DzRRQEW1Q.png" /></figure><p>After that I used ifconfig to check the ip address of the target machine.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/915/1*C50vZJEbT1Q66sLCMc62gg.png" /></figure><p>Then , by using attacker’s machine I started doing my bruteforce attack.I performed it twice .First one with passwords.txt file which had the password of the target machine and the second one with the password.txt which did not have the password of the target machine.</p><p>I used <strong>Hydra (THC Hydra)</strong> as the brute-force testing tool. Hydra is a password-cracking tool commonly used in authorized security testing to test authentication services against multiple username and password combinations.</p><p>I ran the following command :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Kw6xabkrZ0GJAIgy4kiJEw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FQz5Fv0iAmLYOMQnPrXMWA.png" /></figure><pre>hydra -l &lt;USER&gt; -P &lt;PASS_FILE&gt; &lt;TARGET&gt; ssh</pre><p>The objective of this exercise was to observe how Wazuh collects authentication-related logs and identifies repeated failed login attempts. After performing the attack simulation, I accessed the Wazuh Dashboard and examined the generated security events and alerts.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CIHXNwlBTi5J6pYYXQiYWw.png" /><figcaption>First Bruteforce attack</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*M2xWBdQTnNKxga5F7a9BsQ.png" /><figcaption>Second Bruteforce attack</figcaption></figure><p>By analyzing the logs, I was able to understand how repeated authentication failures can indicate a potential brute-force attack and how Wazuh helps security analysts investigate such activities.</p><p>I also used different filters such as rule.description: syslog: User missed the password more than one time and rule.description: sshd: authentication failed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eWlyS0Kb5ZSh-w3aXWct_A.png" /><figcaption>Filter → rule.description: syslog: User missed the password more than one time</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2_c10uSIGkH-PBjx0dYhrw.png" /><figcaption>Filter → rule.description: sshd: authentication failed</figcaption></figure><h3>Conclusion</h3><p>Setting up and exploring Wazuh was a valuable hands-on learning experience that helped me understand how security monitoring and threat detection work in a practical environment.</p><p>Throughout this lab, I learned how to set up Wazuh, connect an endpoint using the Wazuh agent, and analyze the logs collected from the monitored system. I also explored important features such as Vulnerability Detection and Security Configuration Assessment (SCA) to understand how Wazuh identifies potential vulnerabilities and security misconfigurations.</p><p>One of the most interesting parts of this experience was simulating a brute-force attack using Hydra from Kali Linux and analyzing the resulting authentication logs and security alerts in the Wazuh Dashboard. This helped me understand how suspicious login activities can be monitored and investigated.</p><p>Overall, this lab strengthened my understanding of SIEM tools, endpoint monitoring, attack simulation, and log analysis. As someone learning cybersecurity, this practical experience was another important step in my journey towards understanding real-world Security Operations Center (SOC) activities.</p><p>I’m looking forward to exploring more cybersecurity tools, performing additional lab exercises, and continuously improving my practical security skills.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8249897f1085" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Building My First Home SOC Lab with Splunk: A Beginner’s Hands-on Guide]]></title>
            <link>https://medium.com/@bhumika04/building-my-first-home-soc-lab-with-splunk-a-beginners-hands-on-guide-06ee1d09fa3f?source=rss-b3537fa54661------2</link>
            <guid isPermaLink="false">https://medium.com/p/06ee1d09fa3f</guid>
            <category><![CDATA[splunk-enterprise]]></category>
            <category><![CDATA[splunk]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[soc-analyst]]></category>
            <dc:creator><![CDATA[Bhumika Sejwal]]></dc:creator>
            <pubDate>Mon, 09 Nov 2026 10:44:47 GMT</pubDate>
            <atom:updated>2026-11-09T18:20:27.195Z</atom:updated>
            <content:encoded><![CDATA[<p><em>My journey of setting up a Security Information and Event Management (SIEM) environment using Splunk Enterprise, Ubuntu, and Windows 11.</em></p><h3>Introduction</h3><p>As someone exploring the field of cybersecurity, I wanted to move beyond theoretical knowledge and understand how security monitoring actually works in a real-world environment.</p><p>One of the most important components of a Security Operations Center (SOC) is a SIEM (Security Information and Event Management) tool. SIEM solutions help security analysts collect, monitor, analyse, and investigate logs from different systems to identify potentially suspicious activities.</p><p>To gain practical experience, I decided to build my own <strong>Home SOC Lab using Splunk Enterprise</strong>.</p><p>In this project, I configured Splunk Enterprise on an Ubuntu machine and connected a Windows 11 endpoint using Splunk Universal Forwarder. The objective was to establish centralized log collection and create a basic environment for practicing security monitoring and log analysis.</p><p>Let’s walk through how I built it.</p><h3>What is Splunk?</h3><p>Before getting into the practical implementation, let’s understand what Splunk is and why it is important in cybersecurity.</p><p><strong>Splunk</strong> is a powerful data analytics and monitoring platform that is widely used in cybersecurity, especially in Security Operations Centers (SOCs). It collects and analyses machine-generated data, such as system logs, application logs, network events, and security-related information.</p><p>In cybersecurity, Splunk is commonly used as a SIEM solution. It helps security analysts monitor activities across different systems, identify unusual patterns, investigate suspicious events, and gain visibility into potential security threats.</p><p>One of the most useful features of Splunk is its <strong>Search Processing Language (SPL)</strong>, which allows analysts to search, filter, and analyse large amounts of log data.</p><p>For example, if multiple failed login attempts occur on a system, an analyst can use Splunk to search the authentication logs and investigate whether the activity could indicate a potential brute-force attack.</p><h3>Why did I choose Splunk for my Home SOC Lab?</h3><p>I chose Splunk because it provides an opportunity to understand how security monitoring works in practice. It allows beginners to explore real system logs, perform searches, and understand how a SOC analyst works with security events.</p><p>Through this project, I wanted to learn how data from different endpoints can be collected in one centralized platform and used for security monitoring and investigation.</p><h3>1. Understanding the Lab Architecture</h3><p>Before starting the installation, I first understood the basic architecture of my home lab.</p><p>The lab consists of three main components:</p><ul><li><strong>Splunk Enterprise (Ubuntu):</strong> Acts as the central SIEM server.</li><li><strong>Windows 11 Machine:</strong> Acts as the endpoint and generates system logs.</li><li><strong>Network:</strong> Connects both machines through the same LAN or NAT network.</li></ul><p>The Windows machine sends its logs to the Splunk server through the Universal Forwarder.</p><p><strong><em>Note</em></strong>: <em>Hostnames and system computer names have been redacted in the screenshots below to follow standard security privacy best practices.</em></p><h3>Ports used in the lab</h3><p>Port — Purpose</p><p>8000 — Splunk Web Interface</p><p>8089 — Management communication</p><p>9997 — Receiving forwarded logs</p><p>Understanding these ports was important because they allow the different components of the lab to communicate.</p><h3>2. Installing Splunk Enterprise on Ubuntu</h3><p>The first major step was installing Splunk Enterprise on Ubuntu.</p><p>I started by updating the system packages and installing the required utilities.</p><pre>sudo apt update &amp;&amp; sudo apt upgrade -y<br>sudo apt install curl wget -y</pre><p>Next, I created a free Splunk account and downloaded the Splunk Enterprise Linux package in .deb format from <a href="https://www.splunk.com/en_us/download/splunk-enterprise.html">https://www.splunk.com/en_us/download/splunk-enterprise.html</a> .</p><p>After downloading the package, I installed it using:</p><pre>sudo dpkg -i file_name.deb</pre><p>Once the installation was completed, I started Splunk and accepted its license agreement.</p><pre>sudo /opt/splunk/bin/splunk start --accept-license</pre><p>During the initial startup, I created an administrator username and password.</p><p>I also configured Splunk to start automatically when the system boots:</p><pre>sudo /opt/splunk/bin/splunk enable boot-start</pre><p>This makes the lab easier to manage without manually starting Splunk every time.</p><h3>3. Accessing the Splunk Web Interface</h3><p>After starting the Splunk service, I accessed its web interface through my browser.</p><p>For local access, I used:</p><pre>http://127.0.0.1:8000</pre><p>For remote access from another machine, the format is:</p><pre>http://&lt;ubuntu_ip&gt;:8000</pre><p>I logged in using the administrator credentials created during installation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/713/1*mIyukZ4HoUNtVm1tpeGkrg.png" /></figure><p>This interface is where I could manage the Splunk environment, configure data inputs, and search collected events.</p><h3>4. Configuring Splunk to Receive Logs</h3><p>Installing Splunk alone was not enough. I also needed to configure it to receive logs from my Windows machine.</p><p>I opened:</p><p><strong>Settings → Forwarding and Receiving → Receive Data → Add New</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/655/1*vba0TITy8CbQv02uy1TIPQ.png" /><figcaption>Settings -&gt; Forwarding and receiving</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*O3hRGsXIktM3peuKik2Oew.png" /><figcaption>Under Receive data ,select Add new .</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Mz_kv799uanamgEcBjko6A.png" /><figcaption>Select New Receiving Port .</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UNJ7qTkJXXGl5p1nMYavww.png" /><figcaption>Configure the receiving port as 9997.</figcaption></figure><p>I configured the receiving port as:</p><pre>9997</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5JhrtKjHPxyg0Jxb3MxzAA.png" /></figure><p>After saving the configuration, I created a dedicated index for Windows logs.</p><p>I navigated to:</p><p><strong>Settings → Indexes → New Index</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/630/1*M8CQCXPPyPpFsyx7l7zAFQ.png" /><figcaption>Settings -&gt; Indexes</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/596/1*XRb7l7WaEwM6Jt5UWNEkjw.png" /><figcaption>Add new index .</figcaption></figure><p>And created an index named:</p><pre>windows11</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dPa97YWjkwdgNGnXenjkBg.png" /></figure><p>An index in Splunk is where collected and processed event data is stored. Creating a separate index helped organize the Windows logs.</p><h3>5. Installing Splunk Universal Forwarder on Windows 11</h3><p>Now that the Splunk server was ready to receive data, I moved to the Windows 11 machine.</p><p>I downloaded <strong>Splunk Universal Forwarder </strong>from<strong> </strong><a href="https://www.splunk.com/en_us/download/universal-forwarder.html">https://www.splunk.com/en_us/download/universal-forwarder.html</a> , which is a lightweight component designed to collect data from a machine and forward it to a Splunk Enterprise server.</p><p>During installation, I:</p><ol><li>Ran the Windows .msi installer.</li><li>Accepted the license agreement.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/620/1*7ZHogY7ww4oRC0tW8ln6cw.png" /></figure><p>3. Configured the required credentials.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/618/1*lO4o1TFV1ruy-rHH7SkDtw.png" /></figure><p>4 .Entered the Ubuntu server’s IP address.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/611/1*66SMw1--lYBBZ_Wk_O6lEA.png" /></figure><p>5. Configured the management port as 8089.</p><p>6. Configured the receiving port as 9997.</p><p>This steps connected my Windows endpoint to the central Splunk server.</p><h3>6. Verifying the Forwarder Connection</h3><p>After completing the configuration, I needed to verify whether the Windows machine was successfully communicating with Splunk.</p><p>On the Splunk server, I navigated to:</p><p><strong>Settings → Forwarder Management</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dKwBcLf0YuLmq12LKpxZCQ.png" /></figure><p>I checked whether the Windows machine appeared in the list of connected forwarders.</p><p>A successful connection should show the forwarder’s hostname and connected status.</p><p>This confirmed that the forwarding setup was working.</p><p>Now, add data source in the Splunk.</p><p>So, I navigated to forward, then added the server class and created the Server Class name as windows11-latest and then clicked next.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7dZeoOduFP1kTYcHWQffmg.png" /></figure><p>Then selected local event logs and added all the event logs and clicked next.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0sn7LD7CygoQCaRG8GIqyA.png" /></figure><p>After that I added window11 as index and clicked Review.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JitCHJ4d7cZDpIZHU_0czA.png" /></figure><p>After reviewing the configuration ,I clicked on Submit and selected Start Learning.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9hJ5ayGJbf_0HrytmUTwlA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZblolowaS7Mt_wcw_e_TNg.png" /></figure><h3>7. Verifying Log Ingestion Using SPL</h3><p>This was one of the most important steps in the entire setup.</p><p>I opened:</p><p><strong>Apps → Search &amp; Reporting</strong></p><p>To check whether Splunk was receiving data, I executed the following search query:</p><pre>index=*</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NzluidUbEIjRvnmw0Ne2aw.png" /></figure><p>To specifically search for Windows logs, I used:</p><pre>index=windows11</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*V49UbqdA6ZEB4_WkFPNfNg.png" /></figure><p>SPL stands for <strong>Search Processing Language</strong>. It is Splunk’s search language, which allows analysts to retrieve, filter, and analyse machine-generated data.</p><p>When events appeared in the search results, it confirmed that my Windows logs were successfully reaching Splunk.</p><p>This meant my basic Home SOC Lab was operational!</p><h3>8. What I Achieved Through This Project</h3><p>Setting up this lab helped me understand several important cybersecurity concepts through practical implementation.</p><p>By completing this deployment, I established:</p><ul><li>Centralized log collection.</li><li>Windows endpoint telemetry ingestion.</li><li>Communication between a SIEM server and an endpoint.</li><li>Basic understanding of Splunk indexing.</li><li>Practical exposure to SPL searches.</li><li>A foundation for incident detection and log analysis.</li></ul><p>More importantly, I understood how endpoint logs can be collected and made available in one centralized monitoring platform.</p><h3>Conclusion</h3><p>Building this Home SOC Lab was a valuable hands-on learning experience.</p><p>It helped me understand how Splunk works, how Windows logs are forwarded to a centralized SIEM platform, and how security analysts can use collected data for monitoring and investigation.</p><p>I believe that practical experimentation is one of the best ways to learn cybersecurity. Instead of just reading about SIEM tools, setting up my own environment gave me a better understanding of how the different components work together.</p><p><strong>This is my first step towards building practical SOC Analyst skills, and there is a lot more to explore!</strong></p><p><em>If you’re also a beginner exploring cybersecurity, I hope this guide helps you take your first step towards building your own Home SOC Lab.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=06ee1d09fa3f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Understanding the WannaCry Ransomware Attack: A Hands-On Simulation Using Kali Linux and Metasploit]]></title>
            <link>https://medium.com/@bhumika04/understanding-the-wannacry-ransomware-attack-a-hands-on-simulation-using-kali-linux-and-metasploit-9c6a626b55e5?source=rss-b3537fa54661------2</link>
            <guid isPermaLink="false">https://medium.com/p/9c6a626b55e5</guid>
            <category><![CDATA[ethical-hacking]]></category>
            <category><![CDATA[ransomware]]></category>
            <category><![CDATA[kali-linux]]></category>
            <category><![CDATA[penetration-testing]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[Bhumika Sejwal]]></dc:creator>
            <pubDate>Thu, 05 Nov 2026 13:09:41 GMT</pubDate>
            <atom:updated>2026-11-05T13:09:41.716Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Exploring how ransomware exploits system vulnerabilities, gains access, and encrypts files through a controlled virtual lab environment.</strong></p><h3>Introduction</h3><p>Ransomware is one of the most dangerous forms of cyberattacks in today’s digital world. It is a type of malicious software that encrypts a victim’s files and demands a ransom payment in exchange for restoring access to the data.</p><p>One of the most infamous examples is <strong>WannaCry</strong>, a ransomware attack that spread across the world in May 2017, affecting thousands of organizations, businesses, and healthcare institutions.</p><p>In this blog, I’ll walk through a hands-on simulation of the WannaCry ransomware attack in a controlled virtual environment. The objective was to understand how attackers identify vulnerable systems, exploit security weaknesses, gain access, and ultimately execute ransomware.</p><h3>1. Understanding the WannaCry Attack</h3><p>WannaCry was a ransomware attack that exploited a vulnerability in Microsoft’s Windows operating system.</p><p>It leveraged an exploit known as <strong>EternalBlue</strong>, which targeted the Server Message Block (SMB) protocol.</p><p>The vulnerability was associated with <strong>MS17–010</strong> and allowed attackers to execute malicious code on vulnerable Windows systems.</p><p>What made WannaCry particularly dangerous was its ability to spread across networks by exploiting vulnerable machines.</p><p>Instead of affecting just one computer, it could move from one system to another, causing widespread disruption.</p><h3>2. Setting Up the Virtual Lab Environment</h3><p>To understand how this attack works, I created a virtual lab using two machines.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6cMgJusaXosYWeB_Z4R2Xw.png" /><figcaption>Attacker(Kali Linux) and Victim Machine (Windows 7)</figcaption></figure><p><strong>Attacker Machine:</strong></p><ul><li>Operating System: Kali Linux</li><li>Tools: Nmap and Metasploit Framework</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/965/1*JU4l4b8J4BpM6o4-NtlBXw.png" /><figcaption>Attacker Machine on the same virtual network as Victim Machine</figcaption></figure><p><strong>Victim Machine:</strong></p><ul><li>Operating System: Windows 7</li><li>Purpose: To simulate a vulnerable target system containing sample files.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/970/1*jFmdzMID3_baKHfUbg2H9g.png" /><figcaption>Victim Machine on the same virtual network as the Attacker Machine</figcaption></figure><p>Both machines were configured within a virtual network for the simulation.</p><p>The objective was to create an environment where the attack could be studied without targeting real-world systems.</p><h4>Creating a Virtual Machine Snapshot</h4><p>Before proceeding with the attack simulation, I created a snapshot of the Windows 7 virtual machine using VirtualBox.</p><p>A snapshot captures the current state of a virtual machine, allowing it to be restored to that earlier state if something goes wrong during an experiment.</p><p>Since this simulation involved ransomware, creating a snapshot was particularly important. It provided a recovery point to return to the original state of the victim machine after the experiment.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KIM2NfD4XCeMmj2y0FGfPA.png" /><figcaption>Creating a snapshot of the Windows 7 virtual machine in VirtualBox.</figcaption></figure><h3>3. Understanding the Attack Workflow</h3><p>The simulation was divided into three major stages:</p><ol><li>Network scanning and identification of the vulnerable machine.</li><li>Exploitation of the vulnerability to gain access.</li><li>Uploading and executing the ransomware sample.</li></ol><p>Let’s understand each stage.</p><h3>4. Phase One: Network Scanning Using Nmap</h3><h4>Step 1: Identifying the Attacker’s IP Address</h4><p>First, I used the ifconfig command in Kali Linux to identify the active network interface and its assigned IP address.</p><p>The output showed that the Kali Linux machine was using the IP address 10.0.2.4.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/897/1*lWkZ3PLZ5TDCYdQ5HFecaQ.png" /><figcaption>Identifying the Kali Linux network configuration using ifconfig.</figcaption></figure><h4>Step 2: Operating System Detection Using Nmap</h4><p>Next, I used the Nmap operating system detection option:</p><pre>nmap -O 10.0.2.0/24</pre><p>The -O option enables OS detection. It helps identify the operating system running on the target machine by analyzing its network responses.</p><p>This step helped determine whether the target was running Windows or another operating system.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RVvdTl9bxOkLXhjXfdeuxg.png" /><figcaption>Nmap operating system detection results.</figcaption></figure><h4>Step 3: Vulnerability Scanning and Service Detection</h4><p>After identifying the target, I performed another scan using Nmap’s vulnerability detection scripts and service version detection.</p><p>The command is:</p><pre>nmap --script vuln -sV 10.0.2.3</pre><p>Here’s what the options mean:</p><ul><li>--script vuln: Runs Nmap scripts designed to check for known vulnerabilities.</li><li>-sV: Detects the services running on open ports and attempts to identify their versions.</li><li>10.0.2.3: IP address of the target Windows machine.</li></ul><p>This scan helped gather more information about the services running on the target and identify potential security weaknesses.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pX5T21RlzGs2rqCPL7Shhg.png" /><figcaption>Nmap vulnerability and service detection results.</figcaption></figure><p>During the scanning process, I observed that port 445 (SMB) was open on the target Windows machine. This finding was relevant because the WannaCry attack exploited vulnerabilities associated with the SMB protocol. The scanning phase provided the information needed for the next stage of the simulation</p><h3>5. Phase Two: Exploiting the MS17–010 Vulnerability Using Metasploit</h3><p>After identifying the target Windows 7 machine during the scanning phase, the next step was to explore the MS17–010 vulnerability using the Metasploit Framework.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1JSOy3l9H-Zx6quTR9fNUw.png" /></figure><p>Metasploit is a penetration testing framework that provides tools and modules for testing known security vulnerabilities in controlled environments.</p><h4>Step 1: Searching for the MS17–010 Exploit</h4><p>I first opened the Metasploit Framework and searched for the available exploit modules related to MS17–010.</p><pre>search ms17-010</pre><p>This command displayed the available exploit modules associated with the MS17–010 vulnerability.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JShVae8PNS4mx63xMvwWCQ.png" /><figcaption>Searching for MS17–010 exploit modules in Metasploit.</figcaption></figure><h4>Step 2: Selecting the Exploit Module</h4><p>After identifying the relevant module, I selected it using:</p><pre>use 0</pre><p>This loaded the selected exploit module into the Metasploit console.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uvEwcqGD1E5K0uGjCXONdA.png" /><figcaption>Loading the selected MS17–010 exploit module.</figcaption></figure><h4>Step 3: Configuring the Target Machine</h4><p>Next, I configured the remote host (RHOST), which represents the IP address of the target machine.</p><pre>set RHOSTS 10.0.2.3</pre><p>This specified the Windows 7 virtual machine as the target for the lab exercise.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rE0Ru6tHLP0HzfRQQg1Urw.png" /><figcaption>Configuring the target IP address.</figcaption></figure><h4>Step 4: Running the Exploit</h4><p>After configuring the target, I used the run command to execute the selected module.</p><pre>run</pre><p>The exploitation attempt established a remote session with the target machine in the controlled lab environment.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aAL5TWBHH3wMebgK2iBZFA.png" /><figcaption>Metasploit execution result.</figcaption></figure><h4>Step 5: Checking the Working Directory</h4><p>After establishing the session, I used:</p><pre>pwd</pre><p>The pwd command displays the present working directory of the remote session. This helped me understand the location from which the session was operating.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/965/1*zsMMkCt5uGM75MCDO5629g.png" /><figcaption>Checking the current working directory.</figcaption></figure><h3>6. Understanding Remote Access</h3><p>Once access was established, the next step was understanding the level of control available over the target machine.</p><p>The simulation demonstrated how remote access can allow an attacker to interact with a compromised system and transfer files.</p><p>This stage helped me understand an important cybersecurity concept: <strong>unauthorized access to one machine can potentially expose its resources and data.</strong></p><p>It also demonstrated why organizations need to monitor suspicious remote connections and restrict unnecessary network access.</p><h3>7. Phase Three: WannaCry Ransomware Execution</h3><p>The final stage involved simulating the ransomware execution.</p><h3>Step 1: Uploading the File</h3><p>I used the Metasploit file transfer functionality to upload the WannaCry executable from the Kali Linux machine to the Windows 7 virtual machine.</p><p>This demonstrated how files can be transferred between an attacker machine and a compromised system through an established remote session.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1022/1*mjY3mTjfzxBHI7xbLGwi9Q.png" /><figcaption>Uploading the WannaCry executable to the victim machine.</figcaption></figure><h3>Step 2: Verifying the Uploaded File</h3><p>After transferring the file, I used the ls command to check the contents of the destination directory.</p><p>This helped verify whether the executable was successfully transferred to the target machine.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uX3aGfOCCtfvLEibtg65tA.png" /><figcaption>Verifying the uploaded file in the target directory.</figcaption></figure><h3>Step 3: Ransomware Execution</h3><p>The final stage involved executing the WannaCry sample in the controlled virtual lab.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*XGEHMDVpd7zIBt7ezcKWxQ.png" /><figcaption>Executing the WannaCry.exe .</figcaption></figure><p>After execution, the ransomware began encrypting the sample files stored on the victim machine.</p><p>The files that were previously accessible became unavailable, and a ransom notification appeared on the screen.</p><p>This demonstrated the basic impact of a ransomware infection:</p><ul><li>Files become encrypted.</li><li>Users lose access to important information.</li><li>A ransom demand is displayed.</li><li>Normal system operations can be disrupted.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/822/1*dZdkFWcdRVFS7IEnnzhUVg.png" /><figcaption><em>WannaCry ransomware notification.</em></figcaption></figure><h3>8. Before and After the Attack</h3><p>One of the most interesting parts of this simulation was observing the difference between the system before and after ransomware execution.</p><p><strong>Before the attack:</strong></p><ul><li>Sample files were accessible.</li><li>Documents could be opened normally.</li><li>The system was functioning as expected.</li></ul><p><strong>After the attack:</strong></p><ul><li>Files were encrypted.</li><li>Normal access to the sample data was disrupted.</li><li>A ransom notification appeared.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zNvntdtbQ911EtHKUaN2nw.png" /><figcaption><em>Victim machine before the attack.</em></figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ktqctL0hK-SLv4ntLsYWpw.png" /><figcaption><em>Victim machine after the attack.</em></figcaption></figure><p>This comparison helped demonstrate the real impact ransomware can have on individuals and organizations.</p><h3>9. What Did I Learn From This Simulation?</h3><p>This hands-on exercise helped me understand several important cybersecurity concepts:</p><p><strong>1. Network Scanning</strong></p><p>I learned how Nmap can identify active devices, open ports, and services running on a network.</p><p><strong>2. Vulnerability Exploitation</strong></p><p>I understood how an unpatched Windows system can become vulnerable to attacks targeting known security weaknesses.</p><p><strong>3. Metasploit Framework</strong></p><p>I gained practical exposure to Metasploit and its role in authorized penetration testing.</p><p><strong>4. Remote Access</strong></p><p>I understood how successful exploitation can potentially provide access to a target machine’s resources.</p><p><strong>5. Ransomware Behaviour</strong></p><p>I observed how ransomware can encrypt files and disrupt access to important information.</p><p>Most importantly, I understood how multiple stages of an attack can combine to compromise a system.</p><h3>Conclusion</h3><p>The WannaCry ransomware simulation was a valuable hands-on learning experience that helped me understand how ransomware attacks work beyond theoretical explanations.</p><p>By using Kali Linux, Nmap, Metasploit, and a Windows 7 virtual machine, I explored the different stages of an attack, from identifying a vulnerable system to observing the impact of ransomware execution.</p><p>This exercise reinforced an important lesson:</p><p><strong>Cybersecurity is not just about understanding how attacks happen; it is also about learning how to identify vulnerabilities, prevent exploitation, and protect systems before an attack occurs.</strong></p><p>This is one of the practical steps in my journey of learning cybersecurity, and I look forward to exploring more security tools, vulnerabilities, and hands-on labs.</p><p><em>Disclaimer: This exercise was conducted strictly for educational purposes in a controlled virtual lab environment. The techniques discussed should only be tested on systems you own or have explicit authorization to assess. Never execute ransomware samples on personal, organizational, or publicly accessible systems.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9c6a626b55e5" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>