<?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 Jalin Mayberry on Medium]]></title>
        <description><![CDATA[Stories by Jalin Mayberry on Medium]]></description>
        <link>https://medium.com/@mayberryjalin?source=rss-fa502f0487ec------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*RxOjItFu-VumqUVEROe7IA@2x.jpeg</url>
            <title>Stories by Jalin Mayberry on Medium</title>
            <link>https://medium.com/@mayberryjalin?source=rss-fa502f0487ec------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 17:31:57 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@mayberryjalin/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[Splunk4Rookies Workshop: Unveiling the Power of Data with Splunk]]></title>
            <link>https://medium.com/@mayberryjalin/splunk4rookies-workshop-unveiling-the-power-of-data-with-splunk-6abb30cf8def?source=rss-fa502f0487ec------2</link>
            <guid isPermaLink="false">https://medium.com/p/6abb30cf8def</guid>
            <category><![CDATA[data-visualization]]></category>
            <category><![CDATA[splunk-dashboards]]></category>
            <category><![CDATA[splunk]]></category>
            <category><![CDATA[splunk-administration]]></category>
            <dc:creator><![CDATA[Jalin Mayberry]]></dc:creator>
            <pubDate>Fri, 01 Sep 2023 05:13:49 GMT</pubDate>
            <atom:updated>2023-09-01T05:13:49.433Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jWCJlCNoO7Qm7jOKgRZDVQ.png" /></figure><p>As I prepare for my upcoming Splunk certification exams, I’m trying to familiarize myself with the tool as much as I can. Recently, I attended the Splunk4Rookies workshop, which expanded my understanding of data analysis and showed me how potent Splunk can be if set up correctly. Here is a brief overview of the topics:</p><h3>Accessing Your Lab Environment: Where the Journey Begins</h3><p>The workshop kicked off by guiding us through the process of setting up our own Splunk instance using the Splunk Show portal. This allowed us to actively engage with the hands-on exercises and delve into the practical aspects of working with data in a controlled environment.</p><h3>Creating an App and Adding Data: Unveiling the Data Universe</h3><p>During our exploration of Splunk, we developed our own customized application. We were able to configure our Splunk instance to track sample web server logs and add data to it. This exercise helped us better understand the complexities involved in data ingestion and the crucial importance of data preprocessing in making it ready for analysis.</p><h3>Exploring Data and Searching: Navigating the Data Landscape</h3><p>We were taught the significance of exploring and searching through data effectively. The practical demonstrations helped us enhance our skills in constructing accurate searches, using Boolean operators, and refining queries by utilizing specific field values. These techniques proved to be very helpful in efficiently navigating through large amounts of data.</p><h3>Visualizing Data with Charts: From Raw Data to Actionable Insights</h3><p>In the context of data analysis, visualization plays a crucial role. In the workshop, we were introduced to various chart types, including Column Charts, Area Charts, and Single Value visualizations. Witnessing the conversion of raw data into coherent and significant visual representations highlighted the significance of utilizing data to narrate stories.</p><h3>Customizing Dashboards: Crafting Interactive Data Narratives</h3><p>In the workshop’s final phase, we delved into the area of dashboard customization. We gained knowledge on how to give it a personal feel by incorporating custom background images, adjusting panels, and connecting them with the global time picker. This enabled us to create dynamic dashboards that could efficiently communicate insights. The interactive activity emphasized the importance of data accessibility and a design that puts the user at the center.</p><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/1*IiIN_G6NGpKKL7WTRlfVfA.png" /><figcaption>Crafted Dashboard for Fictional Enterprise</figcaption></figure><p>The Splunk4Rookies workshop was a game-changing experience that equipped me with essential skills for harnessing the power of data. With my newfound abilities, I am confident in my capacity to create a dashboard that provides valuable insights and visualizations for enterprise teams. This journey has been a stepping stone towards realizing the boundless possibilities that data-driven decision-making can offer, from maximizing Splunk’s potential to mastering data visualization and dashboard design.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6abb30cf8def" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[PowerShell: Streamlining Batch PDF Printing]]></title>
            <link>https://medium.com/@mayberryjalin/powershell-streamlining-batch-pdf-printing-301f25c1cd03?source=rss-fa502f0487ec------2</link>
            <guid isPermaLink="false">https://medium.com/p/301f25c1cd03</guid>
            <category><![CDATA[powershell]]></category>
            <category><![CDATA[automation]]></category>
            <category><![CDATA[scripting]]></category>
            <dc:creator><![CDATA[Jalin Mayberry]]></dc:creator>
            <pubDate>Sun, 27 Aug 2023 14:01:06 GMT</pubDate>
            <atom:updated>2023-08-27T14:01:06.312Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/256/0*4-i2VZ1zKbJe61Zz.png" /></figure><p>In a recent scenario at our organization, we encountered a situation where we needed to print a large number of documents that contained important procedural information for upcoming implementations. Initially, it appeared to be a simple task, but it became a time-consuming challenge due to the limitations of Windows printing capabilities.</p><h3>The Situation: A Bottleneck in Printing</h3><p>During my attempt to print a number of important documents, I encountered an unexpected issue. While attempting to print them all, I discovered that Windows only permitted me to batch print a maximum of 15 PDF files at a time to the default printer. This posed a challenge in terms of printing efficiently, and despite my best efforts, I ultimately had to manually initiate print jobs in batches of 15. This approach caused concern that I might have overlooked certain files, and unfortunately, some incorrect documents were printed, creating additional work and potential issues for later on.</p><h3>The Solution: Automating with PowerShell</h3><p>I realized that my efforts were inefficient and prone to errors, so I decided to seek help instead of continuing to struggle. I reached out to our skilled Infrastructure engineering specialist, who has always been a reliable teammate. I explained my situation to them and admitted that I was unsuccessful in my attempts to write a script to solve the problem. One of my attempts resulted in the files opening infinitely instead of printing 😂.</p><p>With the help of my colleague, we revisited the idea of automating the printing task using PowerShell. With their insights and a clearer understanding of the method, I made the necessary modifications to the script to enable all PDF files to be printed with just a single keystroke.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/520/1*aD5Jb82sx0rFbjBznCbdEA.png" /><figcaption>Real path redacted</figcaption></figure><p>The initiative was successful using the following script:</p><p><strong>Get-ChildItem -Path “C:/path” -Filter *.pdf | ForEach-Object {</strong></p><p><strong>. Start-Process -FilePath $_.FullName -Verb Print</strong></p><p><strong>}</strong></p><p>Let’s break it down:</p><p><strong>Get-ChildItem -Path “C:\path” -Filter *.pdf</strong></p><p><em>This command fetches a list of PDF files in the designated folder, using the </em><strong><em>Get-ChildItem</em></strong><em> cmdlet with the </em><strong><em>-Filter</em></strong><em> parameter set to </em><strong><em>*.pdf</em></strong><em>.</em></p><p><strong>| ForEach-Object { … }</strong></p><p><strong><em>The pipe (|)</em></strong><em> symbol pipes the list of PDF files into the </em><strong><em>ForEach-Object</em></strong><em> cmdlet, which processes each file sequentially.</em></p><p><strong>Start-Process -FilePath $_.FullName -Verb Print</strong></p><p><em>Within the script block, the </em><strong><em>Start-Process</em></strong><em> cmdlet is employed to initiate the printing action for each PDF file. The </em><strong><em>-FilePath</em></strong><em> parameter uses </em><strong><em>$_ (representing the current file)</em></strong><em> to access the file’s full path, and the </em><strong><em>-Verb Print</em></strong><em> parameter instructs Windows to perform the default print action.</em></p><p>Looking back, what initially appeared to be a difficult and frustrating task ended up being a valuable learning experience. By collaborating, we were able to not only successfully resolve the issue at hand but also equip me with a new skillset — namely, the ability to automate simple tasks using PowerShell scripting. This project showcased how automation can streamline workflows and especially emphasized the importance of seeking help when faced with obstacles.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=301f25c1cd03" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Incident Response at Home: The Firewall That Cried Wolf]]></title>
            <link>https://medium.com/@mayberryjalin/incident-response-at-home-the-story-of-the-firewall-that-cried-wolf-6f008507559c?source=rss-fa502f0487ec------2</link>
            <guid isPermaLink="false">https://medium.com/p/6f008507559c</guid>
            <category><![CDATA[ubiquiti]]></category>
            <category><![CDATA[network-security]]></category>
            <category><![CDATA[firewall]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[incident-response]]></category>
            <dc:creator><![CDATA[Jalin Mayberry]]></dc:creator>
            <pubDate>Thu, 17 Aug 2023 04:55:50 GMT</pubDate>
            <atom:updated>2023-08-17T05:19:51.321Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/643/1*_zarLGkKaBVh-uEiuAByDg.jpeg" /></figure><p>In the rapidly evolving landscape of cybersecurity, every alert serves as a clarion call to action. As stewards of our digital realm, we are tasked not only with identifying potential threats but also with crafting swift and effective responses that safeguard our networks, systems, and data. This incident response report chronicles a recent episode that unfolded within my digital ecosystem — a false positive alert originating from a London-based platform, TryHackMe that unveiled invaluable insights into the interplay of threat detection, contextual understanding, and proactive defense strategies.</p><h3>Preparation:</h3><p>In my initial <a href="https://medium.com/@mayberryjalin/enhancing-network-security-with-ubiquiti-and-unifi-os-1295fbf9cb2c">network configuration</a>, I took proactive steps to fortify my digital defenses by implementing firewall rules and fine-tuning threat detection and prevention thresholds. This strategic preparation ensured that assets were well-guarded against potential threats.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/603/1*y8zLAtmOpZJ_sIcJB_1AJw.png" /><figcaption>UniFi OS on the Dream Machine Pro includes settings for detection sensitivity and how you’d like the threat to be handled</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/624/1*ILmGelwwjaxvB9yzW17mOg.png" /><figcaption>35 threat types that UniFi OS can detect and block</figcaption></figure><h3>Detection and Analysis:</h3><p>An alert caught my attention, originating from an IP address targeting my UniFi Controller. The alert featured two distinct signatures: “ET ATTACK_RESPONSE PowerShell NoProfile Command Received In PowerShell Stagers” and “Base64 Encoded Content Command Common In PowerShell Stagers M1.” Still unsure of what was occurring, I delved into a thorough analysis to grasp the potential risk posed by this scenario.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FVOP8R3uxbn7_8nE7uacOg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/335/1*liOQpnn1BauGZkWJEEStuw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/343/1*HrOlVwtVXULU-yV0ZLBGZQ.png" /><figcaption>The threat signatures</figcaption></figure><blockquote>ET ATTACK_RESPONSE PowerShell NoProfile Command Received In PowerShell Stagers</blockquote><ol><li><strong>ET</strong>: This likely refers to Emerging Threats, which is a community-driven organization that provides threat intelligence and signature rules for network intrusion detection and prevention systems.</li><li><strong>ATTACK_RESPONSE</strong>: This suggests that the signature is related to detecting responses or actions taken in response to an attack.</li><li><strong>PowerShell</strong>: This is a scripting language developed by Microsoft for task automation and configuration management. It’s also commonly used by attackers for various malicious activities due to its powerful capabilities.</li><li><strong>NoProfile</strong>: This indicates that the PowerShell command is being executed without loading the user’s profile. In other words, it’s a way of running PowerShell in a more discreet manner, potentially to avoid detection.</li><li><strong>Command Received In PowerShell Stager</strong>s: This suggests that the signature is specifically looking for instances where a command is received within a PowerShell stager. A stager in the context of cyber threats often refers to a small piece of code used to download and execute a larger payload or perform further actions.</li></ol><blockquote>Base64 Encoded Content Command Common In PowerShell Stagers M1</blockquote><ol><li><strong>Base64 Encoded Content Command</strong>: This suggests that the alert is focused on detecting the presence of a command or script encoded in Base64 within PowerShell. Base64 encoding is a way to represent binary data as ASCII text, often used to obfuscate or hide malicious commands.</li><li><strong>Common In Powershell Stagers</strong>: This part of the alert indicates that the Base64 encoded content command is a common pattern observed within PowerShell stagers. As mentioned earlier, a stager is a piece of code used to download and execute a larger payload or perform further actions in a cyber attack.</li><li><strong>M1</strong>: The “M1” could refer to a specific variant or version of this type of threat detection, potentially indicating different variations of the same behavior.</li></ol><h3>Containment:</h3><p>My threat detection and prevention systems sprang into action, intercepting the flagged threat in alignment with my firewall configurations. The automated response swiftly contained the suspicious activities, thwarting any further unauthorized access attempts.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/341/1*73U6skk91ZBb1cBOlfqBIw.png" /></figure><h3>Eradication and Recovery:</h3><p>To ensure comprehensive risk mitigation, I took the step of initiating an additional inbound and outbound IP block to neutralize any potential harm from the identified IP address. My incident response team (me, myself, and I) scanned the targeted device for any malicious executables.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/288/1*6T_ojWrw-qRXoIyNbgul8A.png" /><figcaption>Quick surface scan</figcaption></figure><h3><strong>Lessons Learned:</strong></h3><p>This incident, which was indeed a false positive, brought a valuable revelation. The source of the alert was traced back to TryHackMe, a London-headquartered company. Coincidentally, I was actively engaged on their platform using virtual machines while immersed in Splunk certification studies. The subsequent inbound and outbound IP block had an immediate and undeniable impact — the Splunk machine lost connectivity. This swift outcome provided concrete confirmation of the false positive nature of the alert.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/821/1*fAvdGiQWKV5hW-lWd0imxg.png" /></figure><p>The significance of dynamic incident response cannot be overstated — one that is customized not only to possible threats but also to the circumstances in which they arise. The convergence of threat identification, accurate analysis, and contextual comprehension creates the harmony of durable incident response.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6f008507559c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Enhancing Network Security with Ubiquiti and UniFI OS]]></title>
            <link>https://medium.com/@mayberryjalin/enhancing-network-security-with-ubiquiti-and-unifi-os-1295fbf9cb2c?source=rss-fa502f0487ec------2</link>
            <guid isPermaLink="false">https://medium.com/p/1295fbf9cb2c</guid>
            <category><![CDATA[networking]]></category>
            <category><![CDATA[network-security]]></category>
            <category><![CDATA[ubiquiti]]></category>
            <category><![CDATA[network-engineering]]></category>
            <category><![CDATA[network-administration]]></category>
            <dc:creator><![CDATA[Jalin Mayberry]]></dc:creator>
            <pubDate>Mon, 31 Jul 2023 14:23:58 GMT</pubDate>
            <atom:updated>2023-08-17T05:39:15.391Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/557/1*ZsMuIj3jsyQg31CdMiyduw.jpeg" /></figure><p>In today’s world, network security is essential for protecting sensitive information and maintaining uninterrupted operations. The founder of Ubiquiti, Robert Para, previously worked for Apple, ensuring FCC compliance for the company’s Wi-Fi electromagnetic emissions. Para’s aim was to bridge infrastructure gaps in emerging markets that needed dependable internet access. Ubiquiti has since expanded its range of products, including switches, routers, access points, and security cameras. In this blog, I will share my experience of deploying my home network infrastructure, utilizing the power of Ubiquiti’s UniFi Dream Machine Pro, U6 Access Points, and UniFI&#39;s design center to improve security and efficiency.</p><h3>Architecture</h3><p>The UniFi Design Center offers a user-friendly platform for planning and deploying networks, allowing for meticulous control and optimization. By utilizing this tool, network architects can receive visual feedback when stacking Ubiquiti’s product suite within a facility using accurate floor plans.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*g3k55JuG4U1vViEZfSwlVw.png" /><figcaption>A reference floor plan to simulate dual-band coverage and the effect of obstacles such as walls and windows</figcaption></figure><h3>Hardware</h3><h4>Part 1</h4><p>In the original setup, my home network relied on the ASUS RT-AC86U as the sole router and access point. While this router performed adequately initially, I soon encountered issues with <a href="https://www.asuswrt-merlin.net/">Asuswrt-Merlin </a>firmware incompatibility when attempting to implement a more complex network topology. The limitations of the firmware hindered the smooth integration of additional devices and services, ultimately leading to a significant reduction in network uptime. To address these challenges and achieve better reliability and performance, I recognized the need to upgrade the hardware and explore more advanced router options that could accommodate my evolving network requirements.</p><p>Next, I tried building a custom router solution. I initially wanted to utilize a powerful open-source solution using an MSI A6200 laptop running pfSense. To ensure top-notch performance, I planned to address the USB 2.0 480MBs bottleneck by adding a 2-port USB 3.0 Express34 expansion card and incorporating two USB 3.0 to RJ45 adapters. For seamless connectivity and excellent Wi-Fi coverage, I included a Ubiquiti USW Flex mini POE switch and a Ubiquiti U6 Mesh access point.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4Qjt8bHIdT13H5bzH2UuDw.jpeg" /><figcaption>Pictured: MSI A6200 (pfSense), Ubiquiti U6 Mesh Access Point, and a Ubiquiti USW Flex Mini</figcaption></figure><p>As I delved into the project, I encountered some unexpected challenges with the MSI A6200 laptop. The Express34 slot proved to be unreliable, hindering the overall performance I had envisioned. Additionally, the laptop generated considerable heat, with little room for ventilation, and as the project progressed, I couldn’t help but yearn for a single pane of glass solution, where all the network components could work harmoniously under a centralized system. This would not only simplify management but also offer better scalability and efficiency.</p><h4>Part 2</h4><blockquote><strong><em>Network Hardware List: </em></strong><em><br>Ubiquiti UniFI Dream Machine Pro,</em></blockquote><blockquote><em>1 U6 Mesh w/POE injector,</em></blockquote><blockquote><em>2 U6 Extenders</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*s1bubwJuNdjBNdny0C24RA.png" /><figcaption>UniFI topology map</figcaption></figure><p>I searched for a new solution to upgrade my home network and found the perfect option: the Ubiquiti UniFI Dream Machine Pro. This powerful hardware is the core of my new setup, providing excellent performance and security. For seamless Wi-Fi coverage, I also used the Ubiquiti U6 Mesh WiFi access point from my previous router project, which I placed in the center of the house for optimal coverage. For hardwired endpoints that require Gigabit speeds, I utilized CAT6a cables to ensure lightning-fast connections to support up to 10GBp/s if needed. To improve the signal strength in hard-to-reach areas, I added two Ubiquiti U6 Extenders as downlinks to the central access point, which improved signal reliability.</p><h3>Engineering</h3><blockquote>DNSSEC</blockquote><p>To strengthen the security and performance of my home network, I added two DNS servers: 9.9.9.9 and 142.112.112.112. These DNS servers are highly regarded for their reliability and dedication to protecting users like us in the vast world of the internet. The first DNS server, 9.9.9.9, is operated by Quad9, an exceptional organization committed to enhancing privacy and preventing malware threats. Quad9 uses threat intelligence data from multiple cybersecurity companies to keep users safe by blocking access to malicious domains. The second DNS server, 142.112.112.112, acts as a backup to Quad9’s primary DNS server 9.9.9.9, providing redundancy and additional support to users seeking secure and reliable DNS resolution.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/339/1*eaB5Lta6CSEgYnoFn1Iy2Q.png" /><figcaption><a href="https://www.quad9.net/">https://www.quad9.net/</a></figcaption></figure><blockquote>Network Segmentation: VLANs</blockquote><p>The implementation of VLANs (Virtual Local Area Networks) offers logical segmentation, effectively isolating different network components. This network is comprised of six VLANs, each with its own specific purpose, including security cameras, IoT devices, garage devices, guests, a SenseCAP Helium hotspot, and main users. This separation mitigates the risk of lateral movement and unauthorized access.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JEvZh0dHDzmruVgLtqef2Q.jpeg" /><figcaption>Complete Network Topology Map: With devices spread across the property, access points carry the subnet configurations with them</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/766/1*QAJr2nbA51yBipmE4O18Ug.png" /><figcaption>With 7 Wi-Fi networks coexisting between 3 access points (in addition to Vivint’s dedicated access point), I’ve kept the AP broadcast channels set to automatic. I have had little to no issue with channel interference across both radio frequencies</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/655/1*_FKF18QdVy6TdBbAK3AKtQ.png" /></figure><p>The Main Users VLAN (VLAN 10) is for our primary devices to ensure their privacy and separation from other network segments. IoT devices such as smart TVs and Zigbee devices are isolated in the IoT devices VLAN (VLAN 20) to reduce the security risks posed by sporadically supported firmware. My SenseCAP Helium hotspot is located at VLAN 30, while the Vivint Smart Home Security Access Point, which hosts the smart panel and perimeter cameras, is at VLAN 40. Additionally, the Garage VLAN (VLAN 50) is for static devices in the garage, including the door opener. Lastly, the Guest Network VLAN (VLAN 60) is for visitors to our home, creating a separate network environment to ensure their privacy and restrict access to our primary network.</p><blockquote>Threat Mitigation: Firewall Rules &amp; Port Security</blockquote><p>Firewall rules serve as an additional layer of defense, enforcing security policies within the network. This setup includes rules for client isolation, VLAN isolation, and geo-filtering, effectively blocking suspicious traffic, limiting lateral movement, and preventing unauthorized access.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/828/1*zjdUjtdqs8BjOjPBygC50w.png" /><figcaption>VLAN isolation configuration</figcaption></figure><p>Click <a href="https://www.linkedin.com/posts/jalinmayberry_networking-networksecurity-ubiquiti-activity-7065783582392291328-kVxr?utm_source=share&amp;utm_medium=member_desktop">here</a> to check out my VLAN and client isolation concept.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/826/1*Yl9LaXL3sRqYlyS1oI9F8A.png" /></figure><p>Since the UniFi Dream Machine Pro has an 8-port switch, disabling unused ports brings several significant benefits. For one, it can enhance network security by eliminating potential attack vectors. Unutilized ports may be exploited by unauthorized individuals or devices trying to gain access to the network. By disabling these ports, you can create a more secure environment, minimizing the chances of rogue devices connecting to the network and potential security breaches.</p><p>Another benefit of disabling unused ports is that it can improve network performance and efficiency. Having unnecessary active ports may lead to broadcast storms, which occur when excessive broadcast traffic floods a network, causing congestion and degrading overall performance. However, disabling any unused ports, can mitigate broadcast storms and optimize network resources for active connections, resulting in improved data transmission and reduced latency.</p><blockquote>Network Administration: Automation &amp; Monitoring</blockquote><p>Proactive network administration is crucial for maintaining a secure and efficient network. Automated backups ensure that critical network configurations and settings are regularly saved, allowing for a swift recovery in case of a system failure or security incident. Automated firmware updates ensure that devices are equipped with the latest security patches, reducing vulnerabilities.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/806/1*TdMFD0o7RqYar21lKTa3Wg.png" /><figcaption>Automatic updates are scheduled to occur during low-production hours</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/803/1*sRM6_KwzdGsZNmQORQwU0w.png" /><figcaption>System and configuration backups occur weekly</figcaption></figure><p>With UniFi OS, monitoring and managing assets is a piece of cake. The client dashboard provides a comprehensive overview of all network devices and their current status, allowing administrators to detect potential security threats, monitor network performance, and effectively manage network assets.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/433/1*npdA7M_U5mT4CLzaotN_UQ.png" /><figcaption>Clients are typically identified automatically by the UniFi operating system. If it fails to recognize the device, manual overrides can be done to display corrected device names</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VIDSE7Jf6a55sSh7s66FkA.png" /><figcaption>Identified traffic from the Security Insights dashboard: SSL/TLS traffic is displayed from usual web traffic over HTTPS</figcaption></figure><p>UniFi OS also comes with a solid security insights dashboard. This dashboard provides a comprehensive overview of all the network traffic occurring, from the protocols being used to the specific applications accessing the network.</p><blockquote><strong>Bonus: Secure Remote Access</strong></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*i_HxXyvhGAoyErlOnIX8fQ.jpeg" /><figcaption>The UniFi iOS dashboard interface</figcaption></figure><p>While setting up my network, I found the UniFi iOS mobile app to be incredibly convenient. It allowed me to configure a significant portion of my network while moving around my home freely. I was able to access and adjust settings on the go, ensuring that all access points were functioning seamlessly and providing optimal Wi-Fi coverage throughout my house. With the app, I could monitor real-time performance and make any necessary adjustments effortlessly, whether I was in the living room, kitchen, or even outside in the backyard.</p><p><strong>Note: While utilizing the UniFi iOS mobile app for remote access to the Ubiquiti console is incredibly convenient, it’s essential to be aware of potential vulnerabilities that can arise from remote access. When enabling remote access to the console, there is a heightened risk of unauthorized access if proper security measures are not in place. It’s crucial to implement strong passwords, enable two-factor authentication, and regularly update the app and device firmware to mitigate these vulnerabilities. Additionally, connecting to the console over public or unsecured networks can expose sensitive information to potential eavesdropping or man-in-the-middle attacks.</strong></p><p>With the UniFi WiFiman app and its Teleport feature, I can easily access all of my UniFi devices, monitor, and optimize my network without any hassle. Teleport allows me to securely connect to my home network from anywhere in the world through a zero-configuration VPN used to encrypt remote console connections.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/554/1*9_-YY8VBN_r_bKU3v7Fuiw@2x.jpeg" /><figcaption>Teleport configuration dashboard</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/642/1*ymrKRn7OcTsntzaw3UMG2Q@2x.jpeg" /><figcaption>Teleport enabled</figcaption></figure><p>To summarize, my experience of upgrading my home network’s security and performance using Ubiquiti and UniFi OS has been truly transformative. By carefully selecting and deploying Ubiquiti’s innovative hardware, I now have a secure and reliable network infrastructure. Thanks to the UniFi Design Center and VLAN configurations, I have meticulous control over my Wi-Fi coverage and can maintain a logical network segmentation. Furthermore, implementing DNS servers at 9.9.9.9 and 142.112.112.112 has enhanced my network’s security, while firewall rules and port security measures have further minimized potential threats. Lastly, I can proactively manage my network with automated backups and firmware updates, ensuring a resilient environment.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1295fbf9cb2c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Mastering Network Traffic Analysis: A Closer Look at TCPDump]]></title>
            <link>https://medium.com/@mayberryjalin/mastering-network-traffic-analysis-a-closer-look-at-tcpdump-eedcd9e8ea74?source=rss-fa502f0487ec------2</link>
            <guid isPermaLink="false">https://medium.com/p/eedcd9e8ea74</guid>
            <category><![CDATA[ssh]]></category>
            <category><![CDATA[wireshark]]></category>
            <category><![CDATA[linux]]></category>
            <category><![CDATA[tcpdump]]></category>
            <dc:creator><![CDATA[Jalin Mayberry]]></dc:creator>
            <pubDate>Fri, 21 Jul 2023 06:09:58 GMT</pubDate>
            <atom:updated>2023-08-17T04:58:53.675Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/479/1*gsUVMFZvM_YSA1WzZHsR2w.png" /></figure><p>In this blog post, we delve into the world of network traffic analysis using TCPDump, a powerful command-line packet analyzer. Specifically, we will focus on capturing and examining SSH-related packets to gain valuable insights into network activities. By breaking down a comprehensive shell script, we will uncover the intricacies of utilizing TCPDump to its full potential and effectively analyze SSH traffic. So, let’s embark on this journey of mastering network traffic analysis and enhancing our understanding of the SSH protocol!</p><p><strong>Part 1</strong><br>In Visual Studio, the script reads as follows:</p><blockquote><em>sudo tcpdump port 22 -i any -#XXtttt -w sshcapture.pcap -C 3 -G 600</em></blockquote><ol><li>sudo: This command is used to run the tcpdump tool with administrative privileges, as it requires elevated access to capture network traffic.</li><li>tcpdump: This is the command-line packet analyzer tool used for capturing and analyzing network packets.</li><li>port 22: This filter option tells tcpdump to capture only the network traffic related to the SSH protocol, which operates on port 22.</li><li>-i any: This flag instructs tcpdump to capture network traffic on any available network interface. It allows capturing SSH traffic on all active network interfaces.</li><li>-#XX: Replace # with the desired number to specify the maximum number of packets tcpdump should capture. For example, -100 would capture 100 packets.</li><li>tttt: This flag instructs tcpdump to print the timestamp of each captured packet in human-readable format.</li><li>-w sshcapture.pcap: This option tells tcpdump to write the captured packets to a file named sshcapture.pcap. The .pcap extension indicates it will be saved in the standard packet capture file format.</li><li>-C 3: This flag specifies the maximum size (in megabytes) of each capture file. In this case, tcpdump will create a new file when the current one reaches 3MB in size.</li><li>-G 600: This option sets the time interval (in seconds) for creating a new capture file. In this example, every 600 seconds (or 10 minutes), tcpdump will create a new file to capture subsequent packets.</li></ol><p><strong>Part 2</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/746/1*_t2kgmZ_m-ljW9yNxSWO4A.png" /><figcaption>After ensuring that the syntax is correct, we can grant execute permissions using the chmod command.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1013/1*3xAwnrGd02JUGXCpCS633Q.png" /><figcaption>Once the script is executed, the .pcap file becomes visible.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/880/1*kaYMk_3JYFFrX-ujnWZcyg.png" /><figcaption>Let&#39;s generate SSH traffic by using the &quot;ssh localhost&quot; command.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/747/1*Mb6pzxZhHdpJqJKUiXgiEw.png" /><figcaption>As shown, the script has captured some SSH traffic. We&#39;ll import the previously created .pcap file into Wireshark for analysis.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*j7_m7NHKQ-uFloMRdF7W-g.png" /><figcaption>Voilà, the SSH traffic is easily noticeable on Wireshark. Though the source IP is from our host machine, it would appear vastly different in real-world scenarios.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/941/1*a4z-0T16CFo5bvvw82b9TQ.png" /><figcaption><strong>As a helpful tip, if there are numerous packets involved, it is easier to locate them quickly by using display filters.</strong></figcaption></figure><p>In this blog, we delved into network traffic analysis using TCPDump, focusing on capturing and analyzing SSH-related packets across various interfaces. Through a meticulously crafted shell script, we mastered capturing a targeted number of SSH packets while managing file size and capture intervals effectively. This skillset equips us to monitor network activities and troubleshoot potential issues, contributing to enhanced network security. Let us stay curious, keep learning, and continue making strides in refining our skills to create a safer, more connected digital landscape.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=eedcd9e8ea74" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Configuring a Detection/Monitoring Homelab]]></title>
            <link>https://medium.com/@mayberryjalin/configuring-a-detection-monitoring-homelab-f78d208f9306?source=rss-fa502f0487ec------2</link>
            <guid isPermaLink="false">https://medium.com/p/f78d208f9306</guid>
            <category><![CDATA[splunk]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[Jalin Mayberry]]></dc:creator>
            <pubDate>Tue, 03 Jan 2023 07:31:11 GMT</pubDate>
            <atom:updated>2023-01-03T07:31:11.095Z</atom:updated>
            <content:encoded><![CDATA[<p>Gaining proficiencies in Cybersecurity topics and tools will require self-discipline. With that being said, I took some initiative to allot time for refreshing my memory of tools and concepts I learned during my cybersecurity bootcamp this past year.</p><p>I followed a <a href="https://cyberwoxacademy.com/building-a-cybersecurity-homelab-for-detection-monitoring/">step-by-step guide</a> from Cyberwox Academy to configure a simulated enterprise network for practicing SOC analyst procedures.</p><p>—</p><p><strong>Topology</strong></p><p>This network was comprised of virtual machines built using VMWare Workstation 17 including:<br><strong>pfSense</strong> — to provide a firewall and network segmentation</p><p><strong>Windows Server 2019</strong> — to serve as the domain controller for the victim network managing separate Windows 10 machines/users</p><p><strong>Ubuntu</strong> — to run a Splunk instance with access to the graphical user interface (GUI) for log queries</p><p><strong>Kali</strong> — to do some troublemaking</p><p><em>The lab also called for a Security Onion (CentOS 7) install which is intended to monitor SPAN port traffic from the domain controller. Since my direct focus at the moment is on Splunk, I find this to be redundant, but I installed it anyway to potentially use later.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/740/1*tG_dALt8TOFQPLOBvgLqIA.jpeg" /><figcaption>Network topology: Cyberwox Academy</figcaption></figure><p>—</p><p><strong>pfSense Configuration</strong></p><p>To begin, I needed to add 5 additional network adapters to my pfSense system settings. These adapters were used to provide direct connectivity to their corresponding machines.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/339/1*tkutPPgoCvf7neAd-H23Hg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/721/1*yKOzy2ixgr7q33FoPUxLlQ.png" /><figcaption>pfSense configuration</figcaption></figure><p>Each virtual network adapter needed a static IP address.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HSeIIdcwr4jhVdh1d4wZvA.png" /><figcaption>DNS settings (Google)</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/920/1*MpV76J5KWLoPcNqLpZottw.png" /><figcaption>Ensuring network interfaces are configured and named properly.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/961/1*BobqTW0hhV5UHV-n53AO6Q.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/979/1*ReFZueHHnJVVJ_U1LFjkZQ.png" /><figcaption>WAN and Victim Network will need IPv4 set to “ANY” to allow connectivity.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/966/1*ULX5XsBiBktIU2rHtjBlbQ.png" /><figcaption>To attach the SPAN port for Security Onion to the Victim Network, I enabled a bridge.</figcaption></figure><p>After the initial configuration, I navigated to the GUI using https://192.168.1.1 to configure DNS, interface settings, and firewall rules. To do this I configured a Kali Linux machine which will also be used as the trouble maker for later projects. <strong>VMnet 2</strong> was used to communicate with pfSense. By default pfSense firewalls need to be told to allow incoming packet traffic or they won’t. This will apply to both the WAN and victim network that will host the domain controller.</p><p>—</p><p><strong>Security Onion</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/332/1*w7-l5HqUCVuyE1xjBPZkFw.png" /><figcaption>VMnet4 = pfSense; VMnet5 = SPAN Port (Victim Network)</figcaption></figure><p>Security Onion needed to be connected to pfSense via <strong>VMnet4</strong> and it also needed to be attached to the network adapter set previously to host the victim network via <strong>VMnet5</strong>. It’s job is very similar to Splunk (monitoring logs via local machines/ports) but it takes quite of bit of computing resources to run along with the other machines so I didn’t do much beyond basic configuration for now.</p><p>—</p><p><strong>Domain Controller Configuration</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/545/1*RZ9S34KGENGPU0wfpBLKzg.png" /><figcaption>Installing certificate service and domain service packages on Windows Server 2019.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/743/1*afQXUSo9vsnllZKMcYrD1A.png" /><figcaption>2 users created per the guide (Joe Smith &amp; Kate Baker) but this can be increased as desired.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/786/1*eqTsPZsS86qO6iNEUZ9TaA.png" /><figcaption>Using pfSense static address as the default gateway.</figcaption></figure><p>Domain control was done with Active Directory on Windows Server 2019. <strong>VMnet 3</strong> was used to connect the domain controller to pfSense. I added two additional end users to the domain which will be placed on Windows 10 machines. There is no specific requirement for the number of machines used in this setup and I will likely mess around with various configurations on each of them to simulate levels of vulnerability.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/111/1*z1Wl_z-vdJsH0gUNXW0Xzw.png" /><figcaption>Splunk forwarder install with default settings.</figcaption></figure><p>Splunk will need a way to log data from the domain controller and one of the ways it can achieve this is by utilizing a universal forwarding tool installed locally on the machine.</p><p>—</p><p><strong>Splunk Configuration</strong></p><p>To finalize the barebones of the lab, I configured an Ubuntu server that will be dedicated to running the Splunk daemon. Initially the server is headless (CLI). The guide specified two ways to access it: Using the OpenSSH configuration or installing a Ubuntu GUI on top.</p><p>I was able to install the GUI using:</p><p><strong><em>“sudo apt install tasksel” and “sudo tasksel install ubuntu-desktop”</em></strong></p><p><em>If you’re going to use the GUI you can likely get away with configuring a standard Ubuntu install without going through the server install to begin with. Splunk Enterprise can be acquired </em><a href="https://www.splunk.com/en_us/download/splunk-cloud.html"><em>here</em></a><em> with a 60-day trial to complete this section.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gbaipuUzrBINhaKe2MczyQ.png" /><figcaption><strong>./splunk start to begin the Splunk instance.</strong></figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/459/1*cZPYO1vmMO1MQARUhKAXNw.png" /><figcaption><strong>http://splunk:8000 to access the web interface.</strong></figcaption></figure><p>—</p><p><strong>Splunk Configuration (cont.)</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/880/1*09jEALY_UQFb8guMV-Y6MQ.png" /><figcaption>By default, the forwarder uses port 9997 for index receiving.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/802/1*OpaFpMrPEIFB2XD4WRy-sA.png" /><figcaption>Creating an index to manage domain controller logs.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/758/1*oglgrA1b1c0i-pxXbFor8g.png" /><figcaption>The domain controller will appear after configuring the forwarder.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*haEbLZCPnGJZXks2r6JZyg.png" /><figcaption>For initial testing, I will use the local event logs emitting from the forwarder.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/935/1*hpTem8P4SWV87DM1nMCguw.png" /><figcaption>Directing the local event logs to the <strong>winevents</strong> index configured earlier.</figcaption></figure><p>After installing Splunk on the Ubuntu machine and launching it via the terminal, I made my way to the web interface and directed the software to log local queries from the universal forwarder configured earlier. These logs would be sent over port 9997 to an index set aside specifically for these events.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/890/1*6q6CqsDGo_2maKbp_bhe3Q.png" /><figcaption>List of logs populating the index.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/761/1*0N8_Nx6nTRaxOUMA1Vkm8Q.png" /><figcaption>EventCode=1074</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*D0NqZd6GMEM6jif5bvgngw.png" /><figcaption>Configuring an alert for EventCode=1074</figcaption></figure><p>With all configurations executed properly, I took some time to look through the Splunk interface for queries as I initiated events on the domain controller. For example, On a shutdown sequence I located EventCode=1074 which identifies a remote system shutdown. For extra measure, I later configured a simple alert to fire on EventCode=1074 parameters.</p><p>—</p><p>In conclusion, Splunk Enterprise is a powerful tool and I can see why its heavily chosen in the industry. <a href="https://www.thegeekghost.com/2022/01/27/how-to-monitor-your-windows-machine-with-splunk/">The Geek Ghost</a> provides a great article containing examples of common queries which will come in handy as I continue familiarizing myself with Splunk. I also plan to run automation experiments with Splunk SOAR in later labs and projects.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f78d208f9306" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>