Page 261 of the DSE Security Knowledge Hub, with source-backed guidance, checklists, explainers, and playbooks.
An evidence lock can preserve selected video beyond normal retention. Define who may create, extend, review, and remove each lock before storage and legal obligations collide.
Read the playbook
Edge failover can copy camera recordings back after a server outage, but timing and trigger behavior vary. Acceptance must use the deployed camera, firmware, recorder, and event mode.
Read the checklist
A camera setting does not guarantee the same frame rate reaches storage. Validate the entire path under representative load and with production image features enabled.
Read the briefing
Panoramic cameras can deliver different views and dewarping options. Confirm that the archive preserves the view investigators need, not only a convenient live layout.
Read the guide
A sharp test chart at one distance can hide unusable foreground or background detail. Commission lens choice and focus across the full operational zone.
Read the checklist
Image-health analytics can flag blocked, redirected, blurred, or underexposed views, but they cannot determine operational intent. Validate alerts against each scene and workflow.
Read the guide
RTP control reports can expose packet loss and interarrival jitter. They help diagnose delivery but do not prove that recorded video is complete or usable for the intended task.
Read the explainer
SRTP can protect RTP and RTCP media traffic, but its result depends on key management and does not secure camera administration, storage, export, or operator access.
Read the explainer
RTSP is stateful and includes session timeout behavior. Verify keepalives, transport choices, recovery, and version support through the exact production path.
Read the checklist
Retention capacity is only one edge-storage requirement. Sustained writes, media endurance, outage duration, and copy-back time determine whether the design can recover.
Read the guide