Security engineer working where GRC meets infrastructure — I write the policy and the Terraform that enforces it.
I own the compliance framework and cloud security posture across three SaaS products, which in practice means my week swings between an ISO 27001 control narrative and a 2 a.m. kubectl describe pod. I started in Customer Success and ended up thinking like an attacker. The detour turned out to be the point: most security failures are communication failures wearing a technical costume.
B.Tech in Computer Science & Engineering, specialising in Cyber Security → MSc in Data Science. Which is a long way of saying I like problems that are half threat model, half dataset.
- 🤖 Autonomous SRE agent — detects and remediates GCP incidents (GKE, Compute Engine, Cloud SQL), and provisions new infrastructure straight from a PRD
- 🔐 ISO 27001 / SOC 2 programs, end to end — policy framework, vendor security reviews, audit scope, evidence
- 🧠 CIPHER — a RAG-based GRC assistant (n8n + Qdrant + GPT-4o) that answers control questions from the policy corpus → cipher.anmolseth.xyz
- ☁️ Cloud security posture and detection engineering across GCP + AWS
- 📱 Vibe-coding side projects when nobody's looking
Cloud security (GCP, AWS) · Detection engineering · ISO 27001, SOC 2, DPDP Act 2023 · Incident response · Turning compliance theatre into controls that actually run
Cloud & Infra
Security & Compliance
Languages & Automation
