HYCU's Free aiR Graph Maps Every Agent in Entra ID and Okta, Then Asks If You Can Recover

Thu, 08 Oct 2026 20:33:18 +0000

Ask an IT leader how many AI agents are running in their company and you'll usually get a pause. Ask which of those agents can delete data and the pause gets longer.

That's not negligence. Agents don't arrive through one front door. A team turns on a copilot. A developer registers an app in Entra ID so an agent can write to Salesforce. Someone grants an OAuth scope in Okta so a workflow agent can run overnight. Each decision makes sense on its own. Together they add up to a population of non-human identities nobody counted, with permissions nobody reviewed as a set.

HYCU is going after the counting problem first. The company made aiR Graph generally available today, free to any organization, customer or not. It connects read-only to Microsoft Entra ID, including Entra Agent ID where it's enabled, and to Okta, including Okta AI Agents where an organization subscribes. On the first scan, it maps the applications in the tenant and flags the copilots and agents among them.

For each agent, aiR Graph pulls the details you'd want before trusting it with production data: its OAuth scopes, which data sources it can read and which it can write, whether it has organization-wide access, whether it acts unattended, how many people can invoke it, and whether anyone is recorded as its owner or sponsor.

"Every organization we talk to is adding AI agents faster than it can count them," said Simon Taylor, HYCU's founder and CEO.

An inventory is useful. But knowing an agent exists doesn't tell you what happens when it goes wrong. That's where aiR Graph goes further than most agent inventories. It adds a protection gap view that asks a blunt question: if this agent damages the data it can reach, is there an independent copy to recover from? Agents with write access to systems of record that have no backup rank first.

That ordering follows an argument HYCU has been making for months. When I talked with Amarnath Rampratap, HYCU's head of R&D India, in September, he said the root cause he sees most isn't a bad prompt. "Nearly every incident that reaches us has an over-scoped, long-lived token in the chain," he said. The PocketOS incident is the public example: a Cursor agent found a Railway token with far more reach than its job required, and one API call took a production database and its backups with it. aiR Graph is designed to find that kind of credential before an agent uses it.

Severity in aiR Graph tracks capability. The more an agent can reach and change, the higher it ranks. HYCU's examples of top findings include unattended access to all user data, broad access combined with write or delete rights, and enabled accounts whose agent identity has been deleted. That last one deserves a second look. An agent can be retired while the account behind it stays live, which leaves a working credential with no one watching it.

Jerome Wendt, CEO and principal analyst at DCIG, put the gap plainly: "Knowing an agent can modify data in Salesforce, GitHub, or Confluence only identifies the risk." The other half is whether you can undo what the agent did.

The design choice developers will notice most is what HYCU left out. "We made a deliberate choice to keep language models out of the risk assessment," said Anant Chintamaneni, HYCU's chief product officer. Every finding comes from an explicit rule applied to identity-provider data. "Run it twice on the same tenant, and you get the same answer," he said. And each finding traces back to the identity field that produced it.

That matters more than it might seem. A risk score generated by a model is hard to defend. If two runs disagree, which one goes to the auditor? Which one goes into the ticket? With deterministic rules, the difference between two scans reflects a real change in the tenant, not variance in the model. You can rerun the assessment after tightening scopes and see exactly which findings cleared. There's some irony in a tool for governing AI agents that keeps AI out of its own judgment. But it's the right call for something security and compliance teams will be asked to stand behind.

When a scan finishes, one click produces a point-in-time assessment report with an executive summary, recommended triage actions, and the full inventory. HYCU first showed the tool at the IT Press Tour in Ljubljana last month, and select customers ran it in preview before today's release.

A few things to keep in mind before you run it. Entra ID and Okta are the first discovery sources, and HYCU says more are coming. Discovery runs through the identity provider, so an agent whose credentials never touch Entra ID or Okta, like a personal access token sitting in a CI secret store, won't show up there. The report is a snapshot, not continuous monitoring. And the protection gap view naturally points toward HYCU R-Cloud, which covers more than 100 workloads. The tool is free, but it also shows HYCU exactly where its backup product fits. That doesn't make the findings less accurate. It's just worth knowing.

For developers who've built agents themselves, the most useful exercise may be the simplest one. Run the scan, find the agents your team registered, and compare the scopes they hold against the scopes they need. Then check whether the systems they can write to have a copy they can't reach.

Most teams can't answer the two questions this piece started with. Now there's a free way to get a first answer to both, and a third question worth asking after that: if one of these agents goes wrong tonight, what do you restore from in the morning?

Coder Legion - Recent posts tagged dataresilience

HYCU's Free aiR Graph Maps Every Agent in Entra ID and Okta, Then Asks If You Can Recover