Cohesity FIPS Object Module for OpenSSL
Caveat: When installed, protected and initialized as assumed by the Crypto Officer role and as specified in the provided Security Policy. Installation and protection shall be completed 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 specified protection, installation and initialization procedures will result in a non FIPS 140-2 compliant module. This validation entry is a non-security relevant modification to Cert. #2398
Certificate
| Certificate number | 2676 |
|---|---|
| Standard | FIPS 140-2 |
| Status | historical |
| Overall level | 1 |
| Module type | Software |
| Embodiment | Multi-Chip Stand Alone |
| Vendor | Cohesity, Inc. · website |
| Software versions | 1.0.1 [1] and 1.0.2 [2] |
Module description
The Cohesity FIPS Object Module for OpenSSL is a general purpose cryptographic module compiled from the source code for the OpenSSL FIPS Object Module. It is incorporated into the CS2000 family of Cohesity Storage Systems.
Security level exceptions
- Roles, Services, and Authentication: Level 2
- Physical Security: N/A
- Design Assurance: Level 3
- Mitigation of Other Attacks: N/A
Approved algorithms
| Algorithm | CAVP certificate |
|---|---|
| AES | 3967, 5426 |
| CVL | 796, 1876 |
| DRBG | 1162, 2117 |
| DSA | 1081, 1395 |
| ECDSA | 873, 1442 |
| HMAC | 2585, 3591 |
| RSA | 2027, 2906 |
| SHS | 3271, 4353 |
| Triple-DES | 2176, 2724 |
Other algorithms
EC Diffie-Hellman; RSA (encrypt/decrypt)
Tested configurations
- CentOS 7.2 running on a Cohesity CS2500 (single-user mode)
Validation history
| Date | Type | Lab |
|---|---|---|
| 2016-07-11 | Initial | Leidos Accredited Testing & Evaluation (AT&E) Lab |
| 2018-10-12 | Update | Leidos Accredited Testing & Evaluation (AT&E) Lab |
| 2019-11-08 | Update | Leidos Accredited Testing & Evaluation (AT&E) Lab |
Status timeline
As observed by this tracker's snapshots. NIST publishes no dates for list moves; observation began 2026-08-21, so earlier changes carry no date.
- 2026-08-21: first observed by this tracker, status historical
- Validation dates on record: 2016-07-11, 2018-10-12, 2019-11-08