<?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 Jacob Ferguson on Medium]]></title>
        <description><![CDATA[Stories by Jacob Ferguson on Medium]]></description>
        <link>https://medium.com/@jfergitlife?source=rss-7063327e59dd------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*5_Emcba2qKag_Em2CEO37g.jpeg</url>
            <title>Stories by Jacob Ferguson on Medium</title>
            <link>https://medium.com/@jfergitlife?source=rss-7063327e59dd------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 11:52:55 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@jfergitlife/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[MSP Client Network Deployment Lab Part 1: Network Design and Topology]]></title>
            <link>https://jfergitlife.medium.com/msp-client-network-deployment-lab-part-1-network-design-and-topology-785b6dcda60b?source=rss-7063327e59dd------2</link>
            <guid isPermaLink="false">https://medium.com/p/785b6dcda60b</guid>
            <category><![CDATA[cisco-certifications]]></category>
            <category><![CDATA[cisco-packet-tracer]]></category>
            <category><![CDATA[network-engineering]]></category>
            <category><![CDATA[ccna-training]]></category>
            <dc:creator><![CDATA[Jacob Ferguson]]></dc:creator>
            <pubDate>Tue, 02 Jun 2026 11:01:01 GMT</pubDate>
            <atom:updated>2026-06-02T11:01:01.204Z</atom:updated>
            <content:encoded><![CDATA[<p>Today I started building out my MSP Client Network Deployment Lab as part of my CCNA studies.</p><p>The goal of this project is to simulate how a managed service provider might onboard a new small business client network from scratch. I want this to be more than just a Packet Tracer Lab. I want to document the full process from design, configuration, verification, troubleshooting, and eventually automation.</p><p>For Part 1, I focused only on the network design and topology. No configuration has been completed yet.</p><h4>Project Scenario</h4><p>The client is a small business that needs a segmented and manageable network. The network needs to support corporate users, servers, VoIP phones, printers, guest access, and network management.</p><p>The design includes:</p><p><strong>Internet-Server</strong> — Public test server used later for NAT and internet access testing.</p><p><strong>ISP-Router</strong> — Simulated outside network provider.</p><p><strong>R1</strong> — Edge router for routing, NAT, and inter-VLAN routing.</p><p><strong>SW1</strong> — Core/distribution switch connecting the router, server, printer, and access switch.</p><p><strong>SW2</strong> — Access switch connecting end-user devices.</p><p><strong>Server1</strong> — Internal server representing VLAN 20.</p><p><strong>Printer1</strong> — Office printer representing VLAN 50.</p><p><strong>PC1</strong> and<strong> PC2</strong> — Corporate user test devices representing VLAN 10.</p><p><strong>Phone1</strong> — VoIP phone representing VLAN 30.</p><p><strong>GuestPC1</strong> — Guest client representing VLAN 40.</p><p>The idea is to build this like a real project instead of just randomly configuring commands.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*D8Vx_SC09jHtfl7z-zgneg.png" /><figcaption>Initial Packet Tracer topology for the MSP Client Network Deployment Lab. This design includes a simulated ISP, edge router, core/distribution switch, access switch, internal server, printer, corporate users, VoIP phone, guest client, and public test server for future NAT testing.</figcaption></figure><h4>VLAN Plan</h4><p>For this lab, I created the following VLAN and subnet plan:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fdatawrapper.dwcdn.net%2FpJ4xk%2F1%2F&amp;display_name=Datawrapper&amp;url=https%3A%2F%2Fdatawrapper.dwcdn.net%2FpJ4xk%2F1%2F&amp;image=https%3A%2F%2Fdatawrapper.dwcdn.net%2FpJ4xk%2Fplain-s.png%3Fv%3D1&amp;type=text%2Fhtml&amp;schema=dwcdn" width="600" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/11ac24c4f5a9676d3e2dee78dd3807fe/href">https://medium.com/media/11ac24c4f5a9676d3e2dee78dd3807fe/href</a></iframe><p><strong>Default Gateway Plan</strong></p><p>Each VLAN will eventually need a default gateway. These will be configured later during the inter-VLAN routing section.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fdatawrapper.dwcdn.net%2F3b7y9%2F1%2F&amp;display_name=Datawrapper&amp;url=https%3A%2F%2Fdatawrapper.dwcdn.net%2F3b7y9%2F1%2F&amp;image=https%3A%2F%2Fdatawrapper.dwcdn.net%2F3b7y9%2Fplain-s.png%3Fv%3D1&amp;type=text%2Fhtml&amp;schema=dwcdn" width="600" height="307" frameborder="0" scrolling="no"><a href="https://medium.com/media/64c3232b685f218b28e106a3347b8fa8/href">https://medium.com/media/64c3232b685f218b28e106a3347b8fa8/href</a></iframe><p><strong>Why This Design Matters</strong></p><p>The main goal of this design is segmentation.</p><p>Instead of putting every device into one flat network, each device type has its own VLAN. This makes the network easier to manage and helps reducs unnecessary access between different types of devices.</p><p>For example:</p><ul><li>Corporate users should not be on the same VLAN as guest devices.</li><li>Guest Wi-Fi should not be able to reach internal servers.</li><li>Printers should be separated from user workstations.</li><li>Network management should have its own dedicated VLAN.</li></ul><p>This design gives me a foundation to practice multiple CCNA topics in a realistic way.</p><p><strong>What This Lab Will Eventually Cover</strong></p><p>The Project will be broken down into multiple parts:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fdatawrapper.dwcdn.net%2FKO5zf%2F1%2F&amp;display_name=Datawrapper&amp;url=https%3A%2F%2Fdatawrapper.dwcdn.net%2FKO5zf%2F1%2F&amp;image=https%3A%2F%2Fdatawrapper.dwcdn.net%2FKO5zf%2Fplain-s.png%3Fv%3D1&amp;type=text%2Fhtml&amp;schema=dwcdn" width="600" height="496" frameborder="0" scrolling="no"><a href="https://medium.com/media/480b7d6d9dcde69b537fecc87a433a7b/href">https://medium.com/media/480b7d6d9dcde69b537fecc87a433a7b/href</a></iframe><p>I want to build the network manually first, verify that it works, document the process, and then later automate tasks like configuration backups and show command collection.</p><h4><strong>What I Learned</strong></h4><p>The biggest takeaway from Part 1 is that the design matters before the commands.</p><p>It is easy to jump straight into configuring routers and switches, but having a clear topology, VLAN plan, IP addressing plan, and success criteria makes the lab much easier to build and troubleshoot later.</p><h4>Next Steps</h4><p>The next part of the lab will focus on base device configuration.</p><p>I will configure hostnames, basic security settings, interface descriptions, local user accounts, and SSH access for the routers and switches.</p><h3>Connect With Me</h3><p>I’m currently studying for the CCNA and building hands-on networking labs to strengthen my understanding of routing, switching, segmentation, troubleshooting, and network documentation.</p><p>If you’re also studying networking, working in IT, or building a technical portfolio, feel free to connect with me.</p><p>LinkedIn: <a href="https://www.linkedin.com/in/itlife/">https://www.linkedin.com/in/itlife/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=785b6dcda60b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What Actually Happens When You Type a URL Into Your Browser?]]></title>
            <link>https://cybersecuritywriteups.com/what-actually-happens-when-you-type-a-url-into-your-browser-62dfeeeb0725?source=rss-7063327e59dd------2</link>
            <guid isPermaLink="false">https://medium.com/p/62dfeeeb0725</guid>
            <category><![CDATA[networking]]></category>
            <category><![CDATA[soc-analyst]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[information-technology]]></category>
            <dc:creator><![CDATA[Jacob Ferguson]]></dc:creator>
            <pubDate>Wed, 25 Feb 2026 22:30:05 GMT</pubDate>
            <atom:updated>2026-02-25T22:30:05.652Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mYtGt4tw0-f9l8x7lw1AnQ.jpeg" /></figure><p>Lets say you type <a href="http://www.google.com/">www.google.com</a> into your browser. Most people don’t actually understand what happens, but if you are in the fields of Information Technology or Cybersecurity then this is a fundamental requirement.</p><h3>Step 1: Finding The Address</h3><p>Computers don’t actually understand website names like google.com. What they understand is IP addresses like 142.250.190.78. Could you imaging trying to remember that?</p><p>The browser needs to translate the name into an IP address which is where DNS (Domain Name System) comes in.</p><p>Picture DNS as the Internets phone-book.</p><p>But before DNS, your system checks locally:</p><ul><li>your browser cache</li><li>your operating system cache</li><li>your router or ISP’s cache</li></ul><p>If the IP address is still unknown, now DNS comes into play.</p><h3>DNS Hierarchy</h3><p>Think of DNS like those Matryoshka dolls. DNS works like a chain of responsibility.</p><ol><li>Root Server</li><li>TLD Servers (.com, .org, .net, etc.)</li><li>Authoritative Name Server</li></ol><h4>Root Server</h4><p>Your DNS resolver ask the root server:</p><p>“Where can I find information about .com domains?”</p><p>Since the root server doesn’t know the IP address of your site, it responds:</p><p>“Ask the .com TLD servers.”</p><h4>TLD Server</h4><p>Next, your resolver ask the .com server:</p><p>“Who handles google.com?”</p><p>The TLD server responds with:</p><p>“Go ask the authoritative name server.”</p><p>The TLD server doesn’t know the final IP either, it just knows who owns the domain’s records.</p><h4>Authoritative Name Server</h4><p>At last, your resolver ask the authoritative server:</p><p>“What is the IP address for www.google.com?”</p><p>The authoritative server owns the actual DNS records so it responds with the correct IP address.</p><p>Your browser finally knows where the website lives.</p><h3>Back to the Cache</h3><p>Now that the IP address is found, it gets cached at multiple levels (browser, OS, ISP)</p><p>Each DNS record has something called a TTL (Time to Live), which determines how long it can be stored before it must be refreshed.</p><h3>Step 2: TCP — Opening a Connection</h3><p>Your browser knows the IP address by now. Now its time to open a reliable connection.</p><p>This is done by using TCP (Transmission Control Protocol)</p><p>Before your computer sends data, your computer in the server perform what is called the “three-way handshake:</p><ol><li>Can we talk? (SYN)</li><li>Server replies: “yes, I’m ready.” (SYN-ACK)</li><li>Computer replies: “Great, let’s begin (ACK)</li></ol><p>Once the three-way handshake is established, a communication channel is open.</p><h3>Step 3: HTTPS</h3><p>Look at your URL. Does it start with https? If so, then the browser has established a secure connection using TLS (Transport Layer Security).</p><p>Here is how it works:</p><ul><li>The server sends its security certificate</li><li>Your browser verifies it’s legitimate</li><li>Both sides agree on encryption keys</li></ul><p>The little lock you see on your address bar represents this encrypted connection.</p><h3>Step 4: HTTP Request &amp; Response</h3><p>Now the browser can finally send the actual request: “Please give me the homepage.”</p><p>The server will respond with something along the lines of:</p><ul><li>A status code (200 OK)</li><li>HTML content</li><li>Links to CSS files</li><li>JavaScript files</li><li>Images and other assets</li></ul><p>Next your browser:</p><ul><li>parses the HTML</li><li>Builds the page structure</li><li>Downloads additional resources</li><li>Executes JavaScript</li><li>Applies styles</li><li>Renders everything visually</li></ul><p>And just like that, the website appears.</p><h3>Putting it simple:</h3><ol><li>DNS translates the domain name into an IP address.</li><li>TCP establishes a reliable connection</li><li>HTTPS secures the communication</li><li>HTTP request and receives the webpage.</li><li>The browser renders the content</li></ol><p>I hope you have found this write-up helpful. If this knowledge is new to you, study it and be able to comfortably talk about it. You will thank me later in your job interview.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=62dfeeeb0725" width="1" height="1" alt=""><hr><p><a href="https://cybersecuritywriteups.com/what-actually-happens-when-you-type-a-url-into-your-browser-62dfeeeb0725">What Actually Happens When You Type a URL Into Your Browser?</a> was originally published in <a href="https://cybersecuritywriteups.com/">Cyber Security Write-ups</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why BTL1 is Different..]]></title>
            <link>https://cybersecuritywriteups.com/why-btl1-is-different-951970588309?source=rss-7063327e59dd------2</link>
            <guid isPermaLink="false">https://medium.com/p/951970588309</guid>
            <category><![CDATA[soc-analyst]]></category>
            <category><![CDATA[blue-team]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[certification]]></category>
            <category><![CDATA[incident-response]]></category>
            <dc:creator><![CDATA[Jacob Ferguson]]></dc:creator>
            <pubDate>Thu, 29 Jan 2026 01:40:18 GMT</pubDate>
            <atom:updated>2026-01-29T01:40:18.792Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*u88iAxMGxRzN3POO8hggEA.png" /></figure><p>The Cybersecurity certification space is crowded with exams that reward memorization more than real-world skill. this makes it hard to identify which certifications actually translate to job-ready capability.</p><p>The Blue Team Level 1 (BTL1) certification stood out to me because it prioritizes how defenders think and work over what they can memorize.</p><p>This article breaks down my BTL1 experience, who the certification is best suited for, and what it realistically validates for cybersecurity professionals, IT engineers, and aspiring cyber practitioners.</p><p>If you’re trying to avoid certifications that look good on paper but fail to build real investigation skills, BTL1 deserves a closer look.</p><h4>What the BTL1 Exam Actually Test</h4><p>Unlike traditional multiple-choice cybersecurity, BTL1 evaluates applied defensive skills.</p><p>The exam focuses on your ability to:</p><ul><li>Follow a structured incident response methodology</li><li>Investigate logs, systems, and artifacts effectively</li><li>Correlate evidence across multiple data sources</li><li>Clearly document findings and justify conclusions</li></ul><p>If you have worked through blue team labs, SOC investigations, or real-world incident response scenarios, you will notice the exam feel closer to reality.</p><p>My BTL1 Preparation Strategy (What Actually Worked)</p><p>I saw a lot of people recommend the <strong>TryHackMe SAL1 pathway</strong> as preparation for the BTL1 exam. While it’s a solid learning path, I personally found it to be <strong>more distracting than helpful</strong> for exam-specific preparation.</p><p>BTL1 doesn’t reward broad exposure… it rewards <strong>depth</strong>.</p><p>Instead of spreading my focus across multiple platforms and tools, I narrowed everything down to what actually matters during the exam.</p><p>Repeat after me:</p><p><strong>Splunk. Wireshark. Autopsy.</strong></p><h3>Focus on the Core Blue Team Tools</h3><p>You can practice <strong>Splunk and Wireshark for free</strong>, and that’s where the majority of your effort should go.</p><p>For Wireshark specifically, I highly recommend <strong>Chris Greer’s YouTube channel</strong>:<br> 👉 <a href="https://www.youtube.com/@ChrisGreer">https://www.youtube.com/@ChrisGreer</a></p><p>What makes his content valuable is his <strong>thought process</strong>. Watching how he:</p><ul><li>Approaches a PCAP</li><li>Identifies what <em>doesn’t</em> matter</li><li>Builds hypotheses</li></ul><p>That mental framework translates directly to the BTL1 exam and real SOC work.</p><h3>Why Note-Taking Was the Most Important Part of My BTL1 Preparation</h3><p>Tool familiarity gets you through the labs.<br> Good notes get you through the exam.</p><p>One of the biggest advantages I had going into the BTL1 exam was not how many labs I completed, but how well I documented what I learned while doing them.</p><p>I used <strong>Obsidian</strong> as my primary note-taking system.</p><h3>What I Actually Wrote Down</h3><p>I did not rewrite theory or course content. That is already available in the material and can be re-read at any time.</p><p>Instead, my notes focused on <strong>execution</strong>.</p><p>For <strong>Splunk</strong>, I documented:</p><ul><li>Core SPL queries I used repeatedly</li><li>What each query returned and why it mattered</li><li>How small changes in fields or filters affected results</li><li>Common investigation patterns such as narrowing time ranges, pivoting on fields, and validating assumptions</li></ul><p>For <strong>Wireshark</strong>, I documented:</p><ul><li>Filters I reached for first in an investigation</li><li>What each filter was designed to isolate</li><li>How to quickly eliminate noise and focus on relevant traffic</li><li>Indicators that told me I was looking at something suspicious versus normal behavior</li></ul><p>For <strong>Autopsy</strong>, I focused on:</p><ul><li>Navigation workflows</li><li>Where key artifacts are typically located</li><li>How to validate findings rather than accepting the first result</li></ul><p>These notes were short, direct, and written in my own words.</p><h3>How I Structured My Notes in Obsidian</h3><p>Structure mattered just as much as content.</p><p>Each tool had its own folder.<br> Each folder contained:</p><ul><li>A main reference note</li><li>Individual notes for commands, filters, or workflows</li><li>Linked notes that connected tools to investigation steps</li></ul><p>Everything was searchable. If I typed a keyword, command, or artifact name, I could immediately pull up context.</p><p>This reduced cognitive load during practice and made recall much easier during the exam.</p><h3>Final Thoughts</h3><p>The BTL1 exam is not about how many platforms you touched or how many paths you completed.</p><p>It is about how well you can think, investigate, and document under pressure.</p><p>Focusing deeply on <strong>Splunk, Wireshark, and Autopsy</strong> gave me far more value than spreading my attention across additional content. Watching experienced analysts break down traffic, practicing queries until they became instinctive, and documenting everything in a way that made sense to me is what ultimately mattered.</p><p>Good tools matter.<br> Good process matters more.<br> Clear thinking matters most.</p><p>If you are preparing for BTL1, my advice is simple. Narrow your focus. Build real familiarity with the tools you will actually use. Take notes like you are building a personal playbook, not studying for a trivia test.</p><p>Passing the exam is important.<br> Building confidence in your ability to operate as a defender is the real win.</p><p>That mindset carries far beyond BTL1.</p><h3>Let’s Connect</h3><p>If you are currently preparing for the BTL1 exam or transitioning into blue team or SOC work, feel free to reach out.</p><p>I am always open to connecting with other cybersecurity professionals, IT engineers, and those breaking into the field. If you have questions about preparation, tooling, or study strategy, I am happy to share what worked for me.</p><p>You can connect with me on <a href="http://www.linkedin.com/in/blueteamanalyst"><strong>LinkedIn</strong></a>, and I welcome thoughtful conversations and knowledge sharing.</p><p>We all get better by learning from each other.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=951970588309" width="1" height="1" alt=""><hr><p><a href="https://cybersecuritywriteups.com/why-btl1-is-different-951970588309">Why BTL1 is Different..</a> was originally published in <a href="https://cybersecuritywriteups.com/">Cyber Security Write-ups</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[DeepBlueCLI Walkthrough: Detecting Meterpreter Activity Using Windows Event Logs]]></title>
            <link>https://cybersecuritywriteups.com/deepbluecli-walkthrough-detecting-meterpreter-activity-using-windows-event-logs-1196bdbcf3b5?source=rss-7063327e59dd------2</link>
            <guid isPermaLink="false">https://medium.com/p/1196bdbcf3b5</guid>
            <category><![CDATA[btlo]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[incident-response]]></category>
            <category><![CDATA[windows]]></category>
            <category><![CDATA[soc-analyst]]></category>
            <dc:creator><![CDATA[Jacob Ferguson]]></dc:creator>
            <pubDate>Thu, 22 Jan 2026 04:49:57 GMT</pubDate>
            <atom:updated>2026-01-22T05:24:35.587Z</atom:updated>
            <content:encoded><![CDATA[<h4>A hands-on blue team investigation using DeepBlueCLI to analyze Windows Security and System event logs</h4><blockquote>Windows Event Logs are one of the most valuable — and often overlooked — data sources for blue team detection and incident response. When properly analyzed, they can reveal attacker behavior such as initial execution, persistence, and privilege escalation.</blockquote><blockquote>In this walkthrough, I use <strong>DeepBlueCLI</strong> to analyze recovered <strong>Windows Security and System event logs</strong> to identify <strong>Meterpreter activity</strong>, trace a malicious executable, and uncover attacker persistence techniques. This is a hands-on, analyst-focused investigation that mirrors the type of log analysis performed in real SOC environments.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KzRIaeN6qQI1UbSa9G2JJA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/442/1*FYqHXfXnKJ-xRiygt7ToNQ.png" /></figure><p><strong>Q1: Using DeepBlueCLI, investigate the recovered Security log (Security.evtx). Which user account ran GoogleUpdate.exe?<em>(4 points)</em></strong></p><p>First, navigate to the DeepBlue directory. Inside the DeepBlueCLI-master folder, you’ll find both DeepBlue.ps1 and the recovered Security.evtx file.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/701/1*jbTxiokZHheTmvs2ORt3kw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/530/1*lJPNzLUQEG0YbrTglau5AQ.png" /></figure><p>Running DeepBlueCLI against the Security log reveals the user account responsible for executing GoogleUpdate.exe.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/933/1*M-RBrub48te5lECn2ajuew.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1023/1*Fsa2a3B31Oij2yJalH1O0g.png" /></figure><p><strong>Answer:</strong><br><strong>Mike Smith</strong></p><p>Q2: Using DeepBlueCLI investigate the recovered Security.evtx log. At what time is there likely evidence of Meterpreter activity?<em>(4 points)</em></p><p>DeepBlue flags suspicious activiy associated with Meterpreter within the Security log.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/589/1*XoxwRZvKtbATw4X67M5N1Q.png" /></figure><p><strong>Answer: 4/10/2021 10:48:14</strong></p><p>The timestamp is critical, as it helps anchor later activity and narrow the investigation window.</p><p><strong>Q3: Using DeepBlueCLI investigate the recovered System.evtx log. What is the name of the suspicious service created?<em>(5 points)</em></strong></p><p>Next, I analyzed the recovered System.evtx log using DeepBlueCLI to identify suspicious service creation events.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/701/1*dHaySvNrHOWcEZWEIBVHSQ.png" /></figure><p>DeepBlue highlights an abnormal service name that does not match typical system or application naming conventions.</p><p><strong>Answer: rztbzn</strong></p><p><strong>Q4: Investigate the Security.evtx log in Event Viewer. Process creation is being audited (event ID 4688). Identify the malicious executable downloaded that was used to gain a Meterpreter reverse shell, between 10:30 and 10:50 AM on the 10th of April 2021.<em>(4 points)</em></strong></p><p>Using the Meterpreter timestamp identified earlier (10:48:14), I focused on process creation events leading up to that time.</p><p>Reviewing Event ID <strong>4688</strong>, I identified a suspicious executable downloaded shortly before the Meterpreter activity occurred.</p><p>At <strong>10:46:55</strong>, an executable named <strong>serviceupdate.exe</strong> was created and executed, closely preceding the Meterpreter session.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8QRjA-jd4Attht6fNuGaYA.png" /></figure><p><strong>Answer: Mike Smith | Serviceupdate.exe</strong></p><p><strong>Q5: It’s also believed that an additional account was created to ensure persistence between 11:25 AM and 11:40 AM on the 10th April 2021. What was the command line used to create this account? (Make sure you’ve found the right account!)<em>(4 points)</em></strong></p><p>Reviewing the Security log during this timeframe revealed a new local account creation event.</p><p>At <strong>11:29:15 AM</strong>, a user named <strong>ServiceAct</strong> was created. Further events show this account was immediately elevated, indicating an attempt to establish persistence.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/440/1*MiquuBMLufcDnxGvbqCJtg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/862/1*QecngG1P63Zgzzq3uh-6DQ.png" /></figure><p>A few events above that you will see that the user is also being added to the administrators and remote desktop groups.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qfouTDww3BR7fFafFymoSA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1001/1*l-kFE91QnU9_J0P6esHbRg.png" /></figure><p><strong>Answer: net user ServiceAct /add</strong></p><p><strong>Q6: What two local groups was this new account added to?<em>(4 points)</em></strong></p><p>Following the account creation, additional events show the account being added to privileged groups.</p><p><strong>Answer: Administrators, Remote Desktop Users</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/850/1*ruVi41cdz1B_MYCs0JHJXQ.png" /></figure><h3>Skills Demonstrated</h3><ul><li>Windows Event Log Analysis (Security.evtx, System.evtx)</li><li>Using <strong>DeepBlueCLI</strong> for threat detection</li><li>Identifying Meterpreter-related activity</li><li>Investigating process creation events (Event ID 4688)</li><li>Detecting suspicious services and persistence mechanisms</li><li>Timeline analysis and correlation of attacker activity</li><li>Identifying privilege escalation through group membership changes</li></ul><h4>Connect with me:</h4><p>If you enjoyed this write-up and want to follow my journey in CyberSecurity, feel free to connect with me below.</p><p>I regularly share:</p><ul><li>Hands-on blue team labs &amp; write-ups</li><li>Incident response &amp; detection practice</li><li>Certification progress and study strategies</li><li>Lessons learned breaking and defending systems</li></ul><p>Let’s Connect:</p><p>🔗 <strong>LinkedIn:</strong> <a href="http://www.linkedin.com/in/blueteamanalyst">www.linkedin.com/in/blueteamanalyst</a></p><p>🧠 <strong>TryHackMe:</strong> <a href="https://tryhackme.com/p/jfergusoncloudpro">https://tryhackme.com/p/jfergusoncloudpro</a></p><p>💻 <strong>Portfolio:</strong> <a href="https://jacobferguson.dev/">https://jacobferguson.dev/</a></p><p>📝 <strong>Medium:</strong> Follow me here for future write-ups</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/781/1*mOCw75wFo7Q2asYee1OmAA.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1196bdbcf3b5" width="1" height="1" alt=""><hr><p><a href="https://cybersecuritywriteups.com/deepbluecli-walkthrough-detecting-meterpreter-activity-using-windows-event-logs-1196bdbcf3b5">DeepBlueCLI Walkthrough: Detecting Meterpreter Activity Using Windows Event Logs</a> was originally published in <a href="https://cybersecuritywriteups.com/">Cyber Security Write-ups</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Kali Linux Lab Home lab — Part 1]]></title>
            <link>https://cybersecuritywriteups.com/kali-linux-lab-home-lab-part-1-4402655dbaa2?source=rss-7063327e59dd------2</link>
            <guid isPermaLink="false">https://medium.com/p/4402655dbaa2</guid>
            <category><![CDATA[threat-hunting]]></category>
            <category><![CDATA[incident-response]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[kali-linux]]></category>
            <category><![CDATA[blueteamlabs]]></category>
            <dc:creator><![CDATA[Jacob Ferguson]]></dc:creator>
            <pubDate>Sat, 10 Jan 2026 19:21:34 GMT</pubDate>
            <atom:updated>2026-01-11T03:40:47.416Z</atom:updated>
            <content:encoded><![CDATA[<h3>Kali Linux Lab Home lab — Part 1</h3><h4>How I designed an isolated Kali environment in VirtualBox</h4><p>This is part 1 of a series where I&#39;ll build on this foundation with vulnerable targets, detection exercises, and defensive tooling.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*okvI5Lyf05NZgwH394vKjA.png" /></figure><h4>Why This Lab Exist</h4><p>I decided that before running a single scan or exploit, I wanted to make sure my lab was designed intentionally. What that meant was separating management traffic from attack traffic, validating isolation, and understanding exactly how my environment behaved before trusting it.</p><p>This write-up documents how I laid the groundwork for a Kali Linux homelab that I can confidently build on for future offensive and defensive security labs.</p><p>Rather than rushing the setup process, I defined a few clear goals for what this lab needed to accomplish.</p><p><strong>Lab Objectives</strong>:</p><ul><li>Deploy Kali Linux using VirtualBox</li><li>Segment management traffic from attack traffic</li><li>Enforce network isolation using an internal network</li><li>Validate behavior through connectivity testing</li><li>Apply basic threat modeling to the lab design</li></ul><p><strong>Environment</strong>:</p><ul><li>Host OS: Windows</li><li>Hypervisor: Oracle VirtualBox</li><li>Guest OS: Kali Linux</li><li>Networking Model: Dual-NIC (Bridged + Internal Network)</li></ul><h4><strong>What This Is / What This Isn’t</strong></h4><ul><li>This <strong>is</strong> a foundation for future cybersecurity labs</li><li>This <strong>is</strong> focused on network design, isolation, and validation</li><li>This <strong>is not</strong> a walkthrough of Kali tools or exploitation techniques</li><li>This <strong>is not</strong> meant to be flashy</li></ul><p>Every configuration choice in this lab is followed by validation to confirm it behaves exactly as intended.</p><h4><strong>Step 1: Setting up VirtualBox and Kali Linux</strong></h4><p>The first step was to install Oracle VirtualBox on my Windows host along with the VirtualBox Extension Pack. Skipping over the Extension pack will tend to cause problems later.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pybXVKtm-WWsGxYV_ThKww.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/743/1*ZJEcisyPguIb3KUGeKOx8Q.png" /></figure><p>Once VirtualBox was up and running, I moved on to Kali.</p><h4><strong>Step 2: Choosing and Importing Kali Linux</strong></h4><p>I simply chose the pre-built Kali Linux VirtualBox image to reduce the installation overhead.</p><p>Once imported, I configured the VMs resources as follows:</p><ul><li>4 GB RAM</li><li>2 CPUs</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sU_u54M4RKOiEpKocAH7Bg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RkCzTarhIuh0_x8g_r3JCA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/803/1*gryNhl2Ay6a1Y3fCGT-A3Q.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/936/1*nCl9C75zDZVxHDaif8Zh6g.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/766/1*AcPwfWBy3rhhFqCtF2CjYA.png" /></figure><p>For this lab and my upcoming labs, these resources will suffice.</p><h4><strong>Step 3: Network Architecture Design</strong></h4><p>I configured Kali with two network interfaces, each serving a specific role.</p><pre>                         Home Network<br>                        192.168.1.0/24<br>                               |<br>                        (Bridged Adapter)<br>                               |<br>┌────────────────────────────────────────────────────────┐<br>│                  Windows Host                           │<br>│                                                        │<br>│             Oracle VirtualBox Hypervisor                │<br>│                                                        │<br>│   ┌────────────────────────────────────────────────┐   │<br>│   │              Kali Linux VM                      │   │<br>│   │                                                │   │<br>│   │  eth0 → 192.168.1.168/24  (Bridged)             │   │<br>│   │  eth1 → 172.30.1.20/24     (Internal: HackLabs) │   │<br>│   │                                                │   │<br>│   └────────────────────────────────────────────────┘   │<br>│                                                        │<br>└──────────────────────────────┬─────────────────────────┘<br>                               |<br>                        HackLabs Network<br>                         172.30.1.0/24<br>                    (No Gateway • No Internet)                </pre><p>To explain this a little more, here is how the interfaces are used:</p><p><strong>eth0</strong>: Management Interface</p><ul><li>bridged to the host network</li><li>Used for updates and management</li><li>Internet access allowed</li></ul><p><strong>eth1</strong>: Attack Interface</p><ul><li>Internal Network (HackLabs)</li><li>No gateway</li><li>No NAT</li><li>No internet access</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/777/1*bDuEV__s6veV2gjQ_NkklQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/762/1*yhRS6eIy-rAXJCJeA3DgjQ.png" /></figure><p>With these settings, I can update Kali and manage it normally, while anything happening on the lab network stays completely contained.</p><h4><strong>Step 4: Booting Kali and Verifying the Interfaces</strong></h4><p>Now that I got Kali spun up and am able to log-in, the first thing I checked was if the interfaces were working as I expected.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/784/1*n4JVgcvKUpy9Gyc_Efx0Mg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/628/1*RMkUpp4JHDzmIqB-H9ORbg.png" /></figure><p>eth0 and eth1 show the correct IPs which confirms that VirtualBox and Kali are in alignment.</p><h4><strong>Step 5</strong>: Testing Connectivity (Why Failure is Success)</h4><p>Now came the connectivity test.</p><p>From the host, I pinged Kali’s management interface</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/647/1*boGnYC7y5it2cQzUOT36eg.png" /></figure><p>This worked as expected.</p><p>Next, I tested the internal network:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/589/1*tEHiWyQAIfnTq4k6iElKmg.png" /></figure><p>The 100% packet loss tells me that the internal network has no routing, no gateway, and no accidental escape paths. This isolation is exactly what is planned. Do not fret my friend.</p><h4><strong>Step 6</strong>: Update Kali</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/630/1*xF_9MX-w3EfDabY2vCmsYw.png" /></figure><p>After this, I wrapped it up for Day 1. When building a home lab you do not have to do everything in one go. This is setting the ground work for what is to come.</p><p>What can this lab set you up for?</p><ul><li>Vulnerable VM deployment</li><li>Internal scanning and enumeration</li><li>Lateral movement simulations</li><li>Blue Team detection labs</li><li>Forensics and incident response practice</li><li>Malware analysis in a controlled network</li></ul><p>Closing Thoughts</p><p>This lab is intentionally simple. There are no exploits, no payloads, and no dashboards yet simply because I am laying the groundwork for future labs.</p><p>In the next part of the series, ill be introducing vulnerable machines to practice reconnaissance and Incident response.</p><p>Be sure to follow along as this series evolves. If you run into any roadblocks building the lab yourself, feel free to reach out to me.</p><p>You can reach me on my LinkedIn:</p><p><a href="http://www.linkedin.com/in/blueteamanalyst">www.linkedin.com/in/blueteamanalyst</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4402655dbaa2" width="1" height="1" alt=""><hr><p><a href="https://cybersecuritywriteups.com/kali-linux-lab-home-lab-part-1-4402655dbaa2">Kali Linux Lab Home lab — Part 1</a> was originally published in <a href="https://cybersecuritywriteups.com/">Cyber Security Write-ups</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>