BlackBerry Cryptographic Java Module
BlackBerry Cryptographic Java Module, from Research In Motion Ltd., holds FIPS 140-2 certificate #1765 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.
Certificate
| Certificate number | 1765 |
|---|---|
| Standard | FIPS 140-2 |
| Status | historical |
| Overall level | 1 |
| Module type | Software |
| Embodiment | Multi-chip standalone |
| Vendor | Research In Motion Ltd. · website |
| Software versions | 2.8 and 2.8.7 |
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 Java Module is a software module that provides cryptographic services to BlackBerry® products such as the BlackBerry® PlayBook Administration Service, and other BlackBerry® products.
Approved algorithms (10)
Other algorithms
ARC2; ARC4; MD2; MD4; MD5; HMAC-MD5; DES; DESX; ECIES; ECQV; RSA (key wrapping; key establishment methodology provides between 112 and 256 bits of encryption strength; non-compliant less than 112 bits of encryption strength)
Tested configurations
- Red Hat Linux AS 5.5, 32-bit
- Red Hat Linux AS 5.5, 64-bit
- Solaris 10, 64-bit
- Sun Java Runtime Environments (JRE) 1.5.0 and 1.6.0 running on [Solaris 10, 32-bit
- Windows 2008 Server, 64-bit] (single-user mode)
- Windows Vista, 32-bit
- Windows Vista, 64-bit
Validation history
| Date | Type | Lab |
|---|---|---|
| 2012-07-31 | Initial | EWA - Canada |
| 2012-10-10 | Update | EWA - 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: 2012-07-31, 2012-10-10