Module Name
RSA BSAFE® Crypto-J JSAFE and JCE Software Module 6.2.5
Validation Dates
02/17/2021;02/24/2021
Caveat
When operated in FIPS mode. No assurance of the minimum strength of generated keys.
Security Level Exceptions
- Physical Security: N/A
- Design Assurance: Level 3
Embodiment
Multi-Chip Stand Alone
Description
RSA BSAFE Crypto-J security software is designed to help protect sensitive data as it is stored using strong encryption techniques to provide a persistent level of protection. It supports a wide range of industry standard encryption algorithms offering Java developers the flexibility to choose the option most appropriate to meet their requirements.
Tested Configuration(s)
- Google(TM) ART(TM) 8.0 on Google(TM) Android 8.0 ARM(R) v8 (64 bit) running on Samsung S9(TM) with a Qualcomm(R) Snapdragon(TM) 845 processor
- OpenJDK 8.0 on CentOS 7.6 (64-bit) running on Dell PowerEdge(TM) R710 with an Intel Xeon(R) E5 processor (single-user mode)
- Oracle(R) JRE 8.0 on Microsoft(R) Windows(R) Server 2016 (64-bit) running on Dell(TM) Poweredge(TM) T130 with an Intel(R) Xeon(TM) E3 processor
FIPS Algorithms
| AES |
Cert. #C662 |
| CKG |
vendor affirmed |
| CVL |
Certs. #C662 and #C1762 |
| DRBG |
Cert. #C662 |
| DSA |
Cert. #C662 |
| ECDSA |
Cert. #C662 |
| HMAC |
Cert. #C662 |
| KBKDF |
Cert. #C662 |
| KDA |
vendor affirmed |
| KTS |
AES Cert. #C662; key establishment methodology provides between 128 and 256 bits of encryption strength |
| PBKDF |
vendor affirmed |
| RSA |
Cert. #C662 |
| SHA-3 |
Cert. #C662 |
| SHS |
Cert. #C662 |
| Triple-DES |
Cert. #C662 |
Allowed Algorithms
Diffie-Hellman (CVL Certs. #C662 and #C1762, key agreement; key establishment methodology provides 112 or 128 bits of encryption strength); EC Diffie-Hellman (CVL Certs. #C662 and #C1762, key agreement; key establishment methodology provides between 112 and 256 bits of encryption strength); MD5; RSA (CVL Cert. #C662, key wrapping; key establishment methodology provides 112 or 128 bits of encryption strength)
) or https:// don't prove our archive is authentic, only that you securely accessed it. Note that we are working to fix that :)
