808bits

Symantec Java Cryptographic Module Version 1.1

FIPS 140-2 certificate #1676 · Symantec Corporation · data as of 2026-10-21

Symantec Java Cryptographic Module Version 1.1, from Symantec Corporation, holds FIPS 140-2 certificate #1676 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. RNG SP800-131A Revision 1 Transition. Federal agencies may reference historical validations for existing systems only, not for new procurement.
Caveat: When operated in FIPS mode with module RSA BSAFE® Crypto-J Software Module validated to FIPS 140-2 under Cert. #1291 operating in FIPS mode

Certificate

Certificate number1676
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-chip standalone
VendorSymantec Corporation · website
Software versions1.1

Module description

Quoted from the NIST CMVP entry for this certificate.

The Symantec Java Cryptographic Module Version 1.1 provides a comprehensive set of cryptographic services for Symantec products including, but not limited to, the Symantec Data Loss Prevention Suite.

Approved algorithms (9)

AlgorithmCAVP certificates
AES1109
DRBG15
DSA357
ECDSA130
HMAC621
RNG616
RSA522
SHS1032
Triple-DES806

Other algorithms

DES; Diffie-Hellman (key agreement; key establishment methodology provides 112 bits of encryption strength; non-compliant less than 112 bits of encryption strength); DESX; ECAES (non-compliant); EC Diffie-Hellman (key agreement; key establishment methodology provides between 112 and 256 bits of encryption strength; non-compliant less than 112 bits of encryption strength); ECIES; MD2; MD5; PBE (non-compliant); RIPEMD 160; RC2; RC4; RC5; RSA OAEP (non-compliant); Raw RSA (non-compliant); RSA Keypair Generation MultiPrime (non-compliant); RSA (key wrapping; key establishment methodology provides between 112 and 150 bits of encryption strength; non-compliant less than 112 bits of encryption strength); HMAC-MD5; ANSI X9.31 RNG (non-compliant); MD5Random; SHA1Random (non-compliant)

Tested configurations

  • Microsoft Windows XP SP2 with Sun JRE 5.0
  • Microsoft Windows XP SP2 with Sun JRE 6.0 (single-user mode)

Validation history

DateTypeLab
2012-03-09InitialEWA - Canada

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: 2012-03-09

Source documents