About Runtime Warden

RuntimeWarden exists because:

1. The hard part of security is no longer finding the problem; it is living with the fix.
2. Many people in this space never hear from a Christian voice.

The industry has gotten very good at spotting what is wrong in technology, and the next decade will be about governing systems that make their own decisions, at machine speed, while the business keeps running underneath them.

The short version is that runtime governance is bigger than threat detection. It is identity, authorization, policy, cost, and protection applied to everything while it is live, and it matters more now than the predictable services of the past. An agent decides what to do at runtime, reaches for tools, and occasionally does something nobody designed for. You cannot govern that with a checklist you ran at deploy time. You govern it at the boundary, in the moment, on a foundation you actually control.

Who is writing this

I'm Derrick Sutherland. I’m a man who desperately needs Christ like the rest of us (and quite frankly, not a huge fan of our current technology direction). However, my career spans nearly two decades and has been spent building secure, cloud-native platforms in hybrid and regulated environments, which is a long way of saying I've made a lot of complicated systems behave under real constraints. My background runs through microservice software development, Kubernetes, DevSecOps, single-sign-on frameworks, and infrastructure automation at scale. More recently, I've been getting pulled hard toward agentic AI governance, the identity, authorization, and policy problems that it feels like most people are asking questions about, but no one is really solving completely.

What you will find here

Christian articles about the real faith for those curious, and field notes on agentic security, Kubernetes, runtime protection, identity and SSO, gateway architecture, cost control, and prompt guarding. Some of it is hands-on, built and broken in my own lab before it shows up on the page. Some of it is thought pieces, because the space is young enough that the right questions are still being settled, and I would rather be useful than neutral. I try to write the way I would explain something to a sharp colleague who does not have the patience for fluff.

Where I stand

I am a follower of Christ, and that is not just a footnote on how I approach everything in my life; it is the root of it. If I'm being honest, I'm concerned for various reasons around how the technological landscape is evolving; however, putting my head in the sand is not going to solve these problems and not help people swim through these difficult changes.

I think technology this powerful deserves to be built by people who take stewardship seriously, who care about the downstream human cost of what they ship, and who are willing to say the responsible thing even when the aggressive thing is faster. You do not have to share my faith to get something out of what I write, but you should know where I am standing when I write it.

A note on independence

Everything here is my own view, written on my own time. It does not represent my employer, my clients, or anyone I work with, and nothing here should be read as their position. When I point to a tool or a vendor, it is because it is relevant to the argument, not because anyone paid for the placement.