808bits

Cygnus X-2 Postal Security Device

FIPS 140-2 certificate #1121 · Pitney Bowes, Inc. · data as of 2026-09-12

Cygnus X-2 Postal Security Device, from Pitney Bowes, Inc., holds FIPS 140-2 certificate #1121 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. RNG SP800-131A Revision 1 Transition. Federal agencies may reference historical validations for existing systems only, not for new procurement.
Caveat: None

Certificate

Certificate number1121
StandardFIPS 140-2
Statushistorical
Overall level3
Module typeHardware
EmbodimentMulti-chip standalone
VendorPitney Bowes, Inc. · website
Hardware versions1MEC BBC/BAJ (Canada), 1MES BBC/BAJ (Canada), 1MCT BBC/BAJ (Canada), 1MET BBC/BAJ (Canada), 1M00 BBC/BAJ (US) and 1M05 BBC/BAJ (US)

Module description

Quoted from the NIST CMVP entry for this certificate.

The Pitney Bowes Cygnus X-2 Postal Security Device (PSD) has been designed in compliance with FIPS 140-2 and IPMAR security protection profile in order to support the USPS IBIP and international digital indicia standards globally. The PSD 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 (7)

AlgorithmCAVP certificates
DSA200
ECDSA48
HMAC246
RNG272
SHS562
Triple-DES503
Triple-DES MACvendor affirmed

Other algorithms

Diffie-Hellman (key agreement; key establishment methodology provides 80 bits of encryption strength; non-compliant)

Validation history

DateTypeLab
2009-04-14InitialUL 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: 2009-04-14

Source documents