808bits

Gemalto FIPS Object Module

FIPS 140-2 certificate #3466 · Gemalto, a Thales Company · data as of 2026-08-28
Historical. SP 800-56Arev3 transition. Federal agencies may reference historical validations for existing systems only, not for new procurement.
Caveat: When operated in FIPS mode. The module generates cryptographic keys whose strengths are modified by available entropy

Certificate

Certificate number3466
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-Chip Stand Alone
VendorGemalto, a Thales Company · website
Software versions2.1.0

Module description

The Gemalto FIPS Object Module is a hardened version of the general purpose OpenSSL FIPS Object module designed to provide FIPS 140-2 validated cryptographic functionality.

Security level exceptions

  • Physical Security: N/A
  • Design Assurance: Level 3
  • Mitigation of Other Attacks: N/A

Approved algorithms

AlgorithmCAVP certificate
AES5829
CKGvendor affirmed
CVL2098
DRBG2407
DSA1473
ECDSA1558
HMAC3840
RSA3078
SHS4615
Triple-DES2861

Allowed algorithms

Diffie-Hellman (key agreement; key establishment methodology provides between 112 and 219 bits of encryption strength); EC Diffie-Hellman (CVL Cert. #2098, key agreement; key establishment methodology provides between 112 and 256 bits of encryption strength); NDRNG; RSA (key agreement; key establishment methodology provides between 112 and 256 bits of encryption strength)

Tested configurations

  • Android 4.4 running on LG Nexus 4 with ARMv7 with PAA
  • Android 4.4 running on LG Nexus 4 with ARMv7 without PAA
  • Android 5.1 running on Samsung Galaxy S6 with ARMv8 without PAA
  • Android 6.0 running on Huawei Nexus 6P with ARMv8 without PAA
  • Android 7.1 running on Google Pixel XL with ARMv8 without PAA
  • Android 8.1 running on Google Pixel 2 with ARMv8 without PAA
  • iOS 10.3 running on iPhone 5 with ARMv7 without PAA
  • iOS 11.4 running on iPhone 8 with ARMv8 without PAA (single-user mode)
  • iOS 9.3 running on iPhone 6 with ARMv8 without PAA

Validation history

DateTypeLab
2019-06-03InitialAcumen Security

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: 2019-06-03

Source documents