PlainID

PlainID The identity leader built for the AI era - the only enterprise Runtime Authorization Platform.

27/10/2026

The agents aren’t waiting for your IAM strategy to catch up ⏳ Agentic IAM Day 2026 is tomorrow.

We’re going Beyond Who Gets In, into what your autonomous agents are doing right now and how to govern them with true Zero Standing Privileges.

Join IAM leaders from around the world who already do this in production as they share the playbooks that work and the failures they learned from. Here’s what we’ll cover:

✔️ The new identity crisis: policy sprawl, NHIs, and legacy IAM at its breaking point
✔️ Owning the MCP access path before it owns you
✔️ When agents become the business enabler, and how to scale them safely
✔️ A closing fireside chat on where IAM goes next: Zero Access

There’s one day left to save your spot 👉 https://hubs.ly/Q04CgpqP0

26/10/2026

The assumption we hear most from IAM teams: an AI agent is just another service account.

And it’s this assumption that quietly breaks their whole authorization model.

A service account is one known thing you request, approve, and provision once. An agent collects different credentials for different jobs, spins up for a single task, and disappears. It never asked permission to exist.

So the traditional loop - request it, wait for sign-off, get it provisioned - falls apart. The agents are already running. Most enterprises have several agent registries that don’t even know about each other, scattered across every hyperscaler and framework in the stack.

Which puts one question at the front of any agentic program: who owns this agent? If no one can name an owner, it has no business running inside your enterprise.

Gal Helemski and Andre Priebe, CTO of IC Consult, spent the session discussing exactly that, from discovering the agents you didn’t know you had to holding someone accountable for a fleet of them.

Watch the full recording: https://hubs.ly/Q04Cg6Cq0

23/10/2026

AI agents are now the main attacker behind most of 2026’s breaches. Almost none of it needed a new trick: 79% still came down to a stolen key, token or credential.

The finding comes from The State of the NHI & AI Agent Breach Report 2026, released this week by our friends at NHI Mgmt Group. They analysed 200+ real breaches from 2017 to October 2026, across more than 1,000 public sources. A few of the numbers that stood out to us:

✔️ 33 of the 53 breaches they tracked in 2026 involved AI agents, LLM platforms or AI attack routes.
✔️ 44% of all breaches began with a leaked, stolen or weak credential.
✔️ 56% involved more than one kind of non-human identity.
✔️ Supply chain is now the number one known way in, where one stolen token can reach every downstream user.

One leaked key rarely stays one key. A single credential reaches the next secret, then cloud roles, then the data, often without a single alert. And we know these credentials will most likely leak. What decides the damage is what that credential, or a hijacked agent, can reach once it is inside.

NHI Mgmt Group are very clear about the fact that the inventory, scope and short credential lifetimes matter more than any single control.

Controlling the scope and lifetime of access is the work PlainID does. We enforce runtime authorization and Zero Standing Privileges across human, non-human and AI agent identities, so a compromised key reaches only what policy allows at that moment, not everything it inherited.

You can access the full report here 👉 https://hubs.ly/Q04BT7NL0

22/10/2026

If you haven’t played Access Creep yet, you should give it a go!

It’s a short game about catching AI agents in disguise before they reach data they shouldn’t have access to. They hide in the flock, carry real credentials, and head for Payments, Customer Data, or HR Records. Your job is to spot them and keep them out, and the rules change on you mid-round.

We call that problem access creep, and it’s what Runtime Authorization handles in production: checking every identity, human or agent, against what it’s actually allowed to reach.

Catch enough of them and you land in the top 10 on the leaderboard, where you can win prizes!

Play here: https://hubs.ly/Q04B-RW10

Is your IAM strategy built for static human users, or autonomous AI agents?If you’re still relying on human-speed review...
21/10/2026

Is your IAM strategy built for static human users, or autonomous AI agents?

If you’re still relying on human-speed review cycles to govern machine-speed workflows, you aren’t just behind - you’re vulnerable.

In just 7 days, join us for Agentic IAM Day 2026, a free virtual summit designed to bridge the gap between autonomous innovation and enterprise security.

📅 October 28 | 🌐 Virtual Summit | 🎓 Earn 1 CPE Credit

Save your spot: https://hubs.ly/Q04BRZgq0

Search for an authorization tool today and the list runs long. So how do you pick the right one?✔️ One verifies the logi...
20/10/2026

Search for an authorization tool today and the list runs long. So how do you pick the right one?

✔️ One verifies the login.
✔️ One certifies access for the auditor.
✔️ One decides a request inside a single app.
✔️ One enforces what an agent can do while it runs.

They're all good at their job, but they might also solve a problem you did not have, while the gap you were worried about stays open.

So we wrote the guide we wanted to hand people who ask us this. It sorts 16 tools into five clear categories, shows what each one actually covers and where it stops, and gives you a five-question test that narrows a long list fast.

It also covers the tools you already run, because for most teams the real question is not which to replace. It is which layer to add on top.

Read it before your next vendor call 👉 https://hubs.ly/Q04BHr0k0

16/10/2026

One agent hands a task off to a sub-agent. The sub-agent calls a tool, and the permission from that first handoff no longer matches what the agent is doing.

The old access model decided permissions once, at login, with a coarse yes-or-no scope.

Agents don’t operate that way. They act on their own, across multiple hops, at machine speed, and every hop can carry more privilege than the task in front of it needs.

In our session with Ken Huang, who co-chairs an AI security working group at the CSA: Cloud Security Alliance, Kobi Gol from our product team walks through the architecture decision that makes or breaks this at scale, and what he sees enterprise customers doing instead of writing access logic into every agent.

The wider conversation with Ken also gets into:
✔️ Why an agent needs its own identity, separate from the human who triggered it
✔️ How each new sub-agent inherits more trust than it should, and why every hop needs its own check
✔️ How a poisoned MCP tool or agent skill, paired with an over-privileged identity, becomes data exfiltration
✔️ Why the audit trail of who asked, what the system decided, and which policy governed it becomes your accountability record when something goes wrong

Bottom line for the architects and AI platform owners watching: if your access control can’t re-evaluate at each hop, at runtime, with the human identity, the agent identity, the requested action, and the intent in context, it will not hold once agents call other agents.

Watch the full recording here 👉 https://hubs.ly/Q04B5yxn0

We ran a poll during our agentic IAM webinar and asked the participants how many AI agents are currently running inside ...
15/10/2026

We ran a poll during our agentic IAM webinar and asked the participants how many AI agents are currently running inside their organizations. Half of them couldn't answer.

You can’t authorize, govern, or assign accountability to an agent you’ve never discovered. And if nobody can see the agent, nobody owns it, which means nobody is accountable the day it does something it shouldn’t.

Most enterprises already run several disconnected agent registries across hyperscalers, agentic frameworks, and the SaaS tools that now ship their own agents. So before you do anything else, start with visibility: knowing which agents exist, and who owns each one. Policy comes after that.

In the session, PlainID's Gal Helemski and Andre Priebe, CTO of IC Consult, walked through the full agentic IAM architecture across five layers: agent identity, discovery, policy management, enforcement, and audit.

If you’re the IAM or security leader trying to bring agents under control before they multiply, you can watch the recording here: https://hubs.ly/Q04B5ykB0

Login was never the hard part. What an identity does after login is.In her SuperbCrew interview, our Co-Founder and CPO ...
14/10/2026

Login was never the hard part. What an identity does after login is.

In her SuperbCrew interview, our Co-Founder and CPO Gal Helemski explains how PlainID authorizes every human, machine and AI agent in real time, so an agent never gets more access than the person it works for.

Read the full interview here: https://hubs.ly/Q04B5y9p0

13/10/2026

2 weeks until Agentic IAM Day 2026!

When AI agents outnumber humans in the enterprise, access creep becomes the real risk. It's time to Go Beyond Who Gets In and control what non-human identities can do at runtime.

What to expect on Oct 28:
✔️ Real perspectives from IAM leads at Cisco, Databricks, Thales, Ericsson, Entrust, iC Consult, Humana, Onepoint, NHI Mgmt Group, Radware, EY, and more!
✔️ Practical playbooks for enforcing Zero Standing Privileges
✔️ 1 CPE Credit for live attendees

Don't miss out 👉 https://hubs.ly/Q04z-H9D0

Address

Tel Aviv

Alerts

Be the first to know and let us send you an email when PlainID posts news and promotions. Your email address will not be used for any other purpose, and you can unsubscribe at any time.

Contact The Business

Send a message to PlainID:

Shortcuts

Share