<?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 Tom Knabe on Medium]]></title>
        <description><![CDATA[Stories by Tom Knabe on Medium]]></description>
        <link>https://medium.com/@tomknabe?source=rss-22361bae1b14------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*o0RsYs51sd96pUgf8a3fZg.png</url>
            <title>Stories by Tom Knabe on Medium</title>
            <link>https://medium.com/@tomknabe?source=rss-22361bae1b14------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 08:21:12 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@tomknabe/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[Accidentally Hacking NSA Infrastructure]]></title>
            <link>https://tomknabe.medium.com/accidentally-hacking-nsa-infrastructure-cf6d50467a0a?source=rss-22361bae1b14------2</link>
            <guid isPermaLink="false">https://medium.com/p/cf6d50467a0a</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[hmi]]></category>
            <category><![CDATA[infrastructure]]></category>
            <category><![CDATA[hacking]]></category>
            <category><![CDATA[plc]]></category>
            <dc:creator><![CDATA[Tom Knabe]]></dc:creator>
            <pubDate>Fri, 01 Jan 2021 19:48:20 GMT</pubDate>
            <atom:updated>2021-01-01T21:13:08.977Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*Rb1D3aDXeIa7gV0NsWQACQ@2x.jpeg" /></figure><p>It’s been two years and I can ‘kind of’ disclose this story about the time I accidentally hacked into critical piece of infrastructure for the <a href="https://en.wikipedia.org/wiki/National_Security_Agency">National Security Agency</a>, <a href="https://en.wikipedia.org/wiki/Central_Security_Service">Central Security Service</a>, <a href="https://en.wikipedia.org/wiki/United_States_Cyber_Command">United States Cyber Command</a> and the <a href="https://en.wikipedia.org/wiki/Defense_Information_Systems_Agency">Defense Information Systems Agency</a>…</p><p>In my free time I like to find bug bounties, in which companies pay people to search for hardware/software exploits. In my past life I was a software engineer and had knowledge about software protocols and poking holes into them.</p><p>As I transitioned my career into automation hardware. I was surprised by how old some of these systems were and how they are powered by some ancient code.</p><p>So let’s talk about HMIs — Human Machine Interfaces. They’re essentially fancy screens used for displaying information from machinery as well as allowing control from an operator. They are a critical piece of hardware in modern times and extremely common on everything from assembly lines to elevators to yachts. HMIs don’t control the machines; they just act as the interface between the controller and the machine. They use many different protocols, some dating back to the 60s.</p><p>TCP/IP is the protocol that allows you to read this article. It allows you to ask Alexa to play “Despacito.” It’s how you buy that pillow on Amazon. It’s fast, cheap, reliable and standardized.</p><p>Picture if you can a Coke bottling plant. Tens of thousands of bottles zipping around at insane speeds without flaw. Now I don’t know about you but I couldn’t even begin to imagine the process of designing that entire system. There are thousands of machines and sensors that all need to communicate at incredible speeds.</p><p>TCP/IP is cheap, easy and, fast, so it’s a no brainer why much of the automation world has been adding support for TCP/IP communication between all of their hardware. It also has the added benefit of being able to send data to the internet which as a feature or flaw can allow your machines to be viewed and controlled via the internet….</p><p>I took my software knowledge of searching for exposed systems and applied it to these hardware systems primarily around HMIs. If you can see an HMI you can see everything important, and in a very easy to digest way – and in an easy-to-read way (unlike digging into a API, where you often have to make sense of obfuscated data.)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EVhmbIByvDCuG5tQN45hLg.png" /><figcaption>Example of data on an HMI</figcaption></figure><p>While performing test scans, I was blown away to see many systems just wide open for viewing. I imagined this is what it felt like to be a hacker in 80s/90s when there was little security and anyone could just pop into a network and look around with very little effort. I had a list of companies that had bounty offers and I would go hunting. I would spend many hours scanning the entire world’s Internet for open HMIs. A dairy farm here, a cookie factory there, HVAC systems for a mansion, etc.</p><p>Then I hit it. I was looking at a screen filled with lots of controls, dials, switches, and gauges. I see historical charts, all beautifully labeled so even a layman such as myself could figure out what I was looking at. My eyes glanced at the title of the machine and in small letters underneath it hits me: Fort Meade, Maryland. I knew I goofed. Fort Meade is the home of the NSA as well as the US government Cyber Security Department.</p><p>Phase 1: Panic.<br>Fort Meade. NSA. None of these were on my bounty list. Regardless of whether I proxied my connection properly I knew the NSA could find me. I was convinced I was going to jail and that would be it. I pictured a black Suburban pulling up in front of my Philadelphia row home and escorting me out of my house.</p><p>Phase 2: Damage control.<br>I can blame the Boy Scouts for instilling “Be Prepared” deep into my brain and that’s exactly what I did. In a panic I tossed a sum of money into a cold storage bitcoin wallet that I turned into a cypher and instructed my proxy on how to access. These funds would be used for my defense team if needed.</p><p>Phase 3: Report.<br> I knew I had to report this and turn myself in as it’s a threat to national security. But how? Is there a number for this? An email? It took a lot of searching but I found a few options. I ended up directly reporting to the Department of Defense Cyber Security team. I filled a ticket and waited… and waited.. Still expecting that Suburban to show up.</p><p>Within a few hours I received a response. My discovery was thanked and flagged as a high severity. The staff I interacted with only went by code names which included the word agent. Over the next few months I was kept in the loop on the resolution.</p><p>No Suburban did show up to take me away, which I am thankful for. There is a large disconnect of security in the hardware world and I hope that changes as more and more hardware continues to adopt TCP/IP protocols. Despite all the stress, it felt good to patch a threat to national security and I still continue to scan for more threats to this day.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cf6d50467a0a" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>