[ SOX / Access to programs and data ]

AI agents with least-privilege access, under SOX

engini gives each AI agent only the tools it needs on your financial systems, each on an account you choose, and records every run under the person who triggered it. So when your auditor asks which identity an agent uses in NetSuite, SAP or Salesforce and what it can do, you have an answer that fits your access controls.

NetSuiteSAP S/4HANASalesforceITGC: logical accessCOSO principle 11
Read about engini skills →
An agent reads AP aging, with a read-only toolset
  1. Agent asks for open vendor billsClaude, through the SDK, toolset ap-readonly
  2. engini checks the toolsettool in scope: netsuite.get_records
  3. NetSuite logo
    Runs on the read-only connectionNetSuite role: AP Viewer
  4. Run recordedtriggered by analyst@example.com
Illustration of the flow on this page, not a product screen.
What it is
Least-privilege access for AI agents on in-scope financial systems
Control area
ITGC: access to programs and data
engini provides
Toolsets, scoped MCP servers, identity of the connected account, run records
You still own
ERP roles, who may create agents, the periodic access review
[ 01 / The problem ]

Auditors now ask which user an AI agent is

Under SOX Section 404, management assesses internal control over financial reporting, and for accelerated filers the external auditor attests to it. The SEC’s interpretive guidance names four IT general control areas that automated controls depend on: program development, program changes, computer operations, and access to programs and data. An AI agent that reads or writes NetSuite, SAP or Salesforce is a new actor inside the access area.

That is where projects stall. A finance team wants Claude or ChatGPT to pull aging reports and draft reconciliations, and the first question from IT audit is simple: what account does the agent use, what can that account do, and who reviews it? KPMG’s 2026 paper on agentic AI in financial reporting puts it plainly, asking whether agents are assigned specific user IDs with roles and permissions or run with a shared service account, and warning that shared service accounts weaken the audit trail.

Why the usual shortcuts fail an access review

  • A personal API token pasted into an agent carries everything that person can do, including posting.
  • One integration user shared by every script and agent shows up in the ERP log as one name, so nobody can tie an action to a person.
  • Long-lived keys sit in prompts, notebooks and config files, outside any access review.
  • New agents appear without an owner or an inventory record, which ISACA flags as a core agentic AI audit risk.

What least privilege looks like for an agent

Treat the agent like any privileged system actor: give it a defined set of actions, on an account whose ERP role matches the job, with every action traceable to a person who can be asked about it. engini is the layer where that happens. Your ERP keeps its own roles and logs; engini decides which of its tools an agent can call and on which connection, and keeps the record.

[ 02 / How it works ]

Four steps to a governed agent your auditor can follow

Built from controls engini ships today. The review and sign-off steps stay with your people, outside the agent run.

01 / Connection

Connect the right account

Connect NetSuite, SAP S/4HANA or Salesforce with an account whose ERP role fits the job, for example a read-only AP role. engini stores the credentials and adds them to each call, so the agent never handles them.

02 / Toolset

Hand the agent a toolset

Build a toolset with only the tools the agent needs, each on that connection. engini enforces it on the server for CLI, SDK and REST API calls: the agent only discovers those tools, and any other call is refused.

03 / MCP

Or a scoped MCP server

For Claude, ChatGPT or Cursor, create an MCP server that exposes only the chosen connections and tools. The client signs in over OAuth, and engini shows who uses each MCP server.

04 / Evidence

Keep the record

Every run is recorded under the user who triggered it, in History and the audit log, which you can export or stream to your SIEM. Add engini users, connections, toolsets and MCP servers to your quarterly access review.

[ 03 / What the agent reads and writes ]

Where each control lives

engini adds a scoped layer in front of your systems. It does not replace the ERP’s own permission model.

SystemRecordsAccess
enginiToolsets, MCP servers, connections, users, roles (custom roles included), workspaces and environmentsConfigureAudit log
NetSuiteThe role on the connected account: which record types and permissions it holdsReadWrite by role
SAP S/4HANAThe OData service and the SAP user or OAuth client on each connectionReadWrite by role
SalesforceThe connected user’s profile and permission setsReadWrite by role
Your SIEMThe streamed audit log, under your own retention and reviewRead
[ 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 least privilege under the line "Each agent, only the tools it needs", and three labels: toolset, connection, run recorded

Editorial image: one agent, one scoped route into each system.

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: every Monday at 7:00, read open vendor bills from NetSuite with my read-only connection, summarize bills older than 60 days by vendor, and post the summary to the #ap-review channel 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 engini enforces, and what it does not

Say it the way your auditor will test it. These are the controls engini ships; the gaps are listed too.

Enforced

Scope and identity

Toolsets limit which tools an agent may call and which account each uses, enforced on the server for CLI, SDK and REST API calls. Toolsets belong to the user who made them, so someone using an agent cannot widen it. MCP servers are limited by their own configuration.

Recorded

Every run, under a person

engini acts with the permissions of the connected account and records every run under the user who triggered it. The audit log supports export and SIEM streaming.

Platform

Who may use engini

SSO (SAML and OIDC), two-factor authentication, session timeout, IP and country filtering, roles including custom roles, workspaces, and API keys tied to one workspace and one environment.

Not offered

Know the gaps

engini has no human approval step before an agent action, no SCIM or just-in-time provisioning, and no data masking. Toolsets do not apply to MCP servers or workflows. Plan your compensating controls around these.

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 make us SOX compliant?

No tool does. SOX compliance belongs to the issuer and is tested by its auditor. engini gives you controls and evidence for the access part of your IT general controls: scoped toolsets, the identity of the connected account, and a record of every run.

Which identity does the agent use in NetSuite or SAP?

The account behind the connection. Connect a person’s own account and engini acts as that person, with that person’s ERP permissions. Use a shared integration account and it acts as that account. Either way, engini records each run under the user who triggered it.

Can an agent do more than we allowed?

Over the CLI, SDK and REST API, an agent with a toolset only discovers the tools in it, and engini refuses any call outside it. An MCP server exposes only the connections and tools chosen when it was set up. The ERP role on the connection still applies on top.

Do agents ever see our ERP credentials?

Your agent never needs your credentials: engini stores them and adds them when it runs each call, so keys stay out of prompts and tool inputs.

Does engini have a SOC 1 report?

No. engini holds SOC 2 Type II and ISO 27001 and is GDPR and HIPAA compliant. engini is not the system of record for transactions; your ERP is. Auditors typically rely on your ERP-side controls and on your monitoring of engini’s audit log, and the SOC 2 Type II report can support conclusions on related IT general controls.

How do we remove a leaver’s access?

Through your normal process: remove the user in your identity provider and in engini, and revoke their connections. engini does not offer SCIM or just-in-time provisioning, so include engini in your deprovisioning checklist and quarterly access review.

Can a person approve an agent action before it runs?

Not inside engini: there is no human approval step before an agent action. Keep approval where it already lives, in the ERP’s own approval routing, and give the agent a connection whose role cannot approve or post.