Page 13 of the DSE Video Surveillance knowledge center, with source-backed guidance and practical next steps.
Practical guidance for camera, recorder, video-management, evidence, firmware, and surveillance-network decisions.
WDR specifications do not prove a usable image at a bright entrance, garage, tunnel, or reflective lobby. Test the installed camera through changing light and motion, then preserve the configuration and evidence.
Read the checklist
License-plate recognition starts with a readable captured plate. Prove the camera at the real lane angle, vehicle speed, capture distance, day/night lighting, and recording settings before trusting the recognition result or gate action.
Read the playbook
A stream can be clear and still arrive too late. Measure sensor-to-screen delay through the production camera, network, VMS, decoder, workstation, and display—under normal and stressed conditions—before live video supports a time-sensitive response.
Read the checklist
Radar can add reliable movement, position, and speed data where light, fog, shadows, or privacy limit video. Its blind spots, reflections, classification limits, zones, and response integrations still need real-scene acceptance testing.
Read the checklist
Vehicle risk is shaped by approach speed, geometry, pedestrian exposure, deliveries, traffic operations, emergency access, and site use. Use CISA’s Plan-Prevent-Protect framework to define the problem before selecting a barrier.
Read the guide
A defensible video export preserves the requested scene, native data and metadata, records who handled it, verifies playback and integrity, and keeps an untouched master separate from working copies.
Read the playbook
Camera, recorder, access-control, identity, alarm, and network records become difficult to correlate when clocks disagree. Build a governed time hierarchy, measure offset, alert on drift, and prove behavior through outage and reboot tests.
Read the guide
A demo proves that an analytic can work. Acceptance testing must show how the complete camera, scene, network, model, rules, operators, and response workflow behave in the conditions where the organization will rely on them.
Read the checklist
NIST SP 1800-36 demonstrates how an IP network and IoT device can establish identity and posture before the device receives operational network credentials—and how that trust can be renewed across its lifecycle.
Read the explainer
Manufacturer Usage Description turns intended IoT communications into machine-readable access policy. Used carefully, MUD can shrink exposure and blast radius while keeping device exceptions visible and governed.
Read the guide