<?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"><channel><title><![CDATA[Improving security by separating server duties]]></title><description><![CDATA[<p dir="auto">Hi selfhosters,</p>
<p dir="auto">I'm considering improving the security of my homelab/server setup and I'd love to hear some more experienced opinions on my plans.</p>
<p dir="auto">Like most self-hosters, I started out with a single-server setup: I cobbled together some old hardware, slapped on a NAS-style OS, bolted on Docker and started experimenting. As things go, my setup has grown a lot over the years. I'm running a <em>lot</em> on that machine - NAS capability, local DNS via pihole, a Wireguard VPN endpoint (so I can tunnel into the LAN from outside), many private services (accessible only from inside the LAN), but also some public ones accessible from the open web.</p>
<p dir="auto">Although I've tried to do my homework in terms of security (various hardening measures for SSH and Docker, reverse proxy, proper SSL termination for everything), I realise I've put a <em>lot</em> of eggs in that one basket and I might want to introduce some network segmentation.</p>
<p dir="auto">I don't think I'm ready for getting a hardware firewall or a router/switch capable of VLANs just yet. What I'm considering, though, is putting my services available from the open internet on a separate server inside my network - a little Pi 5 I've still got lying around. My idea is that <em>if</em> a container on that is breached and <em>if</em> an attacker manages to escape the container to gain root access, compromise would be limited to the few of publicly available services I have on the Pi, thus limiting blast radius. If combined with (software) firewall rules that make the Pi a 'pariah node' (dropping all incoming connection efforts), lateral movement to other devices on the network could be contained.</p>
<p dir="auto">An alternative would be to finally make the move to Proxmox. Everything would <em>still</em> be running on one <em>physical</em> machine, but I'd create several VMs: there would be one for private, one for publicly available services, and I'd firewall the latter off rigorously so it cannot connect to anything else.</p>
<p dir="auto">I'd like your opinion on these plans. Which one would you recommend? Are they both sound, or is there anything I haven't considered? Are there other (easy, non-hardware intense) things I could do to improve security even more?</p>
]]></description><link>https://forum.ieu.app/topic/3b35c647-e9a1-4126-a843-e0cd22bb808a/improving-security-by-separating-server-duties</link><generator>RSS for Node</generator><lastBuildDate>Wed, 21 Oct 2026 20:21:30 GMT</lastBuildDate><atom:link href="https://forum.ieu.app/topic/3b35c647-e9a1-4126-a843-e0cd22bb808a.rss" rel="self" type="application/rss+xml"/><pubDate>Fri, 16 Oct 2026 21:48:53 GMT</pubDate><ttl>60</ttl></channel></rss>