Page 14 of the DSE Security Knowledge Hub, with source-backed guidance, checklists, explainers, and playbooks.
Intune driver update policies can discover, approve, pause, and report applicable Windows drivers and firmware. Use hardware-model pilots and dated approvals, while update rings continue to govern restart and user experience.
Read the playbook
Tier 1 OLTS testing proves total insertion loss, length, and polarity against the selected limit. Tier 2 OTDR testing adds event location, loss, and reflectance. Specify both where needed, test correctly, and receive native traces—not just a pass/fail PDF.
Read the checklist
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
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
The FCC’s voluntary U.S. Cyber Trust Mark is designed for qualifying consumer wireless IoT products and a QR-linked registry. It can strengthen procurement evidence, but it is not an enterprise architecture review or a forever-secure guarantee.
Read the explainer
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