808bits

Pitney Bowes X4 Hardware Security Module (HSM)

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

Pitney Bowes X4 Hardware Security Module (HSM), from Pitney Bowes, Inc., holds FIPS 140-2 certificate #3321 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. SP 800-56Arev3 transition. Federal agencies may reference historical validations for existing systems only, not for new procurement.
Caveat: When operated in FIPS Mode. The module generates cryptographic keys whose strengths are modified by available entropy

Certificate

Certificate number3321
StandardFIPS 140-2
Statushistorical
Overall level3
Module typeHardware
EmbodimentSingle Chip
VendorPitney Bowes, Inc. · website
Hardware versionsPart # 4W84001 Rev AAA (MAX32590 Secure Microcontroller Revision B4)
Firmware versionsDevice Abstraction Layer (DAL) Version 01.01.0103; PB Bootloader Version 00.00.0016; HSM Application Version 21.01.0021

Module description

Quoted from the NIST CMVP entry for this certificate.

The X4 HSM is a single chip cryptographic module using the Maxim MAX32590 hardware. The central purpose of the module is as a physical computing device that safeguards and manages cryptographic keys and provides cryptographic services to connected host devices. The module uses a number of strong identity based authentication mechanisms to provide authentication, integrity, and when necessary non-repudiation.

Approved algorithms (11)

AlgorithmCAVP certificates
AES2826, 2936
CKGvendor affirmed
CVL334, 1138
DRBG487
DSA871
ECDSA529
HMAC1769
KAS49
KTS
RSA1539
SHS2369

Allowed algorithms

NDRNG

Tested configurations

  • N/A

Validation history

DateTypeLab
2018-11-06InitialPenumbra 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: 2018-11-06

Source documents