808bits

Oracle Linux 7 OpenSSH Client Cryptographic Module

FIPS 140-2 certificate #3582 · Oracle Corporation · 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 with module Oracle Linux OpenSSL Cryptographic Module validated to FIPS 140-2 under Cert. #3474 operating in FIPS mode

Certificate

Certificate number3582
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-Chip Stand Alone
VendorOracle Corporation · website
Software versionsR7-4.0.0

Module description

Oracle Linux OpenSSH Cryptographic Module is a software module that supplies cryptographic support for the SSH protocol.

Security level exceptions

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

Approved algorithms

AlgorithmCAVP certificate
AESC422, C423, C429
CVLC429, C611
DRBGC422, C423, C429
ECDSAC429
HMACC422, C423, C429
RSAC429
SHSC422, C423, C429
Triple-DESC429

Allowed algorithms

Diffie-Hellman (CVL Cert #C429 with CVL Cert #C611, key agreement; key establishment methodology provides between 112 and 256 bits of encryption strength); EC Diffie-Hellman (CVL Cert. #C429 with CVL Cert #C611, key agreement; key establishment methodology provides between 112 and 256 bits of encryption strength); NDRNG

Tested configurations

  • Oracle Linux 7.6 64 bit running on Oracle Server X7-2 with an Intel(R) Xeon(R) Silver 4114 with PAA
  • Oracle Linux 7.6 64 bit running on Oracle Server X7-2 with an Intel(R) Xeon(R) Silver 4114 without PAA
  • Oracle Linux 7.6 64 bit running on Oracle X7-2 Server with AMD® EPYC® 7551 with PAA
  • Oracle Linux 7.6 64 bit running on Oracle X7-2 Server with AMD® EPYC® 7551 without PAA (single user mode)

Validation history

DateTypeLab
2019-12-12InitialAcumen Security
2020-05-06UpdateAcumen Security

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: 2019-12-12, 2020-05-06

Source documents