- Популярные видео
- Авто
- Видео-блоги
- ДТП, аварии
- Для маленьких
- Еда, напитки
- Животные
- Закон и право
- Знаменитости
- Игры
- Искусство
- Комедии
- Красота, мода
- Кулинария, рецепты
- Люди
- Мото
- Музыка
- Мультфильмы
- Наука, технологии
- Новости
- Образование
- Политика
- Праздники
- Приколы
- Природа
- Происшествия
- Путешествия
- Развлечения
- Ржач
- Семья
- Сериалы
- Спорт
- Стиль жизни
- ТВ передачи
- Танцы
- Технологии
- Товары
- Ужасы
- Фильмы
- Шоу-бизнес
- Юмор
Secure Boot Certificates
SECURE BOOT CERTIFICATES EXPIRE IN JUNE
This is a "Will it boot?" problem disguised as a security update
Some security issues are noisy. This one is quiet, until it isn’t.
Microsoft’s Secure Boot certificates originally issued in 2011 begin expiring in June 2026. Microsoft is rolling out updated certificates, and most devices will receive them via updates, but some systems may require OEM firmware updates. Devices will continue to boot, but they may enter a degraded state where they can’t receive future boot‑level security protections.
The uncomfortable part: this isn’t just “compliance hygiene.” It’s an operational deadline with security consequences. If you miss it, you can end up with devices that still run… but can’t be fully protected at the boot chain going forward.
If you own this, do this:
Inventory which fleets are at risk (especially older hardware and managed Windows estates that don’t get firmware updates often).
Validate you can access BitLocker recovery keys and that firmware update pathways are actually in place (not just “documented”).
Use the window now to roll it out gradually, waiting until June turns it into a fire drill.
Links for a deeper technical dive are in the comments.
Видео Secure Boot Certificates канала DIESEC
This is a "Will it boot?" problem disguised as a security update
Some security issues are noisy. This one is quiet, until it isn’t.
Microsoft’s Secure Boot certificates originally issued in 2011 begin expiring in June 2026. Microsoft is rolling out updated certificates, and most devices will receive them via updates, but some systems may require OEM firmware updates. Devices will continue to boot, but they may enter a degraded state where they can’t receive future boot‑level security protections.
The uncomfortable part: this isn’t just “compliance hygiene.” It’s an operational deadline with security consequences. If you miss it, you can end up with devices that still run… but can’t be fully protected at the boot chain going forward.
If you own this, do this:
Inventory which fleets are at risk (especially older hardware and managed Windows estates that don’t get firmware updates often).
Validate you can access BitLocker recovery keys and that firmware update pathways are actually in place (not just “documented”).
Use the window now to roll it out gradually, waiting until June turns it into a fire drill.
Links for a deeper technical dive are in the comments.
Видео Secure Boot Certificates канала DIESEC
Комментарии отсутствуют
Информация о видео
17 апреля 2026 г. 11:00:20
00:00:13
Другие видео канала




















