808bits

Trend Micro Java Crypto Module

FIPS 140-2 certificate #3140 · Trend Micro Inc. · 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

Certificate

Certificate number3140
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-Chip Stand Alone
VendorTrend Micro Inc. · website
Software versions1.0

Module description

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

AlgorithmCAVP certificate
AES4702, 5532
CKGvendor affirmed
CVL1342, 1343, 1344, 1345, 1972, 1973, 1974, 1975
DRBG1600, 2190
DSA1244, 1417
ECDSA1160, 1487
HMAC3114, 3684
KAS130, 188
KASvendor affirmed
KBKDF145, 233
KTS
KTSvendor affirmed
KTS
PBKDFvendor affirmed
RSA2562, 2966
SHA-324, 49
SHS3849, 4439
Triple-DES2494, 2785

Allowed algorithms

Diffie-Hellman (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

  • CentOS 6 and OpenJDK 1.7 running on HP ProLiant DL360 G7 Server using an Intel Xeon X5670
  • Red Hat Enterprise Linux 7 with Java SE 8 running on a Dell OptiPlex 755 with an Intel i7 (single-user mode)
  • Windows Server 2012 R2 with Java SE 8 running on a Dell OptiPlex 755 with an Intel i7

Validation history

DateTypeLab
2018-02-26InitialUL Verification Services, Inc.
2018-09-24UpdateUL 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: 2018-02-26, 2018-09-24

Source documents