How do you prove what an AI model was given?

By Verillian. Published . Updated .

Proof of an AI input is a record made when the request was sent, held by you, naming who and what, and showing if it was later altered. Here is what that takes.

A woman holding a paper and a man leaning over a laptop look at the screen together.

You prove it with a record created when the request was sent and held by you rather than the AI vendor. It identifies who sent the request, through which AI service, and when. It preserves the content sent and shows whether anyone changed the record afterward.

A vendor’s chat history, a screenshot, or a policy that says staff should not paste sensitive data each supports part of the story.

None of them, alone, shows what a model actually received. No regulator we found prescribes this exact record. The rules that apply to banks, credit unions, and health systems ask for its ingredients instead. They want activity records you can examine, review, and keep.

Proving an input means answering who sent it, to which service, when, and what it contained. The fourth is the one most organizations cannot answer today.

What does it take to prove what an AI model received?

Three properties, and a record that lacks any of them is weaker than it looks.

  • Content. The prompt, the files, and the pasted material, or a faithful account of them. A log that says a user visited an AI site on a Tuesday shows a visit, not an input.
  • Attribution. Which person, on which device, through which AI service, at what time. Without attribution, content is an anonymous string.
  • Integrity. Some way to tell whether the entry was changed after it was written. A record you can edit without a trace is a note, not evidence.

The record also has to be yours. Evidence you must ask a vendor to produce is evidence on the vendor’s schedule and terms, and a vendor’s history exists in whatever form and for however long its product settings and contract say.

What do the rules require for health systems?

The HIPAA Security Rule asks for audit controls. Under 45 CFR 164.312(b), a covered entity or business associate must “implement hardware, software, and/or procedural mechanisms that record and examine activity in information systems that contain or use electronic protected health information.”

Under 164.308(a)(1)(ii)(D), it must implement procedures to regularly review records of information system activity, such as audit logs, access reports, and security incident tracking reports. And under 164.316(b), documentation the subpart requires must be kept in written or electronic form for six years from the date it was created or last in effect.

None of that text mentions AI. Whether a prompt to an AI tool is activity in an information system that contains or uses electronic protected health information depends on where the tool runs and what was in the prompt, and that’s one to settle with counsel.

Our post on whether HIPAA requires logging what an AI model received takes the question on directly. If you ever have to explain a disclosure, the record above is what you’d want in hand.

What do the rules require for credit unions?

Appendix A to 12 CFR Part 748 asks a federally insured credit union to consider monitoring systems and procedures to detect actual and attempted attacks on or intrusions into member information systems (III.C.1.f), to regularly test key controls (III.C.3), and, for service providers, to monitor them where its risk assessment indicates by reviewing audits, summaries of test results, or equivalent evaluations (III.D.3).

It also asks for response programs when unauthorized access to member information is suspected (III.C.1.g). Each of those is easier to carry out when there is a record of what left the organization. The appendix does not name AI, and it does not say what such a record must contain.

What do the rules require for banks?

The 2023 Interagency Guidance on Third-Party Relationships, issued by the Federal Reserve Board, the FDIC, and the OCC, lists what supports documentation and reporting for a third-party relationship. The list covers an inventory of relationships, risk assessments, due diligence results, executed contracts, monitoring reports, reports of service disruptions or security breaches, and periodic reporting to the board.

It does not mention prompts or inputs, and its preamble mentions artificial intelligence only in describing suggestions from commenters. On September 15, 2026, the OCC, the Board, the FDIC, and the NCUA published a proposal to rescind and replace that guidance, with comments due November 16, 2026.

A bank’s obligation to keep an accurate picture of what it sends to a third party comes from that framework and from its general safety and soundness duties. The bank decides what the record must contain.

Why is a vendor’s chat history not enough?

Because it answers a different question. A vendor’s history shows what the vendor chose to keep of a session in an account. It does not show, from your side, what left your devices, who sent it under which identity, or whether the history you are reading is the history that existed at the time.

It also covers only the vendor’s own service, so it cannot describe AI use across the several tools your people actually use. Consumer and business accounts with the same vendor can differ in what they retain and who can see it, so check the current terms for the exact account type rather than assuming.

What does tamper-evident add?

A tamper-evident record is built so that altering an entry breaks a check. Tamper-evidence detects alteration of captured entries. Each entry is signed on the device, and your own admin server flags any entry that fails to verify when it arrives.

NIST’s Guide to Computer Security Log Management (SP 800-92, 2006) is the general reference for running log management in an organization, and it names the same concern, “preserving the integrity of log data from accidental or intentional modification or deletion”.

Does redaction change what you can prove?

It changes what the model was given. If a tool screens the identifiers your policy flags before a prompt leaves the device, the model received the placeholder, not the value, and the record of what it was given should say so.

Decide in advance which version the record must hold and write that down. Redaction reduces what a model receives, but only the record establishes what it received.

What do you need in place?

  • A list of the AI services your people can reach and the devices you manage, so you know what any record covers.
  • Capture on devices you manage, as requests are sent, rather than relying on each vendor’s history.
  • Entries that name the person, device, AI service and time, with the content encrypted to your organization’s key.
  • Integrity checks that run on your own servers, and a named owner for the record.
  • A written decision on what the record holds when a value was screened before sending, and how long records are kept.

What record does Verillian keep?

Verillian keeps a signed record of every captured AI interaction on your organization’s own servers, each entry naming the person assigned to the enrolled device, the device, the service, and the time.

At the top of every record, Verillian captures the context window, so you can see what the AI was given. Content is encrypted to your organization’s key, created in your administrator’s browser. Verillian never receives that key.

Sources

  • 45 CFR 164.312(b), Audit controls; 164.308(a)(1)(ii)(D), Information system activity review; 164.316(b), Documentation. eCFR, Part 164 Subpart C, read November 3, 2026.
  • 12 CFR Part 748, Appendix A, sections III.C.1.f, III.C.1.g, III.C.3, and III.D.3. eCFR, read November 3, 2026.
  • Board, FDIC, and OCC, Interagency Guidance on Third-Party Relationships: Risk Management, 88 FR 37920 (June 9, 2023), section D.3, Documentation and Reporting. Federal Register, read November 3, 2026.
  • OCC, Board, FDIC, and NCUA, Proposed Third-Party Risk Management Guidance, 91 FR 58536 (September 15, 2026), comments due November 16, 2026. Federal Register, read November 3, 2026.
  • NIST, Special Publication 800-92, Guide to Computer Security Log Management (September 2006). NIST CSRC, read November 3, 2026.

What the record holds

See Verillian govern AI on a real device.