Your directory knows which agent is calling. Ares decides what each job may do.
Keep the directory your IT team already runs. Ares works on top of it, then gives each job its own permission, inspects what passes, sends the sensitive steps to a person and records every decision.
A decade in defence and aerospace. In government procurement since 2016. The same technology since 2019, validated in US DoD and Canadian DND programs.
Directories now register AI agents the way they register people and applications. If you use your identity provider for AI agents today, keep it. Ares works with one directory product today, and others on request.
What agent features in your identity provider are good for
Knowing who is calling. Each agent gets an entry in the directory, an owner and a way to sign in. Your IT team already runs the directory, already reviews who has access, and already has a process to remove access when someone leaves. Agent features extend that habit to agents, and they are often part of a licence you hold. Some products add a gateway that limits which tools or services an agent may reach.
For a security lead this is the right first question: which agents exist, who owns each one, and can we switch one off. The directory answers it.
Where it stops
Identity says who the agent is. What this job may do is a separate question, and products in this category answer it in different ways. Some now scope access to a task, and some check a policy on every call through a gateway. Ask three questions of that layer:
- Does the permission narrow at each handoff? When one agent hands work to another, the helper should hold only what its part of the task needs.
- Can an outside party check the log without the vendor? An auditor should be able to verify every decision, refusals included, on a machine the vendor does not run.
- Who builds the workflow? The steps, their order, and the person who approves each sensitive step have to live somewhere.
Two more things usually sit outside that layer:
- Content inspection. A document is read before the agent sees it, so a hidden instruction in a supplier email is struck out. An answer is checked before it leaves.
- Approvals. A named person approves the sensitive step, in the system where it happens.
Side by side.
Who the agent is
- Agent features in your identity provider
- Its core job: a directory entry, an owner and a sign-in.
- Ares
- Taken from your identity provider. Each agent signs in as itself.
What one job may do
- Agent features in your identity provider
- Varies. Some scope access to a task. Ask whether it narrows when one agent hands work to another.
- Ares
- A credential for this job only. It expires, and it narrows at each handoff.
When access is checked
- Agent features in your identity provider
- Varies by product. Some check on every call through a gateway.
- Ares
- On every call the agent makes, against an access policy you can read.
Documents and answers
- Agent features in your identity provider
- Outside its scope.
- Ares
- Inspected on the way in, checked on the way out.
Sensitive steps
- Agent features in your identity provider
- Outside its scope, unless another product adds them.
- Ares
- Sent to a named person at the step you choose.
The record
- Agent features in your identity provider
- Sign-in and access logs, in the format of that product.
- Ares
- Every decision, refusals included, checked offline with an open-source verifier.
Who builds the workflow
- Agent features in your identity provider
- Your team, in another tool.
- Ares
- Your team on Ares, or we build it with you.
By category. Products differ and change often. Check the current version of yours.
How they fit together
Ares sits on top of your identity provider. It does not replace it, and it does not ask your IT team to run a second directory. The agent signs in through the directory you have. Ares then issues the credential for one job, checks the policy on every call, inspects what passes, runs the workflow and writes the record. When an agent leaves service, you remove it in the directory as you do today.
For your security review that gives two clear answers. The directory says which agents exist. The record says what each one did, step by step, including what it was refused. Security and data handling sets out where data goes and what is recorded.
They do a different job. They can work together.
What Ares does not do
- It does not replace your identity provider. It works on top of it.
- It connects to one identity provider product today. Others are on request, and the briefing confirms yours.
- It does not find agents that were never enrolled.
- Permissions are only as good as the rules you approve.
Questions and answers
Tell us about one workflow.
Name one agent and one system it acts in. We will say what your directory covers today, what Ares adds, and what the first step costs.
A senior member of the team replies within two business days.