808bits

CTERA Crypto Module™ (Java)

FIPS 140-2 certificate #2852 · CTERA Networks Ltd. · data as of 2026-08-28
Historical. Moved to historical list due to sunsetting. Federal agencies may reference historical validations for existing systems only, not for new procurement.
Caveat: When operated in FIPS mode. The module generates cryptographic keys whose strengths are modified by available entropy. No assurance of the minimum strength of generated keys. This validation entry is a non-security relevant modification to Cert. #2804.

Certificate

Certificate number2852
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-Chip Stand Alone
VendorCTERA Networks Ltd. · website
Software versions3.0

Module description

CTERA Crypto Module™ (Java) 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

Approved algorithms

AlgorithmCAVP certificate
AES3756
CVL704, 705, 706
DRBG1031
DSA1043
ECDSA804
HMAC2458
KAS73
KASvendor affirmed
KBKDF78
KTSvendor affirmed
KTS
KTS
PBKDFvendor affirmed
RSA1932
SHA-33
SHS3126
Triple-DES2090

Other algorithms

Diffie-Hellman (CVL Cert. #704, key agreement; key establishment methodology provides 112 bits of encryption strength; non-compliant less than 112 bits of encryption strength); MD5; RSA (key wrapping; key establishment methodology provides 112 or 128 bits of encryption strength; non-compliant less than 112 bits of encryption strength); ARC4 (RC4); Blowfish; Camellia; CAST5; DES; DSTU4145; ElGamal; GOST28147; GOST3410-1994; GOST3410-2001; GOST3411; HMAC-GOST3411; HMAC-MD5; HMAC-RIPEMD; HMAC-TIGER; HMAC-WHIRLPOOL; IDEA; KBKDF (non-compliant); PBKDF (non-compliant); RC2; RIPEMD; PRNG; Scrypt; SEED; Serpent; SipHash; SHACAL-2; TIGER; Twofish; WHIRLPOOL

Tested configurations

  • Java SE Runtime Environment v8 (1.8.0) on CentOS 6.4 on vSphere 6 running on a Cisco UCSB-B200-M4 Blade (single-user mode)

Validation history

DateTypeLab
2017-03-01InitialUL Verification Services, 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
  • Validation dates on record: 2017-03-01

Source documents