Google Researcher Says Windows NT Outclasses Linux as AI Agents Raise New Security Questions

Summary

Google researcher Laurie Kirk, a former Microsoft reverse engineer, argues that the Windows NT kernel has a more coherent architecture than Linux for managing resources and permissions. NT treats processes, files, devices, tokens, and other resources as objects controlled through handles, while its access tokens, ACLs, security descriptors, and audit controls attach authority to those objects. The article notes that NT’s 1995 C2 certification applied only to a standalone, non-networked system, so kernel design alone does not guarantee a secure Windows installation. Linux uses a more composable collection of UIDs, GIDs, file modes, capabilities, namespaces, cgroups, and security modules such as SELinux; Landlock and seccomp can also restrict an agent’s actions. Kirk’s current concern is that an AI agent can execute thousands of operations, run generated code, read files, and chain permissions without asking a user each time. Microsoft is addressing a similar problem with Execution Containers, which let developers declare agent access and enforce it at runtime, and with Agent Workspace isolation and ACLs. Kirk also imagines an “Open NT” that would let companies such as Amazon replace components while preserving a Microsoft-maintained compatibility and security contract. Linux developers counter that long-lived kernel forks are expensive because every security fix must be merged and retested, whereas Linux’s upstream model distributes maintenance. The discussion also acknowledges NT’s driver and compatibility baggage, Linux’s success in servers and cloud computing, and BSD’s capability-oriented alternatives. The article concludes that the real issue is how an operating system represents authority and proves what an agent did, not whether either kernel guarantees security by itself.