Devices used to mean laptops and phones. Now they mean containers, microservices, and AI agents that can act on their own. This week's Zero Trust Foundations post runs the AAVI model through the Device pillar, with real 2026 breach headlines showing what happens when device and workload trust gets skipped, whether the "device" in question has a keyboard or not.

Zero Trust does not become real by buying a tool or redrawing the network diagram. It becomes real when we assess how trust is granted today, adapt existing controls, verify that the changes work, and keep iterating. This post introduces the AAVI model for turning existing environments into functional Zero Trust one protect surface at a time.

Before changing controls, we need to understand what our Zero Trust Architecture is supposed to do. This post uses the Five Pillars—Identity, Device, Network, Application, and Data—to show how legacy security assumptions can be evaluated and transformed into better trust decisions.

Grab a cup of coffee and pull up a chair. This post kicks off a new series for ZT Foundations where we will walk through some of the key ideas from my new book, ZT Foundations: Building Zero Trust with the Tools You Already Have. My goal for this series is simple: take the mystery out of Zero Trust, talk about it in plain language, and show how it can be built from practical decisions instead of shiny buzzwords. Over the next few weeks, we will compare traditional security st

Most GRC programs know how to prove they’re compliant. Zero Trust raises the bar by asking a harder question: how quickly can you eliminate implicit trust—and prove it with real signals, not just audit evidence?