Establishing Firmware Signing Framework for CRA Compliance - Seguridad Mania.com - España y América Latina

The clock is ticking. Every product sold into Europe after December 11, 2027, must be CRA-compliant. The CRA has dozens of requirements that span a product’s entire lifecycle, from first boot to decommissioning. This means OEMs must design their products to support not only the security of today, but also the security of the future, including planning for post-quantum cryptography (PQC). This requires a device to be able to:  Utilize Secure Boot to allow only trusted firmware to run on the devices  Receive and execute software updates, and ensure that the updates are authentic, unaltered, and only from a trusted source.   Securely signing code is the current gold standard for OEMs, but manual processes, siloed signing tools, and keys left unprotected are just a few of the risks that organizations face when preparing to comply with CRA.  In this webinar, you will learn: Why code signing is so important and its multiple roles in product security  Code signing’s significance in the Cyber Resilience Act  How Keyfactor and NXP have come together to overcome the pitfalls of outdated code signing processes