808bits

BlackBerry Cryptographic Kernel

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

BlackBerry Cryptographic Kernel, from Research In Motion Ltd., holds FIPS 140-2 certificate #1146 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. RNG SP800-131A Revision 1 Transition. Federal agencies may reference historical validations for existing systems only, not for new procurement.
Caveat: None

Certificate

Certificate number1146
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeFirmware
EmbodimentMulti-chip standalone
VendorResearch In Motion Ltd. · website
Firmware versions3.8.5.51

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 end-to-end solution. The BlackBerry Cryptographic Kernel is the software module that provides the basic cryptographic functionality for the BlackBerry.

Security level exceptions

  • Design Assurance: Level 3
  • Tested: BlackBerry Storm 9500 with BlackBerry OS Version 4.7

Approved algorithms (7)

AlgorithmCAVP certificates
AES946, 947
ECDSA118
HMAC526
RNG536
RSA456
SHS921
Triple-DES750

Other algorithms

EC Diffie-Hellman (key agreement; key establishment methodology provides 256 bits of encryption strength); ECMQV (key agreement; key establishment methodology provides 256 bits of encryption strength)

Validation history

DateTypeLab
2009-06-24InitialDOMUS
2010-01-28Update

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: 2009-06-24, 2010-01-28

Source documents