Identity Is the Perimeter You Forgot to Guard
Part 2 of the Cloud Security series
Wolkwacht topic
Security guidance built around ownership, identity, architecture and operational visibility.
Cloud security succeeds or fails through connected decisions: who owns risk, how identities are controlled, where boundaries exist and whether operational signals lead to action. These articles examine that system as a whole.
Recommended entry point
The clearest introduction to treating security as an operating system rather than a collection of products.
Selected reading
Part 2 of the Cloud Security series
Part 4 of the Cloud Security series
Most cloud security stories begin in the wrong place.
Azure Kubernetes Service (AKS) removes most of the undifferentiated heavy lifting of running Kubernetes, but it does not remove your responsibility for securing what runs on top of it.
Follow the thread
A practical sequence about architecture, identity, telemetry and ownership.
Automatically updated
The real question is not whether to use the Azure Key Vault provider for the Secrets Store CSI Driver or the External Secrets Operator (ESO). Instead, it’s whether your …
Kubernetes is very good at reporting desired state. A Deployment can be available while its pods restart every few hours. A cluster can show green nodes while workloads have no …
Azure Kubernetes Service (AKS) removes most of the undifferentiated heavy lifting of running Kubernetes, but it does not remove your responsibility for securing what runs on top of it.
In Part 1, we discussed the AppNet architecture, setup process, and waypoint model. This second part shifts focus from mechanics to…
Truth inside AKS with Inspektor Gadget
Part 6 of the Cloud Security series