Evidence You Can VerifyEvidence your team can verify independently.
Decisions on the governed paths you deploy become part of one record for your organization: what was found, what was decided, and who decided it. Changes to entries are detectable, signed checkpoints expose covered tail removal, and the verifier reports an uncovered newest tail. It does not prove every event was recorded.
Example audit chain verified.
$ redactwall verify-audit-chain --plane tenant --anchor /var/lib/redactwall/anchor
verify-audit-chain: plane tenant, tenant ten_a1a1a1a1a1a1a1a1a1a1a1a1
verify-audit-chain: head sequence 3, key version 1
verify-audit-chain: head digest sha256:e4e4e4e4e4e4e4e4e4e4e4e4e4e4e4e4e4e4e4e4e4e4e4e4e4e4e4e4e4e4e4e4
verify-audit-chain: walked 3 entries through sequence 3
verify-audit-chain: signed checkpoint at sequence 3 matches this chain's entry there
verify-audit-chain: VERIFIED - every entry from 1 to 3 re-derived under its own key and MAC domain, and every link digest matched its predecessor.
Example output, reproduced in the format the commands print. The identifiers and digests are examples, not values from any deployment.
What that looks like in practice
An auditor asks what happened on the governed paths deployed last quarter
Hand over a signed package for that reporting window and stated scope.
Someone asks whether the record could have been altered
Your team checks it themselves, on your own systems.
A third party wants to check the package you gave them
They can run the same check you do, on their own systems.
A reviewer makes a call on a held incident
Who decided, and when, is part of the record.
What you get
Supported governed paths can write decision or finding records here. Your team can run the separately shipped verifier on an exported package, on your own systems.
Changes are detectable
Changing or reordering an entry makes verification fail. Signed checkpoints expose covered tail removal, and the verifier names an uncovered newest tail.
Sealed, for a period you name
Export a bundle covering the reporting window you state. Whoever you hand it to can check it standalone.
What is in itRun by your own team
The tool that confirms the record ships to you and runs on your systems, not ours.
See what it reportsThe audit record stores decision metadata, including the kinds of finding and the action taken, rather than prompt bodies.
A separate employee activity store can retain encrypted content after mandatory hard-stop values are removed. Content access is role controlled and reads are audited. Operational retention defaults to 30 days, with a maximum of 90 days. Data handling and training policy
A check that will not flatter you
The check tells you exactly what it covered and what the package proves. A reviewer gets the real result, not a clean pass.
One thing to be clear about
This is evidence your own team can check. Disclosures states where every claim stands today.
Have the proof before anyone asks
Pilots include the checking tools from the start.
- Entry changes and covered tail removal are detectable
- A signed package for a period you name
- Checked by your team, on your systems
- The report states what the check does not prove