Page 20 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.
DDoS readiness requires prioritized public services, provider coverage and emergency contacts, observable baselines, upstream mitigation, exercised decisions, and validated recovery.
Read the playbook
Cyber supply-chain risk management connects enterprise governance, business processes, acquisition, supplier evidence, operating oversight, incident coordination, continuity, and secure exit.
Read the guide
A vulnerability-disclosure program needs clear scope, monitored intake, acknowledgement, secure tracking, technical ownership, coordinated remediation, communication, and measurable closure.
Read the guide
FTC guidance connects immediate operational security, forensic preservation, scope determination, corrective action, accurate communication, and fact-specific legal notification decisions.
Read the playbook
Secure technology procurement evaluates verifiable evidence before purchase and throughout the lifecycle, including defaults, development, components, updates, access, data, support, and exit.
Read the checklist
Administrator-side phishing defense combines phishing-resistant authentication, secure defaults, message and web controls, endpoint protection, rapid reporting, evidence, and tested response.
Read the checklist
DNS over HTTPS protects client-to-resolver traffic, but unmanaged external resolvers can bypass enterprise filtering, logging, caching, internal naming, and split-DNS behavior.
Read the explainer
NIST frames enterprise patching as planned preventive maintenance: identify, prioritize, acquire, install, verify, and govern updates across their full operating lifecycle.
Read the guide
NIST SP 800-61 Rev. 3 integrates incident response across Govern, Identify, Protect, Detect, Respond, and Recover instead of isolating it as an emergency-only process.
Read the playbook
Cyber recovery requires prioritized resources, service-specific playbooks, realistic testing, measurable outcomes, and continuous improvement—not merely a successful backup job.
Read the playbook