Paidwen
Start free

An evidence pack hands your auditor the complete lists of a period.

An evidence pack is a ZIP file signed by Paidwen. It holds the complete lists that an auditor samples from, for one framework and one period: SOC 2, ISO 27001, the HIPAA Security Rule or the EU AI Act. It is not an audit report, a certificate or an attestation: only your auditor or a certification body gives those.

The pack holds eight lists and the configuration.

  • decisions: every decision, with its agent, tool, parameters, cost, verdict, rule, permission, budget, approval and execution.
  • approvals: every decision that waited for a human, with the answer, the person, the channel and the time.
  • executions: every execution, with its start, end, status and error.
  • incidents: every quarantine, disabling, revocation and key change, with who, why and when.
  • identities: every agent, key, trust rule and team created, changed or removed, and every agent that a trust rule created.
  • rule-changes, permission-changes and member-changes: every change, with the request, the result, the author and the time.
  • configuration.json: the organization, its members, its agents with their permissions, its rules, approval groups and trust rules when the pack is created.

Each list comes as CSV and as JSON Lines. report.pdf sorts the lists under the requirements of the framework and states the limits of the pack on its first page. For HIPAA, it ends the activity review with a line for your reviewer to sign.

Every write of the admin API leaves a change line.

Paidwen writes one change line in the journal for each successful write of the admin API: the operation, the object, the request, the result, the author and the time. A read, a refused write and a draft of a rule leave no line. The value before a change is in the previous line of the same object. Keys, tokens and the address of a Teams webhook are masked before the journal.

The signature proves that the pack did not change.

manifest.json lists every file with its SHA-256 digest, its size, its number of rows and the query that produced it. manifest.sig is the RSA signature of manifest.json, with SHA-256. The public keys are at GET /v1/evidence/keys, without a key, and a retired key stays there so that its packs still verify. In the folder of the unzipped pack:

Terminal
curl -s https://api.paidwen.com/v1/evidence/keys \
  | jq -r --arg kid "$(jq -r .key_id manifest.json)" '.data[] | select(.key_id == $kid) | .public_key' > key.pem
openssl dgst -sha256 -verify key.pem -signature manifest.sig manifest.json
jq -r '.files[] | "\(.sha256)  \(.name)"' manifest.json | sha256sum -c

The dashboard and the API export the same pack.

In Actions, open Export and choose Evidence pack, then the framework, the period and the agents. HIPAA and the AI Act need the agents in scope. The API takes an admin key, a period of at most 366 days with its end excluded, and up to 100 agents.

HTTP
GET /v1/evidence?framework=soc2&from=2026-07-01T00:00:00Z&to=2026-10-01T00:00:00Z
GET /v1/evidence?framework=hipaa&from=2026-09-01T00:00:00Z&to=2026-10-01T00:00:00Z&agent_id=0199f1c2-0000-7000-8000-000000000001

The pack has nine limits.

  • It holds only the actions that go through the SDK.
  • The journal can lose lines when its queue overflows or when its collector stays unreachable for more than five minutes. Paidwen counts these losses in its monitoring, not per organization, so the pack cannot list them.
  • The journal keeps a line for the time of your plan: 7 days, 30 days, 90 days or 1 year. Keep the pack of each month to cover a longer period: HIPAA asks for six years.
  • The signature proves that the pack did not change since its creation. It does not prove that the journal was complete.
  • The changes of configuration are in the journal since Paidwen records them, in October 2026.
  • Paidwen has no SOC 2 report of its own yet.
  • Health data in the parameters makes Paidwen a business associate under HIPAA: sign a business associate agreement, or keep the content of the agents concerned off the journal.
  • Policies, risk analysis, training, the response plan and the signed review of access stay with you.
  • Paidwen does not classify an AI system as high-risk, does not qualify a serious incident and notifies no authority.