<?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 Zachary Cater on Medium]]></title>
        <description><![CDATA[Stories by Zachary Cater on Medium]]></description>
        <link>https://medium.com/@zachary.cater34?source=rss-58b36d281846------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*jMtXSggdK_m6SHwg</url>
            <title>Stories by Zachary Cater on Medium</title>
            <link>https://medium.com/@zachary.cater34?source=rss-58b36d281846------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 09:29:00 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@zachary.cater34/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[My Takeaways on Network Telemetry]]></title>
            <link>https://medium.com/@zachary.cater34/my-takeaways-on-network-telemetry-a2aa509d4f5e?source=rss-58b36d281846------2</link>
            <guid isPermaLink="false">https://medium.com/p/a2aa509d4f5e</guid>
            <category><![CDATA[network-forensics]]></category>
            <category><![CDATA[threat-detection]]></category>
            <category><![CDATA[cyber-security-awareness]]></category>
            <category><![CDATA[network-security]]></category>
            <category><![CDATA[incident-response]]></category>
            <dc:creator><![CDATA[Zachary Cater]]></dc:creator>
            <pubDate>Fri, 13 Nov 2026 20:30:17 GMT</pubDate>
            <atom:updated>2026-11-13T20:30:17.749Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Q95z0R6QX26rATUa8SVRrg.png" /><figcaption>Two FTP sessions, one server. The first download failed, and the second succeeded from a different IP address using the same account. AI-generated illustration inspired by Phil Hagen’s article on network telemetry.</figcaption></figure><p>After reading Phil Hagen’s article “Better know a data source: Network telemetry,” I have a better understanding of what defenders can learn from network activity. The article went over three forms of network evidence: packet captures, flow summaries, and logs. Packet captures let you look at individual packets. Flow summaries, like NetFlow records, give you a quicker look at which systems communicated and how much data they exchanged. Logs can give you details about what happened within a service, like whether a file download succeeded or failed. What stood out to me was how much more you can learn when you put those pieces together.</p><p>One example that helped me make that connection was the FTP download. The first attempt returned a 550 response and failed. A short time later, the same account successfully downloaded the file with a 226 response, but the second session came from a different IP address. At first, I was focused on what the response codes meant because FTP was something I studied for Network+. Looking at the timing, the account, and the source IPs together gave me a better idea of what someone investigating the activity might look into next. I’d want to find out why the IP changed and whether both sessions were expected for that account.</p><p>This made me think about PurpleRange. PurpleRange is a home cybersecurity lab I’m building to simulate attacks and see what I can detect. I’m still in the architectural phase, where I’m planning how the virtual machines and networks will be set up. I’m already working through which VMs should be able to communicate and what they should have access to. Now I’m also thinking about what I’ll be able to see when those VMs try to communicate. I might add a controlled file transfer between two lab VMs and compare what the service log shows with what I can see in the network traffic. That would give me a way to test whether I can piece together who connected, when it happened, and whether the transfer worked, all within the isolated lab.</p><p>I’m still learning how to tell when an activity is worth investigating. One thing I wrote down was whether file sharing could lead to privilege escalation. I want to understand what permissions the account already had, what the logs can tell me about how those permissions were used, and what evidence I’d need to show that someone actually gained more access. That’s something I’ll keep in mind when I decide what to log and test in PurpleRange.</p><p>References</p><p>Hagen, P. (2023, November 7). <em>Better know a data source: Network telemetry. </em>Zscaler. <a href="https://www.zscaler.com/blogs/cybersecurity-best-practices/better-know-a-data-source-network-telemetry?utm">Better know a data source: Network telemetry</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a2aa509d4f5e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My Takeaways on npm and GitHub Actions]]></title>
            <link>https://medium.com/@zachary.cater34/my-takeaways-on-npm-and-github-actions-dd43b614975e?source=rss-58b36d281846------2</link>
            <guid isPermaLink="false">https://medium.com/p/dd43b614975e</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[software-supply-chain]]></category>
            <category><![CDATA[devsecops]]></category>
            <category><![CDATA[github-actions]]></category>
            <dc:creator><![CDATA[Zachary Cater]]></dc:creator>
            <pubDate>Fri, 06 Nov 2026 20:17:15 GMT</pubDate>
            <atom:updated>2026-11-06T20:17:15.551Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tYtjlOIr8vDhGGVBCzjTEw.png" /></figure><p>After reading “Disrupting supply chain attacks on npm and GitHub Actions, by Greg Ose and Zachary Steindler,” I have a better understanding of how defense in depth helps protect CI/CD pipelines. I also learned about npm. From what I gathered after doing some research, npm give developers a way to find JavaScript packages in an online registry and install them in their packages.</p><p>The part about read-only access stood out to me because it reminded me of a FastAPI project I built. I was thinking about who should be able to make changes and who should be able to view something. In GitHub’s example, the restriction applies to the shared Actions cache. Limiting what a less-trusted workflow can write helps protect the files another workflow might use later.</p><p>I also saw how least privilege comes into play. Once attackers gain access, they can look for ways to use that foothold to get credentials, gain more privileges, or reach other projects. Limiting what a workflow can do gives attackers fewer ways to build on that initial access.</p><p>I was a little confused at first about install-time scripts. I now understand that they can run automatically when a package is installed. Some packages need them for setup, so the change described in the article is to disable them by default and allow specific scripts when they’re needed.</p><p>I’m still pretty new to GitHub, and this article made me appreciate how much work goes into securing the tools developers rely on. It also got me thinking more about the permissions I give the tools I use in my own projects in the future.</p><p>References</p><p>Ose, G., &amp; Steindler, Z. (2026, July 28). Disrupting suppl chain attacks on npm and GitHub Actions. <em>The GitHub Blog</em>. <a href="https://github.blog/security/supply-chain-security/disrupting-supply-chain-attacks-on-npm-and-github-actions/">Disrupting supply chain attacks on npm and GitHub Actions — The GitHub Blog</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dd43b614975e" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>