808bits

Trend Micro Java Crypto Module

FIPS 140-2 certificate #4368 · Trend Micro Inc. · data as of 2026-10-21

Trend Micro Java Crypto Module, from Trend Micro Inc., holds FIPS 140-2 certificate #4368 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 installed, initialized and configured as specified in the Security Policy Section 3 and operated in FIPS mode. The module generates cryptographic keys whose strengths are modified by available entropy.

Certificate

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

Module description

Quoted from the NIST CMVP entry for this certificate.

The Trend Micro Java Crypto Module provides FIPS Approved cryptographic algorithms for Trend Micro products including Trend Micro Deep Security.

Security level exceptions

  • Physical Security: N/A

Approved algorithms (16)

AlgorithmCAVP certificates
AESA2720
CKGvendor affirmed
CVLA2720
DRBGA2720
DSAA2720
ECDSAA2720
HMACA2720
KAS-SSCvendor affirmed
KBKDFA2720
KTSvendor affirmed
PBKDFvendor affirmed
RSAA2720
SHA-3A2720
SHA-3-Customizedvendor affirmed
SHSA2720
Triple-DESA2720

Allowed algorithms

NDRNG; MD5; RSA (key wrapping; key establishment methodology provides between 150 and 256 bits of encryption strength)

Tested configurations

  • VMware Photon OS 2.0 with JDK 11 on Vmware ESXi 6.7 running on Dell PowerEdge R830 with Intel Xeon E5 (single-user mode)

Validation history

DateTypeLab
2022-11-16InitialAEGISOLVE, 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: 2022-11-16

Source documents