| intCertNum |
1994 |
| strVendorName |
IBM Corporation |
| strURL |
http://www.ibm.com |
| strAddress1 |
12 - 14 Marine Parade |
| strAddress2 |
Seabank Centre |
| strAddress3 |
|
| strCity |
Southport |
| strStateProv |
QLD |
| strPostalCode |
4215 |
| strCountry |
4215 |
| strContact |
Alex Hennekam |
| strEmail |
alexhenn@au1.ibm.com |
| strPhone |
+61 7-5552-4045 |
| strFax |
+61 7 5571 0420 |
| strContact2 |
Peter Waltenburg |
| strEmail2 |
pwalten@au1.ibm.com |
| strFax2 |
+61 7 5571 0420 |
| strPhone2 |
+61 - 5552-4016 |
| intCertNum |
1994 |
| strModuleName |
IBM Crypto for C |
| strPartNumber |
Software Version: 8.2.2.0 |
| memModuleNotes |
When operated in FIPS mode |
| str140Version |
140-2 |
| _sp_ |
Security Policy [pdf][html][txt] |
| _cert_ |
Certificate [pdf] |
| strPURL |
|
| strModuleType |
Software |
| strValidationDate |
08/27/2013 |
| intOverallLevel |
1 |
| memIndividualLevelNotes |
;;-Operational Environment: Tested as meeting Level 1 with Microsoft Windows Server 2008 64-bit running on an ALTECH SH67H3 Intel Core i7-2600 with PAA; Microsoft Windows Server 2008 64-bit running on an ALTECH SH67H3 Intel Core i7-2600 without PAA; Microsoft Windows Server 2008 32-bit running on an IBM 8835 52X AMD Opteron 246; AIX 6.1 64-bit running on an IBM RS6000 7037-A50 PowerPC 5 64; Solaris 10 64-bit running on an SunFire T1000 UltraSPARC T1; Red Hat Linux Enterprise Server 5 32-bit running on an IBM 8835 52X AMD Opteron 246; Red Hat Linux Enterprise Server 5 64-bit running on an ALTECH SH67H3 Intel Core i7-2600 with PAA; Red Hat Linux Enterprise Server 5 64-bit running on an ALTECH SH67H3 Intel Core i7-2600 without PAA; Red Hat Linux Enterprise Server 5 64-bit running on an IBM System p5 185 7037-A50 IBM PowerPC 970; Red Hat Linux Enterprise Server 5 64-bit running on an IBM zSeries z196 type 2817 model M32 IBM zSeries z196 with CPACF; Red Hat Linux Enterprise Server 5 64-bit running on an IBM zSeries z196 type 2817 model M32 IBM zSeries z196 without CPACF (single user mode) |
| strFIPSAlgorithms |
AES (Certs. #2155, #2156, #2157, #2158, #2159, #2160, #2161, #2162, #2163, #2164, #2165, #2166, #2167, #2169, #2170, #2171, #2172, #2179, #2213, #2214, #2421, #2422, #2423, #2424, #2425, #2426, #2427, #2428, #2429, #2430, #2431, #2432, #2433, #2434, #2435, #2436, #2437, #2438, #2439, #2440, #2441 and #2443);
Triple-DES (Certs. #1365, #1366, #1367, #1368, #1369, #1370, #1371, #1372, #1373, #1374, #1375, #1376, #1377 and #1379);
DSA (Certs. #670, #671, #672, #673, #674, #675, #676, #677, #678, #679, #680, #681, #682, #683, #756 and #757);
RSA (Certs. #1109, #1110, #1111, #1112, #1113, #1114, #1115, #1116, #1117, #1118, #1119, #1120, #1121, #1123, #1253 and #1254);
ECDSA (Certs. #325, #326, #327, #328, #329, #330, #331, #332, #333, #334, #335, #336, #337, #338, #398 and #399);
SHS (Certs. #1874, #1875, #1876, #1877, #1878, #1879, #1880, #1881, #1882, #1883, #1884, #1885, #1886, #1889, #1904 and #1905);
DRBG (Certs. #240, #241, #242, #243, #244, #245, #246, #247, #248, #249, #250, #251, #252, #253, #326, #327, #328, #329, #330 and #331);
HMAC (Certs. #1319, #1320, #1321, #1322, #1323, #1324, #1325, #1326, #1327, #1328, #1329, #1330, #1331, #1333, #1506 and #1507) |
| strOtherAlgorithms |
RSA (key wrapping;
key establishment methodology provides between 112 and 150 bits of encryption strength;
non-compliant less than 112 bits of encryption strength);
Diffie-Hellman (key agreement: key establishment methodology provides between 112 and 150 bits of encryption strength;
non-compliant less than 112 bits of encryption strength);
EC Diffie-Hellman (key agreement: key establishment methodology provides between 112 and 256 bits of encryption strength;
non-compliant less than 112 bits of encryption strength);
MD2;
MD4;
MD5;
MDC2;
RIPEMD;
HMAC MD5;
DES;
CAST;
Camellia;
Blowfish;
RC4;
RC2;
KBKDF (non-compliant) |
| strConfiguration |
Multi-chip standalone |
| memModuleDescription |
The IBM Crypto for C v8.2.2.0 (ICC) cryptographic module is implemented in the C programming language. It is packaged as dynamic (shared) libraries usable by applications written in a language that supports C language linking conventions (e.g. C,
C++, Java, Assembler, etc.) for use on commercially available operating systems. The ICC allows these applications to access cryptographic functions using an Application Programming Interface (API) provided through an ICC import library and based on the API defined by the OpenSSL group. |
| intModuleCount |
1 |
| memAdditionalNotes |
|
| strFirstValidtionDate |
08/27/13 00:00:00 |
| strLabName |
atsec |
| strValidationYear |
2013 |
|