Abhishek Moitra

You’ve probably had that unsettling moment. You mention a product in conversation. Minutes later, an ad for it appears on your phone. The reaction is instinctive: “My device is listening.” Most of the time, it isn’t. What you’re seeing is something more structured and far more scalable:

If you’ve ever presented an Identity roadmap to senior leadership, you already know the moment it goes sideways. You’re walking through a carefully structured deck—authentication flows, federation standards, a multi-quarter MFA rollout plan. You mention SAML versus OIDC, device trust, or FIDO2. And then you notice it:

There is a familiar moment that many security leaders eventually experience, even if they rarely talk about it openly. You walk into a board or audit committee meeting with a carefully prepared quarterly security report. The data is clean. The visuals are polished. Most of the indicators are green. You

Introduction Consider a scenario where your lead architect just messaged the "Security-Incident" Slack channel with a single screenshot: a successful login to the production database from an account tied to a DevOps engineer who was offboarded six months ago. Ten minutes later, your auditor emails asking for the

An organization can pour resources into hardened perimeters and advanced endpoint detection, yet still leave itself exposed through neglected access rights. The most likely avenue for a serious compromise isn’t always a brand-new exploit it’s often an old, forgotten identity still carrying excessive privileges. These “orphaned” accounts service

The integration of cognitive automation into Identity and Access Management (IAM) is often obscured by "AI-washing," creating significant operational and regulatory risks. Organizations must transition from manual role mining to AI-based role harvesting to manage the explosion of non-human identities while maintaining human-in-the-loop governance to mitigate algorithmic bias