Reference Guide

ManualsBrandsDell ManualsBSAFEBSAFE Crypto-J

FIPS 140 Compliance Guide

18.07.19

RSA BSAFE

Crypto-J 6.2.5

FIPS 140 Compliance Guide

This document is a guide for users of RSA BSAFE Crypto-J 6.2.5 (Crypto-J) to

implement FIPS 140-2 compliant applications.

Federal Information Processing Standards Publication 140-2 - Security Requirements

for Cryptographic Modules (FIPS 140-2) details the U.S. Government requirements

for cryptographic modules. More information about the FIPS 140-2 standard and

validation program is available on the NIST Cryptographic Module Validation

Program website.

Contents:

Introduction ....................................................................................................... 2

How to Use Crypto-J in a FIPS 140-2 Compliant Way ............................... 3

Crypto-J Configuration ............................................................................. 4

Key and Critical Data Zeroization ........................................................... 4

Summary of content (4 pages)

PAGE 1
FIPS 140 Compliance Guide 18.07.19 RSA BSAFE® Crypto-J 6.2.5 FIPS 140 Compliance Guide This document is a guide for users of RSA BSAFE Crypto-J 6.2.5 (Crypto-J) to implement FIPS 140-2 compliant applications. Federal Information Processing Standards Publication 140-2 - Security Requirements for Cryptographic Modules (FIPS 140-2) details the U.S. Government requirements for cryptographic modules.
PAGE 2
RSA BSAFE Crypto-J 6.2.5 FIPS 140 Compliance Guide Introduction The Crypto-J toolkit provides two public APIs that can be called from an application: • the Java Cryptography Extension (JCE) API which is an officially released Standard Extension to the Java Platform • the JSAFE API which is an RSA proprietary API. Note: The JSAFE API is now deprecated. It is still available for backward compatibility, and may be removed in a future release.
PAGE 3
RSA BSAFE Crypto-J 6.2.5 FIPS 140 Compliance Guide How to Use Crypto-J in a FIPS 140-2 Compliant Way Crypto-J does not enforce all aspects of the FIPS 140 mode of operation. The operators must ensure they follow the guidelines in this document, and the Crypto-J and Crypto-C Micro Edition Security Policy documents. This section provides guidance to the toolkit user to ensure that Crypto-J is used in a FIPS 140-2 compliant way.
PAGE 4
RSA BSAFE Crypto-J 6.2.5 FIPS 140 Compliance Guide Crypto-J Configuration To operate Crypto-J in compliance with Security Level 1 FIPS 140-2 requirements, use the jcmFIPS-6.2.5.jar file. No configuration change is required. The default values of the following security properties ensure that Crypto-J is FIPS 140-2 compliant: • com.rsa.cryptoj.fips140auth LEVEL1 • com.rsa.cryptoj.