<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: SorrelThorncroft</title>
    <description>The latest articles on DEV Community by SorrelThorncroft (@sorrelthorncroft).</description>
    <link>https://dev.to/sorrelthorncroft</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4186436%2F7b4d953a-f50f-4364-98fc-26b483e6b885.png</url>
      <title>DEV Community: SorrelThorncroft</title>
      <link>https://dev.to/sorrelthorncroft</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/sorrelthorncroft"/>
    <language>en</language>
    <item>
      <title>Lab setup tips for practicing network defense at home</title>
      <dc:creator>SorrelThorncroft</dc:creator>
      <pubDate>Thu, 15 Oct 2026 09:47:13 +0000</pubDate>
      <link>https://dev.to/sorrelthorncroft/lab-setup-tips-for-practicing-network-defense-at-home-3ill</link>
      <guid>https://dev.to/sorrelthorncroft/lab-setup-tips-for-practicing-network-defense-at-home-3ill</guid>
      <description>&lt;p&gt;Home labs are the best way to test security controls without risking production. I’ve been refining my setup: isolated VLANs, a SIEM instance, and vulnerable test hosts separated from my main network.&lt;/p&gt;

&lt;p&gt;One key rule: never expose your lab directly to public internet. Even low-interaction honeypots get scanned within minutes.&lt;/p&gt;

&lt;p&gt;What tools do you use in your personal security lab?&lt;/p&gt;

</description>
      <category>cybersecurity</category>
      <category>infrastructure</category>
      <category>networking</category>
      <category>security</category>
    </item>
  </channel>
</rss>
