Page 278 of the DSE Security Knowledge Hub, with source-backed guidance, checklists, explainers, and playbooks.
A mechanical key can bypass identity, schedules, revocation, alarms, and audit trails. Govern high-impact keys with named ownership, least privilege, controlled issue, inventory, return, loss response, and periodic proof of custody.
Read the playbook
A call button that rings once is not a commissioned entry workflow. Verify intelligible two-way audio, visual and identity context, correct release, network and power loss, unanswered-call escalation, accessibility, privacy, and operator action.
Read the checklist
Biometric matching has false matches and false non-matches, while spoofing, environment, enrollment, demographics, privacy, and fallback shape real risk. Pilot the actual population and workflow before treating a biometric as trusted access.
Read the guide
Microsoft Entra authentication context can invoke Conditional Access for a sensitive action inside a capable application. Use it to add risk-appropriate step-up without assuming it protects unsupported paths or replaces baseline access policy.
Read the guide
Microsoft Entra cross-tenant access settings govern inbound and outbound B2B relationships and trust in external MFA or device claims. Inventory real partners, defaults, applications, and lifecycle before broad collaboration becomes the policy.
Read the playbook
Blocking sign-in and revoking refresh tokens are important, but existing access and application sessions can end on different timelines. Run a documented containment workflow and verify effective loss of access across supported services and independent applications.
Read the playbook
Shared mailboxes outlive projects and teams unless someone owns membership, direct sign-in, forwarding, retention, licensing, automation, and closure. Govern each mailbox as a business service, not a permanent bucket of delegated access.
Read the checklist
Retention policies, retention labels, records controls, and eDiscovery holds answer different questions. Route each requirement through legal, records, privacy, workload, license, scope, deployment, validation, exception, and release decisions.
Read the guide
Group Managed Service Accounts let supported domain services use domain-managed passwords and simplified SPN management. Migration still requires application support, dependency discovery, least privilege, host authorization, staged testing, and rollback.
Read the playbook
AD CS can issue credentials used for authentication, signing, and encryption. Treat certification authorities, templates, enrollment rights, web endpoints, keys, revocation, and recovery as high-value identity infrastructure.
Read the playbook