<?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 Izunna Madu on Medium]]></title>
        <description><![CDATA[Stories by Izunna Madu on Medium]]></description>
        <link>https://medium.com/@mcnelson050?source=rss-2c04964ac50f------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*-JMS8XER8loP7O3qdYJT2A.png</url>
            <title>Stories by Izunna Madu on Medium</title>
            <link>https://medium.com/@mcnelson050?source=rss-2c04964ac50f------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 08:20:43 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@mcnelson050/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[From Hash to Alert: Turning Medusa Ransomware Intelligence into a Working Suricata Detection]]></title>
            <link>https://medium.com/@mcnelson050/from-hash-to-alert-turning-medusa-ransomware-intelligence-into-a-working-suricata-detection-87b0560b1745?source=rss-2c04964ac50f------2</link>
            <guid isPermaLink="false">https://medium.com/p/87b0560b1745</guid>
            <category><![CDATA[threat-intelligence]]></category>
            <category><![CDATA[soc-analyst]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[vulnerability]]></category>
            <category><![CDATA[incident-response]]></category>
            <dc:creator><![CDATA[Izunna Madu]]></dc:creator>
            <pubDate>Thu, 08 Oct 2026 12:05:49 GMT</pubDate>
            <atom:updated>2026-10-08T12:05:49.960Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Oo_i8Yv7IVuVJGnrJGv0xw.png" /></figure><p>What I learned identifying a malicious sample among 50 hashes, building a network detection rule, and being honest about what my evidence did and didn’t prove</p><p>Most threat intelligence reports end with a list of indicators. Most detection engineering write-ups end with a rule that “works.” I wanted to connect the two, and to be rigorous about where my proof stopped.</p><p>This is the story of a lab exercise that took me from a pile of 50 file hashes to a validated Suricata alert, and of the lesson that matters most to a SOC: <strong>a rule that loads is not the same as a rule that detects.</strong></p><h3>The Scenario</h3><p>The brief was a healthcare-focused malware campaign. Healthcare is a high-impact target because downtime affects patient care, not just revenue. My job:</p><ol><li>Identify the one malicious file among 50 hashes</li><li>Enrich it with IOCs (IPs, emails, crypto wallets, file extensions, ransom-note names, TOR addresses)</li><li>Build a Suricata rule for a malicious IP</li><li>Test it and present the findings to executive leadership</li></ol><p><strong>Lab environment:</strong> Kali Linux sensor (10.0.4.4/24) running Suricata 8.0.6 on eth0, with a controlled endpoint at 10.0.4.2.</p><p><strong>Baseline check:</strong> Before any testing, I captured the sensor’s interface and addressing.</p><p>bash</p><pre>ip addr show eth0</pre><p>Figure 1. Baseline network configuration</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/984/1*cu19-JVtk4qTayIg2FKp2w.png" /><figcaption>Kali sensor baseline: eth0 is up on the 10.0.4.0/24 lab network.</figcaption></figure><p><strong>Figure 1.</strong> Shows eth0 UP with 10.0.4.4/24.</p><h3>Step 1: Finding the Needle with VirusTotal</h3><p>Checking 50 hashes by hand is slow, so I scripted it with Bash, cURL, and jq against the VirusTotal API:</p><pre>curl -s --request GET \<br>  --url &quot;https://www.virustotal.com/api/v3/files/$HASH&quot; \<br>  --header &quot;x-apikey: $API_KEY&quot;<br><br>echo &quot;$RESPONSE&quot; | jq &#39;.data.attributes.last_analysis_stats.malicious&#39;</pre><p>For each hash, the script pulled the malicious detection count, the flagging vendors, a meaningful file name, and the suggested threat label. I ran the whole batch with:</p><pre>./check_hashes.sh</pre><p><strong>Figure 2.</strong> Hash scanning output</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1008/1*NST3NN0cHkxFytT7JdujJg.png" /><figcaption>The batch script flags one malicious hash among 50</figcaption></figure><p>Figure 2. Terminal output showing several benign results followed by the malicious hit.</p><p>Most hashes came back clean. One did not:</p><pre>SHA-256: 1bc0575b3fc6486cb2510dac1ac6ae4889b94a955d3eade53d3ba3a92d133281<br>Flagged by:   57 vendors<br>Malware name: svhost.exe<br>Threat label: ransomware.medusalocker/medusa</pre><pre>grep -n &#39;1bc0575b3fc6486cb2510dac1ac6ae4889b94a955d3eade53d3ba3a92d133281&#39; &lt;hash-output-file&gt;</pre><p><strong>Figure 3.</strong> Malicious hash identification</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/988/1*B_vQ-zxAGG-3xkNgSHm1_Q.png" /><figcaption>Close-up of the malicious hash, vendor list, malware name, and threat label.</figcaption></figure><p>Figure 3. Close-up of the malicious hash, vendor list, malware name, and threat label.</p><p><strong>57 vendors</strong> is a strong consensus. The file name is also a useful detail. svhost.exe is one letter away from the legitimate Windows process svchost.exe. That is classic masquerading, and it makes a good threat-hunting pivot for any defender.</p><h3>Step 2: Translating Intelligence into a Detection Rule</h3><p>With a malicious external IP selected as the detection target (195.123.246.138), I wrote the rule:</p><pre>alert ip any any -&gt; 195.123.246.138 any (msg:&quot;Detected suspicious IP access&quot;; sid:1000002; rev:1;)</pre><p>The rule says: alert on any IP traffic from any source to this destination. It’s simple, and that simplicity is why it’s useful as a teaching rule, but it is also very broad. In production I’d add direction and flow constraints, threshold logic, and metadata for IOC source, confidence, and expiry.</p><p>I put the rules in a dedicated local.rules file. Custom detections should be kept separate from managed rulesets so updates don&#39;t overwrite them.</p><pre>sudo cat /etc/suricata/rules/local.rules</pre><p><strong>Figure 4.</strong> Rules in local.rules</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/989/1*ThudpCGJ8DLM7rvVsXDy_Q.png" /><figcaption>Custom detections live in local.rules, separate from the managed ruleset.</figcaption></figure><p><strong>Figure 4.</strong> Shows the external IOC rule (and the test rule, once added).</p><h3>Step 3: The Bug That Taught Me the Most</h3><p>My first run produced a warning that no rule files matched. Suricata was searching /var/lib/suricata/rules/local.rules, but my file lived at /etc/suricata/rules/local.rules.</p><p>I confirmed the file location and the configuration with:</p><pre>sudo ls -l /etc/suricata/rules/local.rules<br>sudo grep -n -A3 &#39;^rule-files:&#39; /etc/suricata/suricata.yaml</pre><p>The fix was to reference the path explicitly in suricata.yaml:</p><pre>rule-files:<br>  - suricata.rules<br>  - /etc/suricata/rules/local.rules</pre><p><strong>Figure 5. </strong>Rule-file configuration</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/877/1*fgY6FC_a8_SosWy3hqEVpQ.png" /><figcaption>The one-line fix: explicitly referencing local.rules.</figcaption></figure><blockquote>Figure 5. Shows lines 2330 to 2333 of suricata.yaml with local.rules listed under rule-files.</blockquote><p>Then I validated before running:</p><pre>sudo suricata -T -c /etc/suricata/suricata.yaml</pre><p><strong>Figure 6. </strong>Successful configuration test</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/973/1*WaiGcld7Bgp1Muh3f21oSA.png" /><figcaption>Configuration test passes. Always run -T after any change</figcaption></figure><p>Insert: Figure 6. Shows Suricata 8.0.6 RELEASE running the config test successfully.</p><p><strong>Lesson:</strong> always run -T after any config change. A rule file that silently isn&#39;t loaded is the most dangerous kind of failure, because everything looks fine while you detect nothing.</p><h3>Step 4: Proving the Pipeline Works</h3><p>I didn’t want to send traffic to real malicious infrastructure, so I built a controlled test rule against my own lab endpoint:</p><pre>alert ip any any -&gt; 10.0.4.2 any (msg:&quot;TEST suspicious IP access&quot;; sid:1000001; rev:1;)</pre><p>First, I confirmed the endpoint was reachable:</p><pre>ping -c 5 10.0.4.2</pre><p><strong>Figure 7.</strong> Endpoint reachability</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/934/1*E-19-v1PLc3AYuHVNQTWVg.png" /><figcaption>Figure 7. — Reachability confirmed before detection testing.</figcaption></figure><p>Figure 7. Five replies, 0% packet loss.</p><p>Then I started Suricata on the monitoring interface:</p><pre>sudo suricata -c /etc/suricata/suricata.yaml -i eth0</pre><p>And checked Suricata’s EVE JSON log for the alert:</p><pre>sudo grep -a &#39;1000001\|TEST suspicious IP access&#39; /var/log/suricata/eve.json</pre><p><strong>Figure 8. </strong>Confirmed SID 1000001 alert</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/984/1*xVCKerAGe2erTsbofodNWg.png" /><figcaption>Figure 8. — The custom rule fires and the alert lands in eve.json.</figcaption></figure><p>Figure 8. The EVE JSON event showing signature_id: 1000001, source 10.0.4.4, destination 10.0.4.2.</p><p>The alert fired: signature ID 1000001, source 10.0.4.4, destination 10.0.4.2, logged to eve.json.</p><p>Looking closely at the event, the traffic that triggered it was <strong>DHCP</strong> (UDP 68 → 67). Because my rule matches <em>any</em> IP traffic to that host, it caught background DHCP chatter. That is a real-world lesson in rule breadth: an overly generic rule fires on traffic you didn’t intend, and noisy rules train analysts to ignore alerts.</p><p>The same logs showed an Emerging Threats informational alert:</p><pre>sudo grep -a &#39;2022973&#39; /var/log/suricata/eve.json | tail -n 5</pre><p><strong>Figure 9.</strong> Baseline informational alert</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/998/1*i2A3-iFofFNoiuhOGxxG-A.png" /><figcaption>Figure 9. — Background noise: a benign informational alert proves live inspection.”</figcaption></figure><p>Figure 9. Shows SID 2022973, “ET INFO Possible Kali Linux hostname in DHCP Request Packet.”</p><p>It is benign (SID 2022973, “Possible Kali Linux hostname in DHCP Request Packet”), but it confirmed that Suricata was inspecting live traffic with its full ruleset loaded.</p><h3>The Part Most Reports Skip: What I Did Not Prove</h3><p>My SID 1000001 test proves that the config loads, the rule syntax is valid, Suricata inspects traffic, and alerts reach eve.json.</p><p>It does <strong>not</strong> prove that the malicious-IP rule fires on traffic to 195.123.246.138. That requires separate, authorized, isolated-lab validation. I documented this as a gap instead of overstating the result.</p><p>I think this is what separates detection engineering from checkbox security. In an incident, “we have a rule for that” and “we’ve verified the rule fires” lead to very different outcomes.</p><h3>One More Operational Finding</h3><p>On manual startup, Suricata logged:</p><pre>af-packet: fanout not supported by kernel: Kernel too old or cluster-id 99 already in use.</pre><p><strong>Figure 10.</strong> Startup output showing the warning, thread creation, and packet/drop counters.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/629/1*FNfmaR5TFKPwcELYx1FgOw.png" /><figcaption>“Suricata starts, but the fanout warning needs investigation before production.”</figcaption></figure><p>It still started and inspected packets, but AF_PACKET fanout controls how traffic is distributed across capture threads. In production, this could mean uneven load or dropped packets. I flagged it as something to resolve before calling the deployment production-ready.</p><h3>Recommendations for Leadership</h3><p>The report to executives translated the technical work into ten actions. The five that matter most:</p><ol><li><strong>Govern your IOCs.</strong> Track source, confidence, first/last seen, and expiry. Indefinitely blocking stale IPs creates noise and false confidence.</li><li><strong>Validate detections continuously.</strong> Document for every rule whether it is loaded, triggered, logged, and escalated.</li><li><strong>Don’t rely on network-only visibility.</strong> Ransomware uses encrypted channels and legitimate protocols. Pair Suricata with EDR telemetry.</li><li><strong>Treat backups as a security control.</strong> Offline or immutable backups, with tested restores.</li><li><strong>Centralize telemetry.</strong> Forward EVE events to a SIEM such as Wazuh for correlation and investigation.</li></ol><h3>Key Takeaways</h3><ul><li><strong>Automate triage.</strong> A short Bash/jq script turned 50 manual lookups into one command.</li><li><strong>IOCs decay.</strong> IPs and TOR nodes change quickly. File hashes and artifacts last longer, but attackers can change those too.</li><li><strong>Test your config, then test your rule, then test your IOC.</strong> These are three different claims.</li><li><strong>Broad rules create noise.</strong> Scope them deliberately.</li><li><strong>Honest limitations build trust.</strong> Executives can act on a report that clearly separates validated findings from open gaps.</li></ul><h3>What’s Next</h3><ul><li>Validating the external IOC rule in a fully isolated lab</li><li>Shipping Suricata EVE logs into Wazuh</li><li>Building tighter rules using TLS SNI, DNS, and JA3 fingerprints</li><li>Mapping findings to MITRE ATT&amp;CK</li></ul><p><em>If you work in SOC, threat intelligence, or detection engineering, I’d love to hear how you validate your IOC-based rules. Connect with me, or drop a comment below.</em></p><p>Cybersecurity Threat Intelligence Suricata Ransomware SOC Detection Engineering Blue Team</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=87b0560b1745" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[IOC vs IOA in Cybersecurity: Understanding the Difference Between Indicators of Compromise and…]]></title>
            <link>https://medium.com/@mcnelson050/ioc-vs-ioa-in-cybersecurity-understanding-the-difference-between-indicators-of-compromise-and-359d3f0b0800?source=rss-2c04964ac50f------2</link>
            <guid isPermaLink="false">https://medium.com/p/359d3f0b0800</guid>
            <category><![CDATA[incident-response]]></category>
            <category><![CDATA[threat-hunting]]></category>
            <category><![CDATA[threat-intelligence]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[social-media]]></category>
            <dc:creator><![CDATA[Izunna Madu]]></dc:creator>
            <pubDate>Tue, 22 Sep 2026 12:47:48 GMT</pubDate>
            <atom:updated>2026-09-22T12:47:48.593Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*o9inDljIlGYv1sc_JwUVPQ.png" /></figure><h3>IOC vs IOA in Cybersecurity: Understanding the Difference Between Indicators of Compromise and Indicators of Attack</h3><p>In cybersecurity, detecting an attack is rarely as simple as finding a malicious IP address or noticing that an antivirus solution has flagged a suspicious file.</p><p>Modern attacks are often designed to evade traditional detection mechanisms. Attackers may change their infrastructure, use legitimate tools, compromise trusted accounts, or operate quietly within an environment.</p><p>This is why security analysts need to understand two important concepts:</p><p><strong>IOC — Indicator of Compromise</strong></p><p>and</p><p><strong>IOA — Indicator of Attack</strong></p><p>Although these terms are sometimes used interchangeably, they represent different approaches to identifying malicious activity.</p><p>Understanding the difference is particularly important for <strong>SOC analysts, incident responders, threat hunters, and cybersecurity professionals</strong> because it affects how security teams detect, investigate, and respond to threats.</p><h3>What is an IOC?</h3><p><strong>IOC stands for Indicator of Compromise.</strong></p><p>An IOC is a piece of observable evidence that may indicate that a system, network, account, or environment has already been compromised.</p><p>In simple terms:</p><blockquote><strong><em>An IOC is evidence that something malicious has happened or may have happened.</em></strong></blockquote><p>IOCs are often associated with artifacts left behind by an attacker.</p><p>Examples include:</p><ul><li>Malicious IP addresses</li><li>Malicious domains</li><li>File hashes</li><li>Suspicious filenames</li><li>Malicious URLs</li><li>Registry modifications</li><li>Known malware samples</li><li>Suspicious email addresses</li><li>Command-and-control infrastructure (C2)</li><li>Unusual persistence mechanisms</li><li>Compromised credentials</li><li>Specific malware artifacts</li></ul><p>For example, imagine a SOC analyst receives an alert that a workstation has communicated with:</p><p>185.XX.XX.XX</p><p>Threat intelligence shows that the IP address has previously been associated with malware command-and-control infrastructure.</p><p>That IP address can become an <strong>IOC</strong>.</p><p>Similarly, suppose an analyst discovers that a suspicious executable has the SHA-256 hash:</p><p>1bc0575b3fc6486cb2510dac1ac6ae4889b94a955d3eade53d3ba3a92d133281</p><p>If threat intelligence confirms that the hash belongs to known malware, the hash becomes an IOC.</p><p>The important point is that the IOC is an <strong>observable artifact</strong>.</p><h3>Common Types of IOCs</h3><p>IOCs can exist across different layers of an environment.</p><h3>1. Network IOCs</h3><p>These are indicators observed within network traffic.</p><p>Examples:</p><ul><li>Malicious IP addresses</li><li>Malicious domains</li><li>Suspicious URLs</li><li>Unusual DNS requests</li><li>Known command-and-control servers</li><li>Suspicious ports and protocols</li></ul><p>For example:</p><pre>Internal Host<br>     |<br>     | HTTPS<br>     v<br>Malicious Domain<br>     |<br>     v<br>Command &amp; Control Server</pre><p>A SIEM, IDS, firewall, or network monitoring solution may detect communication with the malicious infrastructure.</p><h3>2. File-Based IOCs</h3><p>These are artifacts associated with malicious files.</p><p>Examples include:</p><ul><li>MD5 hashes</li><li>SHA-1 hashes</li><li>SHA-256 hashes</li><li>Suspicious filenames</li><li>Malicious file paths</li><li>File extensions</li></ul><p>For example:</p><pre>invoice.pdf.exe</pre><p>could be suspicious depending on the context.</p><p>A hash can then be investigated using threat intelligence platforms such as VirusTotal.</p><h3>3. Host-Based IOCs</h3><p>These are artifacts discovered on endpoints or servers.</p><p>Examples:</p><ul><li>Registry modifications</li><li>New services</li><li>Suspicious scheduled tasks</li><li>Unexpected executable files</li><li>Modified system files</li><li>Persistence mechanisms</li><li>Suspicious processes</li></ul><p>For example, a security analyst may discover an unfamiliar scheduled task that launches a suspicious executable every hour.</p><p>That artifact may become part of the investigation’s IOC set.</p><h3>4. Email IOCs</h3><p>Phishing investigations can produce several IOCs.</p><p>Examples include:</p><ul><li>Sender addresses</li><li>Malicious domains</li><li>URLs</li><li>Attachment hashes</li><li>Email subjects</li><li>Reply-to addresses</li><li>Attachment filenames</li></ul><p>For example:</p><pre>From: payroll-update@example-malicious.com<br>Attachment: Salary_Adjustment.xlsm<br>URL: hxxp://example-malicious[.]com/login</pre><p>Each observable artifact can potentially contribute to the investigation.</p><h3>What is an IOA?</h3><p><strong>IOA stands for Indicator of Attack.</strong></p><p>Unlike an IOC, an IOA focuses primarily on <strong>the behavior or activity associated with an attack</strong>.</p><p>In simple terms:</p><blockquote><strong><em>An IOA is evidence of suspicious or malicious behavior that suggests an attack is occurring or being attempted.</em></strong></blockquote><p>This is an important distinction.</p><p>An IOC may tell you:</p><blockquote><em>“This malicious file or IP address has been observed.”</em></blockquote><p>An IOA may tell you:</p><blockquote><em>“Something is behaving like an attacker.”</em></blockquote><p>For example, suppose an attacker gains access to a workstation and executes:</p><pre>powershell.exe</pre><p>PowerShell itself is legitimate.</p><p>Therefore, simply seeing PowerShell does not automatically mean that the system is compromised.</p><p>However, consider a sequence such as:</p><pre>WINWORD.EXE<br>      ↓<br>powershell.exe<br>      ↓<br>Encoded command<br>      ↓<br>Network connection<br>      ↓<br>Suspicious payload execution</pre><p>The <strong>behavioral chain</strong> is much more interesting from a detection perspective.</p><p>The sequence may represent an IOA.</p><h3>Examples of IOAs</h3><p>IOAs are often based on suspicious behaviors, techniques, and attack patterns.</p><p>Examples include:</p><h3>Credential Dumping</h3><p>An attacker attempts to extract credentials from a system.</p><p>Possible behavior:</p><pre>Suspicious Process<br>      ↓<br>Attempts to Access<br>Credential Store</pre><p>The behavior can indicate an attack even if no known malware hash is involved.</p><h3>Lateral Movement</h3><p>An attacker compromises one machine and attempts to access another.</p><p>For example:</p><pre>Workstation A<br>     ↓<br>Administrative Authentication<br>     ↓<br>Server B</pre><p>Repeated unusual authentication activity may represent an IOA.</p><h3>Privilege Escalation</h3><p>An attacker attempts to obtain higher privileges.</p><p>For example:</p><pre>Standard User<br>     ↓<br>Privilege Escalation Attempt<br>     ↓<br>Administrator/System</pre><p>The behavior is important even if the attacker does not use a known malicious file.</p><h3>PowerShell Abuse</h3><p>PowerShell is a legitimate administrative tool.</p><p>However, suspicious PowerShell behavior can be an IOA.</p><p>For example:</p><pre>Office Application<br>       ↓<br>PowerShell<br>       ↓<br>Encoded Command<br>       ↓<br>Download<br>       ↓<br>Execution</pre><p>The individual components may be legitimate, but their combination can indicate malicious activity.</p><h3>Suspicious Account Activity</h3><p>An account normally logs in from Lagos during working hours.</p><p>Suddenly:</p><pre>Login<br>   ↓<br>Unusual Location<br>   ↓<br>Unusual Device<br>   ↓<br>Multiple Failed Attempts<br>   ↓<br>Successful Authentication<br>   ↓<br>Sensitive Resource Access</pre><p>The pattern can represent an IOA even if there is no known malicious IP address or malware hash.</p><h3>IOC vs IOA: The Core Difference</h3><p>The easiest way to remember the distinction is:</p><p><strong>IOC = What evidence was left behind?</strong></p><p><strong>IOA = What is the attacker doing?</strong></p><p>Think of a physical crime scene.</p><p>An IOC is similar to finding:</p><ul><li>fingerprints</li><li>a weapon</li><li>a broken lock</li><li>a specific vehicle</li><li>DNA evidence</li></ul><p>An IOA is more about observing:</p><ul><li>someone attempting to break the lock</li><li>someone moving through restricted areas</li><li>someone trying different doors</li><li>someone attempting to disable security cameras</li></ul><p>One focuses on <strong>artifacts</strong>.</p><p>The other focuses on <strong>behavior</strong>.</p><h3>IOC vs IOA Comparison</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/757/1*X2EoCyCvHYwbepj7Ldtbqg.png" /></figure><h3>Why IOCs Can Become Less Effective</h3><p>One challenge with IOC-based detection is that attackers can change their infrastructure.</p><p>Suppose a security team blocks:</p><pre>malicious-domain.com</pre><p>An attacker may simply register:</p><pre>malicious-domain2.com</pre><p>Similarly, malware can be modified to produce a different hash.</p><p>For example:</p><pre>Malware Version 1<br>SHA-256 → ABC123...</pre><pre>Modified Malware<br>SHA-256 → XYZ789...</pre><p>The malware may still perform essentially the same malicious activity.</p><p>This means that relying exclusively on static IOCs can create a detection gap.</p><h3>Why IOAs Are Important</h3><p>Attackers can change:</p><ul><li>IP addresses</li><li>Domains</li><li>File hashes</li><li>Filenames</li><li>Malware variants</li></ul><p>But some behaviors are more difficult to completely eliminate.</p><p>For example, an attacker who wants to move laterally still needs to perform some form of authentication or remote access.</p><p>An attacker who wants to steal credentials still needs to interact with credential-related processes, files, memory, or authentication mechanisms.</p><p>An attacker who wants persistence still needs to establish some mechanism that allows them to maintain access.</p><p>This is where behavioral detection becomes valuable.</p><p>Instead of asking only:</p><blockquote><em>“Have we seen this malicious file before?”</em></blockquote><p>the analyst can ask:</p><blockquote><em>“Does this activity resemble the behavior of an attacker?”</em></blockquote><h3>A Practical SOC Example</h3><p>Imagine an employee receives a phishing email.</p><p>The employee opens a malicious document.</p><p>The following activity occurs:</p><pre>Email<br>  ↓<br>Malicious Document<br>  ↓<br>Office Application<br>  ↓<br>PowerShell<br>  ↓<br>Script Execution<br>  ↓<br>Outbound Network Connection<br>  ↓<br>Payload Download<br>  ↓<br>Persistence</pre><p>Let’s break this down.</p><h3>Possible IOCs</h3><p>The investigation might identify:</p><ul><li>Sender email address</li><li>Malicious domain</li><li>URL</li><li>File hash</li><li>Filename</li><li>Destination IP</li><li>Downloaded payload hash</li></ul><p>These are observable artifacts.</p><h3>Possible IOAs</h3><p>The investigation might identify:</p><ul><li>Office application spawning PowerShell</li><li>Encoded PowerShell execution</li><li>Suspicious outbound connection</li><li>Download followed by execution</li><li>Creation of persistence</li><li>Unusual process relationships</li></ul><p>These describe behavior.</p><p>The strongest investigation often uses <strong>both</strong>.</p><h3>IOC and IOA in Threat Hunting</h3><p>Threat hunting is where the difference becomes particularly useful.</p><p>Suppose a SOC receives a malicious IP address from a threat intelligence feed.</p><p>The analyst can search the environment for:</p><pre>Which systems communicated with this IP?</pre><p>That is IOC-based hunting.</p><p>But the analyst can go further.</p><p>The analyst might search for:</p><pre>Which systems executed PowerShell<br>followed by suspicious network activity?</pre><p>That is behavioral hunting.</p><p>The second approach may identify activity even if the attacker has already changed their infrastructure.</p><h3>IOC and IOA in SIEM Monitoring</h3><p>A SIEM such as Wazuh, Splunk, Microsoft Sentinel, or Elastic can support both approaches.</p><p>For IOC detection, a security team may create rules around:</p><pre>Known malicious IP<br>Known malicious domain<br>Known malware hash<br>Known malicious URL</pre><p>For IOA detection, the team may create behavioral detections such as:</p><pre>Office → PowerShell → Network Connection</pre><p>or:</p><pre>Multiple Failed Logins<br>       ↓<br>Successful Login<br>       ↓<br>Privileged Resource Access</pre><p>The second type of detection can provide important context.</p><h3>IOC + IOA = Stronger Detection</h3><p>The real value comes from combining both.</p><p>Consider this scenario:</p><pre>1. User receives phishing email<br>             ↓<br>2. Malicious document is opened<br>             ↓<br>3. Word launches PowerShell<br>             ↓<br>4. PowerShell downloads a file<br>             ↓<br>5. File executes<br>             ↓<br>6. System connects to suspicious domain<br>             ↓<br>7. Persistence is created</pre><p>The investigation now has both:</p><p><strong>IOAs</strong></p><p>and</p><p><strong>IOCs</strong></p><p>For example:</p><pre>IOA:<br>Word → PowerShell → Download → Execute</pre><pre>IOC:<br>Malicious domain<br>File hash<br>IP address<br>Filename</pre><p>This gives the analyst a much stronger picture of what happened.</p><h3>IOC and IOA Through the Incident Response Lifecycle</h3><p>Both concepts can support different stages of incident response.</p><h3>1. Identification</h3><p>IOCs can help identify potentially compromised systems.</p><p>IOAs can help identify suspicious activity that may represent an ongoing attack.</p><h3>2. Investigation</h3><p>Analysts can search historical logs for known IOCs.</p><p>They can also investigate behavioral patterns associated with the attack.</p><h3>3. Containment</h3><p>IOCs can be blocked.</p><p>For example:</p><pre>Block malicious IP<br>Block malicious domain<br>Quarantine malicious hash</pre><p>Behavioral detections can also help identify additional systems that may have been affected.</p><h3>4. Eradication</h3><p>Security teams can remove:</p><ul><li>Malicious files</li><li>Persistence mechanisms</li><li>Unauthorized accounts</li><li>Compromised credentials</li></ul><h3>5. Recovery</h3><p>Systems are restored and monitored for recurring suspicious behavior.</p><h3>6. Lessons Learned</h3><p>The organization can improve both:</p><ul><li>IOC-based detection</li><li>Behavioral/IOA-based detection</li></ul><h3>How SOC Analysts Should Think About IOCs and IOAs</h3><p>A common mistake for beginners is to think:</p><blockquote><em>“I found a malicious IP, therefore I found the attack.”</em></blockquote><p>Not necessarily.</p><p>The IP is only one piece of evidence.</p><p>A good SOC analyst asks:</p><p><strong>What system communicated with it?</strong></p><p><strong>When did the communication occur?</strong></p><p><strong>What process initiated the connection?</strong></p><p><strong>Which user was logged in?</strong></p><p><strong>What happened immediately before the connection?</strong></p><p><strong>What happened afterward?</strong></p><p><strong>Was there file creation?</strong></p><p><strong>Was there credential access?</strong></p><p><strong>Was there persistence?</strong></p><p>This turns an isolated IOC into a broader investigation.</p><h3>A Simple Investigation Model</h3><p>When you encounter an IOC, don’t stop at the IOC.</p><p>Use this approach:</p><pre>IOC<br>              ↓<br>       Identify the Host<br>              ↓<br>       Identify the User<br>              ↓<br>       Identify the Process<br>              ↓<br>       Check the Timeline<br>              ↓<br>      Investigate the Behavior<br>              ↓<br>      Identify Related IOCs<br>              ↓<br>      Determine Attack Scope<br>              ↓<br>       Contain &amp; Respond</pre><p>This is where IOC and IOA complement each other.</p><h3>IOC and IOA Are Not Competing Concepts</h3><p>It is tempting to ask:</p><blockquote><em>“Which one is better?”</em></blockquote><p>A better way to think about them is that they answer <strong>different questions</strong>.</p><p>IOC-based detection helps answer:</p><blockquote><em>“Have we observed evidence associated with a known compromise?”</em></blockquote><p>IOA-based detection helps answer:</p><blockquote><em>“Are we observing behavior that resembles an attack?”</em></blockquote><p>A mature security operation benefits from both.</p><h3>Final Thoughts</h3><p>Cybersecurity detection is not simply about collecting malicious IP addresses and file hashes.</p><p>Threat actors can change their infrastructure, modify malware, rotate domains, use legitimate administrative tools, and attempt to blend into normal activity.</p><p>That is why security analysts need to understand both <strong>Indicators of Compromise (IOCs)</strong> and <strong>Indicators of Attack (IOAs)</strong>.</p><p>An IOC gives you a valuable piece of evidence.</p><p>An IOA gives you insight into behavior.</p><p>Together, they help security teams move from:</p><p><strong>“I found something suspicious.”</strong></p><p>to:</p><p><strong>“I understand what happened, how it happened, and what else I should investigate.”</strong></p><p>For anyone learning SOC operations, threat hunting, incident response, or blue-team security, this distinction is fundamental.</p><p>The goal is not simply to detect a malicious artifact.</p><p>The goal is to understand the <strong>activity, context, sequence, and impact</strong> surrounding that artifact.</p><p><strong>Detect the artifact.</strong></p><p><strong>Understand the behavior.</strong></p><p><strong>Build the story.</strong></p><p><strong>Respond to the threat.</strong></p><p>-<strong>The End</strong>-</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=359d3f0b0800" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Investigating a Sophisticated Phishing Attack: A Hands-on SOC Incident Response Case Study]]></title>
            <link>https://medium.com/@mcnelson050/investigating-a-sophisticated-phishing-attack-a-hands-on-soc-incident-response-case-study-61be3a4a259c?source=rss-2c04964ac50f------2</link>
            <guid isPermaLink="false">https://medium.com/p/61be3a4a259c</guid>
            <category><![CDATA[security-operation-center]]></category>
            <category><![CDATA[phishing]]></category>
            <category><![CDATA[incidence-response]]></category>
            <category><![CDATA[threat-intelligence]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[Izunna Madu]]></dc:creator>
            <pubDate>Tue, 28 Jul 2026 03:11:01 GMT</pubDate>
            <atom:updated>2026-07-28T03:11:01.990Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6d6ySytcD11kU4H078p6jA.png" /></figure><p><em>How I investigated a phishing campaign using MXToolbox, VirusTotal, Splunk, and incident response best practices.</em></p><h3>Introduction</h3><p>Phishing remains one of the most effective attack vectors used by cybercriminals. Even organizations with mature technical controls can become vulnerable when attackers exploit human behavior through social engineering.</p><p>To strengthen my practical experience in Security Operations (SOC) and Incident Response, I completed a hands-on phishing investigation project based on a simulated attack against <strong>Medisure Health Network</strong>, a healthcare organization responsible for safeguarding sensitive patient information.</p><p>In this project, I investigated a phishing email disguised as a legitimate vendor invoice, validated email authentication records, analyzed malicious indicators, correlated security logs using Splunk, executed incident response actions, and developed recommendations to improve organizational resilience.</p><h3>Project Objectives</h3><p>The investigation aimed to:</p><ul><li>Identify phishing indicators within a suspicious email.</li><li>Validate sender authenticity using SPF, DKIM, and DMARC.</li><li>Analyze embedded URLs and Indicators of Compromise (IOCs).</li><li>Correlate security events using Splunk.</li><li>Execute containment and remediation activities.</li><li>Improve phishing awareness and incident response readiness.</li></ul><h3>Technology Stack</h3><p>This investigation leveraged several industry-standard cybersecurity tools:</p><ul><li><strong>MXToolbox — </strong>Email authentication validation</li><li><strong>VirusTotal — </strong>URL and IOC reputation analysis</li><li><strong>Splunk — </strong>Log correlation and threat investigation</li><li><strong>AbuseIPDB — </strong>IP reputation analysis</li><li><strong>SOC Incident Response Procedures</strong></li></ul><h3>Phase 1: Initial Email Investigation</h3><p>The investigation started with analyzing the suspicious email.</p><p>Several classic phishing indicators immediately stood out:</p><ul><li>Suspicious sender address</li><li>Reply-to mismatch</li><li>Credential-harvesting URL</li><li>Urgent social engineering language</li><li>Hidden tracking pixel</li></ul><p><em>These indicators suggested a well-crafted phishing campaign designed to steal user credentials.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/975/1*4CdnrBTEC3trS1geDwJrWw.png" /><figcaption>Suspicious Email Header</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/975/1*Z-VEyNXbpA9PTuOQ7PCKrg.png" /><figcaption>Credential-harvesting URL and Urgent social engineering language</figcaption></figure><h3>Phase 2: Email Authentication Analysis</h3><p>Next, I validated the sender’s authenticity using MXToolbox.</p><p>The results confirmed multiple authentication failures:</p><ul><li>SPF: <strong>FAIL</strong></li><li>DKIM: <strong>None</strong></li><li>DMARC: <strong>Invalid</strong></li><li>SpamAssassin Score: <strong>Malicious</strong></li></ul><p><em>These findings strongly indicated sender spoofing and email impersonation.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/975/1*YErjLL7KGicCpoAFzC84qw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/975/1*2yJt_i5-986zimOypeqiGg.png" /><figcaption>MXToolbox SPF/DKIM/DMARC summary</figcaption></figure><h3>Phase 3: IOC Enrichment</h3><p>Using VirusTotal and reputation analysis, I investigated the embedded URLs and IP addresses.</p><p>Key findings included:</p><ul><li>Malicious domains</li><li>Lookalike login pages</li><li>Known phishing infrastructure</li><li>Suspicious IP addresses</li></ul><p><em>IOC enrichment provides analysts with valuable threat intelligence for containment and future detection.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/975/1*SOjpefM43BKKpCec8sU8eg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/975/1*H3jOXogtCGq1TaEag1iikQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/975/1*BjrkGu6blmW9fsQHgCTf-w.png" /><figcaption>VirusTotal detections for IOCs</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/975/1*orlOZNLpuZOz-SIwbVJI2w.png" /><figcaption>VirusTotal detections for IOCs</figcaption></figure><h3>Phase 4: Splunk Investigation</h3><p>The next stage focused on log correlation using Splunk.</p><p>I analyzed:</p><ul><li>Proxy Logs</li><li>Firewall Logs</li><li>Authentication Logs</li><li>IOC Correlation Searches</li></ul><p>The investigation confirmed that:</p><ul><li>Multiple users clicked the phishing link.</li><li>Internal systems communicated with attacker infrastructure.</li><li>Failed login attempts originated from a foreign location shortly after users interacted with the phishing email.</li></ul><p>Fortunately, there was <strong>no evidence of data exfiltration</strong>, although the investigation indicated likely credential compromise for one affected user.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/975/1*kO2QSXBDM4j6z96cQhwklA.png" /><figcaption>Proxy logs — Alice and Bob accessed access-accsecurity.com and sign.in</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/975/1*xDTyQCM8h4JQKhqJdsbP1w.png" /><figcaption>Firewall logs — Internal hosts (10.1.5.23, 10.1.5.89) connected to 89.144.44.41</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/975/1*OvNo5-FTQLR72fZqG1LzUQ.png" /><figcaption>Auth logs — Failed Russia-based login attempt for bob@healthguardmed.net &amp; <a href="/service/mailto:alice@medisurehealthnetwork.com">alice@medisurehealthnetwork.com</a></figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/975/1*kO2QSXBDM4j6z96cQhwklA.png" /><figcaption>Aggregated IOC hits — user counts for malicious domains/IPs</figcaption></figure><h3>Incident Response</h3><p>Once the phishing attack was confirmed, I initiated standard SOC response procedures.</p><p>These included:</p><ul><li>Email quarantine</li><li>Domain and IP blocking</li><li>Password resets</li><li>Host isolation</li><li>Malware scanning</li><li>MFA enforcement</li><li>Enhanced SIEM monitoring</li></ul><p><em>The incident response successfully contained the threat while preventing further compromise.</em></p><h3>Lessons Learned</h3><p>This project reinforced several key cybersecurity principles:</p><ul><li>Email authentication is critical for detecting spoofing.</li><li>Threat intelligence enhances IOC analysis.</li><li>SIEM platforms provide visibility across multiple data sources.</li><li>Rapid containment significantly reduces organizational risk.</li><li>Security awareness remains one of the strongest defenses against phishing.</li></ul><h3>Final Thoughts</h3><p>This project strengthened my practical experience in:</p><ul><li>Security Operations (SOC)</li><li>Phishing Investigation</li><li>Incident Response</li><li>Threat Intelligence</li><li>SIEM Analysis</li><li>Log Correlation</li><li>Email Security</li><li>IOC Analysis</li></ul><p>Hands-on projects like this continue to bridge the gap between theory and real-world cybersecurity operations.</p><p><em>If you’re interested in phishing investigations, SOC operations, or threat detection, I’d love to connect and exchange ideas.</em></p><p><strong>#CyberSecurity #SOCAnalyst #IncidentResponse #ThreatIntelligence #Splunk #BlueTeam #Phishing #EmailSecurity #ThreatHunting #CyberDefense #InformationSecurity #ContinuousLearning</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=61be3a4a259c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[From Vulnerability Discovery to Risk Reduction: A Hands-on Nessus Vulnerability Assessment Project]]></title>
            <link>https://medium.com/@mcnelson050/from-vulnerability-discovery-to-risk-reduction-a-hands-on-nessus-vulnerability-assessment-project-2e72dd5c7671?source=rss-2c04964ac50f------2</link>
            <guid isPermaLink="false">https://medium.com/p/2e72dd5c7671</guid>
            <category><![CDATA[incidence-response]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[security-operation-center]]></category>
            <category><![CDATA[threat-intelligence]]></category>
            <category><![CDATA[vulnerability-management]]></category>
            <dc:creator><![CDATA[Izunna Madu]]></dc:creator>
            <pubDate>Mon, 20 Jul 2026 16:05:47 GMT</pubDate>
            <atom:updated>2026-07-20T16:05:47.219Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wfBMeU_zIjF0Y7_4MfcEdQ.png" /><figcaption><strong>CYBERTECH SOLUTIONS — Comprehensive Nessus Vulnerability Assessment</strong></figcaption></figure><p>How I used Nessus, Linux, Nginx, and Ansible to identify, remediate, and validate security vulnerabilities in an enterprise-like environment.</p><h3>Introduction</h3><p>One of the biggest misconceptions in cybersecurity is that running a vulnerability scan is enough to secure an organization.</p><p>The reality is quite different.</p><p>Vulnerability management is a continuous process that extends beyond identifying weaknesses. It involves understanding risk, prioritizing findings, implementing effective remediation, validating the fixes, and continuously monitoring the environment.</p><p>To strengthen my practical cybersecurity skills, I recently completed a comprehensive Vulnerability Assessment project for <strong>CyberTech Solutions</strong>, where I assumed the role of a <strong>Threat Intelligence/SOC Analyst</strong> responsible for conducting an end-to-end vulnerability assessment of a Linux-based infrastructure and web application environment. The engagement covered the complete vulnerability management lifecycle. From asset identification and vulnerability discovery to remediation, validation, and reporting.</p><h3>Project Objectives</h3><p>The primary objectives of the assessment were to:</p><ul><li>Perform a credentialed vulnerability assessment against a Linux server.</li><li>Assess the security posture of an Nginx-hosted web application.</li><li>Identify vulnerabilities, outdated software, and configuration weaknesses.</li><li>Configure automated vulnerability reporting.</li><li>Remediate identified vulnerabilities using infrastructure automation.</li><li>Validate remediation efforts through follow-up scanning.</li><li>Produce actionable security recommendations.</li></ul><h3>Technology Stack</h3><p>Throughout the assessment, I worked with several industry-standard technologies, including:</p><ul><li>Nessus Essentials</li><li>Linux</li><li>SSH</li><li>Nginx Web Server</li><li>Ansible</li><li>SMTP Email Configuration</li></ul><p>These tools closely mirror those used by <strong>Security Operations Centers</strong> <strong>(SOC)</strong> and <strong>Vulnerability Management teams </strong>in enterprise environments.</p><h3>Assessment Methodology</h3><p>To ensure consistency and accuracy, I followed a structured vulnerability management framework consisting of six phases:</p><ul><li>Asset Identification</li><li>Vulnerability Discovery</li><li>Risk Analysis</li><li>Remediation</li><li>Validation</li><li>Reporting</li></ul><p>Following a defined methodology ensures that vulnerabilities are not only discovered but also effectively remediated and verified.</p><h3>Phase 1: Credentialed Vulnerability Assessment</h3><p>The assessment began with configuring authenticated SSH credentials within Nessus to perform a credentialed scan against the Linux server.</p><p>Credentialed scanning provides significantly deeper visibility than unauthenticated scans because Nessus can inspect installed software, missing patches, system configurations, and operating system settings.</p><p>The scan successfully identified:</p><ul><li>Outdated software</li><li>Missing security updates</li><li>Configuration weaknesses</li></ul><p><strong>Screenshot: </strong><em>Nessus Credentialed Scan Configuration</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/975/1*Kit5nP6z9MXW2LEPfF1q_Q.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/975/1*I7TveeEGkDqt21iGg_0HMw.png" /><figcaption><em>Nessus Credentialed Scan Configuration</em></figcaption></figure><p><strong>Screenshot:</strong> <em>Credentialed Scan Results</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/975/1*cqTTh7JSbEqkEf2oy4I1KQ.png" /><figcaption><em>Nessus Credentialed Scan Results</em></figcaption></figure><h3>Phase 2: Web Application Vulnerability Assessment</h3><p>The second stage focused on assessing the security posture of an Nginx-hosted web application.</p><p>Using Nessus Web Application Scanning, I evaluated the application for security weaknesses affecting the web stack.</p><p>The assessment identified an information disclosure vulnerability associated with an outdated Nginx deployment, demonstrating how application-layer vulnerabilities can increase an organization’s attack surface if left unaddressed.</p><p><strong>Objective</strong></p><p>To assess the security posture of the Nginx-hosted web application and identify vulnerabilities affecting the web stack.</p><p><strong>Activities Performed</strong></p><p>1. Configured Nessus Web Application Scan.</p><p>2. Executed vulnerability assessment.</p><p>3. Reviewed findings and associated CVEs.</p><p><strong>Screenshot:</strong> <em>Web Scan Configuration</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/975/1*hVLOizZfrhB1I3mamPww5A.png" /><figcaption><em>Web Scan Configuration</em></figcaption></figure><p><strong>Screenshot:</strong> <em>Web Application Findings</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/975/1*efHcwntjzXdCaKTQGARKQw.png" /><figcaption><em>Web Application Findings</em></figcaption></figure><p><strong>Screenshot:</strong> <em>Detailed Web Application Finding</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/975/1*_eUYvViil8acyTk4N2J0bA.png" /><figcaption><strong><em>Detailed Web Application Finding</em></strong></figcaption></figure><h3>Phase 3: Automated Vulnerability Reporting</h3><p>Security teams depend on timely reporting to maintain visibility into emerging vulnerabilities.</p><p>To streamline reporting, I configured SMTP integration within Nessus and implemented scheduled email reporting.</p><p>This involved:</p><ul><li>Configuring SMTP settings</li><li>Testing secure email delivery</li><li>Scheduling automated vulnerability reports</li></ul><p>Automation reduces manual effort while ensuring security teams receive consistent updates.</p><p><strong>SMTP Configuration</strong></p><p><strong>SMTP</strong> <strong>Server</strong>: SMTP.gmail.com</p><p><strong>Port</strong>: 587</p><p><strong>Encryption</strong>: TLS</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/975/1*mwekJYH9KjhPW-t4r6g7Qg.png" /><figcaption><strong><em>Nessus SMTP Configuration</em></strong></figcaption></figure><p><strong>Screenshot:</strong> Successful Test Email</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/975/1*U3n2iE9PNruwDFUl04Rpfg.png" /><figcaption><strong><em>Test Email Delivery</em></strong></figcaption></figure><h3>Phase 4: Automated Patch Management</h3><p>Discovering vulnerabilities is only half the job.</p><p>The real objective is reducing organizational risk.</p><p>To achieve this, I used <strong>Ansible</strong> to automate remediation by:</p><ul><li>Creating an inventory file</li><li>Developing a patch management playbook</li><li>Updating package repositories</li><li>Upgrading Nginx</li><li>Restarting services</li><li>Verifying successful installation</li></ul><p>The Nginx server was successfully upgraded from:</p><p><strong>Version 1.15.5 → Version 1.30.1</strong></p><p>Automation significantly improves consistency while minimizing manual configuration errors.</p><p><strong>Screenshot:</strong> <em>Ansible Playbook</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/944/1*CeMCamk576_nHaYFx4B3Hg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/975/1*vmXyPKCblNIvS1hksZ8zZw.png" /><figcaption><em>Ansible Playbook</em></figcaption></figure><p><strong>Screenshot:</strong> <em>Successful Playbook Execution</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/975/1*UfoY7CjcOgX9WfGAgmqXsw.png" /><figcaption>Successful Playbook Execution</figcaption></figure><p><strong>Screenshot:</strong> <em>Nginx Version Verification</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/975/1*BxatoVq8AXui8RaRz3J3Nw.png" /><figcaption><em>Nginx Version Verification</em></figcaption></figure><h3>Phase 5: Validation Scanning</h3><p>Remediation without validation creates uncertainty.</p><p>After patching, I executed a second credentialed scan and repeated the web application assessment to verify that vulnerabilities had been successfully addressed.</p><p>The validation confirmed a substantial reduction in organizational risk.</p><h3>Before Remediation</h3><ul><li>High Vulnerabilities: <strong>6</strong></li><li>Medium Vulnerabilities: <strong>14</strong></li></ul><h3>After Remediation</h3><ul><li>High Vulnerabilities: <strong>0</strong></li><li>Medium Vulnerabilities: <strong>0</strong></li></ul><p>This demonstrated that the remediation strategy was effective in eliminating exploitable vulnerabilities.</p><p><strong>Screenshot:</strong> <em>Validation Scan Results Dashboard</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/975/1*Z_39vyKvxffiNBKxlJhpRQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/975/1*lFmrZ82uWuRFIc9XfcVJew.png" /><figcaption>Validation Scan Results Dashboard</figcaption></figure><h3>Key Takeaways</h3><p>This project reinforced several important cybersecurity principles:</p><p>✔ Vulnerability scanning alone does not improve security.</p><p>✔ Effective remediation is what reduces organizational risk.</p><p>✔ Infrastructure automation accelerates secure patch deployment.</p><p>✔ Validation scanning confirms remediation success.</p><p>✔ Continuous vulnerability management is essential for maintaining a strong security posture.</p><h3>Final Thoughts</h3><p>This project provided valuable hands-on experience with technologies commonly used in enterprise cybersecurity environments and strengthened my understanding of the complete vulnerability management lifecycle.</p><p>Beyond the technical implementation, it reinforced the importance of structured methodologies, automation, and continuous improvement in reducing organizational risk.</p><p>As I continue building my cybersecurity career, I remain committed to expanding my expertise in:</p><ul><li>Vulnerability Management</li><li>Security Operations (SOC)</li><li>Threat Detection</li><li>Incident Response</li><li>Security Automation</li><li>Cloud Security</li></ul><p>Thank you for reading!</p><p>If you’re interested in cybersecurity, vulnerability management, or security operations, I’d be happy to connect and exchange ideas.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2e72dd5c7671" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Deploying & Using MISP for Threat Actor Investigation: Profiling the Callisto Group]]></title>
            <link>https://medium.com/@mcnelson050/deploying-using-misp-for-threat-actor-investigation-profiling-the-callisto-group-36b0af3a83b7?source=rss-2c04964ac50f------2</link>
            <guid isPermaLink="false">https://medium.com/p/36b0af3a83b7</guid>
            <category><![CDATA[security-operation-center]]></category>
            <category><![CDATA[threat-intelligence]]></category>
            <category><![CDATA[threat-hunting]]></category>
            <category><![CDATA[blue-team]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[Izunna Madu]]></dc:creator>
            <pubDate>Mon, 18 May 2026 07:31:00 GMT</pubDate>
            <atom:updated>2026-05-18T07:31:00.896Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aH4uFFQdL-0aLBe6kQ3FQQ.png" /></figure><h3>Investigating the Callisto Group Using MISP Threat Intelligence Feeds</h3><h4>Introduction</h4><p>Threat intelligence has become one of the most important components of modern cybersecurity operations. Organizations across the world continuously face attacks from sophisticated threat actors targeting government agencies, critical infrastructure, media organizations, and private enterprises.</p><p>As part of a cybersecurity project, I deployed a full MISP (Malware Information Sharing Platform) environment using Docker (see previous article) and conducted a threat intelligence investigation on the Callisto Group using real-world MISP feeds.</p><p>This project focused on collecting Indicators of Compromise (IOCs), correlating threat data, analyzing infrastructure, and building a threat actor profile.</p><h3>Project Overview</h3><h3>Scenario</h3><p>I acted as a member of a national CERT (Computer Emergency Response Team) responsible for investigating malicious activities targeting European government agencies and critical infrastructure.</p><p>The assigned threat actor for this investigation was:</p><h3>Callisto Group</h3><p>Also known as:</p><ul><li>Star Blizzard</li><li>SEABORGIUM</li><li>COLDRIVER</li><li>TA446</li></ul><p>The objective was to:</p><ul><li>Collect threat intelligence from MISP feeds</li><li>Identify malicious infrastructure</li><li>Analyze IOC correlations</li><li>Build a threat actor profile</li><li>Provide defensive recommendations</li></ul><h3>Deploying the MISP Platform with Docker</h3><p>The first phase of the project involved deploying a full MISP threat intelligence environment on Kali Linux using Docker.</p><h3>Core Components Deployed</h3><ul><li>MISP Core</li><li>MariaDB</li><li>Redis</li><li>MISP Modules</li><li>SMTP Service</li></ul><h3>Accessing MISP Platform</h3><p>Once the all container were running, I accessed the MISP web interface through my kali browser by navigating to:</p><p><a href="http://localhost/"><strong>http://localhost</strong></a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/954/1*RCK3g7muAi6QbUXZmarRYg.png" /><figcaption>docker containers running successfully</figcaption></figure><p>This confirmed that the platform was deployed successfully and ready for use.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JGMSAsD72b9f_8ohRfazRA.png" /><figcaption>MISP login page</figcaption></figure><h3>Threat Intelligence Feeds</h3><p>To populate MISP with relevant data, I enabled default threat intelligence feeds. This involved the loading of the feed and activating selected feeds to fetch real-world Indicators of Compromise (IOCs).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*O9EZZuxSgOleeXoAInNHpg.png" /><figcaption>MISP threat intelligence feeds overview</figcaption></figure><h3>Enabling Threat Intelligence Feeds</h3><p>After deployment, multiple OSINT feeds were enabled within MISP.</p><h3>Adding a Custom Feed: FIREHOL</h3><p>To enhance the dataset, a custom threat intelligence feed — FireHOL, was added to provide data about malicious IP addresses. This help to improve visibility into potential harmful infrastructure relevant to the investigation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EWqo-6Ka-kPc2c1KUsYoNQ.png" /><figcaption>FIREHOL threat intelligence feed page</figcaption></figure><h3>Other Feeds Used Includes:</h3><ul><li>CIRCL OSINT Feed</li><li>ThreatFox</li><li>MalwareBazaar</li><li>URLhaus</li></ul><p>These feeds provided access to real-world Indicators of Compromise (IOCs) including:</p><ul><li>Malicious domains</li><li>IP addresses</li><li>Malware hashes</li><li>C2 infrastructure</li><li>Phishing indicators</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MiCSU_T8wNLk-xI6VbfpjQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*m7Wvlm1MQA9iz_FPtUI7iQ.png" /><figcaption>Enabled feeds</figcaption></figure><h3>IOC Collection &amp; Analysis</h3><p>The investigation focused on the following MISP events:</p><ul><li>Event 696</li><li>Event 1470</li><li>Event 2305</li></ul><p>From these events, several indicators were collected.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*J-SefINmmnturxZEtVIMjg.png" /><figcaption>Global search Events Page</figcaption></figure><h3>Domains Identified</h3><ul><li>bsnowcommunications.com</li><li>zoomconference.app</li><li>princess-mens.click</li><li>accounts-google.eu</li><li>authentification-request.top</li><li>security.flyaergyaurd.com</li><li>gebraud.com</li><li>mailmaster.store</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QPqTL8YVV07xD3EiGpkG9w.png" /><figcaption>page showing domain address</figcaption></figure><h3>Malicious IP Addresses</h3><ul><li>167.17.188.244</li><li>91.149.253.134</li><li>91.149.253.99</li><li>89.46.102.43</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Pi85xZVk9pcjGpeQRqs2Hg.png" /><figcaption>page showing IPaddress</figcaption></figure><h3>SHA256 File Hashes</h3><ul><li>e8d0943042e34a37ae8d79aeb4f9a2fa07b4a37955af2b0cc0e232b79c2e72f3</li><li>19bcf7ca3df4e54034b57ca924c9d9d178f4b0b8c2071a350e310dd645cd2b3</li><li>3324550964ec376e74155665765b1492ae1e3bdeb35d57f18ad9aaca64d50a4</li><li>974f6ceebeb889bd97e6641100dddf823376561ddde9e4749f3ea3d77f63a8f9</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BA5e7PAGHTh4xD0LWKRhBQ.png" /><figcaption>page showing SHA256 address</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*O98ml4UjrAFrILnxobW5uw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*L8Dy8hrydyvBu8dWSyak9Q.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*g42yU2JwF7Ms70XuWvdYdA.png" /><figcaption>Event pages</figcaption></figure><h3>Infrastructure Analysis</h3><p>The collected indicators revealed several forms of malicious infrastructure.</p><h3>1. Phishing Infrastructure</h3><p>The domains imitated:</p><ul><li>Authentication services</li><li>Conference platforms</li><li>Email providers</li></ul><p>This strongly suggested credential harvesting operations.</p><h3>2. Command &amp; Control (C2) Servers</h3><p>Several IP addresses were associated with:</p><ul><li>Cobalt Strike activity</li><li>Malware communications</li><li>Remote command execution</li></ul><h3>3. Malware Delivery Infrastructure</h3><p>ThreatFox indicators revealed payload delivery systems linked to malware distribution campaigns.</p><h3>4. Remote Access Trojans (RATs)</h3><p>The investigation identified references to:</p><ul><li>PhantomCaptcha</li><li>Multi-stage WebSocket RAT</li></ul><h3>Threat Actor Profile — Callisto Group</h3><h4>Known Aliases</h4><ul><li>Callisto Group</li><li>Star Blizzard</li><li>SEABORGIUM</li><li>COLDRIVER</li><li>TA446</li></ul><h3>Suspected Origin</h3><ul><li>Russia</li></ul><h3>Motivation</h3><p>The group is widely associated with:</p><ul><li>Cyber espionage</li><li>Intelligence collection</li><li>Credential theft</li><li>Information operations</li></ul><h3>Common Targets</h3><ul><li>Government agencies</li><li>NATO countries</li><li>Journalists</li><li>NGOs</li><li>Research institutions</li><li>Critical infrastructure organizations</li></ul><h3>Tactics, Techniques &amp; Procedures (TTPs)</h3><ul><li>Spear phishing</li><li>Credential harvesting</li><li>Fake login portals</li><li>Malware deployment</li><li>Command &amp; Control infrastructure</li><li>Social engineering</li></ul><h3>Tools &amp; Malware Observed</h3><ul><li>Cobalt Strike</li><li>PhantomCaptcha</li><li>WebSocket RAT</li><li>Credential phishing kits</li></ul><h3>Key Lessons Learned</h3><p>This project provided hands-on experience in:</p><ul><li>Threat intelligence operations</li><li>IOC analysis</li><li>MISP administration</li><li>Docker-based deployments</li><li>Threat correlation</li><li>Infrastructure analysis</li></ul><p>It also demonstrated how modern threat actors reuse infrastructure and evolve phishing campaigns to target organizations globally.</p><h3>Recommendations for Organizations</h3><h4>Defensive Recommendations</h4><ul><li>Enable Multi-Factor Authentication (MFA)</li><li>Monitor DNS and outbound traffic</li><li>Block known malicious domains and IPs</li><li>Continuously update threat intelligence feeds</li><li>Conduct phishing awareness training</li><li>Deploy email filtering and sandboxing</li></ul><h3>Conclusion</h3><p>Deploying and using MISP provided valuable practical insight into modern threat intelligence workflows.</p><p>By leveraging real-world intelligence feeds and IOC correlations, it became possible to build a clearer picture of the Callisto Group’s operational patterns and infrastructure.</p><p>This project reinforced the importance of threat intelligence sharing, proactive monitoring, and collaborative defense strategies in modern cybersecurity operations.</p><h3>About Me</h3><p>I am Izunna Madu, passionate about:</p><ul><li>Cybersecurity</li><li>Threat Intelligence</li><li>Governance, Risk &amp; Compliance (GRC)</li><li>Network Security</li><li>SOC Operations</li><li>Threat Hunting</li></ul><p>Feel free to connect with me on LinkedIn (link in my bio) and follow my cybersecurity journey.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=36b0af3a83b7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Deploying a Full MISP Threat Intelligence Platform with Docker: A Practical Guide & Troubleshooting…]]></title>
            <link>https://medium.com/@mcnelson050/deploying-a-full-misp-threat-intelligence-platform-with-docker-a-practical-guide-troubleshooting-4dc2d660d062?source=rss-2c04964ac50f------2</link>
            <guid isPermaLink="false">https://medium.com/p/4dc2d660d062</guid>
            <category><![CDATA[security-operation-center]]></category>
            <category><![CDATA[threat-intelligence]]></category>
            <category><![CDATA[cyberattack]]></category>
            <category><![CDATA[information-security]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[Izunna Madu]]></dc:creator>
            <pubDate>Mon, 04 May 2026 08:01:04 GMT</pubDate>
            <atom:updated>2026-05-04T08:01:04.382Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kqh4Z-qHcxqynuujpETNQg.png" /><figcaption>MISP Threat Intelligence Platform Dashboard (Local Deployment)</figcaption></figure><h3>Deploying a Full MISP Threat Intelligence Platform with Docker: A Practical Guide &amp; Troubleshooting Walkthrough</h3><h3>Introduction</h3><p>In today’s cybersecurity landscape, threat intelligence is no longer optional, it is essential. One of the most powerful open-source platforms for threat intelligence sharing is <strong>MISP (Malware Information Sharing Platform)</strong>.</p><p>In this article, I walk through my hands-on experience deploying a full MISP environment using Docker, including the real-world challenges I encountered and how I resolved them.</p><p><strong>This guide is designed for:</strong></p><ul><li>Cybersecurity beginners</li><li>SOC analysts</li><li>Threat intelligence enthusiasts</li><li>Anyone building a home lab</li></ul><h3>Why MISP?</h3><p>MISP enables organizations to:</p><ul><li>Share threat intelligence indicators (IOCs)</li><li>Collaborate across teams and organizations</li><li>Automate threat analysis and enrichment</li></ul><p>It is widely used in:</p><ul><li>Security Operations Centers (SOC)</li><li>Incident response teams</li><li>Threat intelligence platforms</li></ul><h3>Environment Setup</h3><p>I deployed MISP using Docker on a Linux environment (Kali Linux).</p><h3>Prerequisites:</h3><ul><li>Docker &amp; Docker Compose installed</li><li>Stable internet connection</li><li>Minimum 4GB RAM (8GB recommended)</li></ul><h3>Deployment Process</h3><h3>Step 1: Clone the Repository</h3><pre>git clone https://github.com/MISP/misp-docker.git<br>cd misp-docker</pre><p>Step 2: Deploy Containers</p><pre>sudo docker compose down -v<br>sudo docker compose pull<br>sudo docker compose up -d</pre><p>At this point, Docker begins pulling and spinning up multiple containers.</p><h3>Understanding the Architecture</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6EyxGStEXjpeGEnMMr221Q.png" /><figcaption>High-level architecture of MISP deployed using Docker containers</figcaption></figure><p>The deployment consists of multiple services:</p><ul><li><strong>MISP Core</strong> → Main application</li><li><strong>MariaDB</strong> → Database</li><li><strong>Redis</strong> → Caching</li><li><strong>MISP Modules</strong> → Enrichment &amp; integrations</li><li><strong>SMTP Server</strong> → Email functionality</li></ul><h3>Challenge 1: Docker Permission Denied</h3><h3>Error:</h3><pre>permission denied while trying to connect to the docker API</pre><h3>Root Cause:</h3><p>The current user was not part of the Docker group.</p><h3>Fix:</h3><pre>sudo usermod -aG docker $USER<br>newgrp docker</pre><p>This is a very common issue in real-world deployments.</p><h3>Challenge 2: Unhealthy MISP Modules Container</h3><h3>Error:</h3><pre>dependency failed to start: misp-modules-1 is unhealthy</pre><h3>Root Cause:</h3><ul><li>Permission issues</li><li>Containers not fully initialized</li></ul><h3>Fix:</h3><pre>docker compose down -v<br>docker compose pull<br>docker compose up -d</pre><p>After resolving permissions, the containers started correctly.</p><h3>Challenge 3: Docker Logs Not Accessible</h3><h3>Error:</h3><pre>docker logs &lt;container&gt;<br>permission denied</pre><h3>Fix:</h3><p>Same as above — ensuring Docker group access.</p><h3>Important Observation: Environment Variable Warnings</h3><p>During deployment, multiple warnings appeared:</p><pre>VARIABLE is not set. Defaulting to a blank string</pre><h3>Insight:</h3><p>These are <strong>optional configurations</strong>, including:</p><ul><li>LDAP authentication</li><li>SSO (OIDC)</li><li>Email services</li><li>Cloud storage (S3)</li></ul><p>For a basic lab setup, they can be safely ignored.</p><h3>Final Deployment Status</h3><p>After troubleshooting, all services became healthy:</p><ul><li>Database → Healthy</li><li>Redis → Healthy</li><li>MISP Modules → Healthy</li><li>Mail → Running</li><li>MISP Core → Started</li></ul><h3>Accessing the Platform</h3><p>Open your browser:</p><h3>Default Credentials:</h3><ul><li>Username: admin@admin.test</li><li>Password: admin</li></ul><pre>https://localhost<br></pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9BxGaKJqYhcGRvGDdVuRDQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aVDMl8q7T4mJtJCVwxLq-A.png" /><figcaption>MISP login interface accessed via localhost</figcaption></figure><h3>Key Lessons Learned</h3><p>This deployment highlighted several important real-world skills:</p><ul><li>Debugging containerized environments</li><li>Understanding service dependencies</li><li>Managing Linux permissions</li><li>Interpreting Docker logs effectively</li></ul><h3>Conclusion</h3><p>Deploying MISP is more than just running containers — it is an exercise in <strong>troubleshooting, system thinking, and persistence</strong>.</p><p>With this setup, you now have a fully functional threat intelligence platform that can be extended with:</p><ul><li>Threat feeds</li><li>SIEM integrations</li><li>Automated analysis tools</li></ul><h3>Final Thoughts</h3><p>If you’re serious about cybersecurity, building and troubleshooting environments like this is what sets you apart.</p><p>End.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4dc2d660d062" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Breaking into Metasploitable2: A Hands-On Penetration Testing Lab]]></title>
            <link>https://medium.com/@mcnelson050/breaking-into-metasploitable2-a-hands-on-penetration-testing-lab-8f31168c017a?source=rss-2c04964ac50f------2</link>
            <guid isPermaLink="false">https://medium.com/p/8f31168c017a</guid>
            <category><![CDATA[threat-intelligence]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[soc-analyst]]></category>
            <category><![CDATA[penetration-testing]]></category>
            <dc:creator><![CDATA[Izunna Madu]]></dc:creator>
            <pubDate>Wed, 11 Mar 2026 08:01:00 GMT</pubDate>
            <atom:updated>2026-03-11T08:01:00.754Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sAOPyWbmAV4M2sTGpRzilA.png" /><figcaption>Breaking into Metasploitable2: A Hands-On Penetration Testing Lab</figcaption></figure><p>Understanding how attackers exploit systems is a key part of becoming a cybersecurity professional. To develop practical skills, I conducted a penetration test against the intentionally vulnerable system Metasploitable 2 using Kali Linux and the Metasploit Framework.</p><p>The goal of this lab was to simulate the workflow of a real penetration test:</p><p>Reconnaissance → Enumeration → Exploitation → Post-Exploitation → Reporting.</p><h3>Lab Overview</h3><p><strong>Target System:</strong> Metasploitable 2<br> <strong>Target IP:</strong> 10.0.4.5<br> <strong>Assessment Type:</strong> Authorized lab penetration test<br> <strong>Environment:</strong> Controlled virtual lab</p><p>The system intentionally contains vulnerable services used for cybersecurity training.</p><p>During the assessment, I identified <strong>multiple critical vulnerabilities leading to full system compromise</strong>.</p><h3>1. Reconnaissance and Enumeration</h3><p>The first step in the assessment was discovering open ports and services.</p><p>I used the network scanner <strong>Nmap</strong> to identify running services.</p><p>Example scan command: nmap -sV -A 10.0.4.5</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/668/1*TgsUufPeHrFV9Qg9-SkoDQ.png" /><figcaption>Exposed services</figcaption></figure><p>Screenshot: Nmap Scan Output Showing Open Ports</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/637/1*l5-sfBcyPzvi1TjoKp-ZFQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/633/1*ws_dQgDopl4aPLXyG6GqTA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/648/1*viYTRSLD80SRSADz-wuFdg.png" /><figcaption>Nmap Scan Output Showing Open Ports</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/636/1*Z_IKo-cZbsMhFKRb9WTeLQ.png" /><figcaption>Nmap Scan Output Showing Open Ports</figcaption></figure><h3>2. Vulnerability Identification</h3><p>After enumeration, vulnerable services were analyzed and prioritized.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/757/1*qb9SdE_-xbXA3xMzFJtbeg.png" /><figcaption>Vulnerability Detection or Exploit Search Results</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/635/1*5d--VP_rmnaBheekbAIrkw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/625/1*hwZWNguk4xVkc1ksMh7VQA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/634/1*hY0yCwtvSh0FM6EZqj0v2w.png" /><figcaption><strong>Screenshot: Vulnerability Detection or Exploit Search Results</strong></figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/641/1*bN0_nSlc9okWGKsTuCzmYA.png" /><figcaption><strong>Screenshot: Vulnerability Detection or Exploit Search Results</strong></figcaption></figure><h3><strong>3. Exploitation Phase</strong></h3><p>Using <strong>Metasploit Framework</strong>, I validated each vulnerability by executing exploit modules.</p><h3>Exploit 1 — VSFTPD Backdoor (Port 21)</h3><p>Exploit module:</p><pre>exploit/unix/ftp/vsftpd_234_backdoor</pre><p>This vulnerability triggers a backdoor shell that provides <strong>root access</strong> to the system.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/635/1*D0cFTJrv_Mc_uMOrH6KoGg.png" /><figcaption>Screenshot: VSFTPD Exploit Execution</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/632/1*iYGsbP6EYpvRJiFBalORwA.png" /><figcaption>Screenshot: Successful Shell Session</figcaption></figure><h3>Exploit 2 — Samba Username Map Script (Port 139)</h3><p>Exploit module:</p><pre>exploit/multi/samba/usermap_script</pre><p>This exploit allowed <strong>remote command execution</strong> on the system.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/643/1*FNkyx8DClHsIq5hjhk_uww.png" /><figcaption>Screenshot: Samba Exploit Execution</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/646/1*DsxCvtjdl5cvFbd_hPGnjg.png" /><figcaption>Screenshot: Meterpreter Session Established</figcaption></figure><h3><strong>Exploit 3 — Apache Tomcat Manager (Port 8180)</strong></h3><p>Exploit module:</p><pre>exploit/multi/http/tomcat_mgr_upload</pre><p>This vulnerability allowed the upload of a malicious <strong>WAR payload</strong>, which resulted in a remote shell.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/638/1*ZDYxpYsmFnvKGAVhXv11Tw.png" /><figcaption>Screenshot: Tomcat Manager Login</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*e0tv2GWfISWN66eoF5hhEw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nEIMuUS2QonvFaKNgo-uVw.png" /><figcaption>Screenshot: WAR Payload Upload</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/644/1*Z9FMz8ounQdKo3Uf8Yea2w.png" /><figcaption>Screenshot: Shell Access</figcaption></figure><h3><strong>Exploit 4 — MySQL Weak Credential Access (Port 3306)</strong></h3><p>Using the MySQL client, I attempted authentication to the database.</p><pre>mysql -h 10.0.4.5 -u root -p --ssl=0</pre><p>This demonstrated that the database could be accessed using weak credentials.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/653/1*zRuzVabyolQ0VIcztRTkdw.png" /><figcaption>Screenshot: MySQL Login</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/634/1*UuOUAdu4gU6rvIP4sbK6_A.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/632/1*PEf2ZQsZCW01YWABd3xoOQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/650/1*p51DHUfxv8XuAnz1xBIoSQ.png" /><figcaption>Screenshot: Database Enumeration</figcaption></figure><h3>4. Post-Exploitation</h3><p>Once access was obtained, system enumeration was performed.</p><p>Commands executed:</p><pre>whoami<br>hostname<br>ifconfig<br>uname -a<br>netstat -an<br>cat /etc/passwd</pre><p>These commands revealed:</p><ul><li>Root privileges</li><li>Kernel version</li><li>Active network connections</li><li>Local user accounts</li></ul><p><strong>Screenshot</strong>: whoami</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/635/1*D0cFTJrv_Mc_uMOrH6KoGg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/643/1*FNkyx8DClHsIq5hjhk_uww.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/641/1*PcdNHJ6wiEkbJb9c1Yzj-Q.png" /><figcaption>Screenshot: whoami</figcaption></figure><p><strong>Screenshot</strong>: hostname</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/606/1*aU64ApiDU_00ILwsXeaOOA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/643/1*BokZ_zVgvsP4n9xEy6laaA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/641/1*MQ42EXOYeM9dHGJCDTrCtg.png" /><figcaption>Screenshot: hostname</figcaption></figure><p><strong>Screenshot</strong>: ifconfig / ip a</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/632/1*iYGsbP6EYpvRJiFBalORwA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/644/1*EXBKbG5gSmHtTykZmIusKQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/641/1*MQ42EXOYeM9dHGJCDTrCtg.png" /><figcaption>Screenshot: ifconfig / ip a</figcaption></figure><p><strong>Screenshot</strong>: uname -a</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/641/1*4PCkKtPgX0ctHKDnzWXuqg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/632/1*S6W7KmRWPWk2weYOREXg2w.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/597/1*Q7GETD9BoVLeZ4Jh1bu1gA.png" /><figcaption><strong>Screenshot</strong>: uname -a</figcaption></figure><p><strong>Screenshot</strong>: netstat -an</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/602/1*5tE52FasbvVhVor8plLlnw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/610/1*PuSv0Nix8xtzGud6Z7nOtg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/611/1*mm9cz41AKQKpP3o34pmh6g.png" /><figcaption><strong>Screenshot</strong>: netstat -an</figcaption></figure><p><strong>Screenshot</strong>: /etc/passwd output</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/553/1*T5jLFf7EebJ-dNOABj1bZQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/590/1*x1G8QSwpbE4yfW5LXD9OyA.png" /><figcaption><strong>Screenshot</strong>: /etc/passwd output</figcaption></figure><h3>5. Security Recommendations</h3><p>To mitigate these vulnerabilities, the following actions are recommended:</p><h3>vsftpd</h3><ul><li>Upgrade to latest version</li><li>Replace FTP with SFTP</li><li>Restrict port 21 access</li></ul><h3>Samba</h3><ul><li>Upgrade to patched version</li><li>Disable vulnerable usermap functionality</li></ul><h3>Tomcat</h3><ul><li>Remove default credentials</li><li>Restrict Manager interface access</li></ul><h3>MySQL</h3><ul><li>Enforce strong password policies</li><li>Disable remote root login</li></ul><h3>Final Thoughts</h3><p>This lab demonstrated how <strong>misconfigured services and outdated software can lead to complete system compromise</strong>.</p><p>Practicing on systems like <strong>Metasploitable 2</strong> provides valuable experience with:</p><ul><li>vulnerability discovery</li><li>exploitation techniques</li><li>post-exploitation analysis</li><li>professional reporting</li></ul><h4>The End</h4><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8f31168c017a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[️ Building and Testing a SOC Lab: My SoluTech Network Security Capstone]]></title>
            <link>https://medium.com/@mcnelson050/%EF%B8%8F-building-and-testing-a-soc-lab-my-solutech-network-security-capstone-cd0df307a4f9?source=rss-2c04964ac50f------2</link>
            <guid isPermaLink="false">https://medium.com/p/cd0df307a4f9</guid>
            <category><![CDATA[blue-team]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[red-team]]></category>
            <category><![CDATA[penetration-testing]]></category>
            <category><![CDATA[security-operation-center]]></category>
            <dc:creator><![CDATA[Izunna Madu]]></dc:creator>
            <pubDate>Mon, 02 Feb 2026 14:43:57 GMT</pubDate>
            <atom:updated>2026-02-02T14:43:57.515Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>By Nelson Madu</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qWtls3pMppROeUOeABPEfQ.png" /></figure><p>Cybersecurity isn’t truly understood from slides — it’s understood from logs, alerts, failed attacks, and the moment you realize your firewall just saved a system.</p><p>For this project, I designed and tested a <strong>mini Security Operations Center (SOC) environment</strong> for a fictional company called <strong>SoluTech</strong>. The goal was simple:</p><p><strong><em>Simulate real cyberattacks, detect them using SIEM, and respond like a real SOC analyst.</em></strong></p><p>This project combined <strong>offensive security (attacking)</strong> and <strong>defensive security (monitoring and response)</strong> exactly how modern security teams operate.</p><h3>Project Overview: SoluTech Network Architecture</h3><p>SoluTech is modeled as a <strong>mid-sized tech consulting company</strong> with internal systems, servers, and a perimeter firewall. I built a lab environment that included:</p><ul><li><strong>pfSense Firewall</strong> — Network traffic control &amp; segmentation</li><li><strong>Wazuh SIEM</strong> — Security monitoring and alerting</li><li><strong>Ubuntu Server</strong> — Linux target machine</li><li><strong>Windows 10 Machine</strong> — Windows target system</li><li><strong>Kali Linux</strong> — Attacker machine used for simulations</li></ul><p>The architecture was designed to reflect a <strong>real enterprise network</strong>, including internal networks and a DMZ.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/864/1*y_j60uWqoGMfXA627Q6dZA.png" /><figcaption>Flow Diagram Showing SoluTech Network Structure</figcaption></figure><h3>SOC Incident Report</h3><h3>1 Executive Summary</h3><p>To test the effectiveness of the SOC, I launched <strong>controlled cyberattacks</strong> from a Kali Linux machine. These included:</p><ul><li>Password brute-force attempts</li><li>Port scanning</li><li>Web vulnerability scanning</li><li>Directory enumeration</li></ul><p>The SOC, powered by <strong>Wazuh SIEM</strong>, successfully detected:</p><ul><li>Repeated failed login attempts</li><li>Suspicious internal traffic</li><li>Brute-force behavior patterns</li></ul><p>Using <strong>pfSense firewall logs</strong>, I confirmed that malicious traffic was identified and blocked.</p><p>This exercise demonstrated the importance of:</p><p>✔ Continuous monitoring<br> ✔ Network segmentation<br> ✔ Fast incident response<br> ✔ Proper SOC documentation</p><h3>2 Attack Simulation Summary</h3><p>Here’s what the “attacker” (me on Kali Linux) did:</p><h3>Port Scanning — Reconnaissance Phase</h3><p>I used <strong>Nmap</strong> to discover open ports and running services on SoluTech machines.</p><p><strong>Goal:</strong> Find entry points.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rEbefkJvnu1PiRKCzcw89w.png" /><figcaption>Nmap scan results showing open SSH, FTP, and HTTP ports</figcaption></figure><h3>Brute-Force Attacks — Credential Attacks</h3><p>Using <strong>Hydra</strong>, I attempted password guessing on:</p><ul><li>SSH services</li><li>FTP services</li><li>HTTP services</li></ul><p>This triggered multiple login failures — which were picked up by Wazuh.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/864/1*SXNssf5NUK3k-3Poo7TCVw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/864/1*hN0ecBJ5zVbyU7ZziyVQCg.png" /><figcaption>Hydra brute-force attempt on FTP</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/864/1*oudWstKIrhqFWz_asZZSjw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/864/1*VsbHE-G3O5-922SqHuDS-w.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*55MDM7cOKc7mk52krb5m0A.png" /><figcaption>Hydra brute-force attempt on SSH</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/864/1*JO5S-8AvRFsXlhpJ_JbcdQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/864/1*KGzMJ6dR0RH_DHx6lUZSLQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/864/1*xvqQH2P3PdmopwMPFxYplg.png" /><figcaption>Hydra brute-force attempt on HTTP</figcaption></figure><h3>Web Server Scanning</h3><p>I used:</p><ul><li><strong>Nikto</strong> → To detect web server misconfigurations</li><li><strong>DIRB</strong> → To find hidden directories and files</li></ul><p>This simulates how attackers look for exposed admin panels, backups, or forgotten files.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LVLZnjQTnFaug7Su1YtROg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1ojkTMr-7HLND08pDlzTdQ.png" /><figcaption>Nikto and DIRB scan outputs</figcaption></figure><h3>3 Detection by the SOC (Wazuh in Action)</h3><p>Wazuh SIEM detected and generated alerts for:</p><ul><li>Multiple failed login attempts</li><li>Suspicious authentication behavior</li><li>Log anomalies on both Ubuntu and Windows machines</li></ul><p>The alerts allowed the SOC to trace the source IP back to the Kali attacker system.</p><ul><li>Wazuh alert for Windows failed logins</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ftr-MRfamVU0mlz-X_FrVg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/864/1*RvAzBxIExw4AwC1LU5eg4w.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/864/1*xeavwFMOe3x3vU5AaEGPew.png" /><figcaption>Alert logs for windows 10 Rdp port login</figcaption></figure><ul><li>Wazuh alert for Ubuntu authentication failures</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/864/1*HoseNbgDhzQaagFcq4RGbQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/864/1*DoXwoJM7rRU_d8Ksin5Tqw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/864/1*yEw6_1d--3dxWdFKtdaqWA.png" /><figcaption>Alert logs for ubuntu ftp/ssh port login</figcaption></figure><ul><li>Wazuh dashboard overview</li></ul><h3>4 Firewall Response (pfSense)</h3><p>After confirming malicious behavior, I implemented firewall rules in <strong>pfSense</strong> to block the attacking IP.</p><p>This shows how SOC monitoring and firewall enforcement work together.</p><p><em>pfSense rule blocking suspicious IP</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/839/1*TzrgA_JFNFUOr73cdpGRNQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/865/1*o-8r0fYaE8Tto7DUyRj6fQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/874/1*jvCRI3DY9_KT5sjrwWKX0Q.png" /><figcaption>pfSense rule blocking suspicious IP</figcaption></figure><h3>Attack Commands from Kali Linux</h3><p>I documented:</p><ul><li>FTP brute-force attempts</li><li>SSH brute-force attempts</li><li>Scans against the Windows machine</li></ul><p><strong>Kali terminal showing attack commands and attack successful outputs</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dlpXrPxR71CAQXKrIn2HaA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GS-wy9lLKRnb7Q1qcftX8A.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fofRnk0O97Vaqz5x0qChNg.png" /><figcaption>Kali terminal showing attack commands</figcaption></figure><h3>Wazuh Alerts &amp; Logs</h3><p>The project captured alerts from:</p><ul><li>Windows event logs</li><li>Ubuntu authentication logs</li></ul><p>These logs are critical because they show <strong>endpoint visibility</strong> — a key SOC capability.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/975/1*Tt1NXqfFgmMtXkobi1kjUA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/975/1*tiOrvMAjkrXBgRN7MeSz2g.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/975/1*HN2gVw76jySV3zWXU9uumQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/975/1*h8y0WdbSJP0nYmj-ik73iA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/975/1*h8y0WdbSJP0nYmj-ik73iA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/975/1*dYoPEOeyEzFO3YUZzX-Uag.png" /><figcaption>Windows Wazuh alert logs/Ubuntu Wazuh alert logs</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/975/1*9Q_x2JntimUXvDv3YFTC4Q.png" /><figcaption>Wazuh dashboard panels</figcaption></figure><h3>pfSense Security Rules</h3><p>I created stronger firewall rules to reduce exposure and stop repeat attacks.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4aicF89Vf3oWgZcY673h2A.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mRWlZxO1hKKIbN6EOhPdrQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*doxtcU1THMT_YkeTk0gk9Q.png" /><figcaption><em>custom pfSense firewall rules</em></figcaption></figure><h3>Lessons Learned: Attacker vs Defender Mindset</h3><p>One of the most powerful parts of this project was understanding both sides.</p><h3>What I Learned as an Attacker</h3><p>Attackers think like intruders:</p><ul><li>They look for open ports</li><li>They search for weak passwords</li><li>They scan for forgotten services</li><li>They test defenses before fully attacking</li></ul><p>They are patient, strategic, and often automate everything.</p><h3>What I Learned as a Defender (SOC Analyst Perspective)</h3><p>Defending is harder than attacking.</p><p>Attackers need <strong>one mistake</strong>. Defenders must protect <strong>everything</strong>:</p><ul><li>Networks</li><li>Users</li><li>Systems</li><li>Applications</li><li>Logs</li></ul><p>I learned that defenders rely heavily on:</p><ul><li>SIEM tools like <strong>Wazuh</strong></li><li>Firewall logs</li><li>Endpoint monitoring</li><li>Automated alerting</li></ul><p>And most importantly:</p><p><strong><em>Defenders respond with process, not panic.</em></strong></p><p>Investigation → Containment → Recovery → Documentation</p><h3>Challenges Faced</h3><p>Not everything worked smoothly — and that’s where the real learning happened.</p><p><strong>Biggest Challenge:</strong><br> Brute-forcing the Windows 10 machine on the DMZ interface was difficult due to network and configuration issues. Debugging this improved my understanding of:</p><ul><li>Network interfaces</li><li>Firewall filtering</li><li>Service exposure risks</li></ul><p>I also learned how to <strong>simulate attacks safely without breaking ethical or legal boundaries</strong>.</p><h3>Recommendations for Real Organizations</h3><p>Based on this project, here are key takeaways for improving security:</p><p>🔹 Strengthen firewall rules<br> 🔹 Enforce strong password policies<br> 🔹 Monitor logs continuously using SIEM<br> 🔹 Train staff on basic cybersecurity awareness<br> 🔹 Stay updated through security forums and threat intelligence feeds</p><h3>Final Thoughts</h3><p>This capstone proved that cybersecurity is not just about tools — it’s about <strong>visibility, detection, and response</strong>.</p><p>By combining <strong>offensive testing</strong> with <strong>defensive monitoring</strong>, I gained real-world SOC experience that mirrors how modern security teams protect organizations every day.</p><p><em>The best defenders understand how attackers think — and this project brought both worlds together.</em></p><h3>Let’s Connect and Learn Together</h3><p>Have you built your own SOC lab or worked with tools like Wazuh or pfSense? I’d love to hear about your setup and lessons learned. Drop a comment below 👇 and let’s learn from each other.<br> If this helped you, don’t forget to <strong>clap and follow</strong> for more practical security projects.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cd0df307a4f9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Deep Dive: Testing and Expanding Network Segmentation in Fintech]]></title>
            <link>https://medium.com/@mcnelson050/deep-dive-testing-and-expanding-network-segmentation-in-fintech-3c5f244073dd?source=rss-2c04964ac50f------2</link>
            <guid isPermaLink="false">https://medium.com/p/3c5f244073dd</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[network-segmentation]]></category>
            <category><![CDATA[network-engineering]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[career-development]]></category>
            <dc:creator><![CDATA[Izunna Madu]]></dc:creator>
            <pubDate>Sat, 31 Jan 2026 05:08:26 GMT</pubDate>
            <atom:updated>2026-01-31T05:08:26.053Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gMWHa74IV8b-5UOTJoFe0g.jpeg" /></figure><p><strong>Network Segmentation Is Not “Set and Forget” — Test It</strong></p><p>In my last article, I showed how <strong>Bunkers Fintech</strong> used VLANs, inter-VLAN routing, and ACLs in <strong>Cisco Packet Tracer</strong> to protect sensitive systems.</p><p>But here’s the real question:<br>👉 <strong>Does your segmentation still hold when things go wrong?</strong></p><p>Because in real fintech environments, failures, misconfigurations, and compromised endpoints are inevitable.</p><p><strong>Open Packet Tracer — Break Your Own Network</strong></p><p>If you truly want to understand segmentation, don’t just build it. <strong>Stress it.</strong></p><p>Try this in your lab:</p><ul><li>Simulate a compromised HR or Engineering PC and test lateral movement</li><li>Modify an ACL rule slightly and observe what suddenly becomes reachable</li><li>Add a new department VLAN and see how quickly “secure by design” can turn into “wide open”</li></ul><p>You’ll quickly realize that <strong>one misconfigured rule can undo an entire security architecture</strong>.</p><p><strong>Scale Like a Real Fintech</strong></p><p>Now push it further:</p><ul><li>Add a <strong>new department VLAN</strong></li><li>Introduce a <strong>DMZ or guest Wi-Fi VLAN</strong></li><li>Expand server access rules and enforce least privilege again</li></ul><p>This is how real-world networks evolve — and how real incidents are born.</p><p><strong>Why This Matters</strong></p><p>For fintechs, segmentation isn’t about neat diagrams. It’s about:</p><ul><li>Containing breaches</li><li>Limiting blast radius</li><li>Protecting financial and customer data</li></ul><p>For learners, this lab mindset builds <strong>real cybersecurity intuition</strong>, not just certification knowledge.</p><p><strong>Your Challenge</strong></p><p>If you built the Bunkers Fintech lab:<br>1️⃣ Break it<br>2️⃣ Fix it<br>3️⃣ Improve it</p><p>That loop is where real networking and cybersecurity skills are formed.</p><p>Secure networks aren’t memorized — <strong>they’re tested</strong>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3c5f244073dd" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Network Segmentation Using Cisco Packet Tracer: A Fintech Case Study]]></title>
            <link>https://medium.com/@mcnelson050/network-segmentation-using-cisco-packet-tracer-a-fintech-case-study-a519f5834596?source=rss-2c04964ac50f------2</link>
            <guid isPermaLink="false">https://medium.com/p/a519f5834596</guid>
            <category><![CDATA[cisco-packet-tracer]]></category>
            <category><![CDATA[networking]]></category>
            <category><![CDATA[network-engineering]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[fintech]]></category>
            <dc:creator><![CDATA[Izunna Madu]]></dc:creator>
            <pubDate>Tue, 27 Jan 2026 08:02:45 GMT</pubDate>
            <atom:updated>2026-01-27T08:02:45.926Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pvOAixYcHRHkwJgdqj-6_Q.jpeg" /></figure><p><em>There is no cybersecurity without networking.</em></p><p>One of the fastest ways to truly understand networking is not by memorizing concepts, but by <strong>building networks and watching them work or fail</strong>. Cisco Packet Tracer provides a practical, hands-on environment where real enterprise network designs can be simulated without physical hardware, making it an excellent learning tool for aspiring network engineers and cybersecurity professionals.</p><p>In modern enterprise environments especially within fintech <strong>flat networks are no longer practical or secure</strong>. As organizations scale, the need to separate users, systems, and services becomes critical for maintaining security, performance, and operational control. This is where <strong>network segmentation</strong> becomes indispensable.</p><p>Network segmentation involves dividing a network into smaller, logically isolated segments where traffic is controlled based on business requirements. When properly implemented, segmentation reduces the attack surface, limits lateral movement during security incidents, improves troubleshooting, and enforces least-privilege access.</p><p>This project demonstrates how <strong>VLANs, inter-VLAN routing, and access control lists (ACLs)</strong> can be implemented in Cisco Packet Tracer to design a secure, realistic fintech network.</p><h3>Case Study Overview: Bunkers Fintech</h3><p><strong>Bunkers</strong> is a growing fintech startup that processes sensitive customer and transactional data. The organization operates multiple departments with different access requirements and relies heavily on its internal network for daily operations.</p><h3>Departments and Endpoints</h3><ul><li><strong>Finance Department</strong> — 2 user endpoints</li><li><strong>Human Resources (HR)</strong> — 2 user endpoints</li><li><strong>Engineering Department</strong> — 2 user endpoints</li></ul><h3>Critical Assets</h3><ul><li><strong>Two database servers</strong> storing customer and transaction data</li></ul><p>In a flat network, any compromised endpoint could potentially access critical systems across the organization. For a fintech company, this represents a serious security risk.</p><h3>Problem Statement</h3><p><strong>How can Bunkers securely segment its internal network to protect critical database systems while maintaining required connectivity between departments?</strong></p><h3>Solution Approach</h3><p>The network was designed using Cisco Packet Tracer with the following security principles:</p><ul><li>Logical separation using VLANs</li><li>Controlled inter-VLAN routing (router-on-a-stick)</li><li>Fine-grained access control using extended ACLs</li><li>Dedicated VLANs for servers and wireless access</li></ul><p>This approach mirrors real-world enterprise and fintech network designs, where segmentation is used to reduce risk while maintaining operational efficiency.</p><h3>Network Design and VLAN Architecture</h3><p>Each department was assigned a dedicated VLAN to enforce isolation at Layer 2.</p><p><strong>Network Design Topology</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jANAn-jKbX0o2059uPgICQ.png" /></figure><h4>VLAN Architecture</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/672/1*nalMz-wBOIOcUCX2U0FsnQ.png" /><figcaption>This structure ensures that devices in one department cannot communicate with others unless explicitly permitted.</figcaption></figure><h3>Technical Implementation Overview</h3><h4>Switch Configuration</h4><p>Access switches were configured with static access ports to prevent VLAN hopping and ensure predictable traffic flow.</p><pre>interface fa0/1<br> switchport mode access<br> switchport access vlan 10</pre><p>Trunk links were configured using IEEE 802.1Q to carry multiple VLANs between switches and the router.</p><pre>interface gig0/1<br> switchport mode trunk</pre><h3>Inter-VLAN Routing (Router-on-a-Stick)</h3><p>A single router was used to enable controlled communication between VLANs. Each VLAN was mapped to a dedicated router sub-interface acting as the default gateway.</p><pre>interface gig0/0.10<br> encapsulation dot1Q 10<br> ip address 192.168.10.1 255.255.255.0</pre><p>This design enables centralized routing and policy enforcement while maintaining VLAN isolation.</p><h3>Server Segmentation and Access Control</h3><p>The database servers were placed in a dedicated <strong>Server VLAN (VLAN 40)</strong>. Access was restricted using extended ACLs.</p><pre>access-list 100 permit ip 192.168.10.0 0.0.0.255 192.168.40.0 0.0.0.255<br>access-list 100 deny ip 192.168.20.0 0.0.0.255 192.168.40.0 0.0.0.255<br>access-list 100 deny ip 192.168.30.0 0.0.0.255 192.168.40.0 0.0.0.255<br>access-list 100 permit ip any any</pre><h4>ACL Policy Logic</h4><p>The access control policy enforced the following logic:</p><ul><li><strong>Finance → Servers</strong> ✅ Allowed</li><li><strong>HR → Servers</strong> ❌ Denied</li><li><strong>Engineering → Servers</strong> ❌ Denied</li></ul><p>This ensures that only authorized business units can interact with sensitive financial data, aligning with the principle of least privilege.</p><h4>Validation and Testing</h4><p>Connectivity tests were performed to verify segmentation enforcement and ACL functionality.</p><h4>Test Results</h4><ul><li><strong>Finance PC → Database Server</strong> ✅</li><li><strong>HR PC → Database Server</strong> ❌</li><li><strong>Engineering PC → Database Server</strong> ❌</li><li><strong>Unauthorized inter-VLAN traffic</strong> ❌</li></ul><p>These results confirm that segmentation and access control policies are functioning exactly as designed.</p><h3>Wireless Network Segmentation</h3><p>Wireless traffic was isolated in <strong>VLAN 50</strong>, preventing unmanaged or mobile devices from directly accessing sensitive internal networks. This supports insider-threat mitigation and improves traffic visibility.</p><h3>Why Network Segmentation Matters in Fintech</h3><p>In fintech environments, a single compromised endpoint can result in significant financial and reputational damage. Network segmentation acts as a <strong>containment mechanism</strong>, preventing attackers from moving laterally across systems.</p><p>Beyond security, segmentation supports:</p><ul><li>Regulatory and compliance requirements</li><li>Improved monitoring and visibility</li><li>Secure and scalable infrastructure growth</li></ul><p>For SOC analysts, threat intelligence professionals, and network engineers, understanding segmented network design provides critical context for incident response and risk assessment.</p><h3>Full CLI Configuration</h3><h4>Router Configuration</h4><pre>enable<br>configure terminal</pre><pre>interface gig0/0<br> no shutdown</pre><pre>interface gig0/0.10<br> encapsulation dot1Q 10<br> ip address 192.168.10.1 255.255.255.0</pre><pre>interface gig0/0.20<br> encapsulation dot1Q 20<br> ip address 192.168.20.1 255.255.255.0</pre><pre>interface gig0/0.30<br> encapsulation dot1Q 30<br> ip address 192.168.30.1 255.255.255.0</pre><pre>interface gig0/0.40<br> encapsulation dot1Q 40<br> ip address 192.168.40.1 255.255.255.0<br> ip access-group 100 in</pre><pre>interface gig0/0.50<br> encapsulation dot1Q 50<br> ip address 192.168.50.1 255.255.255.0<br>end<br>write memory</pre><h3>Example Access Switch Configuration</h3><pre>enable<br>configure terminal</pre><pre>vlan 10<br> name FINANCE<br>vlan 20<br> name HR<br>vlan 30<br> name ENGINEERING<br>vlan 40<br> name SERVERS<br>vlan 50<br> name WIRELESS</pre><pre>interface range fa0/1 - 2<br> switchport mode access<br> switchport access vlan 10</pre><pre>interface gig0/1<br> switchport mode trunk<br>end<br>write memory</pre><h3>ACL Configuration</h3><pre>access-list 100 permit ip 192.168.10.0 0.0.0.255 192.168.40.0 0.0.0.255<br>access-list 100 deny ip 192.168.20.0 0.0.0.255 192.168.40.0 0.0.0.255<br>access-list 100 deny ip 192.168.30.0 0.0.0.255 192.168.40.0 0.0.0.255<br>access-list 100 permit ip any any</pre><h3>Final Thoughts</h3><p>This project demonstrates how <strong>enterprise-grade network segmentation</strong> can be implemented using Cisco Packet Tracer in a fintech scenario. By combining VLAN isolation, inter-VLAN routing, and ACL enforcement, sensitive systems are protected without disrupting business operations.</p><p>The implementation highlights how proper segmentation:</p><ul><li>Reduces the attack surface</li><li>Limits lateral movement</li><li>Protects critical financial assets</li><li>Strengthens organizational security posture</li></ul><p>Secure network architecture is not optional — it is the <strong>foundation of effective cybersecurity</strong>. For anyone pursuing a career in networking or cybersecurity, building and understanding segmented networks is a skill that pays long-term dividends.</p><p><strong>Enjoyed this case-study?</strong><br><em>If you found this case study helpful, consider:</em><br>=&gt; <strong>Clapping </strong>to support the article<br>=&gt; <strong>Saving </strong>it for your networking/cybersecurity study workflow<br>=&gt; <strong>Sharing </strong>it with someone learning Cisco Packet Tracer<br>=&gt; <strong>Following </strong>me for more hands‑on labs, cybersecurity breakdowns, and real‑world network engineering projects.</p><p><strong><em>Your engagement helps this content reach more learners and future engineers cheers.</em></strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a519f5834596" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>