<?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 Ahmed Yasser on Medium]]></title>
        <description><![CDATA[Stories by Ahmed Yasser on Medium]]></description>
        <link>https://medium.com/@ahmedyasserx300?source=rss-99d24ee35a2d------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*Ery810JHFhWnWcUg</url>
            <title>Stories by Ahmed Yasser on Medium</title>
            <link>https://medium.com/@ahmedyasserx300?source=rss-99d24ee35a2d------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 09:04:19 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ahmedyasserx300/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[Building a SOC Home Lab with Wazuh, Suricata, and Sysmon: From Attack Simulation to Incident…]]></title>
            <link>https://medium.com/@ahmedyasserx300/building-a-soc-home-lab-with-wazuh-suricata-and-sysmon-from-attack-simulation-to-incident-273f1ef7c7ac?source=rss-99d24ee35a2d------2</link>
            <guid isPermaLink="false">https://medium.com/p/273f1ef7c7ac</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[soc]]></category>
            <category><![CDATA[information-security]]></category>
            <category><![CDATA[cyber-security-analyst]]></category>
            <dc:creator><![CDATA[Ahmed Yasser]]></dc:creator>
            <pubDate>Sat, 26 Sep 2026 19:23:38 GMT</pubDate>
            <atom:updated>2026-09-26T19:23:38.742Z</atom:updated>
            <content:encoded><![CDATA[<h3>Building a SOC Home Lab with Wazuh, Suricata, and Sysmon: From Attack Simulation to Incident Response</h3><h3>Introduction</h3><p>Building a hands-on Security Operations Center (SOC) environment is a practical way to understand how security monitoring, threat detection, and incident investigation work together.</p><p>As part of my Cisco CyberOps Associate learning journey, I built a SOC home lab using three virtual machines: Kali Linux as the attacker, Windows 10 as the victim, and Ubuntu Server as the SOC monitoring environment.</p><p>The lab integrates Wazuh for centralized security monitoring, Sysmon for Windows endpoint telemetry, and Suricata for network-based threat detection.</p><p>The main goal was to simulate attack scenarios, observe the resulting security events, investigate alerts, and understand how a SOC analyst can respond to suspicious activity.</p><p>This article documents the lab architecture, attack simulation, detection process, investigation workflow, and manual incident response.</p><h3>1. Lab Architecture</h3><p>The SOC home lab consists of three virtual machines running in an isolated Host-Only network. Each machine has a specific role in simulating and monitoring security incidents.</p><p>Virtual MachineIP AddressRoleKali Linux192.168.56.11AttackerWindows 10192.168.56.20VictimUbuntu Server192.168.56.10SOC Monitoring Server</p><p><strong>Kali Linux — Attacker</strong></p><p>Used to simulate attack scenarios, including network reconnaissance and brute-force attempts.</p><p><strong>Windows 10 — Victim</strong></p><p>Acts as the monitored endpoint. Sysmon and the Wazuh Agent provide endpoint telemetry for security monitoring and investigation.</p><p><strong>Ubuntu Server — SOC Monitoring</strong></p><p>Hosts Wazuh Manager and Suricata, providing centralized security monitoring and network-based threat detection.</p><p>The lab uses an isolated Host-Only network to allow attack simulation and security monitoring without exposing the test environment to external networks.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BWm4qBGlZiiUX60e-Cyv6w.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5Yhi5w1K-cCPbsRvb_FJCQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Q5OOVz3s9eYpvP9LZezYtw.png" /><figcaption>Figure 1: The three virtual machines used in the SOC home lab: Kali Linux, Windows 10, and Ubuntu Server.</figcaption></figure><h3>2.Tools and Technologies</h3><p>The lab integrates several security tools to collect endpoint telemetry, monitor network traffic, and detect suspicious activities.</p><h3>1. Wazuh — SIEM and Security Monitoring</h3><p>Wazuh is the central security monitoring platform in this lab. It collects and analyzes security events from monitored endpoints and generates alerts based on configured detection rules.</p><p>In this environment, Wazuh is deployed on Ubuntu Server and integrated with the Windows 10 endpoint through the Wazuh Agent.</p><p>Key capabilities used in the lab include:</p><ul><li>Centralized log collection and analysis.</li><li>Security alert monitoring.</li><li>Custom detection rules.</li><li>Event correlation and investigation.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PrsU5wtACKZceTB51feVqg.png" /><figcaption>Wazuh dashboard deployed on the Ubuntu SOC server.</figcaption></figure><h3>2. Sysmon — Windows Endpoint Monitoring</h3><p>Sysmon (System Monitor) is used to collect detailed activity logs from the Windows 10 endpoint.</p><p>It provides visibility into activities such as process creation, network connections, and file-related events.</p><p>These logs help provide endpoint-level context during security investigations. The Wazuh Agent forwards the relevant Windows events to the Wazuh Manager for analysis.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NW1A8pQsdTLiNxdPsrh06A.png" /><figcaption>Sysmon collecting process creation events on the Windows endpoint.</figcaption></figure><h3>3. Suricata — Network Intrusion Detection</h3><p>Suricata is deployed on the Ubuntu SOC server to provide network-based threat detection.</p><p>It analyzes network traffic and generates alerts when traffic matches its detection rules.</p><p>Suricata complements Wazuh by providing network-level visibility, helping the analyst investigate suspicious activity from a different perspective.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BCHOQZGv_RXo0oWdqyHt7Q.png" /><figcaption>Suricata network event data available in the monitoring environment.</figcaption></figure><h3>4. Kali Linux — Attack Simulation</h3><p>Kali Linux is used as the attacker machine to simulate security scenarios in the isolated lab environment.</p><p>The attack simulations include:</p><ul><li>Network reconnaissance using Nmap.</li><li>Brute-force attempts using SSH.</li><li>SSH login attempts and command execution.</li></ul><p>These activities help generate events that can be monitored and investigated using the security tools in the lab.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0UfOp_-QOd3S_hfNXdWzqw.png" /><figcaption>Nmap reconnaissance performed from the Kali Linux attacker machine.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eQtLdMWfU6C3qVANTUcxJQ.png" /><figcaption>Brute-force attempts using SSH</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qPBEDkfQwcNM-0UReYaFsA.png" /><figcaption>SSH authentication attempts simulated using ٍSSH.</figcaption></figure><h3><strong>3. Attack Simulation and Detection</strong></h3><h4>3.1 Network Reconnaissance with Nmap</h4><p>To simulate network reconnaissance, I used Nmap from the Kali Linux machine to scan the Windows 10 target.</p><p>The scan identified several open ports and running services, including SSH (22), RPC (135), NetBIOS (139), and SMB (445).</p><p>The reconnaissance activity was also recorded in Wazuh, allowing me to review the related events and investigate the scanning activity.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2a9ZEaMm8Muamo5NoXYM_w.png" /><figcaption>Figure: Nmap scan results and the corresponding detection in Wazuh.</figcaption></figure><h4>3.2 SSH Brute-Force Simulation</h4><p>I used Hydra on Kali Linux to simulate SSH brute-force activity against the Windows target.</p><p>The test generated repeated failed authentication attempts, which were monitored by Wazuh.</p><p>A custom Wazuh rule was configured to detect multiple failed SSH login attempts within a defined time window. The activity triggered an alert with Rule ID 100700.</p><p>This demonstrates how custom detection rules can help identify suspicious authentication patterns.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*s2Un7SLHYI3z5MOQPPDGVA.png" /><figcaption>Figure: Wazuh alert generated by the custom SSH brute-force detection rule.</figcaption></figure><h4>3.3 Successful SSH Authentication</h4><p>During the simulated attack sequence, a successful SSH authentication event was recorded.</p><p>I created a custom Wazuh rule to identify this event as the third stage of the attack chain. The alert was generated with Rule ID 100702 and the description Attack Chain Stage 3: Successful SSH Authentication.</p><p>This event provided additional context for investigating the sequence of authentication attempts and helped demonstrate how custom rules can identify important events during an investigation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UqDCP2xFAk_PJJykisDL5A.png" /><figcaption>Figure: Wazuh alert for successful SSH authentication (Rule ID 100702).</figcaption></figure><h4>3.4 Multi-Stage Attack Correlation</h4><p>To correlate different stages of the simulated attack, I created a custom Wazuh rule (Rule ID: 100800).</p><p>This rule was designed to correlate multiple security events, including network reconnaissance, SSH brute-force attempts, successful SSH authentication, and host execution activity.</p><p>The rule generates a critical alert with a severity level of 15 when the defined attack conditions are met. This helps provide a broader view of related activities instead of investigating each event separately.</p><p>This demonstrates how event correlation can help SOC analysts identify and investigate multi-stage attack patterns.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nuWJJHcWdF9PUoN1BEDhVw.png" /><figcaption>Figure: Wazuh alert showing the correlated multi-stage attack (Rule ID 100800).</figcaption></figure><h4>4. Investigation and Analysis</h4><p>After generating the security alerts, I used the Wazuh dashboard to review and investigate the events collected during the simulated attacks.</p><p>The investigation focused on examining the detected activities, reviewing the associated rule IDs, and understanding how the different events were related.</p><p>By correlating reconnaissance, brute-force attempts, successful authentication, and host execution events, I could examine the simulated attack as a sequence of related activities rather than isolated alerts.</p><p>This process demonstrates the importance of alert investigation and event correlation in a SOC environment.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BQRbWfYRAt19QVpW06vEWA.png" /><figcaption>Figure: Wazuh dashboard showing security alerts generated during the lab exercises.</figcaption></figure><h4>5. Incident Response: Blocking the Attacker</h4><p>After detecting and correlating the attack activities in Wazuh, I configured a Windows Defender Firewall rule to perform a manual containment action.</p><p>The rule, named Wazuh-100800-Block-Lab-Attacker, was enabled and configured to block incoming connections from the attacker IP address 192.168.56.11.</p><p>This step demonstrates how a SOC analyst can move beyond detection and investigation by applying a containment measure to restrict network access from a suspicious host.</p><p>The firewall rule was configured as part of the incident response workflow in the lab.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/908/1*LvL187WHQ5_VmwcmFNR-CA.png" /><figcaption><em>Figure: Windows Defender Firewall rule configured to block the attacker IP (192.168.56.11).</em></figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/636/1*nkQMs_3rYDH4pJkpoOSa2w.png" /><figcaption><em>Figure: Windows Defender Firewall rule configured to block the attacker IP (192.168.56.11).</em></figcaption></figure><h4>6. Conclusion</h4><p>In this project, I built a SOC home lab using Wazuh, Suricata, Sysmon, and Kali Linux to simulate and investigate security events in an isolated environment.</p><p>I performed network reconnaissance and SSH brute-force simulations, then developed custom Wazuh rules to detect suspicious activities and correlate multiple stages of the simulated attack.</p><p>As part of the incident response process, I configured a Windows Defender Firewall rule to block the attacker’s IP address, demonstrating a practical network containment technique.</p><p>This hands-on experience helped me gain practical knowledge of security monitoring, alert detection, event correlation, incident investigation, and network containment in a SOC environment.</p><p>In the future, I plan to expand the lab by implementing additional detection scenarios and exploring automated incident response capabilities.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=273f1ef7c7ac" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>