808bits

Qualcomm® Crypto Engine Core

FIPS 140-2 certificate #4647 · Qualcomm Technologies, Inc. · data as of 2026-10-09

Qualcomm® Crypto Engine Core, from Qualcomm Technologies, Inc., holds FIPS 140-2 certificate #4647 at overall level 2. 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

Certificate

Certificate number4647
StandardFIPS 140-2
Statushistorical
Overall level2
Module typeHardware
EmbodimentSingle Chip
VendorQualcomm Technologies, Inc. · website
Hardware versions5.6.2[1], 5.6.1[2] and 5.6.5[3]

Module description

Quoted from the NIST CMVP entry for this certificate.

Qualcomm Crypto Engine Core is a general purpose cryptographic hardware engine capable of securely processing various confidentiality and integrity algorithms across multiple execution environments.

Security level exceptions

  • Mitigation of Other Attacks: N/A

Approved algorithms (4)

AlgorithmCAVP certificates
AESA1656, A2045, A4094
HMACA1656, A2045, A4094
SHSA1656, A2045, A4094
Triple-DESA1656, A2045, A4094

Tested configurations

  • Snapdragon 8cx Gen 3 Mobile Compute Platform[1], Snapdragon 8 Gen 1 Mobile Platform[2], Snapdragon 8+ Gen 1 Mobile Platform[2], Snapdragon 7 Gen 1 Mobile Platform[2] and Snapdragon 6 Gen 1 Mobile Platform[3]

Validation history

DateTypeLab
2023-10-26Initialatsec information security corporation

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: 2023-10-26

Source documents