[ SOX / Evidence ]

An audit trail for every agent action

engini records every tool call and workflow run that passes through it under the user who triggered it, in History and an audit log you can export or stream to your SIEM. So when an auditor asks what an AI agent did in NetSuite, SAP or Salesforce last quarter, and who started it, you can produce the record instead of reconstructing it.

NetSuiteSAP S/4HANASalesforceSIEMAS 1105 evidence
Read about engini skills →
What gets recorded
  1. Agent runs a reconciliationstarted by a staff accountant
  2. engini runs each tool callon the connection you chose
  3. Run recorded under the userHistory: inputs, results, status
  4. Audit log streamedto your SIEM, under your retention
Illustration of the flow on this page, not a product screen.
What it is
A record of every agent call and run, tied to a person
Control area
Evidence for access and operations ITGCs; monitoring
engini provides
History, audit log with export and SIEM streaming, retention settings
You still own
The review of agent activity, retention policy, IPE documentation
[ 01 / The problem ]

If it is not in the log, it did not happen

The SEC’s guidance on internal control over financial reporting says management is responsible for maintaining evidential matter, including documentation, to provide reasonable support for its assessment (Release 33-8810). An AI agent that reads or changes financial data is part of that picture, and the evidence for what it did has to exist, be complete, and be traceable to someone accountable.

ISACA is explicit about agents: every action taken by an AI system should be logged in an audit trail that records who or what initiated it (ISACA, 2025). KPMG warns that agents running on shared service accounts weaken the audit trail, because the ERP log then shows one integration user for every action (KPMG, 2026).

What auditors will ask for

  • Every action an agent took in the period, on which system, with what result.
  • Who started each run, so a person can be asked about it.
  • Evidence the log is complete and retained for the period you need.
  • How the listing you hand over was produced, since PCAOB inspectors keep finding untested system-generated reports (PCAOB, 2025).

What engini records

Calls from agents (over MCP, the SDK, the CLI or the REST API) and workflow runs execute through engini, and each is recorded in History under the user who triggered it, even when the connection is a shared integration account. The audit log supports export and streaming to your SIEM, and retention is configurable. Data is encrypted at rest with AES-256 and in transit with TLS 1.2 or later.

engini records the calls that pass through it. It does not record what an agent does by other paths, and it records tool calls, not the model’s reasoning. Keep prompts and conversations in the agent platform if you need them.

[ 02 / How it works ]

From agent run to audit evidence

The record is engini’s job. The review and the retention policy are yours.

01 / Route

Route agents through engini

Give agents access to financial systems only through engini connections, MCP servers and toolsets, so their calls are recorded in one place.

02 / Attribute

Tie runs to people

Every run is recorded under the user who triggered it. Use personal connections where the ERP log should show the person too.

03 / Keep

Export and stream

Stream the audit log to your SIEM and keep it there under your record-retention rules, or export it for each audit period.

04 / Review

Review it like any log

Assign an owner to review agent activity on a set schedule, and document how the listing is produced so it holds up as evidence.

[ 03 / What the agent reads and writes ]

Where the evidence lives

SystemRecordsAccess
engini HistoryEach workflow run and tool call: user, time, inputs, results, statusRecorded
engini audit logAccount activity, exportable and streamed to a SIEMExportStream
Your SIEMLong-term retention, correlation and review under your controlsRead
NetSuite, SAP, SalesforceEach system’s own audit trail, under the connected accountRead
[ 04 / Build it with the engini skill ]

Describe it in plain words. The engini skill builds the workflow.

engini skills is engini’s plugin for Claude Code and Codex. Its workflow agent, Flo, turns a plain-language request into an engini workflow: it designs the steps, dry-runs them against your own engini account, shows you a proposal, and creates the workflow only after you approve it, always turned off. You check it in the engini designer and turn it on.

Blurred landscape photo with the word on record under the line "Every agent action, under a person", and three labels: History, audit log, SIEM

Editorial image: every action, on the record.

Claude Code: install once
/plugin marketplace add engini/skills
/plugin install skills@engini
Then ask for this solution
Build a workflow in my engini account: on the first business day of each month, read last month's workflow run history for the workflows in folder "Finance agents", count runs by workflow and by user, list failed runs, and post the summary to #it-audit in Slack.
  1. You need an engini account, the engini CLI (npm i -g @engini/cli) and a workspace-scoped API key, ideally a dedicated least-privilege one.
  2. Connect the systems this flow uses in engini first. Flo never creates or changes a connection and never handles your key; it tells you which command to run.
  3. Flo checks your login and workspace, searches the tool catalog, compiles the plan and shows a proposal table with every step. It creates the workflow only when you approve that proposal, and it creates it turned off.
  4. Open it in the engini designer, fill anything it left for you, and turn it on.
engini skills for Claude Code and Codex →
What the skill will never do on its own →
[ 05 / Agent Policy ]

What the record covers, and what it does not

Recorded

Every call through engini

Tool calls from MCP, the SDK, the CLI and the REST API, and every workflow run, recorded under the user who triggered it.

Exported

Export and SIEM streaming

The audit log supports export and streaming to a SIEM. Retention in engini is configurable by plan; keep long-term copies in your own systems.

Protected

Platform controls

AES-256 at rest, TLS 1.2 or later in transit, SSO, two-factor authentication, roles and IP filtering. SOC 2 Type II and ISO 27001 certified.

Not covered

Know the edges

Actions agents take outside engini, the model’s reasoning, and the content of prompts. engini has no SOC 1 report and no human approval step before an agent action.

SOC 2 Type IIISO 27001GDPRHIPAA compliant
[ 06 / Try it now ]

Build it on your own data today

Start free, connect your systems, and build this flow with the engini skill, in Workflow Studio, or from your own agent.

  • 01Workflow Studio. Build the flow on a visual canvas, with an AI agent step where judgment is needed. Start free →
  • 02Your own agent. Give Claude, ChatGPT or Cursor an engini MCP server with only these tools. MCP client setup →
  • 03The engini skill. Ask Flo in Claude Code or Codex and review its proposal. Install the skill →
[ 07 / Questions ]

Questions buyers ask before they start

Does engini log every AI agent action?

Every tool call and workflow run that passes through engini is recorded under the user who triggered it. Actions an agent takes by other paths are outside engini’s record, which is why routing agents through engini matters.

Can we send the audit log to our SIEM?

Yes. engini’s audit log supports streaming to a SIEM and export.

Does the record show the person or the service account?

engini records each run under the user who triggered it, even on a shared integration account. The ERP’s own log shows the connected account, so use personal connections where the ERP log should show the person too.

Does engini record the model’s reasoning or prompts?

No. engini records the tool calls it runs, with their inputs and results. Keep prompts and conversations in your agent platform if your policy requires them.

Can the exported log be used as audit evidence?

That is your auditor’s call. Treat the export like any system-generated report: document the source, the parameters and how completeness is checked.

How long are logs kept?

Retention in engini depends on your plan and settings. For SOX periods, stream or export the log and keep it under your own retention policy.