Compliant Meter Postal Security Device (CoMet PSD)
Compliant Meter Postal Security Device (CoMet PSD), from Pitney Bowes, Inc., holds FIPS 140-2 certificate #547 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.
Caveat: When operated in FIPS mode
Certificate
| Certificate number | 547 |
|---|---|
| Standard | FIPS 140-2 |
| Status | historical |
| Overall level | 3 |
| Module type | Hardware |
| Embodiment | Multi-chip standalone |
| Vendor | Pitney Bowes, Inc. · website |
| Hardware versions | US: 1A00ABA Revision A and 1A0TAAA Revision A; German: 1A51AAA Revision B; Canada: 1AECABA Revision A and 1ACTAAA. |
Module description
Quoted from the NIST CMVP entry for this certificate.
The Pitney Bowes Compliant Meter Postal Security Device (PSD) has been designed in compliance with the United States Postal Service (USPS), Information-Based Indicia Program (IBIP), Canada Post Corporations Digital Indicia Standard, and Deutsche Post's FrankIT New Generation Digital Franking program. 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.
Approved algorithms (8)
| Algorithm | CAVP certificates |
|---|---|
| DSA | 58 |
| ECDSA | vendor affirmed |
| HMAC-SHA-1 | vendor affirmed |
| RNG | vendor affirmed |
| SHS | 86 |
| Skipjack | 6 |
| Triple-DES | 98 |
| Triple-DES MAC | vendor affirmed |
Other algorithms
Diffie-Hellman (key agreement); RSA (PKCS#1, key wrapping)
Validation history
| Date | Type | Lab |
|---|---|---|
| 2005-06-02 | Initial | UL Verification Services, Inc. |
| 2006-02-24 | Update |
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: 2005-06-02, 2006-02-24