<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Closed-Networks on</title><link>https://geekyschmidt.com/tags/closed-networks/</link><description>Recent content in Closed-Networks on</description><generator>Hugo -- 0.160.1</generator><language>en</language><copyright>Copyright © 2002–2025, Nicholas Schmidt; all rights reserved.</copyright><lastBuildDate>Wed, 19 Jan 2011 09:47:59 +0000</lastBuildDate><atom:link href="https://geekyschmidt.com/tags/closed-networks/index.xml" rel="self" type="application/rss+xml"/><item><title>Closed Network != Security</title><link>https://geekyschmidt.com/2011/01/19/closed-network-security/</link><pubDate>Wed, 19 Jan 2011 09:47:59 +0000</pubDate><guid>https://geekyschmidt.com/2011/01/19/closed-network-security/</guid><description>&lt;p&gt;To this day I am flabbergasted by the assertion that because your network is not connected to the big “I” Internet you can practice lax security. Countless places I have walked in the door to find unencrypted email traffic, no antivirus, and zero firewalls. Like the Masons of the middle ages they draw the boundary around the castle/network and assume they are safe. As architects and security professionals it is up to us to remind the Castle Builders that the threat of today is not warded off with simple walls of rock…&lt;/p&gt;</description></item></channel></rss>