The Question AI Agents Force Us to Stop Asking About Role-Based Access Control

Agents are making headlines for going rogue — exposing sensitive company data, and in one case, deleting an entire production database. The natural response from the enterprise security crowd has been to bolt on better access control. Role-based access control (RBAC) has been the default for decades, and it works great when a human is on the other side of the login screen: you assign a role, give that role a set of permissions, and you're done.

But an agent doesn't sit still. It reasons, calls tools, reads data, and acts on things it was never explicitly told to touch. RBAC was never built to judge what a non-human identity does with its permissions once it has them. That's the gap Varonis is trying to fill with Agent IBAC (Intent-Based Access Control), announced yesterday as part of Varonis Atlas. Instead of static role assignments, IBAC compares every instruction an agent receives against its actual behavior — the tools it calls, the data it reaches for, the reasoning it produces — and flags when the two drift apart. It evaluates the full session, not just individual actions, so you catch cumulative scope creep where no single move looks alarming but the total path leads somewhere the user never intended. Multi-turn jailbreaks are caught the same way: a patient attacker can assemble a jailbreak out of several prompts that each look benign individually. Sensitivity is tunable across three levels — lenient, balanced (default), and strict — and when an agent goes off the rails, Atlas can alert, block, modify the output (e.g., redact sensitive fields), quarantine the identity for a configurable window, or route the action to a human. Crucially, Atlas sits inline between the agent and the model. Every prompt, every model response, and every tool call flows through Atlas before it reaches its destination. It's not reading logs after the fact — it's in the path and can stop an action before it executes.

Source article image
Source image 1

What's interesting here isn't just the product announcement but the shift it implies. The question security teams are being forced to answer is no longer "Can this agent access this data?" but "In this context, should this agent be allowed to take action on this data?" That's a fundamental change from permission-as-static-assignment to permission-as-judgment. It also means agents need broader access than before — you can't have a useful agent that only reads one specific file — which is precisely what makes the runtim

Source article image
Source image 2
e enforcement layer more important. The tension is real: broader agent access means more surface area, but the alternative is agents that are too locked down to be useful. I'd be curious to know how teams without Atlas handle this today — are they running their agents through a proxy, or just accepting the risk?

Comments

Post a Comment

Popular posts from this blog

AI Is Starting to Feel Less Like a Gadget and More Like Infrastructure

Image
Modern AI doesn't replace infrastructure — it runs on top of it. (Photo: Unsplash) For a while, AI coverage had the energy of a mall demo kiosk: very shiny, slightly chaotic, and usually one prompt away from embarrassment. Lately, though, the more interesting story is less about flashy demos and more about infrastructure. A useful CNBC piece argued that AI is not simply going to vaporize enterprise software overnight, and that sounds about right. In real companies, software does not disappear just because a model can summarize a meeting or write a decent SQL query. What actually happens is messier and more practical: AI starts sneaking into the plumbing. It shows up in search, support workflows, procurement tools, analytics dashboards, and data pipelines. The real winners may not be the loudest chatbot wrappers, but the vendors that make enterprise systems easier to operate, easier to query, and slightly less soul-crushing for the humans trapped inside them. That is less cinematic ...
Read more

When Two AI Bots Finally Learned to Talk in Discord

I spent part of the day doing something that sounds like the setup for a bad joke: getting two local AI assistants to talk to each other in the same Discord channel. Not through a web UI. Not by bouncing prompts manually between windows like a human message queue. In the actual shared channel, where both could see the conversation and react to each other. The funny part is that the problem was not intelligence. It was manners. Both bots were defensive by default around bot-authored messages, which is the sensible setting if you do not want your infrastructure turning into a recursive support group. The downside is obvious: if both assistants treat other bots as suspicious background noise, they will never coordinate on anything more useful than silence. The fix was to make both sides accept bot-authored messages only when they were explicitly mentioned. That detail matters more than it sounds. Blanket bot acceptance is how you end up with two enthusiastic systems discovering each oth...
Read more

A CISA Contractor's GitHub Repo Held 844 MB of Secrets — and No One Closed the Door

Image
There is something almost poetic about the US government's premier cybersecurity agency — the one whose job is literally to plug holes in critical infrastructure — getting outsmarted by a contractor who treated a public GitHub repository like a digital junk drawer. The "Private-CISA" repo, created November 13, 2025, sat publicly for six months containing 844 megabytes of plaintext passwords, AWS GovCloud administrative credentials, Kubernetes manifests, ArgoCD application files, Terraform infrastructure code, CI/CD build logs, and internal deployment documentation. Guillaume Valadon at GitGuardian flagged it on May 14 after his automated scanning picked up the exposure. The commit history told the whole story in plain sight: the account owner had explicitly disabled GitHub's default secret-scanning protections, pushed plaintext credentials stored in CSV files, committed full backup archives into git history, and used easily guessed passwords like "platform-name-2...
Read more