DPO Radio

IAT Integration

Overview Image

Why IAT Integration Matters

You maintain one audit trail, not two. An AI tool with its own separate audit log leaves you with a second record to keep in step. The two drift, and reconciling them under inspection is costly. Forseti avoids that by writing every AI event to the same IAT that protects every other ComplianceOne event.

The same chain-of-custody anchor protects Forseti events and every other audit event. A tamper-evident proof is produced nightly, so auditors can verify the chain end to end and confirm that no event has been silently removed.

How It Works

Every Forseti Event in the IAT Chain

All of these are recorded in the IAT:

  • chats, tool calls and workflow runs
  • draft creation, approval and rejection
  • MCP calls, MCP write proposals and MCP approvals
  • memory curation
  • redline reviews

Shared Chain-of-Custody Anchor

Forseti events share the chain-of-custody anchor that protects record changes, evidence attachments and configuration changes. There is no separate Forseti audit chain.

Tamper-Evident Hash Chain

The IAT produces a tamper-evident hash chain nightly, which auditors can verify end to end. Silently removing any event would break the chain and show up in verification.

Regulator-Pack Export

Export anchored events through ComplianceOne's standard export to hand to a regulator. The export keeps the same hash anchoring.

Forensic Query Surface

Run forensic queries on the IAT: traces across records, queries over a time window, and queries isolated to one source. The Forseti Audit Lineage view is one of several places that read IAT events.

No Selective Omission

The IAT does not filter out "uncomfortable" events. Rejections, declined approvals, expired pending writes and declined MCP proposals all appear in the chain.

The Difference

Graphic Image

Without IAT Integration

Graphic Image

With Forseti IAT Integration

IconAI events live in a parallel audit system, separate from the main audit trail.
IconEvery Forseti event goes into the same IAT as the rest of ComplianceOne.
IconReconciling AI events with platform events requires manual cross-referencing.
IconOne shared chain-of-custody anchor, one audit record.
IconTamper-evident verification across both systems is difficult.
IconA nightly tamper-evident proof verifies the full chain.

Built for Auditable AI

Build For Image

What makes this auditable is the shared anchor: for chain of custody, the IAT treats AI events and other events the same way.

Build For Image

The tamper-evident hash chain is produced nightly and can be verified; removing an event breaks it.

Build For Image

The IAT export runs through ComplianceOne's standard export. The package you give a regulator holds AI events and other events together, with the same anchoring.

Overview Image

From a Research Event to a Decision

Use the Forseti audit lineage to connect logged work such as a workflow run or delegated reading to the review and the person's decision. Quote-check audit events record verification outcomes without copying the quoted source wording into the log.

Background Image

See IAT Integration in Action

See a regulator export that holds AI events and other events with the same chain-of-custody anchoring. Request a personalised demo.

Demo Image
Ronni K. Gothard Christiansen

Ronni K. Gothard Christiansen - Technical Privacy Engineer & CEO

Technical Compliance Expert, 32+ Years Open Source Advocate, X-BoD Open Source Matters Inc.

Or contact via

ronni@aesirx.io+84 909 500 760

Next Steps

Icon Image

Start a Compliance Pilot

Run a 30-day pilot and verify the nightly IAT proof with your internal audit lead.

Icon Image

Discuss Your Compliance Needs

Talk to our team about how IAT integration helps you prepare for inspection.

Frequently Asked Questions About IAT Integration

No. Every Forseti event goes into the same IAT as the rest of ComplianceOne, under one shared chain-of-custody anchor.

The IAT produces a hash chain every night that auditors can verify end to end. Silently removing any event would break the chain and show up in verification.

Yes. The IAT export runs through ComplianceOne's standard export, and the package holds all events with the same anchoring.

No. Rejections, declined approvals and expired pending writes all appear in the chain.

Yes. Light, Standard and Enterprise all include it. The audit trail is the same on every tier.