808bits

Qualcomm® Crypto Engine Core

FIPS 140-3 certificate #5547 · Qualcomm Technologies, Inc. · data as of 2026-10-21

Qualcomm® Crypto Engine Core, from Qualcomm Technologies, Inc., holds FIPS 140-3 certificate #5547 at overall level 1. The validation is active, with a sunset date of 2031-10-08. Below are its validation history, algorithm certificates and security policy, drawn from the NIST CMVP entry.

Active. Sunset date 2031-10-08, 1811 days away.
Caveat: When operated in approved mode. No assurance of minimum security of SSPs (e.g. keys, bit strings) that are externally loaded, or of SSPs established with externally loaded SSPs.

Certificate

Certificate number5547
StandardFIPS 140-3
Statusactive
Sunset date2031-10-08
Overall level1
Module typeHardware
EmbodimentSingleChip
VendorQualcomm Technologies, Inc. · website

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

  • Software/Firmware security: N/A
  • Operational environment: N/A
  • Physical security: Level 2
  • Non-invasive security: N/A
  • Life-cycle assurance: Level 2
  • Mitigation of other attacks: N/A

Approved algorithms (27)

AlgorithmCAVP certificates
AES-CBCA6448
AES-CBC-CS2A6448
AES-CCMA6448
AES-CMACA6448
AES-CTRA6448
AES-ECBA6448
AES-XTS Testing Revision 2.0A6448
HMAC-SHA-1A6448
HMAC-SHA2-256A6448
HMAC-SHA2-384A6448
HMAC-SHA2-512A6448
HMAC-SHA3-224A6448
HMAC-SHA3-256A6448
HMAC-SHA3-384A6448
HMAC-SHA3-512A6448
SHA-1A6448
SHA2-256A6448
SHA2-384A6448
SHA2-512A6448
SHA3-224A6448
SHA3-256A6448
SHA3-384A6448
SHA3-512A6448
SHAKE-128A6448
SHAKE-256A6448
TDES-CBCA6448
TDES-ECBA6448

Validation history

DateTypeLab
2026-10-09Initialatsec 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-10-21: first observed by this tracker, status active
  • Validation dates on record: 2026-10-09

Source documents