Quick answer: Set the recorder and cameras to the correct site time, use an approved time source, and verify the timestamps you actually export. Keep the available logs and manage HTTPS certificates deliberately. These controls support a useful system record; they do not by themselves establish that footage meets every legal or insurance requirement.
On this page
Start with the site’s time plan
A clip marked 14:05 is difficult to compare with a door event at 14:08 unless you know whether the clocks agree. Before commissioning, ask the customer or IT contact which time reference, time zone and permitted synchronization path the installation should use.
NTP lets a device synchronize its clock over the network. Choose the source or sources supported by the recorder and approved by IT. An internal time service can be useful on a restricted camera network; do not assume that a firewall, router or domain controller supplies NTP merely because it is present.
Record the site’s zone and daylight-saving configuration where applicable. Avoid copying your office settings onto another site. The IETF NTP best-practice reference explains the wider time-service considerations; the device manual controls the recorder’s available settings.
Verify the recorder and the cameras separately
- Set the approved source and confirm the device can reach it through the intended network path.
- Check the recorder’s displayed time against the agreed reference and record the observed difference.
- Check representative camera overlays and exported footage. A correct recorder menu clock does not prove every camera overlay is correct.
- If the recorder offers camera time synchronization, confirm that it works for the connected models. Otherwise use the supported camera time configuration.
- Check time after an authorized restart or power-recovery test when that test is part of the commissioning window. Do not interrupt an occupied site just to complete a checklist.
Agree the accuracy the project needs rather than promising a fixed millisecond result. If a clock is wrong, preserve a note of the observed offset and when it was measured before changing settings around an incident. The time-and-date troubleshooting guide provides a practical diagnostic sequence.
Troubleshoot the actual symptom
An exact hour difference suggests a zone or daylight-saving issue, but it is still a clue to check, not a diagnosis. Gradual drift can indicate unsuccessful synchronization. A difference on only one channel calls for checking that camera’s own configuration and the recorder’s supported synchronization behavior.
Ask IT to verify the required time-service destination and traffic, commonly NTP over UDP 123. On an offline network, identify a reachable approved source rather than entering a public server that the device cannot contact. After power recovery, confirm synchronization actually resumes.
Keep useful logs before they are needed
Inspect which operations, alarms and exceptions this model records. Login history, configuration changes, channel loss and storage faults can be useful where available. Do not promise that a particular user action, source address or export is logged until you have checked it.
Export a commissioning baseline and review relevant entries during service. After an incident, preserve the available logs before routine changes overwrite useful context. Record the time range, device, export date and file location. Log retention and export support vary; a quiet log is not proof that nothing happened.
Use named accounts where supported, restrict access to the records, and discuss central log collection with IT only when the device supports it. See user permissions and handover for the access plan.
Treat HTTPS warnings as something to resolve
Use HTTPS for web management where supported, with the certificate and trust arrangement approved by IT. HTTPS protects that connection; it does not establish encryption for every video stream or storage destination.
A self-signed, expired or mismatched certificate can produce a warning. Verify the correct device, hostname and certificate through the approved process. Do not train users to accept every warning. Where certificate import is supported, agree issuance, installation, renewal and recovery before disabling another management path.
Record expiry and retest after firmware or network changes. Keep the NVR hardening checklist with this record.
Record what was tested
| Check | Record |
|---|---|
| Recorder and camera clocks | Time zone, daylight-saving setting where applicable, approved time source and measured difference from the agreed reference. |
| Synchronization | Last successful sync where visible, permitted network path and any camera time-sync setting actually tested. |
| Logs | Available event types, time range, export filename, protected location and open findings. |
| HTTPS | Approved management address, certificate issuer/trust arrangement, expiry and the functions tested. |
| Follow-up | Owner and date for certificate renewal, time failures or log-storage limitations. |
Keep this information beside the cybersecurity handover checklist. For an investigation, follow the customer’s evidence instructions and preserve the original export. Accurate time and logs help explain the system; they are not a promise of admissibility.
FAQ
Must cameras take time from the NVR?
No. Use that function only where supported and tested. Some installations require camera-side time settings or another approved source.
How long will the recorder keep logs?
Confirm the model, firmware, available storage behavior and event volume. Export important records rather than assuming years of history remain available.
Does HTTPS secure the whole camera system?
It protects the configured web connection. Accounts, firmware, network restrictions and other video paths still need their own review.
Send the full recorder/camera SKUs, firmware versions and required time/log/certificate functions to Anabon technical support when a setting or capability is unclear. Obtain current documentation through the Download Center.
