808bits

QASM Cryptographic Module

FIPS 140-2 certificate #4250 · Crypto4A Technologies Inc. · data as of 2026-10-09

QASM Cryptographic Module, from Crypto4A Technologies Inc., holds FIPS 140-2 certificate #4250 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 with the tamper evident seals installed as indicated in the Security Policy

Certificate

Certificate number4250
StandardFIPS 140-2
Statushistorical
Overall level3
Module typeHardware
EmbodimentMulti-Chip Stand Alone
VendorCrypto4A Technologies Inc. · website
Hardware versions1.0
Firmware versions2.1.0

Module description

Quoted from the NIST CMVP entry for this certificate.

The QASM Cryptographic Module is a high-assurance, tamper-resistant Hardware Security Module (HSM) which secures sensitive data and critical applications by storing, protecting and managing cryptographic keys. It provides end users with industry-leading security and performance. The QASM can be embedded into the QxEDGE family of security appliances for FIPS 140-2 validated key security or be used as a standalone co-processor for an external computing system using a docking-station adapter.

Approved algorithms (13)

AlgorithmCAVP certificates
AESA893
CKGvendor affirmed
CVLA893
DRBGA893
ECDSAA893
ENT
HMACA893
KASA893
KTS
KTS-RSA
RSAA893
SHA-3A893
SHSA893

Tested configurations

  • N/A

Validation history

DateTypeLab
2022-06-13InitialLightship Security, 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 at the time of the earliest snapshot
  • 2026-09-22: observed moving from active to historical
  • Validation dates on record: 2022-06-13

Source documents