MediaTek CryptoCore
MediaTek CryptoCore, from MediaTek Inc., holds FIPS 140-2 certificate #3264 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 | 3264 |
|---|---|
| Standard | FIPS 140-2 |
| Status | historical |
| Overall level | 1 |
| Module type | Firmware-Hybrid |
| Embodiment | Single Chip |
| Vendor | MediaTek Inc. |
| Hardware versions | 1.0 |
| Firmware versions | 1.0 |
Module description
Quoted from the NIST CMVP entry for this certificate.
MediaTek CryptoCore is a firmware hybrid cryptographic module providing foundational security services for the platform, including secure boot, secure life cycle state, platform identity and key management. It offers high-throughput cryptography operations, suitable for a diverse set of use cases.
Security level exceptions
- Mitigation of Other Attacks: N/A
Approved algorithms (11)
| Algorithm | CAVP certificates |
|---|---|
| AES | 4788, 4789 |
| CKG | vendor affirmed |
| CVL | 1428, 1429 |
| DRBG | 1661 |
| ECDSA | 1203 |
| HMAC | 3190, 3191 |
| KBKDF | 155 |
| KTS | |
| RSA | 2621 |
| SHS | 3926, 3927 |
| Triple-DES | 2541, 2542 |
Allowed algorithms
EC Diffie-Hellman (CVL Cert # 1429; key establishment methodology provides between 112 and 256 bits of encryption strength); Diffie-Hellman (key establishment methodology provides 112 bits of encryption strength); NDRNG; RSA (key wrapping; key establishment methodology provides 112 or 128 bits of encryption strength)
Tested configurations
- MediaTek Helio X30 SoC with Android Nougat and Trustonic t-base 311b
Validation history
| Date | Type | Lab |
|---|---|---|
| 2018-08-20 | Initial | CYGNACOM SOLUTIONS INC |
| 2018-08-31 | Update | 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-20, 2018-08-31