Skip to content
Agent count

Find every AI agent running in your company

Part of the 7-day Agentic Trust Review

Some of your AI agents log in as your employees. When one goes wrong, the log blames a person who was asleep. The agent count gives you the list, with an owner on every row.

Why can't you just ask your teams what agents they're running?

You can ask. You'll get a short list, and it'll be wrong.

People build agents without calling them agents. A script with an API key (a password for software). A copilot someone hooked up to a shared drive over a weekend. A survey misses both.

So the count skips the survey. Your team pulls the data straight from your systems, using our method.

Why you can't control the AI agents you never counted →

86%
of AI agents ship without security approval.
Source: Gravitee, Feb 2026

What's an agent identity census?

It's a count of every AI agent in your company. Each one gets a row: what it does and who owns it. It's part of our 7-day Agentic Trust Review.

Agents leave tracks in six places. Your team pulls from all of them:

  • Your identity provider (your login system), like Okta or Entra ID.
  • Your secret store, the vault for software passwords.
  • Your build pipeline accounts. These ship your code.
  • Your AI gateway logs. They show which tools call which AI models.
  • Your laptop and server data. It shows what's running where.
  • Your expense reports. They show who's paying for AI tools.

We give your team the method for each pull. Then we read what comes back.

What does the agent count give you?

Four things, all in writing.

  1. 01

    The list

    One row per agent. What it does, what it logs in as, the kind of password, the owner, the backup owner, and what it can reach. Your team builds it.

  2. 02

    The four findings

    We sort every agent into four problems, with counts. Agents logging in as a person. Agents sharing one login. Keys that never expire. Agents whose owner already left.

  3. 03

    The risk ratings

    Each finding gets a risk rating in the Review's written report. They're ranked, so you know what to fix first.

  4. 04

    The roadmap

    A 30/60/90-day roadmap, riskiest first. Your team can start the first 30 days on Monday.

Why start with identity?

Every other AI control needs a name to work.

To stop an agent, you need to know which one it is. To handle an incident, you need a person to call.

That's why the Agentic Trust Framework starts with identity. Its first question for every agent is: who are you? Answer that, and the other four get easier.

See how the Agentic Trust Framework compares to other AI frameworks →

Who's this for?

Security and tech leaders at regulated companies of 1,000 to 10,000 people. Your agents are already live. And something's forcing the question: an audit finding, a board question, a customer security questionnaire, or a fresh incident.

If your agents are still in planning, start with the free assessment. Come back when they're live.

Who reads the results?

The people who wrote the standard.

We wrote the Agentic Trust Framework. The Cloud Security Alliance published it in February 2026. Thirty days later, Microsoft's Agent Governance Toolkit filed a formal conformance assessment against it and scored 25 of 25. Nobody asked them to.

John Kindervag, who created Zero Trust, wrote the foreword to our book, Agentic AI + Zero Trust.

Our founder, Josh Woodruff, is Co-chair of the CSA Zero Trust Working Group. He's also Founding Chair of the Agentic Trust Framework at the CSAI Foundation.

We've built identity teams and the rules for non-human identities (the logins that software and agents use) inside heavily regulated companies.

That's who reads your results.

Why every AI agent needs one accountable human →

What does the agent count leave out?

The count finds problems, and the report recommends fixes. Your team makes every change.

Rotating keys and moving passwords come next, once you know what you have. Code review and tool buying sit outside the Review too.

Vendor-neutral. No products to sell. Ever.

Frequently asked questions

  • How much of your team's time does it take?

    Your identity and platform teams run the six pulls. We're on hand for questions while they do. Then we sort the results.

  • Does a CMDB already cover this?

    A CMDB (the list of systems IT tracks) knows what your teams added to it. Agents get built outside that process. The count goes straight to your identity provider and expense reports.

  • Can your team run the count on its own?

    Your team does run the pulls. What we bring is the method: where agents hide, and how to sort what comes back. Teams that go it alone usually find the agents they already knew about.

  • Does the count cover all five questions?

    It covers the first one: who are you? The rest of the Review scores all five. The Agentic Trust Framework calls them Identity Management, Behavioral Monitoring, Data Governance, Segmentation, and Incident Response.

  • What happens after the Review?

    You start on the first 30 days of the roadmap. If you need a check against all 25 requirements and a plan with an owner on every step, that's the 30-day Agentic Trust Blueprint.

    See all three lengths →

  • What does it cost?

    The agent count comes with the 7-day Agentic Trust Review. We scope the Review with you, then quote it. To start smaller, take the free assessment or the Advanced ATF Assessment at $5,000.

    See the Agentic Trust Review →

The list of every agent in your company exists somewhere.

Right now it's split across six systems and three people's memories. Give it seven days. You'll have it in one place, with an owner on every row.