808bits

ST3 ACE Token

FIPS 140-2 certificate #2302 · SecureMetric Technology Sdn. Bhd. · data as of 2026-10-09

ST3 ACE Token, from SecureMetric Technology Sdn. Bhd., holds FIPS 140-2 certificate #2302 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

Certificate

Certificate number2302
StandardFIPS 140-2
Statushistorical
Overall level3
Module typeHardware
EmbodimentMulti-chip standalone
VendorSecureMetric Technology Sdn. Bhd. · website
Hardware versions1.0.0

Module description

Quoted from the NIST CMVP entry for this certificate.

ST3 ACE Token is a USB token containing SECUREMETRIC¦s own SECUREMETRIC-FIPS-COS cryptographic operating system. The SECUREMETRIC -FIPS-COS is embedded in an ST23YT66 Integrated Circuit (IC) chip and has been developed to support SECUREMETRIC¦s USB token. ST3 ACE Token is a secure microprocessor smart chip based USB token that work as a miniature cryptography computer designed for strong 2-Factor Authentication (2FA) and identification to support network login, secure online transaction, digital signatures and sensitive data protection.

Security level exceptions

  • Mitigation of Other Attacks: N/A

Approved algorithms (5)

AlgorithmCAVP certificates
AES1473
DRBG58
RSA720
SHS1332
Triple-DES991

Other algorithms

NDRNG; RSA (key wrapping; key establishment methodology provides 112 bits of encryption strength; non-compliant less than 112 bits of encryption strength)

Validation history

DateTypeLab
2015-01-09InitialUL Verification Services, Inc.
2015-05-08UpdateUL 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: 2015-01-09, 2015-05-08

Source documents