Scale AI without scaling risk. Govern developer, device, and agent access in one enforcement layer.
Joined March 2020
- Tweets 3,435
- Following 532
- Followers 18,470
- Likes 2,141
1,063 Photos and videos
Our Head of Product Marketing @KasiaatBI moved into the engineering Gitlab repo. Not to learn Git but to compress distance between product context and marketing distribution 🧵
2
1
250
Full writeup: beyondidentity.ai/blog/what-…
127
It turns out a lot of marketing is repetitive tasks fitted to different contexts. So she built Skills in Claude Code that enforce brand voice, kill AI slop, and pull directly from product specs.
Output: nurture sequences, sales outreach, one pagers, ad copy. All grounded in facts of what actually shipped.
1
118
Pushing it one step further, she built a sign up > HubSpot > enrichment > dashboard automation pipeline.
No engineering ticket. No backlog. A marketer, working in a repo, shipping ops infrastructure. 🤯
57
Beyond Identity retweeted
Your AI agent will do whatever it's told.
Not just by you.
Every tool result is a potential prompt injection and it doesn't have to happen all at once.
Jasson Casey from @beyondidentity calls it the Ron Burgundy problem.
Who's checking yours?
#cloudsecurity #AIsecurity
2
3
243
Step 1: build an agent to manage the deluge of security alerts
Step 2: give said agent credentials and access to do its tasks
Step 3: HOLY SH*T FIGURE OUT HOW TO GOVERN SAID AGENT
Or our security engineer’s adventures building with @claudeai and securing the autonomous agent
1
3
363
Mar 31
Our Ceros dev team shipped three new features this week 🧵
1
1
1
264
Mar 31
3⃣ Chat agent with MCP access: make policy changes from the console or from CLI directly with Claude
1
76
Mar 26
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: beyondidentity.ai/blog/whats…
198
Every new AI agent your team ships = another API key living somewhere you don't fully control.
Nobody's doing anything wrong. That's just how credential checkout works at scale.
The problem compounds quietly until it doesn't. We wrote about what the architecture looks like when you stop distributing secrets to endpoints entirely, check it out:
beyondidentity.ai/blog/crede…
1
2
6
468
Feb 17
Your devs are using AI agents. Do you know whose API keys they're using? Or if their device is secure?
Ceros is an agentic AI trust layer that gives you visibility and control.
- Bind sessions to verified identities
- Enforce device posture
- Vault API keys in hardware
- Control tool & MCP server access
Public preview is now open. Read the announcement: beyondidentity.ai/blog/intro…
5
252
Beyond Identity retweeted
Jan 16
AI has made research 10x faster but the new bottleneck is coordination costs and sharing insights.
We're trying GitHub-first at @beyondidentity: pull what the team contributed overnight, ask Claude "what changed that I should know?" What are other teams trying?
1
2
298
14 Nov 2025
IT teams spend 40% of their time on account lockouts. It's not just costly, it’s avoidable. Not only is Beyond Identity passwordless (no more password resets!) we're also keeping customers ahead of the game with a new self remediation feature: beyondidentity.com/resource/…
226
6 Nov 2025
AI accelerates both defender and adversarial workflows. Great breakdown!
5 Nov 2025
Google Threat Intelligence Group details the ways threat actors are misusing AI tools, including how they are generating and executing AI-enabled malware.
🔗 Read this latest report on our blog: bit.ly/47EzWCq
369
5 Nov 2025
Time to go passwordless
4 Nov 2025
If you feel like you're bad at your job and it's making you depressed, just consider that, as the investigation of the recent heist revealed, the password to access the Louvre's videosurveillance system was "Louvre".
1
379