FAQ

Questions about putting AI agents to work, safely.

Plain answers for security, risk and operations leaders. Can't find yours? Ask us directly →

The basics

What is EvidenceBound?

EvidenceBound is a control point for AI agents. It lets agents do routine work on their own, makes the risky few actions wait for a person to approve, and keeps a signed receipt of everything that happened. Security, risk and audit teams get one place to see, decide and prove what agents did.

What problem does it solve?

AI agents now pay claims, change records, update cloud systems and move money. To do that they are usually given standing access, and when an auditor asks who approved an action, nobody can answer. EvidenceBound removes the standing access, puts a person on the actions that matter, and gives you the proof.

Who is it for?

CISOs, heads of risk and compliance teams at companies putting AI agents into real operations, especially in financial services, healthcare, insurance and other regulated industries. It also suits software vendors whose enterprise deals stall in security review because their product includes agents.

Does it slow my agents down?

No. Routine actions keep flowing automatically; the policy check takes milliseconds. Only the actions you mark as risky, such as a large payment, a bulk data export or a production change, wait for a person.

Is EvidenceBound an AI agent or a model?

Neither. We don't build agents, host models or resell compute. We govern the agents you already use, from any vendor or framework, and we sit above your clouds rather than inside one of them.

How it works

How does approval work?

When an agent asks for a risky action, the right person gets a plain-language request in Slack, Microsoft Teams or the EvidenceBound console: what the agent wants to do, why, and what policy says. They approve or hold. Only that exact action runs, once.

What happens if the agent changes the request after it is approved?

It is refused before anything runs. An approval covers exactly what was approved. A different amount, a new bank account, a wider scope or a second attempt does not match, so it is stopped and recorded.

Do agents still hold passwords or production keys?

No. Approved actions run through an executor in your own environment, with credentials you hold. The agent asks; it never holds the keys.

What is a receipt?

A signed record of every outcome: what was asked, who approved it, what ran or was refused, and when. Receipts are tamper-evident, so an auditor can check them without trusting us or the agent vendor.

Can routine approvals be automated?

Yes, under your control. An administrator can switch on scoped, time-limited rules for patterns that are always approved. That administrator is named on every receipt, risky signals still go to a person, and a kill switch turns the rules off at once.

Getting started

How do we start?

With a free scan that shows which agents and automations can make risky changes today. Then a pilot in monitor mode: every agent action is recorded and nothing is blocked. When you're ready, you turn on approval for the few actions that matter.

How long does a pilot take?

About four weeks: one workflow, one team and one or two sensitive actions. Monitor mode is useful from the first day.

Does it work with our existing tools?

Yes. EvidenceBound connects to AWS, Kubernetes, GitHub Actions, Slack, Microsoft Teams, ServiceNow and Jira, Okta and other single sign-on providers, Splunk, Datadog, Microsoft Sentinel, Google SecOps and MCP-based agents, with SDKs for Python, TypeScript and Go. It also supports the OWASP Agent Control Standard.

Which clouds do you support?

EvidenceBound is cloud-neutral: one control point across your clouds and agent platforms. AWS and Kubernetes are supported today; other clouds follow customer demand.

Where does our data go?

Approved actions run in your environment, with your credentials. Receipts can be kept in your own storage and sent to your SIEM. We don't need copies of your customer records to govern an agent's actions.

Risk and audit

Does EvidenceBound make us HIPAA, SOC 2 or NIST certified?

No product can do that on its own, and we don't claim it. EvidenceBound produces evidence that a control actually ran, mapped to frameworks such as NIST 800-53, HIPAA, SOC 2 and CMMC. Your auditor or assessor makes the call.

How is this different from logging or monitoring tools?

Logs tell you what already happened. EvidenceBound sits in the path, so an unapproved or altered action is stopped before it runs, and the receipt proves it. It complements your SIEM rather than replacing it: receipts flow into Splunk, Datadog, Sentinel or Google SecOps.

How is this different from our cloud provider's agent controls?

Cloud providers govern agents inside their own cloud. Most companies run agents across several clouds and SaaS tools, and keep key controls above any single provider. EvidenceBound gives you one place for all of them, and works alongside the native controls.

Is there a price list?

Not yet. We are working with a small group of design partners and agree terms per pilot. The scan is free.

Start with a free agent scan.

Get started