Module Name

Oracle Solaris Userland Cryptographic Framework

Standard

FIPS 140-2

Status

Active

Sunset Date

11/2/2021

Validation Dates

08/08/2016;11/03/2016;02/13/2018

Overall Level

1

Caveat

When installed, initialized and configured as specified in the Security Policy and operated in FIPS mode

Security Level Exceptions

• Physical Security: N/A
• Design Assurance: Level 3
• Mitigation of Other Attacks: N/A

Module Type

Software

Embodiment

Multi-Chip Stand Alone

Description

The Oracle Solaris Userland Cryptographic Framework module provides cryptographic functionality for any application that calls into it. The module provides encryption, decryption, hashing, secure random number generation, signature generation and verification, certificate generation and verification, message authentication functions, and key pair generation for RSA and DSA. The module can leverage the algorithm acceleration from SPARC and x86 processors when available.

Tested Configuration(s)

• Oracle Solaris 11.3 running on an Oracle Server X5-2 with PAA
• Oracle Solaris 11.3 running on an Oracle Server X5-2 without PAA (single-user mode)
• Oracle Solaris 11.3 running on an Oracle SPARC T5-1B Server with PAA
• Oracle Solaris 11.3 running on an Oracle SPARC T5-1B Server without PAA
• Oracle Solaris 11.3 running on an Oracle SPARC T7-2 Server with PAA
• Oracle Solaris 11.3 running on an Oracle SPARC T7-2 Server without PAA

FIPS Algorithms

AES	Cert. #3936
DRBG	Cert. #1143
DSA	Cert. #1074
ECDSA	Cert. #862
HMAC	Cert. #2558
RSA	Cert. #2011
SHS	Cert. #3245
Triple-DES	Cert. #2159

Other Algorithms

AES (non-compliant); ECDSA (non-compliant); HMAC (non-compliant); SHS (non-compliant); MD4; MD5; HMAC-MD5; RC4; DES; Blowfish; Camelia; Triple-DES (non-compliant); 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)

Software Versions

1.3