Threat Modeling the System That Actually Exists
A useful threat model tracks live trust boundaries, administration paths, transition states, recovery systems, evidence dates, and the changes that made the old model wrong.
Latest
Inspect Both Sides of the LLM Conversation
A practical policy and configuration guide for detecting prompt injection and jailbreak attempts before inference, then blocking unsafe content and sensitive-data disclosure before model output reaches a user, tool, or application.
Prompt Injection Is an Authorization Failure with Words Attached
After reading my post on AI firewalls, a friend asked for my take on prompt injection. Prompt injection becomes dangerous when untrusted content can steer a software principal into using authority that the content never possessed.
Book
·
Mastering Ubuntu Server, Fifth Edition: Strong Foundations with a Few Sharp Edges
A hands-on review of Ken VanDine and Jay LaCroix's practical guide to Ubuntu Server 26.04, based on the supplied Early Review Copy.
Do AI Firewall Sidecars Make Sense with Vendor-Hosted LLMs?
A reader of the Cybersecurity Architect's Handbook Second Edition recently asked whether the Kubernetes sidecar pattern discussed in Chapter 13 applies only when an organization hosts its own large language model. The short answer is no.
Seeing Cybersecurity Architect’s Handbook in the Wild Never Gets Old
Seeing a well-read copy of Cybersecurity Architect’s Handbook, Second Edition out in the wild never gets old.
Watching the Network You Built - Network Security Part 2
Part 2 puts the security in motion: services, the monitoring pipeline your log lines feed, wireless done currently, safe remote access, and where it all leads.
The Packet Walk Comes First - Network Security Part 1
Network security is controls placed where traffic must pass. Part 1 builds the floor: addressing, switching, routing, and your first enforcement reps.
windows
·
Windows Fundamentals for Cybersecurity, Part 2: The Server Assumes You Are Elsewhere
Part 1, The Machine and Its Evidence established one working rule: the GUI shows you what exists, and PowerShell is how you inspect it precisely and repeat the work across ten machines. Windows Server administration assumes you are somewhere else...