808bits

CTERA Crypto Module

FIPS 140-2 certificate #2815 · CTERA Networks Ltd. · data as of 2026-10-09

CTERA Crypto Module, from CTERA Networks Ltd., holds FIPS 140-2 certificate #2815 at overall level 1. The validation is historical: agencies may keep the module in existing systems but not buy it new. Below are its algorithm certificates, its validation history, and the list moves this tracker has observed, which NIST does not date.

Historical. Moved to historical list due to sunsetting. Federal agencies may reference historical validations for existing systems only, not for new procurement. Observed moving to historical on 2026-09-22. It was one of the last FIPS 140-2 certificates, all moved at the 140-2 sunset on 2026-09-21.
Caveat: When operated in FIPS mode. The module makes no assurance of the minimum strength of random strings and generated keys. This validation entry is a non-security relevant modification to Cert. #2038.

Certificate

Certificate number2815
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-Chip Stand Alone
VendorCTERA Networks Ltd. · website
Software versions2.1

Module description

Quoted from the NIST CMVP entry for this certificate.

CTERA Crypto Module™ (Server) is a secure cryptographic engine used by CTERA Enterprise File Services Platform. The platform enables organizations to securely sync, serve and protect data on any private or public cloud infrastructure.

Security level exceptions

  • Physical Security: N/A
  • Mitigation of Other Attacks: N/A

Approved algorithms (9)

AlgorithmCAVP certificates
AES2273
CKGvendor affirmed
DRBG281
DSA709
ECDSA368
HMAC1391
RSA1166
SHS1954
Triple-DES1420

Tested configurations

  • Windows Server 2008 R2 on a Dell OptiPlex 755, CentOS 6.3 on a Dell OptiPlex 755 (single-user mode)

Validation history

DateTypeLab
2017-01-12InitialAcumen Security
2017-01-17UpdateAcumen Security
2018-12-11UpdateAcumen Security
2022-03-18UpdateAEGISOLVE, Inc.

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 at the time of the earliest snapshot
  • 2026-09-22: observed moving from active to historical
  • Validation dates on record: 2017-01-12, 2017-01-17, 2018-12-11, 2022-03-18

Source documents