Reference Guide

4 Crypto-C ME Cryptographic Toolkit
RSA BSAFE Crypto-C Micro Edition 4.1 Security Policy
Level 1
The following table lists the certification levels sought for Crypto-C ME for each
section of the FIPS 140-2 specification.
2.1.1 Laboratory Validated Operating Environments
For FIPS 140-2 validation, Crypto-C ME is tested by an accredited FIPS 140-2 testing
laboratory on the following operating environments:
• Microsoft
®
:
– Windows 7 Enterprise SP1:
• x86 (32-bit), built with Visual Studio 2005, no C runtime library (no CRT)
• x86 (32-bit), built with Visual Studio 2010
• x86-64 (64-bit), built with Visual Studio 2005
• x86-64 (64-bit), built with Visual Studio 2010, no CRT
– Windows 8.1 Enterprise, x86-64 (64-bit), built with Visual Studio 2010, no
CRT
– Windows Server 2003 Enterprise R2:
• x86 (32-bit), built with Visual Studio 2005, no CRT
• x86 (32-bit), built with Visual Studio 2010
• x86_64 (64-bit), built with Visual Studio 2005
• x86_64 (64-bit), built with Visual Studio 2010, no CRT
• Itanium
®
(64-bit), built with Visual Studio 2005
• Itanium (64-bit), built with Visual Studio 2010, no CRT
Table 1 Certification Levels
Section of the FIPS 140-2 Specification Level
Cryptographic Module Specification 3
Cryptographic Module Ports and Interfaces 1
Roles, Services, and Authentication 1
Finite State Model 1
Physical Security N/A
Operational Environment 1
Cryptographic Key Management 1
EMI/EMC 1
Self-Tests 1
Design Assurance 3
Mitigation of Other Attacks 1
Overall 1