[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f924WTpRs9o9VWBisIENF48HFvaxHUfCIcXzrmndcN70":3},{"article":4,"iocs":53,"watch_terms":54,"solutions":55,"lesson":136},{"id":5,"title":6,"slug":7,"summary":8,"ai_summary":9,"brief":10,"url":11,"image_url":12,"published_at":13,"ingested_at":14,"relevance_score":15,"entities":16,"category_id":30,"category":31,"article_tags":35},"571f5f4f-afc9-44d1-bab6-f33c0d22f369","A Critical Deadline Is Approaching for Windows and Linux Security","a-critical-deadline-is-approaching-for-windows-and-linux-security-d6b333","The cryptographic keys that secure your computer's boot sequence will start to expire on June 24. Here's what that means for you.","Three Microsoft-signed certificates essential for Secure Boot on Windows and Linux systems are set to expire on June 24. This expiration poses a risk of increased UEFI-based firmware infections, as Secure Boot's chain of trust relies on these certificates to verify the integrity of boot-time firmware and software. Failure to update these keys could leave systems vulnerable to sophisticated bootkits that load before the operating system and antimalware protections.","Windows and Linux systems face boot security risks as critical cryptographic keys expire June 24.","https:\u002F\u002Fwww.wired.com\u002Fstory\u002Fa-critical-deadline-is-approaching-for-windows-and-linux-security\u002F","https:\u002F\u002Fmedia.wired.com\u002Fphotos\u002F6a342b0819ec74e5dcd4e6ca\u002Fmaster\u002Fpass\u002FGettyImages-1091064696.jpg","2026-06-21T09:00:00+00:00","2026-06-21T10:00:18.593056+00:00",8,[17,20,23,26,28],{"name":18,"type":19},"Secure Boot","product",{"name":21,"type":22},"UEFI","technology",{"name":24,"type":25},"Sednit","threat_actor",{"name":27,"type":25},"Fancy Bear",{"name":29,"type":25},"APT 28","80544778-fabb-4dcd-aa35-17492e5dcf4f",{"id":30,"icon":32,"name":33,"slug":34},null,"Vulnerabilities","vulnerabilities",[36,38,43,48],{"category":37},{"id":30,"icon":32,"name":33,"slug":34},{"category":39},{"id":40,"icon":32,"name":41,"slug":42},"89f78b1c-3503-45a1-9fc7-e23d2ce1c6d5","Malware","malware",{"category":44},{"id":45,"icon":32,"name":46,"slug":47},"c5c77cdb-f7d7-4990-9436-c81dcbff1163","Policy","policy",{"category":49},{"id":50,"icon":32,"name":51,"slug":52},"e7b231c8-5f79-4465-8d38-1ef13aea5a14","Threat Intelligence","threat-intelligence",[],[18],{"controls":56,"vendors":132},[57,86,111],{"slug":58,"name":59,"problem":60,"products":61},"vulnerability-management","Vulnerability scanning and prioritisation","You know which systems are vulnerable, and which ones to fix first.",[62,70,78],{"vendor_slug":63,"vendor_name":64,"vendor_logo":65,"product_slug":66,"product_name":67,"url":68,"description":69},"qualys","Qualys","\u002Fvendor-logos\u002Fqualys.png","vmdr","Qualys VMDR","https:\u002F\u002Fwww.qualys.com\u002Fapps\u002Fvulnerability-management-detection-response\u002F","Vulnerability management, detection and response with risk-based prioritisation.",{"vendor_slug":71,"vendor_name":72,"vendor_logo":73,"product_slug":74,"product_name":75,"url":76,"description":77},"tenable","Tenable","\u002Fvendor-logos\u002Ftenable.png","tenable-vulnerability-management","Tenable Vulnerability Management","https:\u002F\u002Fwww.tenable.com\u002Fproducts\u002Fvulnerability-management","Cloud-based vulnerability scanning and prioritisation, built on Nessus.",{"vendor_slug":79,"vendor_name":80,"vendor_logo":81,"product_slug":82,"product_name":83,"url":84,"description":85},"axonius","Axonius","\u002Fvendor-logos\u002Faxonius.png","axonius-exposures","Axonius Exposures","https:\u002F\u002Fwww.axonius.com\u002Fplatform\u002Fexposures","Brings findings from different scanners together with asset and business context, to show what matters most and track fixes to the end.",{"slug":87,"name":88,"problem":89,"products":90},"patch-management","Automated patch management","Known holes get closed in days, not months.",[91,99,103],{"vendor_slug":92,"vendor_name":93,"vendor_logo":94,"product_slug":95,"product_name":96,"url":97,"description":98},"action1","Action1","\u002Fvendor-logos\u002Faction1.png","action1-patch-management","Action1 Patch Management","https:\u002F\u002Fwww.action1.com\u002F","Cloud-native patch management for Windows, macOS and third-party applications.",{"vendor_slug":63,"vendor_name":64,"vendor_logo":65,"product_slug":87,"product_name":100,"url":101,"description":102},"Qualys Patch Management","https:\u002F\u002Fwww.qualys.com\u002Fapps\u002Fpatch-management\u002F","Patch deployment for operating systems and third-party applications, linked to vulnerability findings.",{"vendor_slug":104,"vendor_name":105,"vendor_logo":106,"product_slug":107,"product_name":108,"url":109,"description":110},"manageengine","ManageEngine","\u002Fvendor-logos\u002Fmanageengine.png","patch-manager-plus","ManageEngine Patch Manager Plus","https:\u002F\u002Fwww.manageengine.com\u002Fpatch-management\u002F","Patch management for operating systems and third-party applications, on premises or in the cloud.",{"slug":112,"name":113,"problem":114,"products":115},"endpoint-management","Device management (MDM and UEM)","Every company laptop and phone is known, encrypted, locked down and up to date.",[116,124],{"vendor_slug":117,"vendor_name":118,"vendor_logo":119,"product_slug":120,"product_name":121,"url":122,"description":123},"ninjaone","NinjaOne","\u002Fvendor-logos\u002Fninjaone.png","ninjaone-patch-management","NinjaOne Patch Management","https:\u002F\u002Fwww.ninjaone.com\u002Fpatch-management\u002F","Automated patching of operating systems and third-party applications from the cloud.",{"vendor_slug":125,"vendor_name":126,"vendor_logo":127,"product_slug":128,"product_name":129,"url":130,"description":131},"microsoft","Microsoft","\u002Fvendor-logos\u002Fmicrosoft.png","intune","Microsoft Intune","https:\u002F\u002Fwww.microsoft.com\u002Fen-us\u002Fsecurity\u002Fbusiness\u002Fmicrosoft-intune","Device management for Windows, macOS, iOS and Android, including update rings and compliance policies.",[133],{"slug":125,"name":126,"logo_path":127,"roles":134},[135],"affected",{"slug":137,"title":138,"body":139,"framework_refs":140,"framework_notes":151},"expiring-secure-boot-certificates-risk-uefi-bootkit-infections","Expiring Secure Boot Certificates Risk UEFI Bootkit Infections","Three Microsoft-signed certificates critical to the Secure Boot chain of trust are expiring on June 24, leaving Windows and Linux systems potentially unprotected against UEFI-based firmware attacks. Secure Boot relies on these certificates to cryptographically verify boot-time firmware and software integrity, meaning expired keys break this verification chain. Without updated certificates, threat actors could exploit the gap to deploy sophisticated bootkits that load before the operating system and any antimalware tools, making them extremely difficult to detect or remove. This matters because firmware-level threats persist across OS reinstalls and can survive traditional remediation efforts, representing one of the most severe and persistent attack vectors available.",[141,142,143,144,145,146,147,148,149,150],"CIS Control 2 – Inventory and Control of Software Assets","CIS Control 7 – Continuous Vulnerability Management","CIS Control 4 – Secure Configuration of Enterprise Assets","NIST SP 800-147 – BIOS Protection Guidelines","NIST SP 800-155 – BIOS Integrity Measurement Guidelines","NIST CSF PR.IP-3 – Configuration Change Control Processes","NIST CSF ID.AM-2 – Software Platforms and Applications Inventoried","NIST SP 800-40 Rev. 4 – Guide to Enterprise Patch Management Planning","ITIL Service Transition – Change and Release Management","ISO\u002FIEC 27001 A.12.6.1 – Management of Technical Vulnerabilities",{}]