Shift Smart, Not Just Left
Security bolted to a sprint is a tax. Built into the platform it’s invisible — and teams ship faster because of it. The paved road must be the secure road.
I engineer security the same way high-scale teams engineer reliability — as a system property designed, enforced, and continuously verified. Production behavior must remain predictable even under adversarial pressure.
Information Security Analyst (IC-2) at ZEE Entertainment, building security control planes across CI/CD, artifact supply chains, Kubernetes runtime, and GCP cloud governance — securing 350+ microservices so that insecure paths become operationally hard and secure delivery is the default.
Anshumaan Singh
Security Systems Engineer
@ ZEE Entertainment
Most security teams react. Watch alerts. Triage tickets. Ship reports. I build systems where the dangerous path is operationally hard before anyone notices it exists.
At ZEE Entertainment I secured 350+ microservices from code commit to production — not by reviewing more, but by making insecure releases structurally impossible. No bypass paths. No rebuilds in prod. No “we’ll fix it next sprint.”
I treat security the way reliability engineers treat uptime: with invariants. If a control can be bypassed — it isn’t one. If a gate produces noise — it erodes trust. If evidence doesn’t travel with the release — it doesn’t exist. That’s the philosophy behind everything I ship.
Six principles tested under production pressure — not borrowed from a framework.
Shift Smart, Not Just Left
Security bolted to a sprint is a tax. Built into the platform it’s invisible — and teams ship faster because of it. The paved road must be the secure road.
Identity is the Control Plane
Network perimeters trust the packet. I trust the identity. Short-lived, OIDC-federated, cryptographically verifiable — unforgeable by design.
Guardrails over Gates
Gates block. Guardrails guide. One kills velocity — the other multiplies it. Build systems where the safe path is also the easiest path.
Detection as Code
An alert no one acts on is just log noise with extra steps. Every detection I ship maps to a playbook and a decision — not a Slack ping.
Evidence over Assertions
Don’t tell auditors you’re secure — show them. SBOM linked to commit. Scan output signed. Promotion gate logged. Theater out. Evidence in.
Risk-based, Not Fear-based
Not every critical CVE is worth blocking. Not every low is safe to ship. CVSS + EPSS + reachability = one decision: block, allow with evidence, or accept with expiry.
Real pipelines. Real enforcement. Built for 350+ services — not a conference slide.
I don’t patch systems. I design them to hold under pressure — where invariants replace assumptions and every control is structural, not procedural.
Source to prod. No untrusted artifact reaches runtime. Every transition has a gate and a receipt.
SBOM / Attestation / Scan pipeline output
Proof-of-implementation artifact — real pipeline output, not a diagram.
Not hypotheticals. Not labs. These happened — here’s what I did.
✓ Reduced recurrence through enforcement + governance
✓ Fewer failures from scanner inconsistency
✓ Full commit-to-production traceability
✓ Improved coverage beyond static analysis
I model threats the way attackers think — not the way auditors check boxes. Kill-chain mapped. Response-ready. No theoretical vectors that can’t be exploited.
Saying you ran the scan isn’t evidence. Here’s what real pipeline evidence looks like.
Real pipeline artifact attached to a release. Not mocked.
Not every critical CVE should block a release. Not every low-severity is safe to ignore. This is how I separate signal from noise and keep engineering teams moving.
Two years. One team. One mission: make insecure releases structurally impossible across 350+ microservices.
ZEE Entertainment Enterprises Ltd
Information Security Analyst (IC-2)
M.Tech — Software Systems (Cybersecurity)
Work-integrated postgraduate: secure software engineering, applied security architecture, cloud security, IAM, and assurance across SDLC.
Vellore Institute of Technology, Chennai
B.Tech — Electronics & Communication Engineering
Engineering foundations: systems, networks, embedded systems, signal processing, and computing fundamentals.
Code I wrote. Problems I solved. You can see the commits.
What I’m actively pulling apart, rebuilding, and planning to ship next.
Tools I’ve shipped in production. Not a wish list.
Six industry exams. All passed. Click any to verify.

CKS
Certified Kubernetes Security Specialist
Verify on Credly ↗

CKA
Certified Kubernetes Administrator
Verify on Credly ↗

GCP Security
Professional Cloud Security Engineer
Verify on Credly ↗

GCP PCA
Professional Cloud Architect
Verify on Credly ↗

Terraform
Terraform Associate
Verify on Credly ↗

GCP ACE
Associate Cloud Engineer
Verify on Credly ↗
Google Cloud Skills Boost: View Profile ↗
Production-grade deployment of CrowdStrike Falcon sensor across Kubernetes clusters — runtime threat detection, DaemonSet topology, and Helm-managed rollouts.
A curated reference every security engineer must master — file inspection, network forensics, process analysis, log investigation, and system hardening from the terminal.
IAM hardening, Cloud Armor WAF, Security Command Center, VPC Service Controls, and posture management for enterprise GCP environments.
What each major compliance framework actually requires, where they overlap, and a pragmatic plan for implementation across engineering and security teams.
Real lessons from implementing cloud security across AWS, GCP, and Azure in production — what actually prevents incidents versus what is security theater.
If you’re building security that has to hold under pressure — or breaking systems to find out what doesn’t — I want to hear from you.