808bits

Zscaler Crypto Module

FIPS 140-2 certificate #3159 · Zscaler Inc. · data as of 2026-10-09

Zscaler Crypto Module, from Zscaler Inc., holds FIPS 140-2 certificate #3159 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 number3159
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-Chip Stand Alone
VendorZscaler Inc. · website
Software versions2.1

Module description

Quoted from the NIST CMVP entry for this certificate.

Zscaler Crypto Module ™ offloads functions for secure key management, data integrity, data at rest encryption, and secure communications to a trusted implementation.

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

  • CentOS 6.3 on a Dell OptiPlex 755
  • Mac OS X 10.8 on a MacBook Air
  • Red Hat Enterprise Linux 6.3 on a Dell OptiPlex 755
  • Windows Server 2008 R2 on a Dell OptiPlex 755 (single-user mode)

Validation history

DateTypeLab
2018-03-26InitialAcumen Security
2021-07-06UpdateAEGISOLVE, 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: 2018-03-26, 2021-07-06

Source documents