Government guidance on AI agents, line by line.
For each requirement: what Ares does today, what needs configuration, and what it does not do. We map requirements. We do not certify your organisation.
One line of guidance. The part of Ares that answers it. Its state.
Each mapping takes a published guide or framework line by line. Next to each line is the part of Ares that answers it, and one of three states. Where Ares does not do something, the row says so and says who does. The guidance lines in the graphic are paraphrased. We check them against the published text before each update.
- Does today: it works now, with no extra setup.
- Needs configuration: Ares enforces it once you set the rule.
- Does not do: outside Ares, and the row says where it belongs.
Five mappings, one record behind them.
Canada: agentic AI guide
The federal Guide on the Use of Agentic Artificial Intelligence: review steps, logs the agent cannot change, agent identity, read-only access, an outside stop, and outside text treated as data.
Read the mappingEU AI Act
Logging, transparency, log retention, human oversight and deployer duties, article by article. The dates are stated as facts, with their status.
Read the mappingCSA agent identity
The Cloud Security Alliance buyer checklist for agent identity, with an honest answer per line, planned items included.
Read the mappingOWASP agentic top 10
The ten agentic risks, and which ones credentials, access policies, inspection and the record address. Some are outside Ares; we say which.
Read the mappingNIST AI RMF
Govern, map, measure, manage: what the record contributes to each. Plus the Canadian directive on automated decisions.
Read the mappingHow to read a mapping
Each row has a state and up to four parts.
- The state. Does today, needs configuration, or does not do. Where a feature is planned and not shipped, the row says planned. Where Ares covers part of a line, the row says partly today and names the part.
- What the guidance asks. Paraphrased, short. Read the source for the exact wording.
- What Ares does. The part of Ares that answers it: a credential for each agent and each job, an access policy checked on every call, inspection of content in and out, workflows with human approval, and the record of every decision.
- What the record shows. The evidence you hand an auditor, so you replay what happened instead of reconstructing it. Hand your auditor the replay pack and ares-verify, the open-source verifier, not a promise.
- What remains yours. No product makes a system compliant. Risk assessments, policies, people and the decision to deploy stay with you.
What these pages are not
This page maps Ares features to a published framework. It is not legal advice, and it does not certify compliance. Your obligations depend on your system, your role and your jurisdiction; check them with your counsel.
What it does not do
- Ares does not certify your organisation. We map requirements to what Ares does.
- It does not assess risk, or decide which of your systems are high-risk.
- It does not find agents you have not enrolled.
- The record shows what agents did, not whether a rule was wise.
Take the mapping into your review.
Tell us about the workflow under review. The architecture and security brief covers the architecture, the data flows and how the record is protected, at the depth these pages leave out. We send it after a short NDA.
A senior member of the team replies within two business days.