808bits

Qualcomm® Inline Crypto Engine (UFS)

FIPS 140-3 certificate #5338 · Qualcomm Technologies, Inc. · data as of 2026-09-12

Qualcomm® Inline Crypto Engine (UFS), from Qualcomm Technologies, Inc., holds FIPS 140-3 certificate #5338 at overall level 1. The validation is active, with a sunset date of 2029-07-24. Below are its validation history, algorithm certificates and security policy, drawn from the NIST CMVP entry.

Active. Sunset date 2029-07-24, 1045 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 number5338
StandardFIPS 140-3
Statusactive
Sunset date2029-07-24
Overall level1
Module typeHardware
EmbodimentSingleChip
VendorQualcomm Technologies, Inc. · website

Module description

Quoted from the NIST CMVP entry for this certificate.

Qualcomm® Inline Crypto Engine (UFS) provides high throughput storage data encryption and decryption. Inline Crypto Engine (UFS) versions 3.2.0 [1], 3.2.1 [2], 4.0.1 [3] and 4.0.2 [4] are supported by various Qualcomm platforms including Qualcomm QCM6490 [1], Qualcomm QCM4490 [2], Qualcomm QCS6490 [1], Qualcomm QCS4490 [2], Snapdragon® 695 5G Mobile Platform [1], Snapdragon 8 Gen 2 Mobile Platform [3], Snapdragon 8+ Gen 1 Mobile Platform [2], Snapdragon 4 Gen 2 Mobile Platform [2], Snapdragon 6 Gen 1 Mobile Platform [2], Snapdragon 7 Gen 1 Mobile Platform [2], Snapdragon 8 Gen 1 Mobile Platform [2], and Snapdragon 8 Gen 3 Mobile Platform [4].

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

Validation history

DateTypeLab
2026-06-17Initialatsec 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 active
  • Validation dates on record: 2026-06-17

Source documents