Compliance

Achieve an audit-ready posture for every AI agent

Continuous compliance for AI agents starts with full visibility into what every agent does at runtime. IntentGate captures every authorization decision the agent makes, signs it into a tamper-evident chain, and exposes the evidence in the formats your auditor already expects.

Why it matters

Use an authorization gateway to make AI compliance demonstrable

An authorization gateway in front of your AI agents is the cleanest way to prove control. Every tool call passes through one place, the decision is recorded with the policy that produced it, and an auditor can replay any window on demand.

Staying compliant is more than adhering to the law. It is about protecting your organisation and the trust customers place in it. Companies running AI in production now face a long list of regulations and standards, including the EU AI Act, GDPR, NIS2, DORA, ISO/IEC 27001, ISO/IEC 42001, and SOC 2 Type II, that mandate strict controls over what AI systems can do and what records the operator must keep. Falling short brings fines, reputational damage, and operational disruption.

Per-framework mapping

How IntentGate maps to each framework

Seven of the regulations and audit standards enterprise buyers ask about. Each card below tells you, in one paragraph, what the framework is actually about and what IntentGate gives you for it. Click through for the full mapping.

EU regulatory

EU AI Act

Europe's law for high-risk AI systems. The company running the agent has to keep a continuous record of what the AI does and prove a human is overseeing it. IntentGate writes that record automatically for every tool call the agent makes.

View mapping →
EU regulatory

GDPR

Europe's data-protection law. You need a record of how personal data gets processed, and the record itself has to be tamper-evident. IntentGate logs every agent action and signs the log with a hash chain so nothing can be rewritten after the fact.

View mapping →
EU regulatory

NIS2

Europe's cybersecurity directive. When a significant incident happens you have 24 hours to file an early warning, 72 hours for an update, and a month for the full report. All three pull from the same gateway audit stream, so there is no scrambling across systems while the clock runs.

View mapping →
EU financial services

DORA

Europe's resilience rule for financial services. Major IT incidents have to be reported in a fixed format. What failed, when, who was affected, how it was contained. IntentGate captures those fields on every authorization decision, so the incident report writes itself from the audit log.

View mapping →
ISO standard

ISO/IEC 42001

The first ISO standard for managing AI systems. The auditor does not just want a written policy that says "we control our AI". They want proof the controls actually ran. IntentGate is that proof: every agent decision logged, signed, and replayable from the audit chain.

View mapping →
ISO standard

ISO/IEC 27001

The mainstream information-security standard. Its long control checklist (Annex A) now expects you to govern AI agents the way you govern people: least privilege, access reviews, full audit trail. IntentGate handles those controls for the agent side, the same way your IAM handles them for humans.

View mapping →
US audit attestation

SOC 2 Type II

The attestation US enterprise buyers ask for before they sign. Type II is not a snapshot of your controls today. It is proof they ran correctly every day for 6 to 12 months. IntentGate makes that proof automatic: every gateway decision is a signed audit event, so there are no gaps to explain.

View mapping →
How IntentGate helps

The control plane your compliance team already wants

Three things every compliance team asks for when AI agents enter production. IntentGate ships all three by default.

1

Per-call policy enforcement

Every tool call passes through one gateway. The Rego policy that produced each decision is pinned to the audit row, so the auditor sees which rules were in force at the moment the AI acted.

2

Tamper-evident audit chain

Decisions land in a hash-chained Postgres store; any modification breaks the chain and is verifiable in one command. Export in OCSF-aligned ndjson into your SIEM, or sign a window for the auditor on demand.

3

Ready-made framework mappings

Seven regulations and audit standards mapped article by article to the gateway output that satisfies each obligation. No translation layer between what the gateway captures and what the regulator wants to see.

Want the mapping for your specific audit?

Each organisation has a different combination of regulations and a different audit cycle. We can walk through the mapping for your specific obligations in a 30-minute call.

Start the conversation