Check XProtect export encryption and signatures separately

Treat recipient access and recording-signature verification as separate checks when preparing an XProtect evidence export.

Source facts

The XProtect Smart Client 2026 R1 documentation separates password encryption from digital signatures in XProtect-format exports. Encryption uses AES-256 and requires a password to open the export. Including digital signatures verifies existing recording signatures during export; a failed verification can prevent a device’s export. Recipients can verify signatures in Smart Client Player. Applying privacy masks removes recording-server signatures, and very recent recordings can have only partial signature coverage.

Source: Milestone — XProtect Smart Client 2026 R1, XProtect format settings.

Applicability

These details concern the cited 2026 R1 XProtect-format settings. Confirm the deployed release and recipient’s Windows playback environment before choosing an export workflow.

DSE recommendation

DSE recommends an export checklist with distinct entries for authorized footage, privacy treatment, password delivery, player compatibility, and signature results. Have the case owner approve cameras and time boundaries. Deliver the password through an agreed separate channel and restrict access to the exported files. Record any missing or partial signature coverage rather than describing the package simply as verified. Preserve the original export and document subsequent handling in the case record.

Verification

Open a sample package in the intended recipient environment and check playback and signature status. Record the exact export options and outcome. These checks support operational handling; they do not establish legal admissibility.

Official reference

Milestone — XProtect Smart Client 2026 R1, XProtect format settings. Reviewed October 14, 2026.