Page 14 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.
A PoE port that powers a device on the bench does not prove the full switch can support every camera, reader, intercom, heater, illuminator, and edge function during cold start, restart, failover, or power-supply loss.
Read the checklist
Post-quantum migration starts with visibility: find where certificates, keys, algorithms, protocols, libraries, firmware, hardware, vendors, data lifetimes, and trust relationships are embedded across IT and physical security.
Read the guide
A bank security review should connect procedures, training, device testing, incidents, local risk, and unresolved exceptions so the security officer can report on program effectiveness, not simply equipment presence.
Read the guide
Genetec’s Security Center 5.14 guide separates Basic and Advanced hardening and warns that greater security can introduce usability, complexity, or performance tradeoffs.
Read the checklist
Profile G standardizes important recording and retrieval interfaces, but a resilient edge-recording design still needs capacity, outage, recovery, and evidence tests.
Read the guide
Profile M standardizes analytics metadata and events between products. It does not certify analytic accuracy, lawful use, model quality, or every conditional feature.
Read the explainer
ONVIF is ending new v1.0 conformance submissions on March 31, 2027. Version 2.0 is scheduled, not yet a final conformance target, so plans need vendor evidence.
Read the briefing
Profile D standardizes communication between access peripherals and a securely located client. It does not certify the complete door, credential, or life-safety design.
Read the guide
SIA’s 2025 Code organizes privacy responsibilities around purpose, impact assessment, minimization, accuracy, retention, security, access, transparency, and review.
Read the playbook
Axis documents distinct certificate roles for HTTPS server identity and 802.1X network authentication. Each needs ownership, expiry monitoring, renewal, and recovery testing.
Read the guide