Reference Guide

Crypto-C ME Cryptographic Toolkit 7
RSA BSAFE Crypto-C Micro Edition 4.1.4 Security Policy Level 1
– Windows Server 2008 Enterprise SP2 on:
• Itanium (64-bit), built with Visual Studio 2010 (/MT).
• Oracle
®
:
– Solaris
®
11.4 on
• SPARC
®
v9-T4 (64-bit), built with Sun C 5.13
• SPARC v8+ (32-bit), built with Sun C 5.13
• SPARC v8 (32-bit), built with Sun C 5.8
• x86_64 (64-bit), built with Sun C 5.13.
– Solaris 10 Update 11 on:
• x86 (32-bit), built with Sun C 5.13.
• Red Hat
®
:
– Enterprise Linux 5.8 on:
• IBM S390
®
x (64-bit), built with LSB 3.0 and gcc 4.3
• IBM S390 (31-bit), built with LSB 3.0 and gcc 4.3.
Note: All Intel x86 (32-bit) and x86-64 (64-bit) environments were tested
with and without the Intel AES-NI Processor Algorithm Accelerator (PAA)
1.1.2 Affirmation of Compliance for other Operating
Environments
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.
Compliance is maintained in all operational environments for which the binary
executable remains unchanged.
The Cryptographic Module Validation Program (CMVP) makes no statement as to the
correct operation of the module or the security strengths of the generated keys when so
ported if the specific operational environment is not listed on the validation certificate.
For Crypto-C ME 4.1.4, RSA affirms compliance for the following operating
environments:
• Apple:
– iOS 12 on:
• ARMv8 (64-bit), built with Xcode 9
– iOS 10 on:
• ARMv8 (64-bit), built with Xcode 9
– macOS 10.12 on x86_64 (64-bit), built with Xcode 7.3.