<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Networking on blanpa</title><link>https://blanpa.github.io/tags/networking/</link><description>Recent content in Networking on blanpa</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>© 2026 blanpa</copyright><lastBuildDate>Sat, 18 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://blanpa.github.io/tags/networking/index.xml" rel="self" type="application/rss+xml"/><item><title>Securing OT Networks — The Purdue Model, OPC-UA Encryption &amp; Segmentation</title><link>https://blanpa.github.io/blog/securing-ot-networks-opcua-purdue/</link><pubDate>Sat, 18 Jul 2026 00:00:00 +0000</pubDate><guid>https://blanpa.github.io/blog/securing-ot-networks-opcua-purdue/</guid><description>&lt;p&gt;Every other post in this series has been about &lt;em&gt;connecting&lt;/em&gt; things — &lt;a href="https://blanpa.github.io/blog/siemens-s7-opcua-node-red/" &gt;PLCs to dashboards&lt;/a&gt;, &lt;a href="https://blanpa.github.io/blog/unified-namespace-sparkplug-node-red/" &gt;protocols to brokers&lt;/a&gt;, &lt;a href="https://blanpa.github.io/blog/nats-edge-to-cloud-pipeline/" &gt;edge to cloud&lt;/a&gt;. This one is about the uncomfortable flip side: every connection you add is also an attack surface. Industrial systems were designed in an era of physical isolation, and we&amp;rsquo;ve spent the last decade enthusiastically networking them without always asking what that means for security. This is the post I wish more IIoT developers read &lt;em&gt;before&lt;/em&gt; their first deployment, not after their first incident.&lt;/p&gt;</description><media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://blanpa.github.io/blog/securing-ot-networks-opcua-purdue/featured.webp"/></item></channel></rss>