ARM® TrustZone® CryptoCell-712
ARM® TrustZone® CryptoCell-712, from ARM LIMITED, holds FIPS 140-2 certificate #3263 at overall level 1. The validation is historical: agencies may keep the module in existing systems but not buy it new. Below are its validation history, algorithm certificates and security policy, drawn from the NIST CMVP entry.
Certificate
| Certificate number | 3263 |
|---|---|
| Standard | FIPS 140-2 |
| Status | historical |
| Overall level | 1 |
| Module type | Firmware-Hybrid |
| Embodiment | Single Chip |
| Vendor | ARM LIMITED · website |
| Hardware versions | 712 |
| Firmware versions | (TEE) 1.1.0.48, (REE) 1.1.0.49 and (TEE ROM) 1.0.0.1145 |
Module description
Quoted from the NIST CMVP entry for this certificate.
Arm TrustZone CryptoCell is a security engine with root of trust and cryptographic accelerator capabilities. It is provided to customers as Silicon IP and accompanying firmware. Arm partners integrate the silicon into the host CPU hardware, and use the firmware to drive the silicon and provide high-level functions
Security level exceptions
- Mitigation of Other Attacks: N/A
Approved algorithms (10)
| Algorithm | CAVP certificates |
|---|---|
| AES | 4743, 4749 |
| CKG | vendor affirmed |
| CVL | 1385, 1386 |
| DRBG | 1630 |
| ECDSA | 1184 |
| HMAC | 3158, 3163 |
| KBKDF | 151 |
| RSA | 2593, 2596 |
| SHS | 3887, 3892 |
| Triple-DES | 2522, 2523 |
Allowed algorithms
Diffie-Hellman (CVL Cert. #1385; key establishment methodology provides 112 bits of encryption strength); EC Diffie-Hellman (CVL Cert. #1385; key establishment methodology provides between 112 and 256 bits of encryption strength); NDRNG; RSA (key wrapping; key establishment methodology provides 112 or 128 bits of encryption strength)
Tested configurations
- Arm Juno rev.2 with Linux 3.18
Validation history
| Date | Type | Lab |
|---|---|---|
| 2018-08-16 | Initial | CYGNACOM SOLUTIONS INC |
Status timeline
As observed by this tracker's snapshots. NIST publishes no dates for list moves; observation began 2026-08-21, so earlier changes carry no date.
- 2026-08-21: first observed by this tracker, status historical
- Validation dates on record: 2018-08-16