Iris for compliance officers
You’re Marcus Brooks, external auditor from a Big Four firm doing SOC 2 fieldwork on an AtmanID customer. This page walks the canonical Iris query patterns for compliance work — evidence collection, control-by-control verification, audit chain integrity checks, and the queries that produce the strongest auditor evidence.
If you’re new to AtmanID’s auditor flow, read Set up an external auditor for SOC 2 evidence collection first — that covers the engagement onboarding and access setup. This page focuses on the query layer.
What you can and can’t see in Iris
As an external_auditor, your Iris access is:
- Read-only. The
external_auditorrole’s permissions are read-only, and every action Iris could propose is checked against your permissions before it runs. - Role-scoped. Iris offers you the people, access, compliance, audit and AI Hub lookups (the audit trail, audit-chain verification, certification status, signed access snapshots and more) and aggregate counts. It does not offer you
iris_sql, agent, credential or infrastructure tools. Iris reads the customer’s live tenant data that your role can see — it is not limited to an evidence pack. - Time-bounded. External-auditor access is granted for a fixed period (up to 90 days) and can be revoked by the customer.
- Logged. Every question Iris answers for you writes a
CHAT_QUERYrow to the customer’s audit log with the tools used and the data provenance (not the raw question text).
This is the read-only forensic-investigator stance: a query interface with safety rails, not a SQL terminal.
Audit chain integrity — your first-day check
Before any control work, verify the audit chain hasn’t been tampered with. Ask Iris:
verify audit chain integrityIris re-computes the hash chain over the most recent entries (up to 500) and reports INTACT, CHAIN_GAP (a missing sequence number) or TAMPERED (a hash that no longer matches), with the range of sequence numbers it checked and the break point if there is one. For a longer range, the chain check on the Audit Log page verifies up to the latest 10,000 entries. The most recent entries are re-verified every night, and the whole history — every entry, checked against the signed chain heads — every week. Each run writes its result to the audit log (AUDIT_CHAIN_VERIFIED or AUDIT_CHAIN_BROKEN; the weekly one is marked full_history), so you can cite the latest full-history result as evidence.
If you see anything other than INTACT — STOP. A broken chain means you cannot rely on the audit log as evidence. Escalate immediately to the engagement contact. This is a P0 finding.
The audit log is append-only and hash-chained, with checkpoints signed outside the database (see Architecture → Audit chain). One limitation to note in your working papers: records written before the chain was introduced (before March 2026) carry no hash and are reported as unchained historical records rather than verified — the verifier distinguishes them from tampering.
SOC 2 control-by-control queries
For each in-scope control, an Iris query that produces useful evidence — and where Iris stops. Iris’s audit tools cover recent activity and counts; for complete populations over a period, export from the Audit Log page.
CC6.1 — Logical access controls
how many active users have not logged in for 90 daysReturns the dormant-account count — the population that should be reviewed or disabled. Combined with:
break down audit events by action type for the last 30 daysReturns event counts per action type (up to 90 days back), including failed authentication (AUTH_FAILURE). For the individual events, ask for “recent AUTH_FAILURE audit events” (newest 100).
CC6.6 — System-level access enforcement
show me recent ENTITLEMENT_GRANTED audit eventsReturns the most recent grant events (up to 100), each with actor, target and recorded state. Combined with:
show me recent ENTITLEMENT_REVOKED audit eventsReturns the corresponding revocations. Auditors testing “is access tracked and lifecycle-managed” get both halves.
For the per-app view of current access:
how many active grants per applicationReturns grant and distinct-user counts per application — showing which apps carry the most access.
CC7.2 — System monitoring
break down audit events by action type for the last 7 daysReturns the action-type frequency distribution — auditors look for unusual patterns (e.g., a spike in RBAC_DENIED, an abnormal volume of USER_CREATED).
who has been most active in the audit log over the last 30 daysReturns the top actors by event count. Iris has no per-user baseline comparison; spikes have to be judged against earlier windows you ask for.
CC7.5 — Anomaly detection
show me recent PROMPT_INJECTION_BLOCKED audit eventsReturns attempts to manipulate the AI assistant that were blocked. Iris has no tools for out-of-hours activity, new IP addresses or actions by deactivated users; use the Audit Log page or your SIEM export for those.
CC8.1 — Change management
show me recent POLICY_UPDATED audit eventsReturns policy-change records with their recorded new state (the action-type filter is a case-insensitive substring match, so related variants are included). Iris cannot test whether each change was preceded by an approval; that correlation needs the full export.
Forensic investigation patterns
“Show me what user X did”
show me the audit events by user@example.comReturns that person’s most recent actions, newest first (up to 100). There is no date-range filter; for a full 90-day timeline, export from the Audit Log page.
“Show me everything that happened to resource Y”
Iris’s audit search filters by action type and actor only — it cannot filter by target resource or request. Use the Audit Log page’s search and export for a resource’s full event history or to reconstruct the chain of events behind one request.
“What access did this person hold on a given date?”
what access did jane@example.com have on 2026-06-30Returns the access they held at that moment, reconstructed by replaying the audit chain. Ask to export it for a signed attestation you can keep in your working papers.
Evidence pack workflow
The full SOC 2 evidence pack flow (engagement setup, pack generation, evidence sharing, closeout) is documented in Set up an external auditor for SOC 2 evidence collection. Brief recap of the Iris-relevant portion:
- Customer admin generates a SOC 2 evidence pack scoped to your engagement
- Pack contains pre-rendered evidence sections per control + queryable audit-row corpus
- You verify pack integrity via the SHA-256 hash provided
- You run Iris queries to dig into specific controls + reconcile with the pre-rendered evidence
- Pack URL has 90-day TTL — download CSVs of relevant evidence rows for your working papers
What you CAN’T do via Iris (need to escalate to engineering)
Honest accounting of Iris’s limits as an auditor tool:
- Look at code or configuration outside the audit log and the curated views. Iris queries the audit + production view layer, not the application source code. For source code review (e.g., “show me the implementation of the audit chain hash function”), contact us for source-code review.
- See data in real-time. Iris responses reflect committed transactions in the database. There may be a few-second lag between an action happening + the audit row being queryable. For continuous monitoring, customers can export audit events to their SIEM every five minutes.
- Modify any state. Even cancelling a stale access request requires the customer’s identity admin. Auditors observe; they don’t act.
- Cross-tenant queries. Iris sees only the customer’s own tenant. Comparing this customer with other customers is not possible through Iris.
Operator best practices for auditors
- Start every session with the chain integrity check. Build the muscle memory; it’s the foundation of every other query’s validity.
- Record the question, time and answer in your working papers. Note the exact question, when you asked it and the “Based on” footer. Each answer has a matching
CHAT_QUERYrow in the customer’s audit log listing the tools used, so the customer can show which tool produced it. - Prefer the catalog tools. Iris’s catalog tools are pre-built and tested. The structured view query (
iris_sql) is not offered to theexternal_auditorrole; ask the customer’s compliance officer to run one if you need it. Iris does not run SQL you paste in. - Document Iris-side discrepancies. If two Iris queries that should agree (e.g., “active users via metric A” vs “active users via metric B”) disagree, file the discrepancy as a finding. The catalog could have a bug; auditor scrutiny is how those get caught.
Adjacent reading
- Set up an external auditor for SOC 2 evidence collection — the engagement onboarding flow
- Architecture → Audit chain integrity — how the audit chain provides the integrity guarantee
- Architecture → Compliance mapping — full SOC 2 + ISO 27001 + NIST control coverage matrix
- Iris → Query patterns cookbook — Marcus’s column in the cookbook (audit forensics queries)
- Iris → Failure modes — how to recognize when Iris isn’t giving you a confident answer
© AtmanID · Privacy