[ Solutions / SOX ]

Adopt AI agents under SOX

US-listed companies want AI in finance and IT, and their auditors want to know which user an agent is, what it can do, what it did, and who changed it. engini is the layer agents go through to reach NetSuite, SAP, Salesforce and your other systems, so it is where you scope them, record them and keep their changes clean. These five solutions map engini’s controls to the IT general controls your auditor already tests, and say plainly what stays with you.

ITGCCOSO 2013PCAOB AS 2201NetSuiteSAP S/4HANA
Read about engini skills →
Where engini sits in your control environment
  1. AI agents and workflowsClaude, ChatGPT, Cursor, your code
  2. enginitoolsets, connections, History, environments
  3. NetSuite logo
    Financial systemsNetSuite, SAP S/4HANA, Salesforce, Workday
  4. Your SIEM and ITSMaudit log streamed; tickets and sign-off
Illustration of the flow on this page, not a product screen.
For
Controllers, CAOs, IT audit and internal audit at SOX filers
Covers
Access, evidence, change management, access reviews, segregation of duties
engini holds
SOC 2 Type II, ISO 27001; GDPR and HIPAA compliant
Not offered
Human approval before an agent action, SCIM, SOC 1
[ 02 / The control map ]

What auditors ask about agents, and where the answer lives

Under Section 404, management assesses internal control over financial reporting, and the external auditor of an accelerated filer attests to it. The SEC names four IT general control areas that automated controls depend on: program development, program changes, computer operations, and access to programs and data (Release 33-8810). In February 2026 COSO published guidance on applying its framework to generative AI, stressing inventories of AI use, clear ownership and continuous monitoring (Journal of Accountancy).

The questions auditors raise about agents follow from those areas, and KPMG lists many of them directly: who can create or change agents, whether agent access is reviewed, whether logs of agent actions are kept, and whether agents have their own user IDs or share a service account (KPMG, 2026).

  • Which user is the agent, and what can it do? Toolsets and scoped MCP servers in engini; the ERP role on each connection. See agent access control.
  • What did it do, and who started it? engini records every run under the user who triggered it, with export and SIEM streaming. See the agent audit trail.
  • Who changed it, and was the change tested? Separate environments, environment-bound keys and export in engini; tickets and sign-off in your ITSM. See change management.
  • Is access reviewed? Read-only agents prepare the review; your owners sign off. See access reviews.
  • Can one actor do it all? Separate toolsets and accounts per duty; approval stays in the ERP. See segregation of duties.

What engini does not do

engini has no human approval step before an agent action, no SCIM or just-in-time provisioning, no data masking, and no SOC 1 report. It records the calls that pass through it, not the model’s reasoning. SOX compliance belongs to the issuer, and reliance is your auditor’s decision; engini gives you controls and evidence to build on.

[ 03 / Agent Policy ]

The agent does only what you allow. Every run is on the record.

Agent Policy is how you govern agents in engini: the tools each agent may call, the account each tool uses, and a record of every call.

Toolsets

Scope every call

Hand the agent a toolset: only the tools it needs, each on the connection you choose, for example read only. engini enforces it on the server for CLI, SDK and REST API calls; a call outside the toolset is refused. An MCP server exposes only the connections and tools chosen when you set it up.

Identity

Acts with the account you connect

engini acts with the permissions of the connected account. Connect a person’s own account and it acts as that person; use a shared integration account and it acts as that account. Every run is recorded under the user who triggered it.

Audit

History and audit log

Each tool call and workflow run is recorded in History and the audit log, which supports export and streaming to your SIEM. Your agent never needs your credentials: engini stores them and adds them when it runs each call.

SOC 2 Type IIISO 27001GDPRHIPAA compliant
[ 04 / 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 →
[ 05 / Questions ]

Questions buyers ask before they start

Can a SOX company use AI agents on its ERP?

Yes, if the agents sit inside the control environment like any other user or program: least-privilege access, a complete record of actions, controlled changes, periodic access review and segregation of duties. engini provides controls for each of these; your auditor decides on reliance.

Does engini make us SOX compliant?

No tool does. SOX compliance belongs to the issuer. engini gives you controls and evidence for the IT general controls that cover agents.

Does engini have a SOC 1 report?

No. engini holds SOC 2 Type II and ISO 27001 and is GDPR and HIPAA compliant. Your ERP stays the system of record, and your ERP-side controls plus your monitoring of engini’s audit log carry the financial-reporting controls.

Can a person approve an agent’s action before it runs?

Not inside engini; there is no human approval step before an agent action. Keep approval in the ERP’s own approval routing, and give agents accounts that cannot approve or post.

Where should we start?

With read-only agents on one financial system, through a toolset or a scoped MCP server, with the audit log streamed to your SIEM. That gives finance value and gives IT audit a record from day one.