| intCertNum |
308 |
| strVendorName |
Entrust, Inc. |
| strURL |
http://www.entrust.com |
| strAddress1 |
1000 Innovation Drive |
| strAddress2 |
|
| strAddress3 |
|
| strCity |
Ottawa |
| strStateProv |
Ontario |
| strPostalCode |
K2K 3E7 |
| strCountry |
K2K 3E7 |
| strContact |
Entrust Sales |
| strEmail |
entrust@entrust.com |
| strPhone |
|
| strFax |
|
| strContact2 |
|
| strEmail2 |
|
| strFax2 |
|
| strPhone2 |
|
| intCertNum |
308 |
| strModuleName |
Entrust Security Kernel Version 7.0 |
| strPartNumber |
Software Version: 7.0 |
| memModuleNotes |
When operated in FIPS mode |
| str140Version |
140-1 |
| _sp_ |
Security Policy [pdf][html][txt] |
| _cert_ |
Certificate [pdf][txt] |
| strPURL |
|
| strModuleType |
Software |
| strValidationDate |
03/07/2003;05/28/2014 |
| intOverallLevel |
2 |
| memIndividualLevelNotes |
-Roles and Services: Level 2*;-EMI/EMC: Level 3;-Key Management: Level 2*;-Operating System Security: Tested as meeting Level 2 with Microsoft Windows NT 4.0 with SP6a, TCSEC C3-2-rated on a Compaq ProLiant 7000 Server;;*When operated in the FIPS mode |
| strFIPSAlgorithms |
Triple-DES (Cert. #6);
AES (Cert. #10);
HMAC-SHA-1 (Cert. #10, vendor affirmed);
DSA/SHA-1 (Cert. #10);
RSA (PKCS #1, vendor affirmed) |
| strOtherAlgorithms |
DES (Cert. #56);
DES MAC;
RC2;
RC4;
IDEA;
MD5;
MD2;
RIPEMD-160;
HMAC-MD5;
HMAC-RIPEMD-160;
CAST;
CAST3;
CAST5;
Diffie-Hellman (key agreement);
Ephemeral-Static Diffie-Hellman;
ECDSA (vendor affirmed;
non-compliant) |
| strConfiguration |
Multi-chip standalone |
| memModuleDescription |
The Kernel is a C++ class library of cryptographic functions bound together by a common object-oriented Application Programming Interface (API). Depending on the configuration and runtime environment of the Kernel, the algorithms may be implemented in software, hardware, or a combination of both. The industry standard Cryptoki API, as described in PKCS #11, is used as the internal interface to hardware-based cryptographic tokens. Decisions are made at runtime whether to perform operations via cryptoki or in software, based on a table that records the crypto capabilities of particular hardware devices. This table is built up at runtime by querying the actual token through Cryptoki. |
| intModuleCount |
1 |
| memAdditionalNotes |
05/28/14: Updated contact information. |
| strFirstValidtionDate |
03/07/03 00:00:00 |
| strLabName |
DOMUS |
| strValidationYear |
2003 |