Ceros is live! The first trust layer built for the agents your IAM stack never planned for.
Your AI agents act with your credentials, on devices your IdP did not issue, calling tools your security team did not sanction. Today that gap closes.
Ceros launches today as a control plane purpose-built for autonomous agents. Five-dimension identity on every agent session: who is running it, how they were authenticated, whether the device is compliant, what tools the agent can touch, what configuration it launched with. Continuous policy enforcement across every action.
If you're at Identiverse, we're at booth 545 with two demos: AI discovery (the inventory you did not run) and live policy enforcement (the agents that stopped before they did the wrong thing).
https://t.co/0w7HiJMzJq
We're at Identiverse this week. Booth 545. Tomorrow we ship something the team has been heads down on for a year.
A category of identity that did not need to exist five years ago is now the most important control plane in your stack: the agents.
The MCP servers running on your developers' laptops. The Claude session that calls your CRM API. The internal automation that just got a key with read-and-write to your data warehouse.
Identity was not built for any of them. We rebuilt it for all of them.
If you're at Identiverse, come find us at booth 545. Tomorrow you'll see the rest.
https://t.co/0w7HiJMzJq
Tried to come up with a clever name for our new deploy flow.
Couldn’t. So it’s Big Easy Deploy.
Get Ceros running in your environment fast: secure agent sessions, full visibility into every agentic action. This week on https://t.co/JKvA8B0Af4
Great video. We spent a lot of time digging into exactly this. Anthropic's compliance API doesnt cover Claude code so how do you actually get visibility into what your devs' coding agents are doing? The agents running on a desktop, the most dangerous ones
This is why we built Ceros.
We put a harness on the machine right next to the agent so you know
1) which user actually invoked the agent
2) which process spun it up and full ancestry chain
3) what each tool call actually did to the machine, how it modified it, exact commands and args, what came back
all of the stuff needed to tell you why the agent did something
🚀 Import your Claude code settings today!
Just dropped in @beyondidentity Ceros: drop in your Anthropic managed-settings.json and instantly get way more granular access control.
Anthropic’s out of the box access controls apply policy org-wide.
But what if a user or group need an exception to an org wide policy?
Ceros lets you enforce these policies by user, group, device posture… and now even argument-level on tools & MCP servers
Manage your agents today with Ceros! Hit me up for a cool demo
someone has to actually build this stuff
Ceros, what we're building at @beyondidentity , handles exactly what you listed. firewalls, secrets management, granular process controls. all without slowing your team down
would love to show you what we're building if you're ever curious
Sanctioning an AI tool ≠ governing it.
A developer runs the Claude Code you approved, but logged in with a personal account. This means your managed config doesn't apply and your audit trail sees nothing.
The agent is sanctioned. The session is not.
Three gaps most security teams miss, and how to close them: https://t.co/JD4mPkuWo7
@ListenLabs Always interesting to see how different teams approach credential infrastructure in the agentic era. We went deep on the same problem building Ceros. Happy to compare notes if you ever want an outside perspective ✌️
Security leaders using Claude Code, how are you actually controlling permissions at org scale?
We just shipped Ceros: identity-scoped rules, continuous device checks, and cryptographic audit trails on top of Anthropic's native system.
The missing layer is here: https://t.co/USNUxnhCmG @beyondidentity@AnthropicAI
I was skeptical at first too, but found the power is being able to share the skill with a team. We keep a lot of internal documentation and decision making documents in a git repo along with skills to maintain it. So we have skills like /style-check , /daily-brief, /pingme, /transcribe, etc. everyone who contributes to the repo automatically gets the skills
@Austen Were building the trust layer for agents! Check out Ceros from @beyondidentity . Our thoughts on the credentialing problem, and our solution here: https://t.co/DOYUd5n1QU
I saw a tweet about the OAuth outage this morning and immediately forwarded it to my team with the message "how do we use this."
They did not respond for six minutes.
I sent a follow up that said "this is urgent."
They got on a call.
I told them I needed to walk into the executive meeting at 2pm looking like I had been thinking about cognitive infrastructure failover strategy for YEARS. Not hours. Years.
My head of strategy, God bless him, said "what is a cognitive infrastructure failover."
I said I don't know but the guy on Twitter seemed very upset about it so it must be important.
We spent 90 minutes building a deck.
I walked into that boardroom and I told those executives that the planet was losing IQ points every time frontier AI stuttered and that we needed a plan.
Our CEO looked at me for a long time.
Then he said "put together a task force."
I have never felt more powerful in my life.
I do not know what the task force will do.
Neither does anyone else.
That's the point.
If you're not turning random tweets into executive strategy by 9am you are already behind. 🔄