808bits

TAISYS JUISE-S2

FIPS 140-2 certificate #3441 · Taisys Technologies Co., Ltd. · data as of 2026-10-09

TAISYS JUISE-S2, from Taisys Technologies Co., Ltd., holds FIPS 140-2 certificate #3441 at overall level 3. 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. Moved to historical list due to sunsetting. 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 number3441
StandardFIPS 140-2
Statushistorical
Overall level3
Module typeHardware
EmbodimentSingle Chip
VendorTaisys Technologies Co., Ltd.
Hardware versions46 43
Firmware versions32 53

Module description

Quoted from the NIST CMVP entry for this certificate.

The TAISYS JUISE-S2 is a module available in contact/contactless form factors that provides security services targeted at mobile devices in a single Integrated Circuit Chip specifically designed for the security of data. Once inside the phone the module becomes an independent secure element to deploy to customers, as government and enterprise, and may download the applications in the card for digital certificate, fintech, cryptography for blockchain applications, cold wallet for cryptocurrency, or health markets.

Approved algorithms (10)

AlgorithmCAVP certificates
AES5461
CKGvendor affirmed
CVL1910, 1911, 1912, 1931
DRBG2134
ECDSA1459
HMAC3619
KBKDF223
KTS
RSA2933
SHS4369

Allowed algorithms

NDRNG

Tested configurations

  • N/A

Validation history

DateTypeLab
2019-04-26InitialCGI Information Systems & Management Consultants Inc
2019-05-08UpdateCGI Information Systems & Management Consultants 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: 2019-04-26, 2019-05-08

Source documents