<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>security on jk jensen</title><link>https://jkjensen.me/tags/security/</link><description>Recent content in security on jk jensen</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Mon, 22 Dec 2025 09:40:00 -0700</lastBuildDate><atom:link href="https://jkjensen.me/tags/security/index.xml" rel="self" type="application/rss+xml"/><item><title>Trusted Execution Environments: Beyond the Hype</title><link>https://jkjensen.me/posts/2025-12-22-trusted-execution-environments/</link><pubDate>Mon, 22 Dec 2025 09:40:00 -0700</pubDate><guid>https://jkjensen.me/posts/2025-12-22-trusted-execution-environments/</guid><description>I&amp;rsquo;ve been thinking a lot about Trusted Execution Environments (TEEs) lately. The gap between what they promise and what people actually get from them keeps getting wider, despite increased adoption. There&amp;rsquo;s this weird duality in the space: you&amp;rsquo;ve got teams absolutely struggling to get TEEs working reliably, and then you&amp;rsquo;ve got other teams running critical workloads on systems that are, frankly, incredibly flaky. Neither situation is great.
So let&amp;rsquo;s talk about what TEEs actually are, why everyone&amp;rsquo;s either excited or frustrated by them, and what it takes to use them properly.</description></item></channel></rss>