808bits

Pitney Bowes iButton Postal Security Device (PSD)

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

Pitney Bowes iButton Postal Security Device (PSD), from Pitney Bowes, Inc., holds FIPS 140-2 certificate #2203 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: When operated in FIPS mode

Certificate

Certificate number2203
StandardFIPS 140-2
Statushistorical
Overall level3
Module typeHardware
EmbodimentMulti-chip standalone
VendorPitney Bowes, Inc. · website
Hardware versionsMAXQ1959B-F50#
Firmware versions09.02.00; Indicia Type: 0, 1, 2, 5, 7 and 8

Module description

Quoted from the NIST CMVP entry for this certificate.

The Pitney Bowes iButton Postal Security Device (PSD) has been designed in compliance with the United States Postal Service (USPS), Information-Based Indicia Program (IBIP), Royal Mail Mailmark and other international postal authorities' specification. It employs strong encryption, decryption, and digital signature techniques for the protection of customer funds in Pitney Bowes global digital metering products. The PSD has been designed to support international postal markets and their rapidly evolving requirements for digital indicia.

Security level exceptions

  • Physical Security: Level 3 +EFP
  • Mitigation of Other Attacks: N/A

Approved algorithms (5)

AlgorithmCAVP certificates
DSA836
HMAC1699
RNG1261
SHS2286
Triple-DES1636

Other algorithms

Triple-DES MAC (Non-Compliant)

Validation history

DateTypeLab
2014-07-09InitialPenumbra 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
  • Validation dates on record: 2014-07-09

Source documents