Hi, how could SE050 possibly contribute to a concept to prevent firmware from being hacked during and after a remote update process?
Our question in detail: During firmware remote data transfer the firmware code is protected by TLS. However, finaly the firmware sits as a de-crypted binary in the NAND or NOR Flash. The identified risk is that this NAND or NOR could be sniffed or the memory hardware component could be extracted from the PCB and put in a spy hardware environment.
Thank you ! Best regards, Bernd