Zero Trust Networks, 2nd Edition
The definitive guide to Zero Trust network architecture. Principles, design patterns, and implementation across modern infrastructure.
View on AmazonTwo decades building and shipping security products. Writing about what actually works in cloud, Zero Trust, and AI from someone who does the work.
Hands-on courses on Microsoft Foundry agents, Zero Trust for AI systems, attack anatomy, and identity. Recorded sessions and full archive on the speaking & training page .
Lessons from building real systems, written down.
The definitive guide to Zero Trust network architecture. Principles, design patterns, and implementation across modern infrastructure.
View on Amazon
Confidential computing on Azure applied through a Zero Trust lens. For architects and engineers building on Azure.
View on Amazon
Building applications across Windows Azure and Office 365. Cloud development patterns for the Microsoft ecosystem.
View on Amazon
The official Microsoft Press exam reference for SC-300. Identity and access management across Azure AD, hybrid environments, and Microsoft 365.
View on AmazonPosts from practice, not theory.
Final article in the five-part series on running Microsoft Entra Agent ID against third-party clouds. Closes the loop with the variants and failure modes that consume the same operational budget as the federated pattern without delivering its security properties, and ends with the takeaways worth pinning to the team wiki.
Fourth article in the five-part series on running Microsoft Entra Agent ID against third-party clouds. Opens up the Federated Identity Credential as a first-class object: single-tenant, cross-tenant SaaS shape, and the orthogonal world of on-behalf-of (OBO) where the agent acts for a signed-in user.
Third article in the five-part series on running Microsoft Entra Agent ID against third-party clouds. Pins down what the UAMI actually is in this architecture, why SAMI breaks federation, the three distinct Entra objects (UAMI, Blueprint, Agent Identity) and the three claims (sub, azp, oid) they each populate, and the production trade-off between federating the UAMI or the Agent Identity to the cloud.
New writing, when it lands.