TrustedKeep Encryption Module
When operated in FIPS mode as assumed by the Crypto Officer role and as specified in Appendix A of the provided Security Policy. Initialization shall be invoked as per Section 4 of the provided Security Policy. Any deviation from the procedures outlined in the Security Policy will result in a non FIPS 140-2 compliant module.
Security Level Exceptions
- Roles, Services, and Authentication: Level 2
- Physical Security: N/A
- Mitigation of Other Attacks: N/A
Multi-Chip Stand Alone
TrustedKeep is a secure object storage and sharing solution, providing robust access controls around your objects and securing them both in transit and at rest. It is designed from the ground up for object-level encryption, assigning a unique key to each object being stored, and capable
of managing billions of objects in a single cluster. TrustedKeep handles all encryption and decryption at the boundaries, maintaining control at all times over key material, so that engineering mistakes do not result in key material (or sensitive data) being swapped to disk or left in memory.
- MacBook Pro running on Intel Core i7 on CentOS 7.3 (gcc Compiler Version 4.8.5) with PAA
- MacBook Pro running on Intel Core i7 on CentOS 7.3 (gcc Compiler Version 4.8.5) without PAA. (single-user mode)
EC Diffie-Hellman (CVL Cert. #1295, key agreement; key establishment methodology provides between 112 and 256 bits of encryption strength); RSA (key wrapping; key establishment methodology provides between 112 and 270 bits of encryption strength)