Article overview

Browse our latest articles exploring the tension between innovation and stability in software development

NuGet Packages: The Suppliers You Forgot to Audit

Published on 2/19/26 5:00 pm by Martin Stühmer

Every NuGet package is a supplier relationship under ISO 27001. Learn how to implement Central Package Management, automated vulnerability scanning, and package signature verification to transform your .NET dependency management from security liability into auditable compliance control.

Observability in AKS CNI Overlay: When Pod IPs Hide Behind Nodes

Published on 2/18/26 5:00 pm by Jendrik Brack

CNI Overlay masks pod IPs behind node IPs through SNAT, breaking traditional observability. Network logs show nodes, application logs show pods. Without Container Insights, correlation IDs, and distributed tracing, you’re debugging blind. SNAT port exhaustion mimics network failures, and timestamp-based correlation is fragile. The cost of proper monitoring is trivial compared to debugging outbound connectivity at 3 AM without visibility.

Your Azure SQL Is Public Right Now. ISO 27017 Demands You Fix It

Published on 2/17/26 5:00 pm by Martin Stühmer

That SQL Server you deployed last week? Publicly accessible. That Storage Account? Same story. Azure defaults are security theater. ISO 27017 calls this a compliance violation, and your next audit will too. Stop trusting “cloud-native” to mean “secure” and start implementing VNets, Private Endpoints, and NSGs before your data becomes someone else’s problem.

Your Incident Response Plan Is a Lie. Here’s How to Fix It.

Published on 2/12/26 5:00 pm by Martin Stühmer

That incident response plan in your Confluence? Nobody reads it. The on-call engineer can’t find it. And when your production API is bleeding at 3 AM, you’ll improvise—badly. ISO 27001 A.16 doesn’t care about your documentation theater. It demands procedures that work. GitHub Actions turns incident response from compliance fiction into executable reality.

AKS Cost Optimization: Resource Governance That Actually Works

Published on 2/11/26 5:00 pm by Jendrik Brack

AKS costs are brutally simple: node sizing, pod density, workload sprawl, and reserved capacity. If you don’t have visibility and governance, your cloud bill will punch you in the face—usually when it’s too late to react without pain. I’ve watched teams scramble to cut costs after the invoice lands, breaking production in the process. This guide is for practitioners who want to avoid that mess. No theory, no vendor fluff: just what actually works to keep AKS costs under control without sacrificing reliability.