Start with a threat model
Identify the assets to protect, the attacker’s access and the consequences of compromise. Cryptographic engine names alone do not specify resistance to side-channel, fault-injection or invasive attacks. Match evaluation evidence to the actual threat model.
Distinguish provisioning options
On-device key generation and externally generated key injection have different custody requirements. An HSM can protect a provisioning service, but the whole path includes operator controls, enrollment records, transport and device lifecycle transitions. The selected flow must be documented.
Build recovery into trust
Secure boot, update authorization and rollback controls are related but distinct. Plan key rotation and recovery for devices already in the field. Disabling debug is not a substitute for a vulnerability-response and servicing process.
