808bits

EZPES Centralized Security Module (CSM)

FIPS 140-2 certificate #4433 · EasyPost · data as of 2026-10-09

EZPES Centralized Security Module (CSM), from EasyPost, holds FIPS 140-2 certificate #4433 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

Certificate

Certificate number4433
StandardFIPS 140-2
Statushistorical
Overall level3
Module typeHardware
EmbodimentMulti-Chip Embedded
VendorEasyPost · website
Hardware versionsCryptoServer CSe-Series 4.00.5.1
Firmware versionsCryptoServer CSe-Series 4.32.0.5; App version: 3.0.0.0

Module description

Quoted from the NIST CMVP entry for this certificate.

The EasyPost Centralized Security Module (CSM) acts as the core security module of a United States Postal Service (USPS) Intelligent Mail Indicia Performance Criteria (IMI PC) conformant online postage evidencing system (PES). Its primary purpose is to perform secure postal financial transactions.

Security level exceptions

  • Physical Security: Level 4

Approved algorithms (18)

AlgorithmCAVP certificates
AESC1122, C1137, C1138, C1140, C1246
CKGvendor affirmed
CVLA1016, C1141, C1165
DRBGA1068
DSAC1195
ECDSAA2367, C1196
ENT
HMACC1142
KAS
KAS-SSCA2227, A2368, A2369
KBKDFC1164
KDAA1016, A2417
KTS
KTS-RSA
RSAC1197
SHA-3C1125
SHSA1067, C1124, C1126
Triple-DESC1128

Tested configurations

  • N/A

Validation history

DateTypeLab
2023-02-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 at the time of the earliest snapshot
  • 2026-09-22: observed moving from active to historical
  • Validation dates on record: 2023-02-09

Source documents