<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Container-Security on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/container-security/</link>
    <description>Recent content in Container-Security on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 17 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/container-security/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted Confidential Computing: Gramine vs Occlum vs Enarx TEE Platforms</title>
      <link>https://www.pistack.xyz/posts/2026-05-17-self-hosted-confidential-computing-gramine-occlum-enarx-tee-guide/</link>
      <pubDate>Sun, 17 May 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-05-17-self-hosted-confidential-computing-gramine-occlum-enarx-tee-guide/</guid>
      <description>&lt;p&gt;Confidential computing uses hardware-based Trusted Execution Environments (TEEs) to protect data while it is being processed. Unlike encryption at rest and in transit, TEEs shield data in use — preventing even the host operating system, hypervisor, or cloud provider from accessing sensitive workloads. Three open-source platforms lead this space: &lt;strong&gt;Gramine&lt;/strong&gt;, &lt;strong&gt;Occlum&lt;/strong&gt;, and &lt;strong&gt;Enarx&lt;/strong&gt;. Each takes a fundamentally different architectural approach to enabling confidential computing for self-hosted deployments.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
