808bits

BlackBerry Cryptographic Java Module

FIPS 140-2 certificate #2981 · BlackBerry Limited · data as of 2026-08-28
Historical. SP 800-56Arev3 transition. Federal agencies may reference historical validations for existing systems only, not for new procurement.
Caveat: When operated in FIPS mode. The module generates cryptographic keys whose strengths are modified by available entropy

Certificate

Certificate number2981
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-Chip Stand Alone
VendorBlackBerry Limited · website
Software versions2.9

Module description

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 Java Module is a software module that provides cryptographic services to BlackBerry products such as the BlackBerry PlayBook Administration Service, and other BlackBerry products.

Security level exceptions

  • Physical Security: N/A

Approved algorithms

AlgorithmCAVP certificate
AES3988, 4299, 4300
CKGvendor affirmed
DRBG1180, 1359, 1360
DSA1084, 1142, 1143
ECDSA884, 1009, 1010
HMAC2603, 2835, 2836
KAS83, 98, 99
KTSvendor affirmed
RSA2046, 2320, 2321
SHS3292, 3537, 3538
Triple-DES2188, 2320, 2321

Allowed algorithms

NDRNG; RSA (key wrapping; key establishment methodology provides between 112 and 256 bits of encryption strength)

Tested configurations

  • Android 6.0.1 with processor Qualcomm 8992 Snapdragon running on BlackBerry PRIV
  • Android OS API Level 17 with processor NXP ARM Cortex-A9 running on Ricoh MP C3004 (single-user mode)
  • CentOS 7.0 with Java JRE 1.8.0 running on a Dell PowerEdge 2950

Validation history

DateTypeLab
2017-08-01InitialEWA - 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: 2017-08-01

Source documents