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_24hr_registrants&utm_medium=calendar&utm_source=brig
 httalk-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_24hr_registrants&utm_m
 edium=calendar&utm_source=brighttalk-transact\n\nPresenter: Aryan Kuma
 r, Product Engineer at Encryption Consulting & Surbhi Singh, Senior Ma
 rketing Consultant at Encryption Consulting\n\nThe EU Cyber Resilience
  Act (CRA) has transformed secure boot and firmware signing from "best
  practices" into mandatory legal requirements for hardware manufacture
 rs. While silicon-specific tools offer a starting point, achieving tru
 e auditable compliance across a diverse product portfolio requires a u
 nified cryptographic strategy that transcends any single vendor.\n\nIn
  this session, we move beyond basic hardware enablement to examine how
  to build a scalable, audit-ready framework for secure boot and firmwa
 re integrity. We will analyze how to integrate hardware roots of trust
  with centralized policy engines to satisfy CRA's stringent "proof of 
 origin" and "trusted code" mandates. Join us to learn how to bridge th
 e gap between silicon-level security features and enterprise-grade lif
 ecycle governance, ensuring your devices remain compliant from the fac
 tory floor to the end-user.\n\nKey Takeaways: \n\n- Analyze how increa
 sed PQC signature sizes impact your existing bootloaders and bandwidth
 -constrained update channels.\n- Implement a dual-signature strategy t
 hat provides both classical and quantum-resistant validation to ensure
  backward compatibility during the transition.\n- Map your software su
 pply chain to identify every point where code is signed, from internal
  developer commits to final production releases.\n- Evaluate the hardw
 are requirements for Hardware Security Modules (HSMs) to support the i
 ncreased computational load of PQC signing algorithms.\n- Develop a ph
 ased migration plan that prioritizes high-risk assets like long-lived 
 firmware and critical system infrastructure.
SEQUENCE:1779288550
END:VEVENT
END:VCALENDAR