808bits

Cygnus X3 Hardware Security Module (XHSM)

FIPS 140-2 certificate #1867 · Pitney Bowes, Inc. · data as of 2026-10-21

Cygnus X3 Hardware Security Module (XHSM), from Pitney Bowes, Inc., holds FIPS 140-2 certificate #1867 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: None

Certificate

Certificate number1867
StandardFIPS 140-2
Statushistorical
Overall level3
Module typeHardware
EmbodimentSingle-chip
VendorPitney Bowes, Inc. · website
Hardware versionsP/N 1R84000 Version A
Firmware versions01.00.06 and 01.03.0074 (Device Abstraction Layer)

Module description

Quoted from the NIST CMVP entry for this certificate.

The Pitney Bowes Cygnus X3 Postal Security Device (PSD) has been designed in compliance with FIPS 140-2 in order to support international digital indicia standards globally. The Cygnus X3 HSM Cryptographic Module employs strong encryption, decryption, and digital signature techniques for the protection of customer funds in Pitney Bowes Postage Metering products.

Security level exceptions

  • Physical Security: Level 3 +EFP

Approved algorithms (11)

AlgorithmCAVP certificates
AES1979
CVL20
DRBG181
DSA632
ECDSA286
HMAC1192
KAS33
RSA1063
SHS1733
Triple-DES1319
Triple-DES MACvendor affirmed

Other algorithms

AES (Cert. #1979, key wrapping; key establishment methodology provides 128 or 256 bits of encryption strength); Diffie-Hellman (key agreement; key establishment methodology provides 112 bits of encryption strength; non-compliant less than 112 bits of encryption strength)

Validation history

DateTypeLab
2012-12-19InitialUL 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: 2012-12-19

Source documents