Page 11 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.
Unauthenticated scans show an outside view; authenticated checks can inspect local configuration, software, and patch evidence. Use both deliberately, protect scanner credentials, prove successful authentication, and handle fragile systems separately.
Read the guide
Removable media can carry essential recovery data, sensitive records, and malicious content across trust boundaries. Define approved uses, managed media, encryption, scanning, transfer stations, custody, retention, and sanitization by risk.
Read the playbook
An exception without an owner, evidence, compensating control, expiry, and removal plan becomes an undocumented standard. Use a common register, risk-based approval, automatic reminders, verification, and escalation for renewal.
Read the playbook
An alternate location is useful only if authorized people can reach it, authenticate, communicate, obtain governed data, perform priority work, and sustain operations. Design and exercise the entire capability, not just the address.
Read the guide
Microsoft has fixed CVE-2026-70329, an Outlook integer-overflow vulnerability rated CVSS 8.8. Exploitation requires a user to open a malicious Office file. Review the exact affected editions, deploy the August 11 security release, and verify the installed build by servicing channel.
Read the briefing
Microsoft reports active exploitation of CVE-2026-68820, a Windows privilege-escalation flaw that can grant SYSTEM access. Inventory affected systems, deploy the applicable August update, and verify the result with evidence.
Read the briefing
Beginning September 1, 2026, Microsoft will start auto-enabling passkeys and registration nudges for SMS- and voice-enabled users in public-cloud Microsoft Entra ID tenants. On February 1, 2027, Microsoft-provided SMS and voice delivery ends; organizations must migrate affected users to a phishing-resistant method or configure a customer-managed telecom provider.
Read the briefing
Information remains exposed before, during, and after an exchange—regardless of whether it moves through an API, portal, file transfer, email, shared database, or manual process. Put protection duties and exit conditions in an owned agreement.
Read the playbook
The most expensive asset is not always the component whose loss matters most. Trace organizational goals through programs, systems, functions, and components so protection, acquisition, maintenance, and recovery follow operational consequence.
Read the guide
Threat and incident information loses value when recipients cannot tell who may receive it. Use the four TLP 2.0 labels consistently, keep the source’s marking intact, and add separate handling instructions when TLP does not answer the need.
Read the guide