Cross-Industry
Automated Financial Forecasting & Audit Trails
Minimal RiskUnverifiedDiscuss / dispute
Cross-ledger aggregation, scenario simulation and draft financial statement assembly with a reviewable audit trail, presented to finance leadership for sign-off.
Classification rationale: Inside the ICFR boundary: figures that reach a reporting cycle need traceable inputs, documented assumptions and a reconciliation to the ledger. SOX §404 makes the model itself a control to be designed and tested, and IFRS/US GAAP govern whether the generated statement is even admissible.
Indicative decision support, not legal advice. Risk classification depends on your concrete deployment context and can change with scope drift — validate the result with qualified counsel.
pricingPer completed financial model / reporting cycle
oversightCFO audit sign-off on a proposed-forecast review interface; no automatic posting to the ledger
Compliance brief
This use case is minimal-risk under the EU AI Act (Minimal Risk); no product-specific obligations beyond general AI literacy apply.
What is owed
- Art. 4. Providers and deployers must ensure sufficient AI literacy of staff dealing with AI systems.
- Art. 25. A deployer becomes the provider (full Art.
Dates that bind
- 2026-08-02 — General applicability + Art. 50. Transparency obligations for chatbots, deepfakes and synthetic content; EU-level enforcement begins.
- 2026-12-02 — Additional prohibitions. Additional bans (deepfake CSAM et al.) and transition period for synthetic content under Art. 50(2).
Maximum exposure
- Sarbanes-Oxley Act (SOX §302 / §404): Certification liability for officers, adverse ICFR opinions, SEC enforcement.
- EU AI Act: Tiered: €35m / 7% (prohibited practices); €15m / 3% (Art. 9–15 high-risk obligations incl. data governance, documentation, logging); €7.5m / 1% (Art. 99(5) — incorrect, incomplete or misleading information to notified bodies or national competent authorities)
- SEC Rule 17a-4 (US Records Retention): SEC enforcement; multi-hundred-million-dollar off-channel/recordkeeping penalties are routine.
First five actions
- Confirm in writing whether this organisation builds/places the system on the market (provider) or only operates it (deployer), since the role is not yet established.
- Commission and confirm the Art. 4, Art. 25 obligations named above as active workstreams with an accountable owner.
- Stand up the named oversight design — Mode 1 — with a documented human-review procedure.
- Produce the technical documentation and evidence artefacts already mapped to this use case (Zero-Data-Retention Vendor Binding, WORM / Immutable Audit Vault, Ephemeral Execution Isolation) before they are requested.
- Put 2026-08-02 — General applicability + Art. 50 — into the compliance calendar with an owner and lead time.
Terms used above: · · ·
Applicable Regulations (5)
Sarbanes-Oxley Act (SOX §302 / §404) (15 U.S.C. §7241 / §7262 (Sarbanes-Oxley §302 / §404))
in-force · verified 2026-08-06 source Cornell LII
Management certification and internal control over financial reporting. Once an agent aggregates ledgers, drafts financial statements, or approves procurement variances, it sits inside the ICFR boundary: the control needs documented design, testing evidence, segregation of duties and an auditable trail of every automated adjustment.
Sanctions: Certification liability for officers, adverse ICFR opinions, SEC enforcement.
EU AI Act (Regulation (EU) 2024/1689)
unverified · no verification date source EUR-Lex
Horizontal, risk-based product-safety law for AI systems and GPAI models. Extraterritorial market-place principle. Staged applicability 2025–2030 (Digital Omnibus: Annex III → 2 Dec 2027, Annex I → 2 Aug 2028).
Sanctions: Tiered: €35m / 7% (prohibited practices); €15m / 3% (Art. 9–15 high-risk obligations incl. data governance, documentation, logging); €7.5m / 1% (Art. 99(5) — incorrect, incomplete or misleading information to notified bodies or national competent authorities)
SEC Rule 17a-4 (US Records Retention) (17 CFR 240.17a-4)
unverified · no verification date source eCFR
Broker-dealer record retention: electronic records must be preserved in non-rewriteable, non-erasable (WORM) or audit-trail form, indexed and reproducible on demand. Retention is tiered, not flat — 17a-4(a) requires six years for blotters, ledgers and customer account records, while 17a-4(b) requires three years for the broader category of communications, trade confirmations and supporting records.
Sanctions: SEC enforcement; multi-hundred-million-dollar off-channel/recordkeeping penalties are routine.
Art. 26 — Deployer Obligations
unverified · no verification date source artificialintelligenceact.eu
Use per instructions, assign competent human oversight, input-data control, log retention ≥ 6 months, inform workers, incident duty.
Art. 12 — Record-Keeping / Logging
unverified · no verification date source artificialintelligenceact.eu
Automatic, tamper-evident event logging over the system lifetime, serving three regulatory objectives: risk identification (Art. 79), post-market monitoring (Art. 72) and deployer oversight (Art. 26(5)). Deployers retain logs ≥ 6 months; financial institutions fold them into statutory internal audit documentation. A bolted-on logging wrapper does not satisfy the requirement — logging must be core architecture.
Legal Obligations (2)
Art. 4 — AI Literacy
Providers and deployers must ensure sufficient AI literacy of staff dealing with AI systems. In force since 2 Feb 2025.
unverified · no verification date read the article artificialintelligenceact.eu
Art. 25 — Value Chain / Role Flip
A deployer becomes the provider (full Art. 8–17 duties) by re-branding, changing intended purpose, or making a substantial modification — e.g. deep fine-tuning or wiring a model into autonomous agent toolchains.
unverified · no verification date read the article artificialintelligenceact.eu
Control Objectives (0)
obligation (article) → operationalized_by → control objective → satisfied_by → component/pattern; control objective → evidenced_by → evidence artifact
Art. 4
control layer: community mandate — propose objectives
Art. 25
control layer: community mandate — propose objectives
Take this into your GRC tooling
A control mapping your ISO/IEC 42001 or CSA AICM workbook can ingest, and an Annex IV skeleton to start the technical file from. Indicative mappings only — cells we are not confident about are exported empty rather than filled in.
Standards & Evidence
IFRS / US GAAP Reporting Assurance
Recognition, measurement and disclosure rules that any AI-assembled financial statement, forecast or scenario model must satisfy. Model-generated figures need traceable inputs, documented assumptions and a reviewable reconciliation to the ledger before they enter a reporting cycle.
in-force · verified 2026-08-06
evidence for: Sarbanes-Oxley Act (SOX §302 / §404)
IEEE CertifAIEd™
Ethics certification (transparency, accountability, algorithmic bias, privacy) for products and professionals; interfaces with the EU ALTAI assessment list.
unverified · no verification date
evidence for: EU AI Act
FprEN ISO/IEC 24970 (AI Logging)
Specifies event logging in AI systems — the concrete implementation target for Art. 12 record-keeping.
formal-vote · verified 2026-08-04 publisher ISO
evidence for: Art. 12 — Record-Keeping / Logging
TAGOF (Audit-as-Code)
Operationalizes governance as code in CI/CD: policy-as-code enforcement, continuous runtime telemetry and automatically generated audit evidence — the execution layer that replaces periodic audits with continuous assurance.
unverified · no verification date
evidence for: Art. 12 — Record-Keeping / Logging
Architecture Blueprint
Agentic RDA Stack (6 Layers)
Regulatory Design & Architecture framework for agentic systems: (1) isolated ephemeral execution (gVisor/Firecracker, read-only root, egress allowlists) → (2) agentic zero-trust identity (per-agent ID, short-lived OBO OAuth 2.1 tokens) → (3) MCP gateway with default-deny ACLs & credential vault → (4) reasoning + guardrail interception (prompt shields, sidecar alignment checks) → (5) human-oversight & durable state persistence (propose-action objects, checkpoint store) → (6) continuous observability & signed audit logs (≥ 6 months, SIEM).
Mode 1 — Assistant (HITL)
Agent proposes, human disposes: every consequential action reviewed before execution. Default for first deployments, irreversible or legally sensitive actions.
Required Technical Components (18)
Zero-Data-Retention Vendor Binding
Sensitive inference is contractually and technically restricted to endpoints under zero-data-retention and non-training terms, evidenced per vendor and re-validated annually.
from: Art. 25
WORM / Immutable Audit Vault
Append-only, hash-chained audit vault (WORM object-lock storage, AES-256 at rest, TLS 1.3 in transit). Guarantees tamper-evidence within the organization's trust domain — which stops your own team, but not an admin who can rebuild the vault. Pair with an external trust anchor and key ceremonies outside the operating team for evidence that holds against the insider scenario.
from: SEC Rule 17a-4 (US Records Retention) · Agentic RDA Stack (6 Layers)
Ephemeral Execution Isolation
gVisor/Firecracker microVMs, read-only root, egress allowlists; container discarded after each task to prevent persistence of exploits.
from: Agentic RDA Stack (6 Layers)
Agentic Zero Trust
Unique cryptographic identity per agent; short-lived, finely-scoped tokens (OAuth 2.1 + PKCE); On-Behalf-Of flow so an agent can never see more than its triggering user.
from: Agentic RDA Stack (6 Layers)
MCP Gateway / Proxy
Central chokepoint for agent tool traffic: default-deny tool ACLs (tools/list vs tools/call), schema & argument inspection, credential injection from vault, rate limits, full audit mirror. Regulatory root cause: the base MCP protocol enforces no authentication or authorization at protocol level — Host/Client/Server topology with Tools/Resources/Prompts primitives ships without an identity layer, so a policy-enforcing gateway is not optional hardening but the only place Art. 12/15 duties can be enforced for tool calls.
from: Agentic RDA Stack (6 Layers)
Guardrail Sidecar / Interception
Rule-based (NeMo/Colang), model-based (alignment checkers) and structural validators deployed as sidecar or gateway plugin (<50 ms), decoupling safety scaling from inference scaling.
from: Agentic RDA Stack (6 Layers)
Propose-Action Objects
Agents never call target APIs directly: they emit typed proposal objects (endpoint, params, risk estimate, rationale) validated by the governance layer before execution; idempotent execution layer.
from: Agentic RDA Stack (6 Layers)
Durable Checkpointing (Pause & Resume)
At oversight gates the complete operational state — working memory, conversation history, tool arguments, intermediate artifacts — is serialized into a durable checkpoint (fast KV store for sub-ms lookups, transactional backend as recovery anchor, vector store for semantic caching of past human decisions). On approval the agent deserializes and resumes at the exact step; matched precedents can shortcut re-planning entirely.
from: Agentic RDA Stack (6 Layers)
Per-Action Autonomy Tiering
Tools tagged read-only / reversible-write / irreversible-write; controls layer routes each action to the matching oversight mode. Mode selection is per action type, never per agent.
from: Agentic RDA Stack (6 Layers)
Agent Identity & Access (IdP)
Per-agent identities, short-lived scoped tokens, OBO flow enforcement — the identity substrate of agentic zero trust.
from: Agentic RDA Stack (6 Layers)
Central Credential Vault
Agents never hold target-system keys; the gateway injects centrally managed credentials after policy checks.
from: Agentic RDA Stack (6 Layers)
OpenTelemetry / FCoT Tracing
Hierarchical trace spans for every sub-task, prompt, retrieved document and API call — the reconstructible decision path for Art. 12/14 and PLD disclosure.
from: Agentic RDA Stack (6 Layers)
Watchdog Supervisor & Rate Limiting
Cost/iteration caps, loop detection, anomaly-triggered mandatory approval (CodeBuddy 'suspicious command override').
from: Agentic RDA Stack (6 Layers)
Trinity Defense (TCB + Command Gates + IFC)
Treats the LLM as an untrusted proposal engine behind a hardened non-LLM Trusted Computing Base. Three pillars: (1) command gates — actions only via a Finite Action Calculus, authorized by a deterministic policy checker before any execution; (2) information-flow control — lattice labels stop confidential data flowing to low-trust sinks without audited declassification; (3) privilege separation — sandboxed low-privilege planner ingests untrusted input, isolated high-privilege worker executes only gate-approved, TCB-normalized actions. Grounded in the impossibility result: token content alone can never unforgeably separate commands from data.
from: Agentic RDA Stack (6 Layers)
Guardian Agents (Runtime Policy Enforcement)
Autonomous supervisory agents outside the supervised agent's reasoning loop: stateful threat engines with graph-based cross-session history (catch multi-turn injection, gradual exfiltration, incremental privilege escalation), event-driven exposure visibility (permission drift, new connectors), and contextual risk correlation into unified issues — interception before execution, not post-hoc logging.
from: Agentic RDA Stack (6 Layers)
Deterministic Policy Engine (OPA / Cedar)
Policy-as-code decision point (PDP) with enforcement points (PEP) in front of every tool call: versioned policies in Git, microsecond evaluation, typed action schemas — authorization decided outside the model's reasoning space, never in the prompt.
from: Agentic RDA Stack (6 Layers)
Shadow-Mode Execution
Run governance controls in observe-and-score mode before enforcement: the policy engine and guardrails evaluate every agent action and log verdicts without blocking, yielding empirical false-positive/negative rates and calibrated thresholds. De-risks the enforcement cutover, produces baseline evidence for Art. 9 risk estimation, and is the standard migration path when retrofitting controls onto a live workflow.
from: Agentic RDA Stack (6 Layers)
Multi-Model Router & Fallback Abstraction
Abstraction layer decoupling application logic from model providers: dynamic routing on capability, cost, latency SLA and regulatory constraint (sensitive-data classes pinned to ZDR private/VPC endpoints or on-prem open-weight instances); real-time health monitoring with automatic fallback to secondary endpoints or local fine-tuned models on outage/latency spikes. Discharges resilience duties (DORA-class), prevents provider lock-in, and makes model deprecations a routing-table change instead of a re-architecture. Router decisions are logged into the decision trace — model version per event is an audit-packet field.
from: Agentic RDA Stack (6 Layers)
Delivery Stack & Pipeline Stage (9)
Service-as-a-Software delivery: the engines, patterns and artifacts this workflow needs on top of the generic obligations. See the full pipeline
Data Lineage & Versioning
Provenance tracking of datasets, features and embeddings; write-time attribution (source, actor, timestamp, confidence).
WORM / Immutable Audit Vault
Append-only, hash-chained audit vault (WORM object-lock storage, AES-256 at rest, TLS 1.3 in transit). Guarantees tamper-evidence within the organization's trust domain — which stops your own team, but not an admin who can rebuild the vault. Pair with an external trust anchor and key ceremonies outside the operating team for evidence that holds against the insider scenario.
pipeline stage 4 — Output audit & human-in-the-loop gateway
Supervisor Attribution Chain
Every model inference, data interaction and client-facing artefact is bound to an authorised supervising natural person — never to a shared service account. Required for SEC Rule 204-2 attribution, SOX segregation of duties and AI Act Art. 26 deployer oversight records.
Explainability API (SHAP/LIME/CoT)
Feature attributions for classical ML, reasoning-trace summaries for GenAI — feeds the human reviewer and the technical file.
HITL Escalation Queue & Review UI
HITL escalation queue & review UI ('Human-as-a-Tool': the agent calls the human like any other tool via propose-action objects). Confidence- and risk-threshold routing, SLA timers, structured accept/modify/reject verdicts with digital reviewer signature at gate release — each verdict is itself Art. 14 evidence and feeds the active-learning loop.
pipeline stage 4 — Output audit & human-in-the-loop gateway
Propose-Action Objects
Agents never call target APIs directly: they emit typed proposal objects (endpoint, params, risk estimate, rationale) validated by the governance layer before execution; idempotent execution layer.
Materiality-Threshold Escalation
Autonomy is bounded by pre-configured limits — variance thresholds, disbursement caps, margin floors, confidence minima. Crossing a limit halts execution and routes the case to a named human with the synthesised context, rather than letting the agent proceed at degraded confidence.
Bitemporal Memory (GDPR×Art.12)
valid_from/valid_to + transaction time on every record: GDPR erasure removes data from the active retrieval path while the HMAC-chained immutable log survives for Art. 12 / PLD defence; tenant-scoped partitions allow physical scrub of PII.
Cognitive Orchestrator
The reasoning and control plane of an agentic workflow: goal decomposition, tool selection across enterprise APIs, confidence scoring per step, and a human-machine interface exposing progress, limitations and a global halt. It is the architectural home of AI Act Art. 14 oversight — oversight that lives only in a downstream UI cannot stop an executing agent.
Build or Buy — Vendor Layer (3)
The graph models vendor CATEGORIES as first-class nodes and keeps named vendors as community-maintained, disputable desc content with lastVerified dates. A category is stable; a vendor list is a currency-layer object like any standard node.
Runtime Security & Guardrail Vendors
First-line inline enforcement: single-pass parallel input/output evaluation proxies, injection & exfiltration defense, PII masking, grounding checks, SecOps routing. Exemplary (community-maintained): Prompt Security, HiddenLayer (MLSDR), Palo Alto AI Runtime Security, AWS Bedrock Guardrails, NVIDIA NeMo Guardrails, Guardrails AI, Robust Intelligence, LLM Guard / Llama Guard OSS class. Selection metrics: single-pass latency (<20 ms class), catch rates, policy-version telemetry into the AI-BOM.
unverified · verified 2026-08-06 community-maintained
selection metrics: single-pass parallel evaluation latency (<20 ms class), injection/hallucination catch rates, SecOps/SIEM routing, policy versioning surfaced into the AI-BOM
supplies: MCP Gateway / Proxy · Guardrail Sidecar / Interception
Agent Orchestration & SDLC Toolkits
Developer middleware for multi-agent networks, tool-use chains, RAG abstraction, state/memory persistence and model routing. Exemplary (community-maintained): LangChain, LlamaIndex, AutoGen, CrewAI; MCP-based tool ecosystems. Regulatory posture: orchestration code is where autonomy tiering, propose-action objects and fallback routing get implemented — the framework choice constrains which controls are cheap and which are retrofits.
unverified · verified 2026-08-06 community-maintained
selection metrics: broad model-API abstraction, state/memory management, error recovery, fallback routing hooks
supplies: Multi-Model Router & Fallback Abstraction · Materiality-Threshold Escalation · Cognitive Orchestrator
Regulated Foundation-Model Platforms
Frontier commercial APIs and open-weight models under enterprise controls: zero-data-retention tiers, data isolation, fine-tuning governance, safety alignment documentation, EU-sovereign options. Exemplary (community-maintained): Anthropic Claude (ZDR enterprise tier), OpenAI GPT enterprise, Google Gemini Enterprise, Cohere (private-cloud RAG), Mistral (EU/self-hosted), Meta Llama (open-weight sovereignty). GPAI-chapter duties and vendor due diligence attach at this layer.
unverified · verified 2026-08-06 community-maintained
selection metrics: ZDR enterprise tiers, data isolation, EU-sovereign options, fine-tuning controls, safety alignment documentation
supplies: Multi-Model Router & Fallback Abstraction
Procurement rule: Derived from three-lines-of-defense separation: the second-line GRC platform must be procured and deployed independently of any first-line runtime or model vendor — a governance tool that only sees its own vendor's models cannot govern a multi-model estate, and closed third-party SaaS AI can only be governed contractually (intake, attestation, AI-BOM disclosure), never by inline inspection.
Outsourced delivery BPO · SaaS · Service-as-a-Software caveats
Delivery Model — BPO · SaaS · Service-as-a-Software
Spectrum
BPO: input-priced (billable hours/FTEs), linear headcount scaling, human error & attrition as primary risk
SaaS: capability-priced (software access), client operates the workload, implementation/adoption failure as primary risk
Service-as-a-Software: outcome-priced (SLA on completed work), provider-managed AI executes 60–80% of cognitive tasks with specialist supervision, algorithmic bias & non-compliance as primary risk
Caveats in regulated markets
— Outcome SLAs move compliance risk onto the provider — but NOT the buyer's deployer duties: Art. 26 oversight, log retention and FRIA obligations stay with the enterprise even when execution is outsourced.
— Provider role analysis is the central legal question: a productized platform that fine-tunes, re-purposes or chains models can flip into the Art. 25 provider role with full high-risk obligations.
— Certified operations (ISO 42001) function as a procurement moat and shortcut third-party risk assessment — but organizational certificate ≠ product conformity (never conflate, see meta.assuranceEcosystem).
— The buyer's evidence chain must reach into the provider: contractually mandated AI-BOM disclosure, ZDR certificates, bias-audit reports and logging-ledger access are the artifacts that make an outsourced workflow auditable.
Threat Profile
LLM09 Misinformation
Hallucinated or wrong outputs create liability and decision risk.
mitigate with: Output Rails / Groundedness Check, Explainability API (SHAP/LIME/CoT)
Audit-Trail Manipulation (Insider)
Evidence tampering by parties with legitimate admin access: rebuilding the WORM vault, truncating hash chains before export, backdating records, selective deletion between audits. The sharper audit test: not whether logs are immutable in normal operation, but whether someone who administers the store can alter them unnoticed. Defeats every log-derived artifact at once (Art. 12, DORA, NIS2, PLD disclosure defence) if successful.
mitigate with: External Trust Anchor (Qualified Timestamp / Ledger), WORM / Immutable Audit Vault, Agentic Zero Trust
Cascading Multi-Agent Failure
One agent's erroneous intermediate output (hallucination, goal drift from the assigned objective over multi-step plans, poisoned context) propagates unchecked through downstream agents and triggers automated cascade decisions — emergent behavior no single-agent review ever approved, with unclear liability boundaries between agent operators. Grows with orchestration depth (central orchestrator vs decentralized message bus) and autonomy tier.
mitigate with: Guardian Agents (Runtime Policy Enforcement), Watchdog Supervisor & Rate Limiting, Per-Action Autonomy Tiering, Shadow-Mode Execution
LLM06 Excessive Agency
Over-broad rights/functions of autonomous agents lead to uncontrolled actions.
mitigate with: MCP Gateway / Proxy, Agentic Zero Trust, Per-Action Autonomy Tiering, Trinity Defense (TCB + Command Gates + IFC), Deterministic Policy Engine (OPA / Cedar), Guardian Agents (Runtime Policy Enforcement)