Release, export and custody

For security officers and instructors: the few actions a person takes in the security pipeline, and how to prove afterwards that nothing changed.

Review a product#

Open Operations → Security. The review queue lists products waiting for a decision with their marking and why they are waiting. For each, choose Release, Withhold or, for a withheld or sealed product, Purge, and add a note. The decision is recorded in custody and the audit log.

Redact by hand#

Instructors and security officers can redact from the debrief page:

• a time span: whole frames are replaced with a slate, or
• a rectangle within a time span: that region is blacked out.

A reason is required. The redacted video replaces the original in both the sanitized and debrief products; custody keeps both hashes.

Export a package#

From the debrief or the Security page, choose Export and the destination network. The zip contains only the products that pass every rule for that network and for you, plus a signed export manifest listing what was included (marking and SHA-256) and what was withheld and why, the custody manifest and the public key.

Verify custody#

Verify custody on the debrief or Security page checks the signature, the chain and that every product file still has its recorded hash. A file changed outside the application is caught. The receiving side can verify a package without access to this system:

aarcv verify-package S-1A2B3C4D_unclass_20261023.zip --public-key aarcv_custody_public_key.pem

It prints a JSON report and exits 0 only if every check passes. Download the public key from the Security page.

Audit checkpoints#

The audit log is hash-chained. Signed checkpoints of its length and head are taken every 50 entries, hourly and on demand, so truncating or rewriting the log is detected. Security officers can take a checkpoint and verify all of them from the Security page.