<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Threat-Modelling - vo.rs</title><link>https://vo.rs/tags/threat-modelling/</link><description>Latest from the Threat-Modelling desk at vo.rs.</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>This work is licensed under a Creative Commons Attribution-NonCommercial 4.0 International License.</copyright><lastBuildDate>Fri, 27 Jun 2025 12:43:00 +0000</lastBuildDate><atom:link href="https://vo.rs/tags/threat-modelling/" rel="self" type="application/rss+xml"/><item><title>A Homelab Threat Model: What You're Actually Defending Against</title><link>https://vo.rs/story/a-homelab-threat-model-what-youre-actually-defending-against/</link><description>&lt;p&gt;Ask a homelabber what they are defending against and you often get a shrug, or a vague gesture at &amp;ldquo;hackers&amp;rdquo;. That vagueness is expensive. It leads people to pour weekends into an elaborate VPN mesh while their backups sit unencrypted on a NAS with the default password, or to obsess over intrusion detection while every service shares one reused credential. Security effort spent against imaginary threats is effort stolen from the real ones. A threat model fixes that by forcing you to write down, plainly, who might come after your setup, what they would want, and what actually stops them.&lt;/p&gt;</description><pubDate>Fri, 27 Jun 2025 12:43:00 +0000</pubDate></item></channel></rss>