808bits

Tigera Cryptographic Module

FIPS 140-2 certificate #4095 · Tigera, Inc. · data as of 2026-08-28
Historical. Moved to historical list due to sunsetting. Federal agencies may reference historical validations for existing systems only, not for new procurement.
Caveat: When installed, initialized and configured as specified in Section 12.1 of the Security Policy and operated in FIPS mode. The module generates cryptographic keys whose strengths are modified by available entropy.

Certificate

Certificate number4095
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-Chip Stand Alone
VendorTigera, Inc. · website
Software versionsae223d6138807a13006342edfeef32e813246b39

Module description

The Tigera Cryptographic Module is a general-purpose cryptographic module integrated in Tigera’s products to provide FIPS 140-2 validated cryptography for the protection of sensitive information.

Security level exceptions

  • Physical Security: N/A
  • Mitigation of Other Attacks: N/A

Approved algorithms

AlgorithmCAVP certificate
AESC1063
CKGvendor affirmed
CVLC1063
DRBGC1063
ECDSAC1063
HMACC1063
KAS-SSCvendor affirmed
KTS
RSAC1063
SHSC1063
Triple-DESC1063

Allowed algorithms

NDRNG; RSA (key wrapping; key establishment methodology provides between 112 and 256 bits of encryption strength)

Tested configurations

  • Debian Linux 4.19.37 (Rodete) running on HPE Z620 with Intel Xeon E5-2680 with PAA
  • Debian Linux 4.19.37 (Rodete) running on HPE Z620 with Intel Xeon E5-2680 without PAA
  • Ubuntu Linux 18.04 running on Google Arcadia-Rome with AMD Rome with PAA
  • Ubuntu Linux 18.04 running on Google Arcadia-Rome with AMD Rome without PAA
  • Ubuntu Linux 18.04 running on Zaius P9 with POWER9 with PAA
  • Ubuntu Linux 18.04 running on Zaius P9 with POWER9 without PAA (single-user mode).

Validation history

DateTypeLab
2021-12-06InitialAcumen Security
2022-07-01UpdateAcumen 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: 2021-12-06, 2022-07-01

Source documents