<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Hardening on Tobias Theel | Senior Software Engineer</title><link>https://blog.noobygames.de/tags/hardening/</link><description>Recent content in Hardening on Tobias Theel | Senior Software Engineer</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 11 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.noobygames.de/tags/hardening/index.xml" rel="self" type="application/rss+xml"/><item><title>Ubuntu Server Hardening — Part 1: The Essentials</title><link>https://blog.noobygames.de/blog/ubuntu-server-hardening-1-essentials/</link><pubDate>Mon, 11 May 2026 00:00:00 +0000</pubDate><guid>https://blog.noobygames.de/blog/ubuntu-server-hardening-1-essentials/</guid><description>&lt;p&gt;This is the first post in a three-part series on hardening a public Ubuntu server.&lt;/p&gt;
&lt;p&gt;In the &lt;a href="https://blog.noobygames.de/blog/secure-ssh-server/"&gt;previous post&lt;/a&gt; we secured SSH: replaced password login with key-based authentication, disabled root, and restricted which users can connect at all. That alone eliminates the majority of attacks targeting internet-facing servers.&lt;/p&gt;
&lt;p&gt;But SSH is one layer. This series adds three more layers per post, ordered by how quickly you can apply them and how much impact they have. Start here — these three take less than fifteen minutes and protect against the most common active threats.&lt;/p&gt;</description></item></channel></rss>