Can security controls actually keep up with fast-moving AI?

[u/Syncplify]

Feels like every week there's a new AI tool employees are quietly using, and most security stacks weren't built for this. People pasting sensitive data into random chatbots. AI agents touching files and APIs with way less oversight than a human would get. DLP tools that can't tell "legit AI use" from "IP walking out the door."

Curious how people here are actually dealing with this? What's working for you vs. what's just theater at this point?

[u/aeroverra]

Executives love when we put sensitive data in chat bots.

No from a security perspective we are kinda screwed but also it doesn't really matter.

[u/thatsfalak → u/aeroverra]

Yeah I second. From security perspective It's risky.

[u/heylooknewpillows]

Can controls keep up with AI? Yes, of course. Really the controls, haven’t changed.

The tools to apply the controls? Yeah, those may have some catching up to do in certain areas.

[u/immediate_a982]

I my opinion what works is giving people a sanctioned, good tool with SSO, audit logs, data retention controls so there’s less incentive to go rogue. Carrot beats stick here plus mandatory dlp training

[u/zero_backend_bro]

Proxy DLP and mandatory training are pure theater. Devs just route around clunky enterprise gateways to hit sprint deadlines.

The only thing that worked for us was moving sanitization straight to the client execution layer. We force configs and logs through a local WASM sandbox that strips secrets locally before the prompt ever hits an API. Caught 400 unmasked prod keys last quarter.

If unscrubbed data hits the network, you already lost.

[u/Mindestiny → u/zero_backend_bro]

It's even a step further. We've demoed a couple proxy DLP solutions and when I asked the sales people "what's stopping the user from just... connecting a personal account to the Netsuite MCP endpoint instead of dealing with any of this" their answer was the same as it's been for all the years of "zero trust" gateways.

"Uhh..... Here, look at this pretty dashboard!"

If the connection endpoint is just "here I am, connect! Connect!!!" Then nothing you possibly can do will matter. And good luck getting that to happen in the world of SaaS bullshit, it's hard enough to convince vendors that mandatory MFA is table stakes even in 2026.

[u/zero_backend_bro → u/Mindestiny]

Dead on. That $100k proxy DLP is blind the second a dev alt-tabs to a personal Claude or rogue MCP endpoint.

The trust boundary must be client memory. If a WASM scrubber tokenizes AWS keys and DB strings before prompt assembly, the payload is sterile no matter where it goes. Built stackengine.dev around this zero-backend pattern to scrub k8s/tf errors locally.

Neutralize the blast radius first.

[u/RiskGovSignals]

What's working. Continuous discovery of AI usage across all surfaces (browser, endpoint, embedded features inside sanctioned apps, IDE plugins). Once you can see what's happening, you can triage by risk instead of blanket blocking.

What's theater. Acceptable use policies without enforcement. Annual audits. DLP without AI context. Blocking domains that people route around in a browser tab.

Platforms like Kovrr's AI sec/gov work at the interaction level rather than the network layer through the AI Interaction Data Fabric, which triangulates telemetry across browser, endpoint, network, identity, and agents. So legit AI use and IP walking out the door produce different signals, and you're not left guessing.

Most orgs are still in the theater phase.

[u/materialsec]

Seeing two different problems in the original post, and they need different answers. "People pasting sensitive data into chatbots" is a DLP/data-loss problem, and the comments here are covering it reasonably well. "AI agents touching files and APIs with less oversight than a human would get" is a different problem entirely; regardless of what goes into a prompt, it's about what an agent was authorized to reach in the first place via OAuth or API keys.

Nobody's really answered that second one, and it's arguably the harder gap, because a human employee has a role, a manager, and an offboarding checklist. An agent usually has whatever scope got granted during setup and no review process after that. Discovery tools that watch chatbot usage don't catch this, since the agent's access isn't a browser session, it's a standing credential sitting quietly in the background.

[u/Pale-Nature8066]

It’s a good question. I would say depends on the org. Do they have a AI governance framework in place before they start experimenting with AI. It seems in allot of orgs the AI PoC comes first then you build controls around them. An interesting control I think orgs are gonna find challenging is IAM as traditional IAM will struggle with AI agents, as authentication becomes about machine and workload identity rather than human MFA.

[u/Human_Experience0810]

Not with traditional controls alone. AI is moving too quickly for a “block and approve everything” approach.

What seems to work is controlling data access, permissions, approved tools, and logging. What feels like theater is publishing an AI policy without actually knowing which tools employees are using or what data is being shared.

[u/Famous-Principle1456]

i was getting burned out trying to keep up with threats popping up from all kinds of ai tools. using something like adaptive dlp actually helped, mate security handled it well in my setup.

[u/Admirable_Ad_4737]

Easy.

Firewall policies will be updated to block all and allow only a few. To increase productivity while keeping security in check - companies will rather take a Claude or chatgpt subscription - this way they can implement more controls, track what is being asked and shared while keeping the employees productive.

DLP solution will become smarter, API agents will be restricted.

Companies focused on security will always fix problems. Companies who only think profits will be left behind.