Release Notes

16 Operating Environment Information
RSA BSAFE Crypto-C Micro Edition 4.1.4 Release Notes
Note: Your RSA software license agreement might not grant you the right to
develop applications on all of the platforms listed above. Contact your RSA
sales representative for information on the development platforms covered by
your license agreement and platform/field of use restrictions.
Linux Standard Base
The goal of the LSB project is to deliver interoperability between applications and the
Linux operating system. The distributions of Crypto-C ME built using the LSB 3.0
and 4.0 Software Development Kits (SDKs) are designed to be compatible with Linux
operating systems that support LSB 3.0 and 4.0 on the CPU architectures listed in
Table 1, Operating Environment Information.
FIPS 140-2 Compliance
FIPS 140-2 (Federal Information Processing Standards Publication 140-2 - Security
Requirements for Cryptographic Modules) details the United States Government
requirements for cryptographic modules. For more information about the FIPS 140-2
standard and validation program, see the FIPS 140-2 page on the NIST Web site at
https://csrc.nist.gov/projects/cryptographic-module-validation-
program/standards.
Note: FIPS 140-2 validation for this release of Crypto-C ME is in progress.
To view the progress, see the
Module In Process List. When the validation
process is complete, certificate information will be updated in the RSA BSAFE
Crypto-C Micro Edition Security Policy documents.
In Table 1, the FIPS column indicates the operating environments tested for FIPS
140-2 compliance by an accredited FIPS 140-2 testing laboratory. These operating
environments are listed on the FIPS 140-2 certificate.
“VA” - Vendor affirmed - indicates the operating environment is not specifically listed
on the FIPS 140-2 certificate, but RSA affirms FIPS 140-2 compliance. Vendor
affirmation of compliance is defined in Section G.5, “Maintaining Validation
Compliance of Software or Firmware Cryptographic Modules” in Implementation
Guidance for FIPS PUB 140-2 and the Cryptographic Module Validation Program.
For the complete list of FIPS 140-2 tested and vendor affirmed operating
environments, and for detailed information about the Crypto-C ME FIPS 140-2
cryptographic module and the secure operation of Crypto-C ME, see the RSA BSAFE
Crypto-C Micro Edition Security Policy documents.
Note: As of February 2017, FIPS 140-2 module validations have a five year
life span from the date of the last validation. Unless modules are revalidated,
the module certificate is moved to the CMVP Historical Validations list.
Validations moved to the CMVP Historical Validations List have not been
revoked outright. The validation still exists, but applications using affected
modules are not to be included in new procurements by Federal Agencies.