Agent Governance & Security

Guardrails, evaluation and monitoring for live agents.

Agents that act on real systems need the same controls as any system that touches money, customers or data. Twistag sets up the guardrails, tests and audit trail that let leadership, risk and IT sign off, and keep signing off.

A curved archive corridor lined with white drawers
Why governance

A pilot is approved once. An agent in daily use has to stay approved every day after.

  • 01An audit no one can answer. Which model made the decision, on what data, approved by whom.
  • 02Agents built by different teams, with different rules. No single view of what is running or what it may do.
  • 03A regulator, client or board asking for evidence. And the evidence lives in chat logs and memory.
What gets set up

Controls that run inside every agent.

Governance is built into the agents at runtime and into the release process, so every action is checked, logged and reversible.

  1. 01Agent registryEvery agent in use, its owner, its permissions and its risk class.
  2. 02Runtime guardrailsTool allow-lists and output schemas enforced on every call.
  3. 03Evaluation on every changeNo prompt or model change ships without passing the test set.
  4. 04Tracing and audit logsEach decision traced to input, model version, prompt and tool call.
  5. 05Human oversightReview queues, confidence thresholds and a way to stop any agent.
  6. 06Regulatory mappingEU AI Act classification and SOC 2 evidence, kept current.
ExampleAgent registry

Every agent, its owner and its risk

AgentOwnerRisk classActionsStatus
Invoice agentFinanceMinimal6Live
Email triageServiceLimited4Live
Contract reviewLegalLimited3Review
Forecast agentOperationsMinimal2Live
CV screeningPeopleHigh—Paused
Vendor chatbotMarketingLimited5Live
6 agents, 2 from vendors1 paused for review
How it runs

Four to eight weeks, set by the agents in scope.

Existing agents keep running while the controls go in. The set-up closes with a review with risk and IT.

Agents in scope
4 weeks
Inventory and risk classesWhat runs, who owns it, how risky
Guardrails and approval rulesAllow-lists, schemas, thresholds
Tracing and audit logsEvery call and decision recorded
Evaluation pipelineTest sets gating every release
Review with risk and ITSign-off and handover
An owner in risk or complianceAgrees the rules and signs off.
Access to agent code and logsRead access is enough to start.
A list of the agents in useIncluding pilots and vendor tools.
After set-up

Keep it running, extend it or hand it over.

Related work

Agents leadership can sign off.

All case studies
Questions

About agent governance.

Does the EU AI Act apply to the company’s agents?

It depends on the use case. Most internal agents fall in the minimal or limited risk classes; some, such as those used in hiring or credit decisions, are high risk. The set-up starts by classifying each one.

Can it cover agents Twistag did not build?

Yes. The registry, guardrails and tracing work with agents from vendors and internal teams, as long as there is access to their code or their logs.

Which tools does it use?

OpenTelemetry traces sent to Langfuse or the observability stack already in place, with evaluations running in the company’s own CI.

Does governance slow the agents down?

Runtime checks add little to each call. Most of the work happens up front: rules, thresholds and test sets.

Who owns the logs and data?

The company. Everything runs in its own cloud accounts and stays there.

What does it cost?

Cost follows scope: the number of agents, the systems they touch and the evidence the business needs. A proposal follows within a week of the first call.
More in AI & Agents

Other AI & Agents services.

AI & Agents overview
Talk to us

Let’s talk.

Tell us about the company and what it needs. A senior lead takes it from there.

A senior lead replies within one working day.

Agent Governance & Security

Tell us where work gets stuck.

A senior engineer replies within one working day.

Interested in

Thirty-minute call

Pick a time.