<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Elijah Udom | Infrastructure &amp; Cloud Engineer (elijahu)</title><link>https://elijahu.me/portfolio/tags/container-security/</link><description>Infrastructure &amp; Cloud Engineering portfolio by Elijah Udom (elijahu) — AWS, Kubernetes, eBPF Security, AI/ML Infrastructure, and Platform Engineering projects.</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Wed, 19 Mar 2025 00:00:00 +0000</lastBuildDate><atom:link href="https://elijahu.me/portfolio/tags/container-security/index.xml" rel="self" type="application/rss+xml"/><item><title>Building an eBPF Container Security Monitor: Debugging Through the Pain</title><link>https://elijahu.me/portfolio/projects/ebpf-container-security/</link><pubDate>Wed, 19 Mar 2025 00:00:00 +0000</pubDate><guid>https://elijahu.me/portfolio/projects/ebpf-container-security/</guid><description>&amp;ldquo;Monitoring containers without eBPF is whack-a-mole blindfolded.&amp;rdquo;
What started as a straightforward container security tool became a weeks-long exercise in kernel panics, parent process deception, and eBPF&amp;rsquo;s complete lack of forgiveness for sloppy code. This is the honest account of what it took to get it working.
Understanding the Fundamentals The Kernel The kernel controls everything — memory, devices, security. Every system call your containerized application makes passes through it.</description></item></channel></rss>