808bits

REDCOM Encryption 140-2

FIPS 140-2 certificate #3189 · REDCOM Laboratories, Inc. · data as of 2026-08-28
Historical. SP 800-56Arev3 transition. 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 number3189
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-Chip Stand Alone
VendorREDCOM Laboratories, Inc. · website
Software versions3.0.1

Module description

REDCOM Encryption 140-2 is a fully FIPS 140-2 validated cryptographic engine for Java and Android based environments. The module delivers core cryptographic functions to these platforms and features robust algorithm support, including Suite B algorithms. REDCOM Encryption 140-2 offloads functions for secure key management, data integrity, data at rest encryption, and secure communications to a trusted implementation. **Oracle and Java are registered trademarks of Oracle and/or its affiliates. **Android is a trademark of Google Inc

Security level exceptions

  • Physical Security: N/A

Approved algorithms

AlgorithmCAVP certificate
AES4702
CKGvendor affirmed
CVL1342, 1343, 1344, 1345
DRBG1600
DSA1244
ECDSA1160
HMAC3114
KAS130
KASvendor affirmed
KBKDF145
KTS
KTSvendor affirmed
KTS
PBKDFvendor affirmed
RSA2562
SHA-324
SHS3849
Triple-DES2494

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 (single-user mode)

Validation history

DateTypeLab
2018-05-31InitialUL 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-05-31

Source documents