Video Recording Integrity: Digital Signature and Watermark Verification

Proving a camera recording hasn’t been altered: the difference between watermarks, SHA-256 and digital signatures, signed export, NTP consistency and the verification sequence followed on site.
Technical summary
Technology
Digital signatures, SHA-256, watermarks, SEI, ONVIF Media Signing, RFC 3161, NTP, OpenSSL
Topic
Technically proving a camera recording hasn’t been altered
Level
Intermediate–advanced
Prerequisites
  • Access to VMS export functions
  • Basic cryptography concepts (hashes, public keys)
  • Knowledge of NTP configuration
In this article8 sections

When a camera recording comes to the table in an incident review, internal investigation or dispute, the first objection is predictable: “This footage has been tampered with.” This objection isn’t answered with “our system is reliable”; it’s shown technically that the recording hasn’t changed. Below we explain what watermarks, cryptographic hashes and digital signatures prove and don’t prove, the difference between signing at camera and VMS level, where integrity breaks during export and how timestamp consistency is ensured. Who received the recording and how, that is, the human side of the process, is in the camera recording incident investigation and chain of custody article. You can assess how to present the source, date and integrity information of a camera recording within the framework of audit evidence types and reliability.

Why integrity must be proven technically

Video editing tools are in everyone’s hands. Cutting footage, removing frames or changing time information takes minutes. When the other side claims a recording has been edited, you need to show, with a method that can be verified independently, that the recording hasn’t changed since a specific moment. Proof, not assertion. Integrity design should answer three questions:

  • Immutability: Has even a single bit of the file changed since it was signed or hashed?
  • Source: Does the recording really come from the camera or recording server claimed?
  • Time: Is the time information in the image and metadata based on a reliable clock source?

Differences between watermarks, digital signatures and hashes

In sales documents, these three concepts are often used interchangeably. The assurance they provide isn’t the same:

Mechanism How it works What it shows Weakness
Visible overlay (OSD) The time and camera name are written onto the image Informational No evidential value
Invisible watermark Manufacturer-specific information is embedded in the image data Suspicion of alteration Closed method; independent verification is hard
Cryptographic hash A SHA-256 digest of the file is taken Immutability after the hash is taken The hash can also be changed; doesn’t show the source
Digital signature The hash is signed with a private key and verified with a certificate Immutability and source Requires key management
Trusted timestamp The hash is sealed by a timestamp authority That the file existed at that moment Requires an external service or an internal TSA

A hash is a file’s fingerprint: if a single bit changes, the SHA-256 value comes out completely different. The problem is that whoever changes the file can also calculate a new hash and write it over the old one. Keeping the hash in a text file next to the file therefore proves nothing on its own. A digital signature closes this gap: the hash is signed with a private key held only by the signer; the verifying party uses the public key or certificate to see both that the content hasn’t changed and that the signature belongs to that key. A trusted timestamp, using the method defined in RFC 3161, has an independent authority confirm that a given hash value existed at a given moment.

Signing at camera and VMS level

Where the signature is produced determines where the integrity chain begins. Wherever the chain starts, the assurance covers what comes after.

Signing at camera level

Some cameras sign video at the source. The common approach is to add hashes and signatures for groups of frames to the H.264/H.265 stream as SEI (Supplemental Enhancement Information) messages; the signing key is kept in the camera’s hardware security component. Axis offers this approach as “Signed Video”; ONVIF has also published the Media Signing specification aimed at standardizing video signing at the source. The advantage is that the chain starts at the camera: even if the recording server or storage is compromised, changes to signed frames are detected. The limit is that the VMS must preserve this SEI data during recording and export, and a verification tool must exist. Verify support on the camera, VMS and player side from the manufacturers’ current documentation; if one link in the chain doesn’t support it, the signature is lost along the way.

Signing at VMS level

Some enterprise VMSs sign recordings written to the database on the recording server and exported packages. In Milestone XProtect, for example, signing can be enabled on the recording server and signatures added to exports in the VMS’s own format; verification is done with the player that comes with the package. In this model, the chain starts at the recording server. If the stream from the camera to the server is altered on the network, this signature won’t notice. That’s why carrying camera–server traffic on a separate VLAN and, where possible, encrypted (RTSPS or SRTP, depending on camera and VMS support) is part of integrity design. A common situation: the signing feature is included in the license but has never been turned on.

Criterion Camera signature VMS signature
Start of the chain The camera’s encoder output Recording server
Against alteration on the network Protects Doesn’t protect
Dependency Camera model and firmware VMS version and license
Verification tool Manufacturer/ONVIF-compatible verifier VMS player

Preserving integrity during export

In enterprise camera systems, the place where the integrity chain breaks most often is export. Everything may be set up correctly on the recording server; a single wrong click by an operator ends the chain. Typical mistakes and the right practice:

  • Format conversion: Exporting directly to MP4 or AVI instead of the VMS’s signed format often leaves the signature outside the file. Re-encoding invalidates camera and VMS signatures in every case. Export in the signed original format first; if needed for sharing, produce a separate converted “viewing copy” and label it as such.
  • Masking and cropping: Blurring the faces of third parties produces a new file and invalidates the original signature. Keep the original signed export, and record which operations produced the edited version.
  • Export password and encryption: Encryption provides confidentiality; it doesn’t prove integrity on its own. They’re separate settings; check both.
  • Off-record copies: A screen recording or filming the monitor with a phone breaks the chain completely. It’s not used in incident investigation.
  • Export record: Who took which range of which camera, and when, should be in the VMS audit trail. Designing the permission model is explained in the access permission model for camera recordings article.

Calculate the hash of the exported package at the time of handover and write it on the handover record. A hash calculated later doesn’t cover the period after handover. The commands below produce SHA-256 on Windows and Linux:

# Windows PowerShell
Get-FileHash -Algorithm SHA256 .\Incident_2026-11-03_Camera12.zip

# Linux
sha256sum Incident_2026-11-03_Camera12.zip > Incident_2026-11-03_Camera12.zip.sha256
sha256sum -c Incident_2026-11-03_Camera12.zip.sha256

If there’s no VMS signature, or additional assurance is wanted, a signature with the organization’s own key and an RFC 3161 timestamp can be added. Example flow with OpenSSL:

# Sign and verify with the organization's key
openssl dgst -sha256 -sign org_key.pem -out package.zip.sig package.zip
openssl dgst -sha256 -verify org_public.pem -signature package.zip.sig package.zip

# Create a timestamp request and send it to the TSA (the address is that of the TSA used)
openssl ts -query -data package.zip -sha256 -cert -out package.tsq
curl -s -H "Content-Type: application/timestamp-query" \
  --data-binary @package.tsq https://tsa.example.local/tsr -o package.tsr
# Verify the TSA response
openssl ts -verify -data package.zip -in package.tsr -CAfile tsa_ca.pem -untrusted tsa.crt

Timestamps and NTP consistency

A signature protects the content; it doesn’t prove that the time in the content is correct. If the camera clock is five minutes behind, the signed recording is five minutes behind too. When footage from two cameras is placed side by side, the sequence of events doesn’t match, and that’s exactly where an objection gets the easiest foothold. Clock drift is an often-overlooked integrity gap. For time consistency:

  • Cameras should connect not to public servers on the internet but to two or more NTP servers inside the organization. NTP version 4 behavior is defined by RFC 5905.
  • Recording servers and cameras should use the same time source. If the difference between the camera timestamp and the server’s receive time goes beyond network latency, there’s clock drift.
  • Time zone and daylight saving settings should be consistent across cameras and the VMS; the exported file should state whether times are UTC or local time.
  • Clock drift should be monitored, with an alarm raised when a threshold is exceeded.
# Sync status on a Linux NTP server (chrony)
chronyc tracking
chronyc sources -v

# Clock status and drift measurement on a Windows recording server
w32tm /query /status
w32tm /stripchart /computer:ntp1.corp.local /samples:5 /dataonly

On most models, the cameras’ clock status is read from the web interface or with the ONVIF GetSystemDateAndTime call. Add this check to the camera health monitoring process; looking manually once a year won’t catch drift.

Verification steps

Before a recording is handed over as evidence, or upon an objection from the other side, follow this sequence:

  1. Check that the exported package matches the SHA-256 value on the handover record.
  2. Verify the VMS or camera signature with the manufacturer’s verification tool; record the tool’s version and the result with a screenshot.
  3. Check whether the result is “all frames verified” or “there is an unsigned range.” Unsigned ranges can occur at recording server changeovers or failover moments; knowing this in advance means no surprises when an objection comes.
  4. Extract the export record (user, time, camera, range) from the VMS audit trail.
  5. Show the NTP sync status of the camera and server clocks on the incident date, from monitoring records if available.
  6. If an organizational signature and RFC 3161 timestamp were used, verify them too.

Limitations

  • Manipulation before the source: A signature protects what the camera sees. A screen placed in front of the camera or compromised camera firmware isn’t detected by a signature; firmware security is a separate topic.
  • Unsigned ranges: If signing was turned on later, earlier recordings are unsigned. Document the date the setting was changed.
  • Long-term verification: So that it can be shown the signature was valid on the date it was applied even after the certificate expires, the timestamp and certificate chain should be kept together with the video recording archive.
  • Legal assessment: How technical integrity evidence is assessed is at the discretion of the court. The technical mechanism gains meaning when presented together with process records.

A signature alone isn’t enough. It carries weight together with the process record. Protecting incident recordings to be kept long-term in immutable form in the archive is the subject of the video recording archiving and backup article. For setting up export permissions and the audit trail, see the camera recording access rights and audit trail service page.

Frequently asked questions

Does a watermark added to a video recording prove it hasn’t been altered?

A visible overlay text (OSD) provides no proof; it’s easily faked. Manufacturers’ invisible watermark features can help detect changes, but most are closed methods. To independently verify that a recording hasn’t changed, use mechanisms based on cryptographic hashes and digital signatures.

Does converting exported video to MP4 break the signature?

A signature in the VMS’s own format usually can’t be verified once the file is converted to another format. Re-encoding invalidates the signature in every case. Keep the original signed export; mark the converted copy as a viewing copy only.

Is a SHA-256 hash value enough on its own?

No. A hash shows that the file hasn’t changed since the moment it was calculated; but the hash value itself can be changed along with the file. Record the hash through a separate channel, sign it or have it sealed with a trusted timestamp.

If the camera’s clock is wrong, is a signed recording valid?

A signature protects the integrity of the file, not the accuracy of the time inside it. If the camera clock is wrong, the signed recording carries the wrong time too. That’s why NTP synchronization of cameras and recording servers and monitoring clock drift are part of integrity design.

Support

Contact us for support or a discovery session on this topic.

Contact form
[email protected]

Eretek Video Surveillance

IP cameras, recording and central management infrastructure. We plan blind spots, retention periods and the camera network around the risks of each site.

Knowledge Center

Other articles