Video evidence export and integrity

Keep file hashes, source details, transformations and custody records with video exports. Record what the available evidence establishes about the footage and its timestamps.

Overview#

Evidence quality depends on faithful retrieval, provenance, time, transformation history, protected custody, and reproducible playback. A file hash proves only that later bytes match the hashed bytes; it doesn't prove the camera, clock, identity, or scene was trustworthy.

Preserve layers#

1. Native/master retrieval: original container/segments, metadata, logs, and vendor player/codec where authorised and needed.
2. Working copy: controlled derivative for review, redaction, or distribution.
3. Disclosure copy: minimum necessary format/content with explicit transformations.

Avoid transcoding the only copy. Open formats improve access but can change compression, resolution, aspect ratio, timestamps, overlays, audio, or metadata. NIST's Standard Practice for Data Retrieval from Digital CCTV Systems specifically notes these risks and emphasizes permission and contemporaneous audit notes.

Export manifest#

Record:

case/request and legal/organizational authority
operator and authenticated account/workstation
source system/device/camera/recording identifiers and versions
requested and actual time range, timezone/offset, clock quality
native segment/track IDs, gaps, audio/metadata inclusion
export format, codec/player and exact options
file names, sizes, cryptographic hash algorithms/values
signatures/certificates and validation time/trust source
every transcode, crop, resize, overlay, redaction, trim, or rewrap
storage/copy/access/transfer/custody events

Store sensitive evidence only in approved evidence systems with access control, encryption, retention, audit, and legal governance controls, not in ordinary documentation repositories.

Interoperability and signing#

NIST IR 8161 Rev. 1 recommends a CCTV digital video export profile supporting interoperability, metadata, and chain of custody/integrity needs. IEC 62676-2-11:2024 defines VMS/VSaaS interoperability levels that include export.

ONVIF's Media Signing Add on is currently a Version 1.0 Release Candidate. It defines source signing for encoded H.264 and H.265 video so a supporting client can verify origin and whether signed frames changed after capture. The verifier still needs trusted certificate material and a defined trust policy. Audio is outside the current Release Candidate. ONVIF expects the final specification at the end of 2026. The 26.06 specification history also records Media Signing support in the ONVIF Export File Format. Verify exact device, client, profile and trust chain support before relying on it.

Validation#

• Verify hash/signature with approved tools and trust anchors; record tool/version/result.
• Play beginning, middle, end, transitions, audio, and representative gaps using preserved and independent playback paths.
• Correlate source time with event/audit and known clock uncertainty.
• Confirm camera/source/scene and that privacy masks/overlays are source or derivative transformations as stated.
• Keep master read only/immutable according to policy; produce new derivatives instead of overwriting.

Privacy and release#

Export authority is separate from viewing authority. Apply case/site/camera/time scope, dual review where required, watermarking/redaction policy, secure transfer, recipient validation, expiration, revocation where possible, and disclosure audit. Redaction creates a derivative and must never be represented as untouched original.

Return to Video surveillance systems.