808bits

Oracle Solaris Userland Cryptographic Framework

FIPS 140-2 certificate #2077 · Oracle Corporation · data as of 2026-10-21

Oracle Solaris Userland Cryptographic Framework, from Oracle Corporation, holds FIPS 140-2 certificate #2077 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 installed, initialized and configured as specified in the Security Policy and operated in FIPS mode. The module generates cryptographic keys whose strengths are modified by available entropy.

Certificate

Certificate number2077
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-chip standalone
VendorOracle Corporation · website
Software versions1.0 and 1.1

Module description

Quoted from the NIST CMVP entry for this certificate.

The Oracle Solaris OS utilizes the Oracle Solaris Userland Cryptographic Framework module for cryptographic functionality for any applications running in user space. It exposes PKCS#11 APIs, uCrypto APIs, and libmd public interfaces to provide cryptography to any application designed to utilize them.

Security level exceptions

  • Physical Security: N/A
  • Mitigation of Other Attacks: N/A

Approved algorithms (8)

AlgorithmCAVP certificates
AES2308, 2569
DSA726, 785
ECDSA373, 443
HMAC1422, 1586
RNG1150, 1221
RSA1191, 1317
SHS1992, 2165
Triple-DES1455, 1556

Other algorithms

AES-XCBC-MAC (non-compliant); SHA-512/224 (non-compliant); SHA-512/256 (non-compliant); MD4; MD5; RC4; DES; Blowfish; RSA (key wrapping; key establishment methodology provides between 112 and 192 bits of encryption strength; non-compliant less than 112 bits of encryption strength); Diffie-Hellman (key agreement; key establishment methodology provides between 112 and 192 bits of encryption strength; non-compliant less than 112 bits of encryption strength); 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)

Tested configurations

  • Oracle Solaris 11.1 running on a M3000 Enterprise Server
  • Oracle Solaris 11.1 running on a Sun Server X3-2 with PAA
  • Oracle Solaris 11.1 running on a Sun Server X3-2 without PAA (single-user mode)

Validation history

DateTypeLab
2014-02-06InitialCGI Information Systems & Management Consultants 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: 2014-02-06

Source documents