Guide · By the Ingenious AI team · Published 14 November 2026 · Reviewed 14 November 2026
How Auditees and Auditors Share Evidence Securely
Short answer
Auditees and auditors share evidence securely when four properties hold at once: the evidence cannot be silently altered (SHA-256 sealing at intake, immutable storage), its provenance is visible (source badges and a shared manifest), access is bounded (a scoped, revocable, read-only grant to one room), and the exchange is recorded (access log and an in-room question thread). AI Audit Exchange is built as exactly that structure. Email attachments and shared drives fail all four properties at once, which is why audits run on them leak time and confidence.
What is secure evidence sharing?
Secure evidence sharing is the controlled exchange of audit artifacts between an auditee and an independent auditor under integrity, provenance, scope and record-keeping controls. On AI Audit Exchange it is implemented as hash-sealed immutable artifacts, an exportable manifest, acceptance-created scoped grants with an access log, and an in-room question workflow — all confined to a single evidence room per engagement.
Property one: the evidence cannot change in transit or at rest
Most sharing failures are integrity failures nobody notices: the file the auditor reads in month three is not the file the auditee sent in month one, because someone tidied it. Sealing defeats this silently and completely. Every artifact is SHA-256 hashed at intake and stored immutably; the manifest records the hash; either side can re-verify at any moment. There is no 'version' problem because there are no competing versions — there is the sealed record, and there are copies that either match it or do not. When a question arises, it is settled by recomputation, not by comparing mailboxes.
Property two: both sides see the same provenance
Security is not only about keeping outsiders out; it is about both insiders looking at the same facts. The manifest is the shared fact-base: filenames, source badges — which product produced the artifact, or that it was a direct upload — formats, sizes, hashes, import dates, retention notes. The auditor samples from it; the auditee answers from it; disagreements start from a common inventory instead of rival folder listings. Provenance badges do particular work here: each side knows, for every file, whether it carries a producing product's authority or the auditee's own, and can weight it without asking. See direct upload vs suite import.
Property three: access is a bounded grant, not a channel
Email and drives share by copying — and every copy is a new, uncontrolled home for the evidence. A room shares by access: the auditor reads in place, under a grant created by acceptance, scoped to that room, read-only, revocable, and logged. Nothing is copied out by the sharing mechanism itself, and when the engagement ends, revocation restores the default state of no access. The auditee's other rooms and periods are never inside the boundary. This is the difference between lending someone a key to one room and photocopying your archive for them: the first can be ended; the second cannot be recalled. The grant model is detailed in scoped auditor access.
Property four: the exchange itself is on the record
A secure channel that keeps no record leaves the audit unable to show how evidence moved and what was discussed. The room records access in its access log and keeps the question-and-answer thread with the evidence. Together they reconstruct the engagement: who looked, what was asked, what was answered, what was imported in response, each fact dated. That record is protected by the room's retention — up to 10 years on paid plans — and by legal hold where required. When a later reviewer asks how the audit was conducted, the answer is a room, not a recollection assembled from sent-mail folders.
The platform's own security posture
The room model sits on the platform's baseline controls, described on the security page: artifacts sealed at intake and stored immutably, manifest hashes re-verifiable at any time, sessions in signed HttpOnly SameSite cookies, API keys stored only as keyed hashes and never in URLs or logs, parameterised queries throughout, and rate-limited authentication endpoints. Room contents are visible only to the owner and a granted auditor — a statement the product makes in its privacy terms and implements in its access model. Security claims in an audit context should always be checkable; on this platform the central one — hash verification — is checkable by the auditor personally, which is the right shape for a control.
A sharing checklist for your own stack, whatever you use
Judge any evidence-sharing method, including this one, by the four properties. Can a file change after sharing without detection? Is provenance attached to the file or carried in someone's head? Does access end, verifiably, when the engagement ends? Is the exchange itself recorded and retained? Attachment-based sharing fails the first and third by design and the second and fourth by practice. A sealed room passes all four structurally. If your current audit runs on drives and email, the migration is smaller than it feels: one room for the next period, imports as produced, a grant at acceptance — and the four properties start holding from the first artifact.
Five actions to take
- Share by access, never by attachment: the auditor reads in the room under a scoped grant.
- Verify integrity together at the engagement's start: sample hashes from the manifest, both sides watching.
- Work from one manifest — auditor samples from it, auditee answers against it.
- Raise and answer all questions in the room so the exchange joins the retained record.
- End sharing deliberately: revoke the grant at close-out and confirm the grants list.
Worked example
A fictional insuretech firm, Harbor & Vine Insurance Tech, ran its previous audit cycle on a shared drive: 112 files, 4 people with edit access, and at one point two files named as final versions of the same record. Its post-cycle review found the auditor had sampled a superseded file for one finding — nobody's fault, and everybody's problem. For the next cycle the firm moves to a room: 68 artifacts sealed at intake, one auditor granted read access, questions in the thread.
The mid-engagement integrity sample — 10 hashes chosen by the auditor from the manifest — verifies 10 of 10. The access log shows only the auditor's reads. At close-out, access is revoked in the manifest-export sitting. The firm's review note is one line: 'The finding about the wrong file cannot happen in a room; there is no wrong file to open.' Four properties, held structurally, removed an entire category of accident.
Frequently asked questions
Why is emailing evidence to the auditor insecure?
Attachments copy evidence into uncontrolled homes, can be edited without detection, carry no provenance, and their access can never be revoked. A room replaces all four failures: sealed originals, badges, scoped grants and a recorded exchange.
Can the auditor download artifacts from the room?
The auditor works the room under read access — examining artifacts, the manifest and validation, and verifying hashes. The sharing mechanism itself is access in place, bounded by the grant, rather than distribution of copies.
How do I know who accessed my evidence?
The room keeps an access log, and the room page lists its active grants with the auditor's firm name. Review both at acceptance, mid-engagement and close-out.
What protects the platform account itself?
Sessions use signed, HttpOnly, SameSite cookies; authentication endpoints are rate-limited; API keys are stored only as keyed hashes. Room contents are visible only to the owner and a granted auditor.
Does secure sharing slow the audit down?
The opposite. Setup is one acceptance; sampling runs off the manifest; integrity checks take minutes. It is attachment archaeology — hunting versions across inboxes — that consumes audit weeks.
Keep reading
All AI Audit Exchange guides · Auditor directory · About AI Audit Exchange · Security · Pricing · AI Audit Exchange home · Previous: Auditor Questions and Answers Inside the Evidence Room · Next: Evidence Room vs Shared Drive: An Honest Comparison
How to Organise AI Audit Evidence by Period · What Evidence Does a CPPA Cybersecurity Audit Need? · What Evidence Does an SB 1119 Audit Need?