Page 285 of the DSE Security Knowledge Hub, with source-backed guidance, checklists, explainers, and playbooks.
A post order should let a qualified officer understand the mission, authority, routine duties, prohibited actions, contacts, emergency priorities, required records, equipment checks, and relief process before accepting the post.
Read the guide
Exterior lighting should support specific human tasks without disabling glare, deep shadow, uncontrolled spill, failed controls, or an unmaintainable layout. Define the task, design to maintained performance, then measure and walk the installed result at night.
Read the guide
Windows devices can keep booting after the 2011 Secure Boot certificates expire yet miss future early-boot protections. Inventory status, update OEM firmware, pilot by hardware family, and verify the 2023 trust chain with evidence.
Read the playbook
Microsoft now plans to disable SMTP AUTH Basic authentication by default for existing Exchange Online tenants at the end of December 2026. Find every sender, choose a supported replacement, pilot it, and prove the legacy path is quiet.
Read the playbook
SMB over QUIC protects Windows file access with TLS 1.3 over UDP 443, but Windows clients can still prefer TCP and external authentication can fall back to NTLM. Prove transport, identity, certificates, and renewal before production.
Read the checklist
RPKI lets resource holders authorize which ASN may originate a prefix and lets operators validate BGP origins. It does not validate the full AS path or prove a route is benign. Build careful ROAs, redundant validators, policy, and monitoring.
Read the playbook
Kubernetes Pod Security Admission can enforce privileged, baseline, or restricted profiles by namespace while audit and warn modes expose violations first. Govern labels, policy versions, exemptions, and controller-created Pods as one system.
Read the playbook
GitHub Actions can exchange a GitHub-issued OIDC token for a short-lived cloud credential instead of storing a long-lived key. The security gain depends on strict trust claims, least-privilege cloud roles, protected environments, and tested revocation.
Read the guide
Azure Policy exemptions preserve compliance visibility while recording a Mitigated or Waiver decision, but expiration is optional and the object remains after expiry. Treat each exemption as a governed, time-bound risk record.
Read the checklist
Cloud optimization requests fail when spend cannot be tied to an accountable product, service, environment, or owner. Build allocation rules, metadata compliance, and explicit shared-cost treatment before setting savings targets.
Read the playbook