Page 7 of the DSE Cybersecurity knowledge center, with source-backed guidance and practical next steps.
Source-backed guidance for identity, vulnerability reduction, ransomware readiness, detection, response, and recovery.
MFA cannot make an already-compromised workstation trustworthy. Dedicated privileged access workstations separate administration from email, general browsing, and everyday applications so high-impact credentials and sessions begin from a controlled device.
Read the guide
Control of a domain registration can redirect websites and email, disrupt public services, or remove an organization’s online identity. Registrar access deserves named ownership, strong authentication, locks, monitored changes, and an exercised recovery plan.
Read the checklist
Memory-safety flaws remain a major source of exploitable software defects. Buyers and builders should ask for an owned roadmap covering new code, legacy components, open-source dependencies, unsafe interfaces, compensating defenses, and measurable progress.
Read the guide
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 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
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