<feed xmlns="http://www.w3.org/2005/Atom"> <id>https://naorhaziz.com/</id><title>Naor Haziz</title><subtitle>Security researcher, Rust devotee, and speaker at fwd:cloudsec and Black Hat USA. My work sits at the intersection of cloud workloads and OS internals, with a focus on real-world impact and sturdy code.</subtitle> <updated>2026-02-17T16:12:31+02:00</updated> <author> <name>Naor Haziz</name> <uri>https://naorhaziz.com/</uri> </author><link rel="self" type="application/atom+xml" href="https://naorhaziz.com/feed.xml"/><link rel="alternate" type="text/html" hreflang="en" href="https://naorhaziz.com/"/> <generator uri="https://jekyllrb.com/" version="4.4.1">Jekyll</generator> <rights> © 2026 Naor Haziz </rights> <icon>/assets/img/favicons/favicon.ico</icon> <logo>/assets/img/favicons/favicon-96x96.png</logo> <entry><title>irql: Compile-Time IRQL Safety for Windows Kernel Drivers in Rust</title><link href="https://naorhaziz.com/posts/irql-compile-time-irql-safety/" rel="alternate" type="text/html" title="irql: Compile-Time IRQL Safety for Windows Kernel Drivers in Rust" /><published>2026-02-17T16:00:00+02:00</published> <updated>2026-02-17T16:00:00+02:00</updated> <id>https://naorhaziz.com/posts/irql-compile-time-irql-safety/</id> <content type="text/html" src="https://naorhaziz.com/posts/irql-compile-time-irql-safety/" /> <author> <name>Naor Haziz</name> </author> <category term="rust" /> <category term="windows" /> <category term="kernel" /> <category term="open-source" /> <summary>It started with a different problem entirely. I was writing a Windows kernel driver in Rust and hit something that bothered me: when Rust’s alloc fails, it panics. In user-mode, that’s a crash. In kernel-mode, a panic is a blue screen. Every Box::new, every Vec::push – any allocation that runs out of memory takes down the entire machine. That’s not acceptable for a driver that might run on mil...</summary> </entry> <entry><title>ECScape: Understanding IAM Privilege Boundaries in Amazon ECS</title><link href="https://naorhaziz.com/posts/ecscape-iam-privilege-boundaries-in-ecs/" rel="alternate" type="text/html" title="ECScape: Understanding IAM Privilege Boundaries in Amazon ECS" /><published>2025-07-21T16:00:00+03:00</published> <updated>2025-08-04T20:25:18+03:00</updated> <id>https://naorhaziz.com/posts/ecscape-iam-privilege-boundaries-in-ecs/</id> <content type="text/html" src="https://naorhaziz.com/posts/ecscape-iam-privilege-boundaries-in-ecs/" /> <author> <name>Naor Haziz</name> </author> <category term="aws" /> <category term="ecs" /> <category term="security" /> <category term="cloud" /> <summary>This post is Part 2 of our educational series on Amazon ECS security. In Part 1 – Under the Hood of Amazon ECS on EC2, we explored how the ECS agent, IAM roles and the ECS control plane provide credentials to tasks. Here we’ll demonstrate how those mechanisms can lead to a known risk when tasks with different privilege levels share the same EC2 host. This cross-task credential exposure highligh...</summary> </entry> <entry><title>Under the Hood of Amazon ECS on EC2: Agents, IAM Roles, and Task Isolation</title><link href="https://naorhaziz.com/posts/under-the-hood-of-amazon-ecs/" rel="alternate" type="text/html" title="Under the Hood of Amazon ECS on EC2: Agents, IAM Roles, and Task Isolation" /><published>2025-07-16T16:00:00+03:00</published> <updated>2025-08-02T12:34:12+03:00</updated> <id>https://naorhaziz.com/posts/under-the-hood-of-amazon-ecs/</id> <content type="text/html" src="https://naorhaziz.com/posts/under-the-hood-of-amazon-ecs/" /> <author> <name>Naor Haziz</name> </author> <category term="aws" /> <category term="ecs" /> <category term="security" /> <category term="cloud" /> <summary>When running containers on Amazon ECS using EC2 instances, there’s a lot happening under the hood on each host. Understanding these internals is crucial for operating ECS securely. In this first part of our deep‑dive, we’ll explore how ECS on EC2 works – focusing on the ECS agent, the IAM roles and credential delivery mechanism, and where the boundaries (and lack thereof) lie between tasks on t...</summary> </entry> </feed>
