How can I prevent AES key being overwritten by hacker in MAX10

[YutaWakasugi]

Hi,

I'm referring Intel® MAX® 10 FPGA Configuration User Guide.
In my understanding, once we program AES key and turn on "Allow encrypted POF only" option, configuring CRAM through JTAG will be prevented, and configuration can be done only from the encrypted(by correct key) config image programmed in CFM.
However, can we still erase and re-program the AES key (AES key is not OTP) without knowing currently programmed AES key, correct?
If so, how can we prevent hackers from replacing AES key by their own key? Do we need to turn on "JTAG secure" option to disable JTAG itself?

Thank you

[YuanLi_S_Intel]

Hi,

Yes, you need to turn on jtag secure mode to prevent the access of JTAG by third party to do full erase on the device.

Regards,

Bruce

[YutaWakasugi]

Hi, 

Thank you for the quick response. Let me confirm.

Once JTAG secure mode is enabled, even the internal developer who knows AES key can't update CFM.
And if we want to update CFM, we need to implement internal logic to issue UNLOCK instruction to JTAG core like below
MAX10 JTAG Secure Unlock | Design Store for Intel® FPGAs
Is my understanding correct?

Thank you,
Wakasugi 

[YuanLi_S_Intel]

Hi,

Yes, you are right.

Regards,

Bruce

[YutaWakasugi · Accepted solution]

I see, Thank you.