Page 156 of the DSE Networks & Infrastructure knowledge center, with source-backed guidance and practical next steps.
Guidance for resilient networks, Wi-Fi, firewalls, cabling, power, exposure reduction, and connected-device planning.
VPN, overlay, encapsulation, and cloud paths can carry less payload than an endpoint interface suggests. Validate bidirectional Path MTU, ICMP behavior, transport adaptation, and representative applications before intermittent stalls reach production.
Read the playbook
IPv6 may be active on endpoints, servers, and network equipment before an organization intentionally deploys it. Unmanaged IPv6 creates a parallel path around inventories, filtering, monitoring, segmentation, and incident procedures designed only for IPv4.
Read the checklist
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
An alarm device is useful only when people can perceive it, distinguish its meaning, report the emergency, take the planned action, and account for others. Test the technology and the workplace plan as one operating sequence.
Read the playbook
A configured DHCP failover relationship is not proof of client continuity. Test both partner paths, relays, lease renewal, new leases, DNS updates, state transitions, scope replication, monitoring, and controlled recovery before relying on it.
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
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
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