BEGIN:VCALENDAR
VERSION:2.0
X-WR-CALNAME:BrightTALK Event
PRODID:-//BrightTALK//NONSGML BrightTALK Event Calendar//EN
CALSCALE:GREGORIAN
METHOD:REQUEST
BEGIN:VEVENT
UID:https://www.brighttalk.com/webcast/20305/666324
DTSTAMP:20260416T131302Z
ORGANIZER:MAILTO:noreply@brighttalk.com
LOCATION:BrightTALK
URL:https://www.brighttalk.com/webcast/20305/666324?utm_campaign=commu
 nication_reminder_starting_now_registrants&utm_medium=calendar&utm_sou
 rce=brighttalk-transact
DTSTART:20260521T150000Z
DTEND:20260521T160000Z
SUMMARY:Live webcast: CRA Compliance Architecture: Securing the Firmwa
 re Supply Chain Across Diverse Hardware
DESCRIPTION:Click here to attend: https://www.brighttalk.com/webcast/2
 0305/666324?utm_campaign=communication_reminder_starting_now_registran
 ts&utm_medium=calendar&utm_source=brighttalk-transact\n\nPresenter: Ar
 yan Kumar, Product Engineer at Encryption Consulting & Surbhi Singh, S
 enior Marketing Consultant at Encryption Consulting\n\nThe EU Cyber Re
 silience Act (CRA) has transformed secure boot and firmware signing fr
 om "best practices" into mandatory legal requirements for hardware man
 ufacturers. While silicon-specific tools offer a starting point, achie
 ving true auditable compliance across a diverse product portfolio requ
 ires a unified cryptographic strategy that transcends any single vendo
 r.\n\nIn this session, we move beyond basic hardware enablement to exa
 mine how to build a scalable, audit-ready framework for secure boot an
 d firmware integrity. We will analyze how to integrate hardware roots 
 of trust with centralized policy engines to satisfy CRA's stringent "p
 roof of origin" and "trusted code" mandates. Join us to learn how to b
 ridge the gap between silicon-level security features and enterprise-g
 rade lifecycle governance, ensuring your devices remain compliant from
  the factory floor to the end-user.\n\nKey Takeaways: \n\n- Analyze ho
 w increased PQC signature sizes impact your existing bootloaders and b
 andwidth-constrained update channels.\n- Implement a dual-signature st
 rategy that provides both classical and quantum-resistant validation t
 o ensure backward compatibility during the transition.\n- Map your sof
 tware supply chain to identify every point where code is signed, from 
 internal developer commits to final production releases.\n- Evaluate t
 he hardware requirements for Hardware Security Modules (HSMs) to suppo
 rt the increased computational load of PQC signing algorithms.\n- Deve
 lop a phased migration plan that prioritizes high-risk assets like lon
 g-lived firmware and critical system infrastructure.
SEQUENCE:1779374782
END:VEVENT
END:VCALENDAR