808bits

IBM® Everyplace™ Wireless Gateway Cryptographic Module

FIPS 140-2 certificate #320 · IBM® Corporation · data as of 2026-10-21

IBM® Everyplace™ Wireless Gateway Cryptographic Module, from IBM® Corporation, holds FIPS 140-2 certificate #320 at overall level 1. 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. Moved to historical list due to sunsetting. Federal agencies may reference historical validations for existing systems only, not for new procurement.
Caveat: None

Certificate

Certificate number320
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-chip standalone
VendorIBM® Corporation · website
Software versions1.6

Module description

Quoted from the NIST CMVP entry for this certificate.

The IBM® Everyplace Wireless Gateway Cryptographic Module provides encryption and other cryptographic services for the IBM® Everyplace Wireless Gateway for Multiplatforms. The IBM® Everyplace Wireless Gateway for Multiplatforms is a distributed, scalable, multipurpose UNIX® communications platform that can support optimized, securityenhanced data access by both Wireless Application Protocol (WAP) clients and non-WAP clients over a wide range of international wireless network technologies, as well as local area (LAN) and wide area (WAN) wire line networks.

Security level exceptions

  • Roles, Services, and Authentication: Level 2
  • EMI/EMC: Level 3
  • Design Assurance: Level 2

Approved algorithms (4)

AlgorithmCAVP certificates
AES36
DSA74
SHA-1127
Triple-DES142

Other algorithms

DES (Cert. #191)

Tested configurations

  • Microsoft Pocket PC 2002
  • Microsoft Windows 2000 SP2

Validation history

DateTypeLab
2003-05-29InitialEWA - Canada

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: 2003-05-29

Source documents