Page 17 of the DSE Security Knowledge Hub, with source-backed guidance, checklists, explainers, and playbooks.
A secure mobile program distinguishes company-owned and personal devices, documents privacy boundaries, enrolls management before access, protects business data, and prepares for loss, reassignment, and retirement.
Read the checklist
Business email compromise succeeds when a convincing message can change where money goes. Add independent verification, separation of duties, evidence, and rapid bank-and-IC3 response to the payment process.
Read the playbook
A useful data register follows information through collection, storage, sharing, backup, export, retention, and deletion so the organization can protect what it needs and stop retaining what it does not.
Read the guide
Annual completion is not the same as readiness. A managed learning program uses role-specific objectives, practical exercises, several measures, leadership support, and continuous improvement to change security and privacy behavior.
Read the guide
Agentic AI combines models with tools, data, memory, and planning so it can act without continuous supervision. Limit its identity, privileges, tools, context, autonomy, and blast radius before deployment.
Read the checklist
A false-alarm-resistant intrusion system depends on verified programming, device-by-device testing, monitoring-center coordination, and a documented user handoff, not merely a panel that supports the right features.
Read the checklist
A physical credential remains trustworthy only when identity verification, approval, issuance, access changes, loss response, periodic review, and revocation operate as one controlled lifecycle.
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
NIST explicitly includes physical access-control systems in OT and frames their security around mapped data flows, segmentation, controlled remote access, and availability.
Read the guide
NIST SP 1339 treats OT recovery as more than copying configuration files: tools, licenses, compatible spares, documentation, integrity, and restore tests all matter.
Read the checklist