Why the Secure Boot Certificate Update Is More Complicated Than It Looks
Secure Boot certificate changes are coming, and most teams don’t know if they’re ready for the June 2026 deadline. This isn’t a simple update you push and move on. It’s a multi-step process across firmware, bootloaders, and the operating system, which means gaps are easy to miss. Devices will continue to boot and reports may still look clean, but that doesn’t mean you’re secure. If updated certificates aren’t fully in place, older trust chains remain, leaving vulnerabilities like Black Lotus (CVE-2022-21894) exposed without any clear signal.
This is where teams get stuck. IT believes it’s handled. Security isn’t convinced. No one can confidently prove it either way.
In this session, we’ll show you how to answer that question with confidence using a new report in Advanced Insights for ConfigMgr, giving you a clear, defensible view of what’s covered and what’s not. We’ll also be joined by Secure Boot expert Jeffrey Sutherland to share his insights and answer your questions live.
Don’t wait for devices to go silent. Save your spot.
What You’ll Walk Away With: