Skip to content

Learn · Audit & evidence

Evidence packs

A portable file that carries a framework’s controls, their evidence, and the entries behind them.

Checked against the product on · written for people who need the evidence

A pack is one JSON Lines stream and one manifest. It carries a framework, its controls, the evidence links on each control, and the logbook entries those links point at. Every hash in it can be recomputed from the file alone.

console.dmzagent.com/records

Prove

Export evidence

1
Framework
SOC 2Controls and their evidence links.
From
2026-07-01
To
2026-07-31
Sign the manifest
YesAdds authenticity. Integrity needs no key.
2The pack is JSON Lines plus a manifest. Anyone can re-derive every hash from the file alone.
3CancelBuild pack
Figure. The export dialog. Framework and window pick what goes into the pack. The evidence export dialog: framework, date range, and what the pack will contain.
  1. Open Records and select Export evidence, then pick the framework and the window.1

  2. Read the format line.2

    Integrity needs no key. Signing adds authenticity on top.

  3. Select Build pack.3

    The pack downloads as the record stream and the manifest.

The record stream

One JSON object per line, each rendered as canonical JSON. Four record types appear, in this order.

The four record types.
TypeOne perCarries
frameworkPack.The framework key, name, version, authority, and scope.
controlControl in the framework.The reference, the title, the status, the owner, and when it was last tested.
evidenceLink from a control to something.The link id, the kind, the entry it points at, and the entry hash captured when the link was made.
ledger_entryDistinct logbook entry referenced by a link.The full entry: index, previous hash, payload hash, hash, time, and payload.

The manifest

Manifest fields.
FieldWhat it holds
kindThe format identifier and its version.
pack_idThis pack’s identifier.
created_atWhen the pack was built.
framework_id · framework_key · scope_refWhat the pack covers.
record_count · ledger_entry_countHow many lines and how many entries to expect.
hash_algo · content_hashSHA-256 over the whole record stream.
sig_algo · signature · signing_key_idPresent when the pack was signed. Absent otherwise.

Build one from code

curl 'https://api.dmzagent.com/v1/compliance/frameworks/FRAMEWORK_ID/export' \
  -H 'Authorization: Bearer YOUR_API_KEY' \
  -o evidence-pack.json
Safe by default. The integrity checks take no secret: a recipient re-derives every hash from the file. The signature is the separate claim that the pack came from us, and checking it takes the shared key.