<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Access-Control on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/access-control/</link>
    <description>Recent content in Access-Control on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 16 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/access-control/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted Linux Mandatory Access Control: SELinux vs AppArmor vs SMACK (2026)</title>
      <link>https://www.pistack.xyz/posts/2026-05-16-self-hosted-linux-mac-selinux-apparmor-smack-guide/</link>
      <pubDate>Sat, 16 May 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-05-16-self-hosted-linux-mac-selinux-apparmor-smack-guide/</guid>
      <description>&lt;p&gt;Mandatory Access Control (MAC) is the most powerful security mechanism available on Linux. Unlike Discretionary Access Control (DAC), where file owners decide who gets access, MAC enforces system-wide security policies that even root cannot bypass. For self-hosted servers running critical infrastructure — web applications, databases, mail servers, and container workloads — implementing a MAC framework is essential defense-in-depth.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
