About
Vamshi Krishna Santhapuri
Infrastructure Security Architect · Hyderabad, India
I started as a NOC engineer in 2011. Since then I’ve spent Over a decade running Linux systems in production — bare metal, VMs, containers, Kubernetes clusters, cloud accounts across AWS, GCP, and Azure.
The title has changed over the years. The work hasn’t changed much: figure out what’s broken, why it’s broken, and make sure it doesn’t break the same way twice. Infrastructure security is the same job — except the blast radius is larger and the failure modes are subtler.
I’m not a vendor. I don’t sell a product. I write about what I actually see in production environments: IAM misconfigurations that have been sitting for two years, eBPF observability gaps that only become visible after an incident, Kubernetes RBAC setups that look fine on paper and fall apart under adversarial conditions.
What I Write About
Cloud IAM: From Zero to Master — a 12-episode series covering identity and access management across AWS, GCP, and Azure. From the foundational model to privilege escalation paths to zero trust architecture. Written for engineers who need to design, audit, or defend cloud access control at scale.
eBPF: From Kernel to Cloud — an 18-episode series on eBPF from kernel internals to production observability. Written for SREs, platform engineers, and security practitioners who want to understand what’s actually happening on their nodes.
Both series are also on Medium (@rrskris) and discussed on LinkedIn.
Where I’ve Been
Linux sysadmin → DevOps → SRE → Cloud Infrastructure → Infrastructure Security Architecture.
Every layer of that stack is still in use. When I review a Kubernetes cluster’s IAM setup, I’m also looking at the OS hardening, the network policy, the audit log configuration, and whether the monitoring stack would catch an attacker moving laterally. The depth comes from having worked every layer, not just the one with the security title.
Open Source
I build open-core infrastructure security tooling under Apache 2.0. Details on the Open Source page as projects go public.
Get in Touch
For consulting engagements: Work With Me
For everything else: LinkedIn is the fastest path. GitHub for code.