RSA BSAFE® Crypto-J Security Policy (jsafeJCE) Versions 3.5.2 and 3.5.3 November 22, 2006 Cryptographic components for Java Co nta ct Inf or ma t ion See our Web sites for regional Customer Support telephone and fax numbers. RSA Security Inc. RSA Security Ireland Limited www.rsasecurity.com www.rsasecurity.ie T ra de ma rks ACE/Agent, ACE/Server, Because Knowledge is Security, BSAFE, ClearTrust, Confidence Inspired, eTitlement, IntelliAccess, Keon, RC2, RC4, RC5, RSA, the RSA logo, RSA Secured, the RSA Secured logo, RSA Security, SecurCare, SecurID, SecurWorld, Smart Rules, The Most Trusted Name in eSecurity, Transaction Authority , and Virtual Business Units are either registered trademarks or trademarks of RSA Security Inc. in the United States and/or other countries. All other goods and/or services mentioned are trademarks of their respective companies. L i ce nse A g re e men t This software and the associated documentation are proprietary and confidential to RSA Security, are furnished under license and may be used and copied only in accordance with the terms of such license and with the inclusion of the copyright below. This software and any copies thereof may not be provided or otherwise made available to any other person. Neither this software nor any copies thereof may be provided to or otherwise made available to any third party. No title to or ownership of the software or any intellectual property rights thereto is hereby transferred. Any unauthorized use or reproduction of this software may be subject to civil and/or criminal liability. This software is subject to change without notice and should not be construed as a commitment by RSA Security. N o t e o n En cr yp t i on T ec hn o logie s This product may contain encryption technology. Many countries prohibit or restrict the use, import or export of encryption technologies and current use, import and export regulations should be followed when exporting this product. D is tr ib ut i on This document may be freely reproduced and distributed whole and intact including this Copyright Notice. R SA Sec urit y N o t ic e The RC5® Block Encryption Algorithm With DataDependent Rotations is protected by U.S. Patent #5,724,428 and #5,835,600. Compaq MultiPrimeTM technology is protected by U.S. Patent #5,848,159 and is the subject of patent applications in other countries. This product includes patented technology licensed from Entrust Technologies Inc. (US Patent# 5,699,431). © 2006 RSA Security Inc. All rights reserved. Published November 22, 2006 Table of Contents Table of Contents 1 INTRODUCTION ............................................................................................................................................. 4 1.1 REFERENCES.............................................................................................................................................. 4 1.2 TERMINOLOGY......................................................................................................................................... 4 1.3 DOCUMENT ORGANIZATION.............................................................................................................. 5 2 CRYPTOJ MODULE ........................................................................................................................................ 6 2.1 INTRODUCTION ....................................................................................................................................... 6 2.2 CRYPTOGRAPHIC MODULE.................................................................................................................. 6 2.3 MODULE INTERFACES ........................................................................................................................... 7 2.4 ROLES AND SERVICES ............................................................................................................................ 8 2.4.1 CryptoOfficer Role ............................................................................................................................... 8 2.4.2 User Role ............................................................................................................................................... 8 2.5 CRYPTOGRAPHIC KEY MANAGEMENT............................................................................................ 9 2.5.1 Key Generation ...................................................................................................................................... 9 2.5.2 Key Storage............................................................................................................................................ 9 2.5.3 Key Protection ....................................................................................................................................... 9 2.5.4 Key Zeroization ..................................................................................................................................... 9 2.6 CRYPTOGRAPHIC ALGORITHMS ...................................................................................................... 10 2.7 SELFTESTS ............................................................................................................................................... 11 2.7.1 PowerUp SelfTests ............................................................................................................................ 11 2.7.2 Conditional SelfTests.......................................................................................................................... 11 2.7.3 Mitigation of Other Attacks ................................................................................................................ 11 3 SECURE OPERATION OF THE CRYPTOJ MODULE ........................................................................... 12 3.1 CRYPTOOFFICER GUIDANCE............................................................................................................ 12 3.2 USER GUIDANCE.................................................................................................................................... 12 4 SERVICES ......................................................................................................................................................... 13 5 ACRONYMS..................................................................................................................................................... 14 6 CONTACTING RSA SECURITY ................................................................................................................. 16 6.1 SUPPORT AND SERVICE....................................................................................................................... 16 6.2 PURCHASING PRINTED PRODUCT DOCUMENTATION............................................................. 16 6.3 FEEDBACK................................................................................................................................................ 16 3 Introduction 1 Introduction This is a nonproprietary cryptographic module security policy for the RSA BSAFE CryptoJ Toolkit Module versions 3.5.2 and 3.5.3 (CryptoJ Module), released by RSA Security Inc. The security policy describes how the CryptoJ Module meets the security requirements of FIPS 1402, and how to securely operate the CryptoJ Module. This policy is prepared as part of the Level 1 FIPS 1402 validation of the CryptoJ Module. The CryptoJ distribution includes two API interfaces: jsafeFIPS.jar JSAFE application programmer interface to the CryptoJ Module jsafeJCEFIPS.jar JCE application programmer interface to the CryptoJ Module. This security policy deals only with the JCE interface to the CryptoJ Module. For details of how the FIPS 1402 evaluation applies to the JSAFE module, see the document RSA BSAFE® CryptoJ Security Policy (jsafe). The FIPS 1402 (Federal Information Processing Standards Publication 1402 ­ Security Requirements for Cryptographic Modules) details the U.S. Government requirements for cryptographic modules. More information about the FIPS 1402 standard and validation program is available on the NIST website http://csrc.nist.gov/cryptval/. 1.1 References This document deals only with operations and capabilities of the CryptoJ Module in the technical terms of a FIPS 1402 cryptographic module security policy. More information is available on the CryptoJ Module and the entire RSA BSAFE product line: The RSA website contains information on the full line of products and services at http://www.rsasecurity.com An overview of the CryptoJ Module is located at http://www.rsasecurity.com/node.asp?id=1204 The RSA BSAFE product overview is provided at http://www.rsasecurity.com/node.asp?id=1202 For answers to technical or sales related questions, please refer to the contact details in section 6 "Contacting RSA Security". 1.2 Terminology In this document the CryptoJ Module will sometimes be referred to as the module. There are two application programmer interfaces to the CryptoJ Module. All references to the CryptoJ Module apply to both interfaces unless explicitly noted. 4 RSA BSAFE Crypto-J Security Policy (jsafeJCE) Introduction 1.3 Document Organization This Security Policy document is one document in the complete FIPS 1402 Submission Package. In addition to this document the complete Submission Package contains: Executive summary Vendor evidence document Finite state machine Module software listing Other supporting documentation as additional references. This document explains the Cryptographic Module's features and functionality relevant to FIPS 1402. This section, "Introduction", provides an overview and introduction to the security policy. "CryptoJ Module" on page 6 describes the Cryptographic Module and how it meets the FIPS 1402 requirements. "Secure Operation of the CryptoJ Module" on page 12 addresses the required configuration for the FIPS mode of operation. "Services" on page 13 lists all of the functions provided by the Cryptographic Module. "Acronyms" on page 14 lists the definitions for the acronyms used in this document. With the exception of this nonproprietary security policy, the FIPS 1402 Certification Submission Documentation is RSA Securityproprietary, and releasable only under appropriate nondisclosure agreements. For access to these documents, please contact RSA Security. 5 Crypto-J Module 2 Crypto-J Module This section provides an overview of the CryptoJ Module, through the following topics: Introduction Cryptographic Module Module Interfaces Roles and Services Cryptographic Key Management Cryptographic Algorithms SelfTest. 2.1 Introduction More than half a billion copies of the RSA BSAFE technology are embedded in today's most popular software applications and hardware devices. Encompassing the most widelyused and rich set of cryptographic algorithms as well as secure communications protocols, RSA BSAFE software is a set of complementary security products relied on by developers and manufacturers worldwide. The CryptoJ Module is the world's most trusted Javalanguage cryptography component, and is at the heart of the RSA BSAFE product line. It includes a wide range of data encryption and signing algorithms, including TripleDES, the highperforming RC5, the RSA Public Key Cryptosystem, the DSA government signature algorithm, MD5 and SHA1 message digest routines, and more. Its software libraries, sample code and complete standardsbased implementation enable nearuniversal interoperability for your networked and ebusiness applications. Any programmer using the RSA BSAFE CryptoJ tools can easily create secure applications without a background in cryptography, mathematics or number theory. 2.2 Cryptographic Module This Cryptographic Module is classified as a multichip standalone module for FIPS 1402 purposes. As such, the module is tested on a particular operating system and computer platform. The cryptographic boundary includes the Cryptographic Module running on selected platforms running selected operating systems, while configured in "single user" mode. The Cryptographic Module is validated for all FIPS 140 2 Level 1 security requirements, including cryptographic key management and operating system requirements. The CryptoJ Module is packaged in a Java Archive (JAR) file containing all the code for the module. In addition, the CryptoJ Module relies on the physical security provided by the host PC in which it runs. The JCE application programmer interface to the CryptoJ Module is provided in the jsafeJCEFIPS.jar file. 6 RSA BSAFE Crypto-J Security Policy (jsafeJCE) Crypto-J Module The CryptoJ Module is tested on the following platforms: Microsoft Windows o Microsoft Windows XP (SP2) ­ Sun JDK 1.4.2 (32bit). Compliance is maintained on platforms for which the binary executable remains unchanged. This includes (but is not limited to): Microsoft Windows o Microsoft Windows NT 4 Sun JDK 1.1.8/1.3.1/1.4.2/1.5, IBM JDK 1.4.2 o Microsoft Windows 2000 Service Pack 4 Sun JDK 1.1.8/1.3.1/1.4.2/1.5, IBM JDK 1.4.2 o Microsoft Windows XP (SP1) Sun JDK 1.1.8/1.3.1/1.4.2/1.5, IBM JDK 1.4.2 o Microsoft Windows 2003 Server. Sun JDK 1.1.8/1.3.1/1.4.2/1.5, IBM JDK 1.4.2. Sun Microsystems o Sun Microsystems Solaris 8, Sparc v9 (32bit) Sun JDK 1.3.1/1.4.2/1.5(32bit) o Sun Microsystems Solaris 8, Sparc v9 (64bit) Sun JDK 1.5 (64bit) o Sun Microsystems Solaris 9, Sparc v9 (32bit) Sun JDK 1.3.1/1.4.2/1.5(32bit) o Sun Microsystems Solaris 9, Sparc v9 (64bit) Sun JDK 1.5 (64bit) o Sun Microsystems Solaris 10, Sparc v9 (32bit) Sun JDK 1.3.1/1.4.2/1.5(32bit) o Sun Microsystems Solaris 10, Sparc v9 (64bit) Sun JDK 1.5 (64bit) o Sun Microsystems Solaris 10, Intel x86 (32bit) Sun JDK 1.3.1/1.4.2/1.5(32bit). Red Hat Linux 7.2 x86 (32bit) o Red Hat Linux 7.2 x86 (32bit) Sun JDK 1.3.1/1.4.2/1.5 o Red Hat Advanced Server 3.0 x86 (32bit). Sun JDK 1.3.1/1.4.2/1.5. HPUX 11 (32bit) o HPUX 11.0 PARISC 1.1 (32bit) HP JDK 1.4.2 o HPUX 11.0 PARISC 2.0 (32bit) HP JDK 1.4.2 o HPUX 11.22 Itanium2 (32bit) HP JDK 1.4.2 o HPUX 11.23 Itanium2 (32bit) HP JDK 1.4.2. IBM AIX 5L v5.3 (32bit) o IBM AIX 5L v5.3, PowerPC (32bit) IBM JDK 1.4.2. For a resolution on the issue of "Multi user" modes, see the NIST document Implementation Guidance for FIPS PUB 1402 and the Cryptographic Module Validation Program at the government website http://csrc.nist.gov/cryptval/1401/FIPS1402IG.pdf. 2.3 Module Interfaces As a multichip standalone module, the CryptoJ Module's physical interfaces consist of a keyboard, mouse, monitor, serial ports, network adapters, and so on. However, the underlying logical interface to the module is the Application Program Interface (API), documented in the RSA BSAFE CryptoJ Developers Guide. The module provides for Control Input through the API calls. Data Input and Output are provided in the variables passed with API calls, and Status Output is provided in the returns and error codes documented for each call. 7 Crypto-J Module 2.4 Roles and Services The CryptoJ Module meets all FIPS 1402 Level 1 requirements for Roles and Services, implementing both a CryptoOfficer (CO) role and a User role. As allowed by FIPS 1402, the module does not require user identification or authentication for these roles. Only one role can be active at a time, and the module does not allow concurrent operators. The API for control of the module are through the "CryptoJ" class. JAR File Prefix jsafeJCEFIPS.jar com.rsa.jsafe.crypto 2.4.1 Crypto-Officer Role An operator can assume the CryptoOfficer role by invoking the method .CryptoJ.setRole() with the argument CRYPTO_OFFICER_ROLE. Once in the CryptoOfficer role, the operator can start the powerup selftests on demand by calling the method .CryptoJ.runSelfTests(). The CryptoOfficer can perform this operation manually at the command prompt by navigating to the directory containing the appropriate jar file, and typing: java -cp .CryptoJ -testAll Alternatively, the CryptoOfficer can call the operation programmatically: .CryptoJ.runSelfTests(); When the CryptoJ Module is loaded, the powerup selftests run automatically. After passing the integrity check, the selftests will not run again unless the module is unloaded and reloaded. So, calling the selftests on demand only results in the powerup knownanswer tests and pairwise consistency checks being performed. 2.4.2 User Role The User role is the default operating role. An operator can, however, explicitly assume the User role by invoking the method .CryptoJ.setRole() with the argument USER_ROLE. The CryptoJ Module API, its functions, and capabilities are documented in the RSA BSAFE CryptoJ Developers Guide. A full list of services is also provided in this document on page 13. 8 RSA BSAFE Crypto-J Security Policy (jsafeJCE) Crypto-J Module 2.5 Cryptographic Key Management 2.5.1 Key Generation The CryptoJ Module supports generation of the DSA, RSA, and DiffieHellman (DH) public and private keys. The module also employs a FIPS 1862 compliant random number generator for generating asymmetric and symmetric keys used in algorithms such as AES, DES 1 , TDES, RSA, DSA or Diffie Hellman. 2.5.2 Key Storage The CryptoJ Module does not provide longterm cryptographic key storage. If a User chooses to store keys, the User is responsible for storing keys returned to the calling application. Volatile (that is, shortterm) memory storage of cryptographic keys and CSPs employed by the cryptographic module is handled as shown in the following table. The User and CO roles have equal and complete access to all keys and CSPs. Table 1. Key and CSP storage Item Storage AES keys In volatile memory only (plaintext) DES keys In volatile memory only (plaintext) Triple DES keys In volatile memory only (plaintext) HMAC with SHA1 and SHA2 keys In volatile memory only (plaintext) Diffie-Hellman public key In volatile memory only (plaintext) Diffie-Hellman private key In volatile memory only (plaintext) RSA public key In volatile memory only (plaintext) RSA private key In volatile memory only (plaintext) DSA public key In volatile memory only (plaintext) DSA private key In volatile memory only (plaintext) PRNG seeds (FIPS 186-2) In volatile memory only (plaintext) 2.5.3 Key Protection All key data resides in internally allocated data structures and can only be output using the module's defined API. The operating system and Java Runtime Environment protects memory and process space from unauthorized access. 2.5.4 Key Zeroization All key data resides in internally allocated data structures that are "cleaned up" by the Java Virtual Machine's (JVM) garbage collector. Java often handles memory in ways that are unpredictable and transparent to the User, and a User can ensure sensitive data is properly zeroized by making use of the clearSensitiveData method for clearing sensitive data. Guidelines for clearing sensitive data are available in the RSA BSAFE CryptoJ Developers Guide, in the section "Clearing Sensitive Data." 1 For legacy system use only; transitional phase only ­ valid until May 19th, 2007. 9 Crypto-J Module 2.6 Cryptographic Algorithms The CryptoJ Module supports a wide variety of cryptographic algorithms. When the module is operated in FIPSmode, FIPS 1402 requires that FIPSapproved algorithms be used. Table 2 lists the algorithms provided by the CryptoJ Module that comply with the FIPS 1402 requirements. Table 3 lists the non FIPSapproved algorithms. Table 2. Crypto-J FIPS-approved algorithms Algorithm Certificate Number AES ­ ECB, CBC, CFB (128), OFB (128) ­ [128, 192, 256 bit key sizes] 271 DES - ECB, CBC, CFB (64bit) , and OFB (64 bit) 326 (for legacy use only; transitional phase only ­ valid until May 19th, 2007) Diffie-Hellman Key Agreement Non-Approved (allowed in FIPS mode) Digital Signature Algorithm (DSA) 140 FIPS 186-2 General Purpose (x-Change Notice(SHA-1) 106 HMAC-SHAx (where x is 1, 224, 256, 384, or 512) 86 RSASSA-PSS (sign, verify) (SHA-1) 71 (Crypto-J 3.5.2), 186 (Crypto-J 3.5.3) RSA PKCS#1 v1.5 (sign/verify) (SHA-1,SHA-224,SHA-256,SHA-384,SHA-512) 71 (Crypto-J 3.5.2), 186 (Crypto-J 3.5.3) Secure Hash Standard (SHA-1, SHA-224, SHA-256, SHA-384, SHA-512) 356 Triple DES - ECB, CBC, CFB (64 bit), and OFB (64 bit) 354 RSA X9.31 (keygen, sign, verify) 71 (Crypto-J 3.5.2), 186 (Crypto-J 3.5.3) For more information on using CryptoJ in a FIPS compliant manner, see the section "Secure Operation of the CryptoJ Module" on page 12. Table 3. Crypto-J non-FIPS-approved algorithms Algorithm DESX MD2 MD5 Random Number Generators (ANSI X9.31, MD5Random, SHA1Random) The RC2® block cipher The RC4® stream cipher The RC5® block cipher PBEWithSHA1And3DES RSA OAEP for key transport Raw RSA encryption and decryption RSA Keypair Generation MultiPrime (2 or 3 primes) RIPEMD160 HMAC-MD5 10 RSA BSAFE Crypto-J Security Policy (jsafeJCE) Crypto-J Module 2.7 Self-Tests The CryptoJ Module performs a number of powerup and conditional selftests to ensure proper operation. If any of these tests fails, the module throws a SecurityException, which provides a status output, and aborts the operation that caused the conditional selftests to fail. 2.7.1 Power-Up Self-Tests The powerup selftests implemented in the CryptoJ module are as follows: PRNG KATs AES KATs DES KATs TDES KATs SHA1 KATs SHA224 KATs SHA256 KATs SHA384 KATs SHA512 KATs HMAC SHA1 KATs HMAC SHA224 KATs HMAC SHA256 KATs HMAC SHA384 KATs HMAC SHA512 KATs pairwise consistency checks for DSA and RSA software/firmware integrity check. Powerup selftests are executed automatically when the module is loaded by the Java Runtime Environment (JRE). 2.7.2 Conditional Self-Tests The CryptoJ Module performs two conditional selftests: a pairwise consistency tests each time the module generates a DSA or RSA public/private key pair, and a continuous random number generator test each time the module produces random data per the FIPS 1862 standard. 2.7.3 Mitigation of Other Attacks RSA key operations implement blinding by default, providing a defense against timing attacks. Blinding is implemented through blinding modes, for which the following options are available: Blinding mode off Blinding mode with no update, where the blinding value is constant for each operation Blinding mode with full update, where a new blinding value is used for each operation. 11 Secure Operation of the Crypto-J Module 3 Secure Operation of the Crypto-J Module The CryptoJ Module does not require any special configuration to operate in conformance with FIPS 1402 requirements. The following guidance must be followed, however, to achieve a FIPSmode of operation. 3.1 Crypto-Officer Guidance The CryptoOfficer is responsible for installing the module. Installation instructions are provided in the RSA BSAFE CryptoJ Installation Guide. The module's default state is FIPS_MODE. CryptoOfficers must not take the module out of FIPS_MODE. 3.2 User Guidance The User must only use algorithms approved for use in a FIPSmode of operation. Table 2 lists the approved algorithms. The FIPSapproved bitlength for a DSA key pair must be between 512 and 1024 bits in multiples of 64, and the FIPSapproved RNGs must be seeded with values of at least 160 bits in length. The FIPSapproved bit lengths for an RSA 2 key pair must be between 1024 and 4096 bits in multiples of 512. The FIPSapproved bit lengths for the DiffieHellman 3 key agreement must be between 1024 and 2048 bits. The FIPSapproved bit lengths for an HMAC key must be between 80 and 4096 bits. If RSA key generation is requested in FIPS mode, the module always uses the FIPSapproved RSA X9.31 keygeneration procedure. The module's default state is FIPS_MODE. Users must not take the module out of FIPS_MODE. Users should take care to zeroize CSPs when they are no longer needed. Please follow the procedure for clearing sensitive data as outlined in the "Clearing Sensitive Data" section of the RSA BSAFE CryptoJ Developer's Guide. 2 When used for transporting keys and using the minimum allowed modulus size, the minimum strength of encryption provided is 80 bits. 3 Using the minimum allowed modulus size, the minimum strength of encryption provided is 80 bits. 12 RSA BSAFE Crypto-J Security Policy (jsafeJCE) Services 4 Services The CryptoJ Module meets all FIPS1402 Level 1 requirements for Roles and Services, implementing both a CryptoOfficer role and a User role. The module does not require user identification or authentication for these roles. Only one role can be active at a time, and the module does not allow concurrent operators. The following table lists the services provided by the CryptoJ Module in terms of the module's interface. For more information on each function, see the RSA BSAFE CryptoJ Developers Guide. Table 4. Services for Crypto-J (jsafeJCEFIPS.jar) Service Service Service CryptoJ.runSelfTests* AlgorithmParameters Mac CryptoJ.setRole AlgorithmParameterGenerator MessageDigest CryptoJ.getRole Cipher SecretKeyFactory CryptoJ.setMode KeyAgreement SecureRandom CryptoJ.getMode KeyFactory Signature CryptoJ.getState KeyGenerator CryptoJ.selfTestPassed KeyPairGenerator *Only available to the CryptoOfficer role. 13 Acronyms 5 Acronyms Acronym Definition AES Advanced Encryption Standard. A fast block cipher with a 128-bit block, and keys of lengths 128, 192 and 256 bits. This will replace DES as the US symmetric encryption standard. API Application Programming Interface. Attack Either a successful or unsuccessful attempt at breaking part or all of a cryptosystem. Various attack types include an algebraic attack, birthday attack, brute force attack, chosen ciphertext attack, chosen plaintext attack, differential cryptanalysis, known plaintext attack, linear cryptanalysis, and middleperson attack. CBC Cipher Block Chaining. A mode of encryption in which each ciphertext depends upon all previous ciphertexts. Changing an IV alters the ciphertext produced by successive encryptions of an identical plaintext. CFB Cipher Feedback. A mode of encryption that produces a stream of ciphertext bits rather than a succession of blocks. In other respects, it has similar properties to the CBC mode of operation. CSP Cryptographic Service Provider. DES Data Encryption Standard. A symmetric encryption algorithm with a 56-bit key. See also Triple DES. Diffie-Hellman The Diffie-Hellman asymmetric key exchange algorithm. There are many variants, but typically two entities exchange some public information (for example, public keys or random values) and combines them with their own private keys to generate a shared session key. As private keys are not transmitted, eavesdroppers are not privy to all of the information that composes the session key. DSA Digital Signature Algorithm. An asymmetric algorithm for creating digital signatures. ECB Electronic Code Book. A mode of encryption in which identical plaintexts are encrypted to identical ciphertexts, given the same key. Encryption The transformation of plaintext into an apparently less readable form (called ciphertext) through a mathematical process. The ciphertext may be read by anyone who has the key that decrypts (undoes the encryption) the ciphertext. FIPS Federal Information Processing Standards. HMAC Keyed-Hashing for Message Authentication Code. KAT Known Answer Test. Key A string of bits used in cryptography, allowing people to encrypt and decrypt data. Can be used to perform other mathematical operations as well. Given a cipher, a key determines the mapping of the plaintext to the ciphertext. Various types of keys include: distributed key, private key, public key, secret key, session key, shared key, subkey, symmetric key, and weak key. MD5 A secure hash algorithm created by Ron Rivest. MD5 hashes an arbitrary-length input into a 16-byte digest. NIST National Institute of Standards and Technology. A division of the US Department of Commerce (formerly known as the NBS) which produces security and cryptography-related standards. OFB Output Feedback. A mode of encryption in which the cipher is decoupled from its ciphertext. OS Operating System. PC Personal Computer. private key The secret key in public key cryptography. Primarily used for decryption but also used for encryption with digital signatures. PRNG Pseudo Random Number Generator. RC2 Block cipher developed by Ron Rivest as an alternative to the DES. It has a block size of 64 bits and a variable key size. It is a legacy cipher and RC5 should be used in preference. RC4 Symmetric algorithm designed by Ron Rivest using variable length keys (usually 40 bit or 128 bit). RC5 Block cipher designed by Ron Rivest. It is parameterizable in its word size, key length and number of rounds. Typical use involves a block size of 64 bits, a key size of 128 bits and either 16 or 20 iterations of its round function. 14 RSA BSAFE Crypto-J Security Policy (jsafeJCE) Acronyms Acronym Definition RNG Random Number Generator. RSA Public key (asymmetric) algorithm providing the ability to encrypt data and create and verify digital signatures. RSA stands for Rivest, Shamir, and Adleman, the developers of the RSA public key cryptosystem. SHA Secure Hash Algorithm. An algorithm which creates a unique hash value for each possible input. SHA takes an arbitrary input which is hashed into a 160-bit digest. SHA-1 A revision to SHA to correct a weakness. It produces 160-bit digests. SHA-1 takes an arbitrary input which is hashed into a 20-byte digest. SHA-2 The NIST-mandated successor to SHA-1, to complement the Advanced Encryption Standard. It is a family of hash algorithms (SHA-256, SHA-384 and SHA-512) which produce digests of 256, 384 and 512 bits respectively. TDES Triple-DES. 15 Contacting RSA Security 6 Contacting RSA Security The RSA Security Web site contains the latest news, security bulletins and information about coming events. The RSA BSAFE Web site contains product information. The RSA Laboratories Web site contains frequently asked questions. 6.1 Support and Service If you have any questions or require additional information, see RSA Support or RSA SecurCare Online. 6.2 Purchasing Printed Product Documentation All documentation for your RSA Security product is included in electronic format on the CD or in the download you have received. You can print product documentation directly from these files if you require a hard copy. RSA Security also offers customers the option to purchase printed and bound copies of key documents for some products. Contact your RSA Security sales representative for more information. 6.3 Feedback We welcome your feedback on RSA Security documentation. Please email bsafeuserdocs@rsasecurity.com. 16 RSA BSAFE Crypto-J Security Policy (jsafeJCE)