<?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 ShieldedBytes</title>
    <link>https://linuxeries.org/tags/hardening/</link>
    <description>Recent content in Hardening on ShieldedBytes</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Wed, 13 May 2026 11:01:32 +0200</lastBuildDate>
    <atom:link href="https://linuxeries.org/tags/hardening/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Hardening SSH with Linux Kernel&#39;s Built-in Features and a Few Surprising sysctl Tweaks</title>
      <link>https://linuxeries.org/post/2026-05-13-hardening-ssh-with-linux-kernels-built-in-fea/</link>
      <pubDate>Wed, 13 May 2026 11:01:32 +0200</pubDate>
      <guid>https://linuxeries.org/post/2026-05-13-hardening-ssh-with-linux-kernels-built-in-fea/</guid>
      <description>&lt;h2 id=&#34;introduction-to-ssh-hardening&#34;&gt;Introduction to SSH Hardening&lt;/h2&gt;&#xA;&lt;p&gt;Securing your SSH connection is crucial - I&amp;rsquo;ve seen this go wrong when a friend of mine had his server compromised due to a weak SSH setup. In today&amp;rsquo;s world, with cyber threats lurking around every corner, hardening your SSH setup using Linux kernel&amp;rsquo;s built-in features and sysctl tweaks is essential. This article will guide you through the process of securing your SSH connection using practical examples and commands.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Hardening Your Linux Desktop with Mandatory Access Control and a Little Bit of Common Sense</title>
      <link>https://linuxeries.org/post/2026-05-12-hardening-your-linux-desktop-with-mandatory-a/</link>
      <pubDate>Tue, 12 May 2026 11:50:33 +0200</pubDate>
      <guid>https://linuxeries.org/post/2026-05-12-hardening-your-linux-desktop-with-mandatory-a/</guid>
      <description>&lt;h2 id=&#34;introduction-to-mandatory-access-control&#34;&gt;Introduction to Mandatory Access Control&lt;/h2&gt;&#xA;&lt;p&gt;Mandatory Access Control (MAC) is a security framework that enforces access control decisions based on a set of rules, rather than relying on user identity or group membership. On Linux, one of the most popular MAC implementations is SELinux (Security-Enhanced Linux) and AppArmor. I&amp;rsquo;ve found AppArmor to be generally easier to use and more widely supported, so we&amp;rsquo;ll focus on hardening your Linux desktop using AppArmor.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Hardening Your Linux Desktop with Mandatory Access Control and Namespace Isolation</title>
      <link>https://linuxeries.org/post/2026-05-11-hardening-your-linux-desktop-with-mandatory-a/</link>
      <pubDate>Mon, 11 May 2026 11:46:42 +0200</pubDate>
      <guid>https://linuxeries.org/post/2026-05-11-hardening-your-linux-desktop-with-mandatory-a/</guid>
      <description>&lt;h2 id=&#34;introduction-to-linux-hardening&#34;&gt;Introduction to Linux Hardening&lt;/h2&gt;&#xA;&lt;p&gt;I&amp;rsquo;ve seen many Linux systems compromised due to lack of proper hardening. To prevent this, you can use a combination of Mandatory Access Control (MAC) and namespace isolation. These two security features can help prevent unauthorized access to sensitive data and system resources. In this article, we&amp;rsquo;ll explore how to implement MAC and namespace isolation on a Linux desktop.&lt;/p&gt;&#xA;&lt;h2 id=&#34;mandatory-access-control&#34;&gt;Mandatory Access Control&lt;/h2&gt;&#xA;&lt;p&gt;Mandatory Access Control is a security feature that enforces a set of rules defining what actions a user or process can perform on a system. One popular MAC system for Linux is SELinux (Security-Enhanced Linux), which was integrated into the Linux kernel in 2003. SELinux provides a robust security framework that can help prevent attacks such as buffer overflows and privilege escalation. Don&amp;rsquo;t bother with other MAC systems unless you have a specific reason to - SELinux is well-maintained and widely supported.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
