808bits

BlackBerry® Enterprise Server Cryptographic Kernel

FIPS 140-2 certificate #445 · Research In Motion Ltd. · data as of 2026-10-21

BlackBerry® Enterprise Server Cryptographic Kernel, from Research In Motion Ltd., holds FIPS 140-2 certificate #445 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: When operated in FIPS mode with FIPS validated Microsoft® Base Cryptographic Providers Certificates #76 or #103 operating in FIPS mode

Certificate

Certificate number445
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-chip standalone
VendorResearch In Motion Ltd. · website
Software versions1.0.0.2

Module description

Quoted from the NIST CMVP entry for this certificate.

BlackBerry® is the leading wireless enterprise solution that allows users to stay connected with secure, wireless access to email, corporate data, phone, web and organizer features. BlackBerry® is a totally integrated package that includes hardware, software and service, providing a complete endtoend solution. The BlackBerry® Cryptographic Kernel is the software module that provides the basic cryptographic functionality for the BlackBerry®

Security level exceptions

  • EMI/EMC: Level 3
  • Design Assurance: Level 3

Approved algorithms (4)

AlgorithmCAVP certificates
AES104
HMAC-SHA-1vendor affirmed
SHA-1195
Triple-DES216

Other algorithms

Rijndael

Tested configurations

  • Windows NT Server 4.0 SP6a

Validation history

DateTypeLab
2004-06-30InitialDOMUS
2005-08-24Update

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: 2004-06-30, 2005-08-24

Source documents