808bits

Trend Micro Cryptographic Module with CCJ 3.0.0

FIPS 140-2 certificate #3414 · Trend Micro Inc. · data as of 2026-09-03

Trend Micro Cryptographic Module with CCJ 3.0.0, from Trend Micro Inc., holds FIPS 140-2 certificate #3414 at overall level 1. The validation is historical: agencies may keep the module in existing systems but not buy it new. Below are its validation history, algorithm certificates and security policy, drawn from the NIST CMVP entry.

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. This validation entry is a non-security relevant modification to Cert. #2804.

Certificate

Certificate number3414
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-Chip Stand Alone
VendorTrend Micro Inc. · website
Software versions3.0.0

Module description

Quoted from the NIST CMVP entry for this certificate.

The Trend Micro Cryptographic Module provides FIPS-approved cryptographic algorithms for Trend Micro products including Trend Micro Deep Security.

Security level exceptions

  • Physical Security: N/A

Approved algorithms (14)

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

Allowed algorithms

Diffie-Hellman (CVL Cert. #704, key agreement; key establishment methodology provides 112 bits of encryption strength); MD5; RSA (key wrapping; key establishment methodology provides 112 or 128 bits of encryption strength)

Tested configurations

  • Java SE Runtime Environment v7 (1.7.0) on Solaris 11 on vSphere 6 running on a Cisco UCSB-B200-M4 Blade and 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
2019-03-22InitialAEGISOLVE, 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: 2019-03-22

Source documents