Implementation Guide
Applying the IIA AI Auditing Framework to LLM Applications
To apply the IIA AI Auditing Framework to LLM applications, treat the framework as the top-level structure and build an LLM-specific layer beneath it. Inventory every application, model, retrieval pipeline, tool, and agent with a named owner. Map each framework domain to specific LLM risks and control objectives. Define tests that examine the controls around non-deterministic outputs rather than the outputs alone. Confirm that runtime logs, policy enforcement records, and change records exist to support those tests.
From framework to audit evidence
The approach moves through four stages, each building on the one before it.
| Stage | Description |
|---|---|
| 1. Scope | Inventory LLM applications, models, pipelines, tools, agents, and owners. |
| 2. Map | Link each framework domain to LLM risks and control objectives. |
| 3. Test | Define design and operating effectiveness tests for each control. |
| 4. Evidence | Identify the runtime records that show controls operated in production. |
Scope the LLM system inventory first
Inventory every application, model, retrieval pipeline, tool, and agent, and assign each a named owner. Build the LLM inventory with owners, data access, and tool or agent capabilities.
Decide the sampling approach and population source before fieldwork begins, so that testing draws on a defined and complete inventory.
Map domains to LLM risks and control objectives
Treat the IIA framework as the top-level structure and build an LLM-specific layer beneath it. Map each framework domain to specific LLM risks and control objectives, and write testable control objectives for each framework domain you adopt.
Example risk-to-control mapping
A risk-to-control mapping connects each adopted framework domain to its LLM risks and control objectives, then to the tests that show whether each control is designed and operating effectively, and finally to the evidence that supports those tests.
Identify the evidence sources and where runtime governance helps
Confirm that the following records exist to support your tests:
- Runtime logs
- Policy enforcement records
- Change records
Confirm log completeness, retention, tamper evidence, and auditor access. Record gaps where evidence cannot be produced and report them as control findings.
Audit preparation checklist
- Obtain the current IIA framework text and note any updates issued since your last review.
- Build the LLM inventory with owners, data access, and tool or agent capabilities.
- Write testable control objectives for each framework domain you adopt.
- Decide the sampling approach and population source before fieldwork begins.
- Confirm log completeness, retention, tamper evidence, and auditor access.
- Record gaps where evidence cannot be produced and report them as control findings.