Security

A robust security implementation requires a combination of hardware and software to achieve the desired level of security on a given product. Nordic provides a secure platform and all the necessary enablers to make this process easy for our customers

Features	nRF52840	nRF5340	nRF9160
True Random Number Generator (TRNG) Secure cryptography relies on secret and unpredictable random numbers.	Yes	Yes	Yes
Crypto Acceleration Hardware acceleration of symmetric and asymmetric encryption and hashing operations.	CryptoCell 310	CryptoCell 312	CryptoCell 310
Secure Storage Hardware enforced protection of data at rest.	Yes	Yes	Yes
Secure Key Usage Hardware enforced protection of key material at runtime.	Yes	Yes	Yes
Secure Boot Immutable boot partition verifying authenticity of application with anti-rollback prevention.	Yes	Yes	Yes
Secure Update Verify authenticity and integrity of firmware update.	Yes	Yes	Yes
Secure Attestation Proving device identity to establish a trusted interaction with the outside world.	-	Yes	Yes
Isolation Security by separation of trusted and non-trusted services. Protecting data, code, and peripherals.	-	Yes	Yes
Erase all protection Prevent externally triggered erase all operation	-	Yes	Yes
PSA Certified Level	Level 1	Level 2	Level 2

Generating a truly random number is a complex process, and any biases in its generation can be exploited by hackers to make key acquisition faster and easier. Pseudo Random Number Generators (PRNG), which produce random numbers from pre-set algorithms, are particularly susceptible to this vulnerability. Nordic's devices, however, employ True Random Number Generation and comply with NIST 800-90B, AIS-31, and FIPS 140-2 standards.

The building blocks of a secure device should consist of a basic set of trustworthy services for hardware accelerated cryptographic operations. 

To protect private data from being copied or disclosed outside a trusted service or device, it must be securely linked to them. The confidentiality and accuracy of private data are usually ensured through the use of keys, which must also be connected to the device and service.

Cryptographic primitives that provides confidentiality, integrity, and authenticity can provide these security properties only if the secret and private keys stays protected and secure. If a key value gets compromised then the cryptographic primitive can no longer guarantee any security.

To ensure only authorized software is executed on the device, secure boot and loading processes are necessary. Any attempt to boot with unauthorized code should be detected and prevented, although exceptions may be made for software that poses no threat to the device.

Ensuring that previous software versions can't be reinstated is crucial, and this is achieved by preventing rollback. However, in recovery situations, rollback may be permitted if authorized.

To ensure the device is secure and up-to-date with new features, secure updates are a must-have. Only legitimate firmware updates should be installed on the device, and they must be authenticated at the time of download. The update's execution must also be authorized through a secure boot process.

Attestation provides proof of a device's properties, such as its identity and the status of its security throughout its lifecycle. Verifying the device identification is a critical step in the device verification process.

The purpose of isolation is to safeguard services from being impacted by others, so that potential breaches don't comprise your entire device. This is achieved through separating trusted, less trusted, and untrusted services from each other.

Read more about security by separation in our Trusted Firmware-M DevZone blog.

Preventing unauthorized access or use of the device is an important security feature. When erase all protection is configured the erase all operation cannot be triggered externally (e.g. with a debug probe).