808bits

Core Crypto Engine

FIPS 140-2 certificate #4352 · SZ DJI Technology Co., Ltd. · data as of 2026-10-09

Core Crypto Engine, from SZ DJI Technology Co., Ltd., holds FIPS 140-2 certificate #4352 at overall level 1. The validation is historical: agencies may keep the module in existing systems but not buy it new. Below are its algorithm certificates, its validation history, and the list moves this tracker has observed, which NIST does not date.

Historical. Moved to historical list due to sunsetting. Federal agencies may reference historical validations for existing systems only, not for new procurement. Observed moving to historical on 2026-09-22. It was one of the last FIPS 140-2 certificates, all moved at the 140-2 sunset on 2026-09-21.
Caveat: When operated in FIPS mode. No assurance of the minimum strength of generated keys

Certificate

Certificate number4352
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeFirmware-Hybrid
EmbodimentSingle Chip
VendorSZ DJI Technology Co., Ltd. · website
Hardware versions0xDF
Firmware versionsTEE 1.1.0, REE 1.1.0, TEE Secure Boot ROM 1.0.0

Module description

Quoted from the NIST CMVP entry for this certificate.

DJI Core Crypto Engine is a firmware hybrid cryptographic module providing foundational security services for the entire platform, including cryptography, key management, platform identity, secure boot, and secure Life Cycle State (LCS). Serving for DJI self-developed SOC, it offers high-throughput cryptography engines suitable for a diverse set of use cases.

Security level exceptions

  • Mitigation of Other Attacks: N/A

Approved algorithms (8)

AlgorithmCAVP certificates
AESA2277, A2278
CKGvendor affirmed
DRBGA2277
ECDSAA2277
HMACA2277, A2278
KBKDFA2277
RSAA2277, A2279
SHSA2277, A2278

Tested configurations

  • Linux 4.9 running on a DJI H6 SoC with an ARM Cortex A7

Validation history

DateTypeLab
2022-11-02InitialUL Verification Services, 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 at the time of the earliest snapshot
  • 2026-09-22: observed moving from active to historical
  • Validation dates on record: 2022-11-02

Source documents