808bits

TRICX Cryptographic Library

FIPS 140-2 certificate #2987 · Trustonic · data as of 2026-10-09

TRICX Cryptographic Library, from Trustonic, holds FIPS 140-2 certificate #2987 at overall level 1. The validation is historical: agencies may keep the module in existing systems but not buy it new. Below are its validation history, algorithm certificates and security policy, drawn from the NIST CMVP entry.

Historical. SP 800-56Arev3 transition. Federal agencies may reference historical validations for existing systems only, not for new procurement.
Caveat: No assurance of the minimum strength of generated keys. The module generates cryptographic keys whose strengths are modified by available entropy

Certificate

Certificate number2987
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-Chip Stand Alone
VendorTrustonic · website
Software versions1.0

Module description

Quoted from the NIST CMVP entry for this certificate.

TRICX is a general-purpose cryptographic library designed to be statically linked with a Trusted Application running on Trustonic's Kinibi operating system in a Trusted Execution Environment.

Security level exceptions

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

Approved algorithms (10)

AlgorithmCAVP certificates
AES4468
CVL1180
DRBG1450
ECDSA1090
HMAC2965
KAS119
KTS
RSA2443
SHS3680
Triple-DES2398

Allowed algorithms

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

Tested configurations

  • Trustonic Kinibi 400A running on a HiSilicon Kirin 620 with an ARM Cortex-A53 with PAA
  • Trustonic Kinibi 400A running on a HiSilicon Kirin 620 with an ARM Cortex-A53 without PAA (single-user mode)

Validation history

DateTypeLab
2017-08-10InitialUL Verification Services, Inc.
2019-07-19UpdateUL Verification Services, Inc.
2019-07-24UpdateUL Verification Services, Inc.

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: 2017-08-10, 2019-07-19, 2019-07-24

Source documents