Sample record · Cyber insurance · claims

An accounts-payable agent pays a lookalike vendor

An AI agent changes a vendor's bank details from a lookalike-domain email and releases USD 184,300 four minutes later, with no human approval. Claims triage matches the record to the notice of loss, and a handler opens recovery.

Fictional scenario, real seals. No company, person or transaction here is real. Each record was sealed on Verdict’s public sandbox and logged on Sigstore Rekor, a public log Verdict does not run. This chain was sealed in one sitting, so its log times are seconds apart; in a live deployment each step is logged when it happens.
What the log time settles in a real case

Whether the money left before anyone approved it, and in what order the insured, the triage system and the handler acted.

  1. Step 1 of 3 · AI agent changes bank details and paysNo human approval

    Agent updates the vendor's remittance account and releases payment of USD 184,300 four minutes later. No human approval before release; the agent's policy allowed bank changes for existing vendors.

    Logged on Rekor
    2026-10-13 16:57:26 UTC
    Log index
    3245335975
    Record id
    ser_69f678d5ce2de128c1647a7775f7510e
    Verify in your browser →Open the Rekor entry ↗Download the record
  2. Step 2 of 3 · Claims triage AI refers the fileAwaiting human review

    AI matches the record to the loss: bank details changed and payment released by the agent within 4 minutes, request came from a lookalike vendor domain, no human approval. Refers the file to a claims handler and recommends asking for the agent's action log.

    Logged on Rekor
    2026-10-13 16:57:26 UTC
    Log index
    3245336025
    Record id
    ser_11f54a5cce17f0b2b1de278bafa58594
    Verify in your browser →Open the Rekor entry ↗Download the record
  3. Step 3 of 3 · Claims handler opens recoveryHuman approved

    Claims handler (fictional) accepts the notice, opens recovery with the receiving bank and asks the insured for the agent's last 30 days of actions. Reason recorded: the sealed agent record fixes what the agent did and when, so the timeline does not rest on the insured's recollection.

    Logged on Rekor
    2026-10-13 16:57:27 UTC
    Log index
    3245336100
    Record id
    ser_5bd929823839a7c957a9e266ad2df4b7
    Verify in your browser →Open the Rekor entry ↗Download the record

How to check the time yourself. Open the Rekor entry and compare its logged hash with the SHA-256 of the record’s commitment, which the verifier shows. If they match, the entry’s integrated time is the earliest moment this content is proven to have existed. Log times above were read from Rekor on 2026-10-15.

A record proves what it says has not changed since it was logged. It does not prove the event happened as described, or who made the record. What Verdict proves, and what it doesn’t →

All sample records →