808bits

WatchKey ProX USB Token Cryptographic Module

FIPS 140-2 certificate #4159 · WatchData Technologies Pte Ltd · data as of 2026-10-09

WatchKey ProX USB Token Cryptographic Module, from WatchData Technologies Pte Ltd, holds FIPS 140-2 certificate #4159 at overall level 3. The validation is historical: agencies may keep the module in existing systems but not buy it new. Below are its algorithm certificates, its validation history, and the list moves this tracker has observed, which NIST does not date.

Historical. Moved to historical list due to sunsetting. Federal agencies may reference historical validations for existing systems only, not for new procurement. Observed moving to historical on 2026-09-22. It was one of the last FIPS 140-2 certificates, all moved at the 140-2 sunset on 2026-09-21.
Caveat: When operated in FIPS mode

Certificate

Certificate number4159
StandardFIPS 140-2
Statushistorical
Overall level3
Module typeHardware
EmbodimentMulti-Chip Stand Alone
VendorWatchData Technologies Pte Ltd · website
Hardware versionsSmart Card Chip AS518 and K023314A
Firmware versions36410102

Module description

Quoted from the NIST CMVP entry for this certificate.

The WatchKey ProX USB Token is a USB-based PKI, two-factor authentication token device. It provides digital signature generation/verification for online authentications and data encryption/decryption for online transactions. The user's private and public key pairs can be generated and stored on the embedded chip.

Security level exceptions

  • Mitigation of Other Attacks: N/A

Approved algorithms (8)

AlgorithmCAVP certificates
CVL(Cert. #C2203
AES3196
CKGvendor affirmed
DRBG673
ECDSA585
RSA1630
SHS2647
Triple-DES1822

Allowed algorithms

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

Tested configurations

  • N/A

Validation history

DateTypeLab
2022-02-17Initialatsec information security corporation

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 at the time of the earliest snapshot
  • 2026-09-22: observed moving from active to historical
  • Validation dates on record: 2022-02-17

Source documents