<?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 Mary Isioma O on Medium]]></title>
        <description><![CDATA[Stories by Mary Isioma O on Medium]]></description>
        <link>https://medium.com/@isiomamary?source=rss-21e7e8858664------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*OeMiv0PL7HREX_6abdHFWw@2x.jpeg</url>
            <title>Stories by Mary Isioma O on Medium</title>
            <link>https://medium.com/@isiomamary?source=rss-21e7e8858664------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 04:59:53 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@isiomamary/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[Exploiting Port 21 in a Safe Lab Environment (Ethical Hacking with Metasploit)]]></title>
            <link>https://medium.com/@isiomamary/exploiting-port-21-in-a-safe-lab-environment-ethical-hacking-with-metasploit-37b87a285c50?source=rss-21e7e8858664------2</link>
            <guid isPermaLink="false">https://medium.com/p/37b87a285c50</guid>
            <category><![CDATA[ethical-hacking]]></category>
            <category><![CDATA[metasploit]]></category>
            <category><![CDATA[ftp]]></category>
            <category><![CDATA[metasploitable]]></category>
            <category><![CDATA[exploitation]]></category>
            <dc:creator><![CDATA[Mary Isioma O]]></dc:creator>
            <pubDate>Tue, 26 Aug 2025 14:47:14 GMT</pubDate>
            <atom:updated>2025-08-26T14:47:14.749Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*OvmqaJ0XJFG1NRfzFoa9vA.png" /></figure><p>When people think of hacking, they often picture “breaking in” through mysterious backdoors. In reality, many attacks start with something simple: <strong>open ports</strong>. Every service that runs on a system — whether FTP, HTTP, or SSH — is a potential doorway. If those services are outdated or misconfigured, attackers can walk right in.</p><p>When I first launched <strong>Metasploit (msfconsole)</strong>, it felt like entering a hacker’s cockpit. But instead of targeting the real world, I set up a <strong>controlled lab</strong> with Metasploitable2 — a purposely vulnerable machine. My mission? Explore how attackers exploit <strong>port 21 (FTP) </strong>how defenders can stop them.</p><h3>Step 1: Reconnaissance 🔎</h3><p>First, I scanned the target with <strong>Nmap</strong>:</p><pre>nmap -sS -sV -A &lt;target-ip&gt;</pre><p>This revealed services running on Port 21 (FTP); high-value target. <strong>FTP</strong> often exposes outdated servers like vsftpd or ProFTPD.</p><h4>🎯 Exploiting Port 21 (FTP)</h4><p>FTP servers have a history of backdoor vulnerabilities. Using <strong>Metasploit</strong>, I launched an attack:</p><p>Inside msfconsole, the process went like this:</p><pre>msfconsole<br>search ftp_version<br>use 0<br>show options<br>set RHOSTS target IP<br>show options<br>run</pre><p>At this stage, the module attempted exploitation but needed more context. To cross-reference, I used <strong>Searchsploit</strong> in a separate terminal to look up vulnerabilities for the detected FTP version:</p><pre>searchsploit vsftpd</pre><p>This pointed me towards a known <strong>backdoor command execution</strong> flaw. Returning to Metasploit:</p><pre>back<br>search backdoor command execution<br>use 0<br>show options<br>set RHOSTS target ip<br>show options<br>run</pre><h3>🖥️ Result</h3><p>The exploit fired successfully — I gained shell access on the target 🎉</p><p>To confirm privilege:</p><pre>whoami<br>hostname</pre><p>The response showed <strong>root access</strong> — proving the exploit worked inside my lab.</p><h3>Here’s my Final Thoughts 💭</h3><p>Working through the exploitation of FTP in the lab was eye-opening. What looked like a simple service running on Port 21 quickly turned into a full system compromise once an outdated version was identified and exploited.</p><p>The big lesson for me was this: <strong>reconnaissance and research matter just as much as the exploit itself</strong>. By combining Nmap, Metasploit, and Searchsploit, I was able to map the service, test potential modules, cross-reference public exploits, and eventually land a shell with root access.</p><p>But just as important was looking at it through the defender’s lens:</p><ul><li>If FTP isn’t needed, disable it.</li><li>If it is needed, upgrade to <strong>SFTP/FTPS</strong> and keep it patched.</li><li>Limit access with firewalls and strong authentication.</li><li>Monitor for suspicious sessions that could indicate exploitation attempts.</li></ul><p>In the end, Port 21 reminded me that <strong>an open service is an open invitation </strong>and attackers will take the invitation if it’s left unsecured.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=37b87a285c50" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How I Built (and Secured) My First Mini-Network in Cisco Packet Tracer]]></title>
            <link>https://medium.com/@isiomamary/how-i-built-and-secured-my-first-mini-network-in-cisco-packet-tracer-9078ee7d0964?source=rss-21e7e8858664------2</link>
            <guid isPermaLink="false">https://medium.com/p/9078ee7d0964</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[networking]]></category>
            <category><![CDATA[protocol]]></category>
            <category><![CDATA[firewall-security]]></category>
            <category><![CDATA[cisco-packet-tracer]]></category>
            <dc:creator><![CDATA[Mary Isioma O]]></dc:creator>
            <pubDate>Mon, 25 Aug 2025 01:47:30 GMT</pubDate>
            <atom:updated>2025-08-25T03:04:16.296Z</atom:updated>
            <content:encoded><![CDATA[<p>When I first opened <strong>Cisco Packet Tracer</strong>, it felt like staring at a box of Lego for the digital world. Routers, switches, PCs, cables — all waiting to be connected. But I didn’t want to just <em>connect devices</em>, I wanted to understand how they <strong>talk</strong> to each other, and how to make them <strong>secure</strong>.</p><p>So, I gave myself a challenge:<br> — Build a tiny network with a server and a few PCs.<br> — Get them all talking.<br> — Then… throw in a firewall rule to block sneaky traffic.</p><p>Here’s how it went.</p><h3><strong>Step 1: Just a PC and a Server 🖥️ ↔️ 🖥️</strong></h3><p>I started small: one PC and one server, joined with a crossover cable.</p><ul><li>PC: 192.168.0.2</li><li>Server: 192.168.0.1</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bdq1oer877W5MqQROzX4Mw.png" /></figure><p>After assigning IPs, I nervously typed:</p><p><em>ping 192.168.0.1</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/716/1*rBcY5flnuLWTixjL7ggtAQ.png" /></figure><p>🎉 Success! My PC could “see” the server.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/920/1*hDmx8l7SssRiZINRHThTaQ.png" /></figure><p>To double-check, I used Packet Tracer’s Simple PDU tool (basically sending a one-time “hello” packet). The server answered back — connection established!</p><h3><strong>Step 2: Growing the Family 👨‍👩‍👧‍👦</strong></h3><p>Next, I added two more PCs and a switch to create a little LAN.</p><ul><li>PC0: 192.168.0.2</li><li>PC1: 192.168.0.3</li><li>PC2: 192.168.0.4</li><li>Server: 192.168.0.1</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*R1klpzl4vfrTW7gWiIuZtQ.png" /></figure><p>Soon, everyone was chatting away happily. Every PC could ping the server and each other. It was like watching a group chat light up for the first time.</p><h3>Step 3: Adding Security 🔒</h3><p>Now for the fun part. Connectivity is cool, but in the real world, networks get probed all the time. Ever heard of a <strong>ping sweep</strong>? Hackers send pings across a network to see what’s alive.</p><p>So on my server, I enabled the firewall and wrote a simple rule:</p><ul><li>Block ICMP (ping) traffic</li><li>Allow normal IP traffic (like browsing)</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1019/1*FvFZkP8hJek-0rPx1emNoA.png" /></figure><p>The result?</p><p>Pings to the server started failing</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/973/1*ssYDqSb1_QHIgE7L3adRAg.png" /></figure><p>But when I opened the web browser on a PC and typed the server’s IP… the web page loaded fine.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UuOkkVJwlof0Dck3PTsu8Q.png" /></figure><p>Boom. My first taste of <em>security vs usability</em>.</p><h3>What I Learned</h3><ul><li><strong>IP addressing isn’t scary</strong> once you practice — it’s just giving each device its own “phone number.”</li><li><strong>Testing is everything.</strong> Ping, ipconfig, and Packet Tracer’s tools helped me confirm what was happening at each step.</li><li><strong>Security is about balance.</strong> Blocking pings kept reconnaissance out, but allowing web traffic kept services available.</li></ul><h3>Oops Moments 🙃</h3><p>At first, I blocked <em>all</em> traffic by mistake and locked myself out of the server completely. Lesson learned: firewall rules need to be precise. I had to re-order the rules so “allow IP” came after “deny ICMP.”</p><h3>What’s Next 🚀</h3><p>This was just the beginning. If I keep building on this mini-lab, I want to:</p><ul><li>Add VLANs for segmentation (users vs servers).</li><li>Try DHCP so PCs don’t need static IPs.</li><li>Set up NAT and ACLs like a real edge router.</li><li>Experiment with Spanning Tree and EtherChannel to see redundancy in action.</li></ul><h3>Final Thoughts 💭</h3><p>It may look like just a few icons in Packet Tracer, but this tiny lab taught me the foundations of networking <em>and</em> security. I started with a cable, an IP address, and a ping. By the end, I understood how firewalls shape traffic, and how small changes can protect a network without breaking it.</p><p>Not bad for a first time basic networking, right? 😉</p><p>✨ <em>If you’re learning networking or cybersecurity, try this! Build something small, test it, break it, fix it. That’s where the real learning happens.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9078ee7d0964" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>