| ALMA-09-002990 | V1R2 | AlmaLinux OS 9 SSH client must be configured to use only encryption ciphers employing FIPS 140-3 validated cryptographic hash algorithms to protect the confidentiality of SSH client connections. | |
| ALMA-09-003100 | V1R2 | AlmaLinux OS 9 must implement DOD-approved encryption ciphers to protect the confidentiality of SSH client connections. | |
| ALMA-09-003210 | V1R2 | AlmaLinux OS 9 SSH client must be configured to use only Message Authentication Codes (MACs) employing FIPS 140-3 validated cryptographic hash algorithms. | |
| ALMA-09-003320 | V1R2 | AlmaLinux OS 9 must implement DOD-approved encryption ciphers to protect the confidentiality of SSH server connections. | |
| ALMA-09-003325 | V1R2 | AlmaLinux OS 9 SSH server must be configured to use only FIPS 140-3 validated key exchange algorithms. | |
| ALMA-09-003430 | V1R2 | AlmaLinux OS 9 must implement DOD-approved systemwide cryptographic policies to protect the confidentiality of SSH server connections. | |
| ALMA-09-003540 | V1R2 | AlmaLinux OS 9 SSH server must be configured to use only Message Authentication Codes (MACs) employing FIPS 140-3 validated cryptographic hash algorithms. | |
| ALMA-09-003760 | V1R2 | AlmaLinux OS 9 must implement DOD-approved TLS encryption in the GnuTLS package. | |
| ALMA-09-003980 | V1R2 | AlmaLinux OS 9 must implement DOD-approved encryption in the OpenSSL package. | |
| ALMA-09-004090 | V1R2 | AlmaLinux OS 9 must implement DOD-approved TLS encryption in the OpenSSL package. | |
| OL07-00-040180 | V3R2 | The Oracle Linux operating system must implement cryptography to protect the integrity of Lightweight Directory Access Protocol (LDAP) authentication communications. | |
| OL07-00-040190 | V3R2 | The Oracle Linux operating system must implement cryptography to protect the integrity of Lightweight Directory Access Protocol (LDAP) communications. | |
| OL07-00-040200 | V3R2 | The Oracle Linux operating system must implement cryptography to protect the integrity of Lightweight Directory Access Protocol (LDAP) communications. | |
| OL07-00-040400 | V3R2 | The Oracle Linux operating system must be configured so that the SSH daemon is configured to only use Message Authentication Codes (MACs) employing FIPS 140-2 approved cryptographic hash algorithms. | |
| OL08-00-010287 | V2R4 | The OL 8 SSH daemon must be configured to use system-wide crypto policies. | |
| OL08-00-010293 | V2R4 | The OL 8 operating system must implement DoD-approved encryption in the OpenSSL package. | |
| OL08-00-010294 | V2R4 | The OL 8 operating system must implement DoD-approved TLS encryption in the OpenSSL package. | |
| OL08-00-010295 | V2R4 | The OL 8 operating system must implement DoD-approved TLS encryption in the GnuTLS package. | |
| OL08-00-040342 | V2R4 | OL 8 SSH server must be configured to use only FIPS-validated key exchange algorithms. | |
| OL09-00-000252 | V1R1 | The OL 9 SSH daemon must be configured to use systemwide cryptographic policies. | |
| OL09-00-000254 | V1R1 | OL 9 SSH server must be configured to use only ciphers employing FIPS 140-3 validated cryptographic hash algorithms to protect the confidentiality of SSH server connections. | |
| OL09-00-000255 | V1R1 | OL 9 SSH server must be configured to use only Message Authentication Codes (MACs) employing FIPS 140-3 validated cryptographic hash algorithms to protect the confidentiality of SSH server connections. | |
| OL09-00-000261 | V1R1 | OL 9 SSH client must be configured to use only DOD-approved encryption ciphers employing FIPS 140-3 validated cryptographic hash algorithms to protect the confidentiality of SSH client connections. | |
| OL09-00-000262 | V1R1 | OL 9 SSH client must be configured to use only DOD-approved Message Authentication Codes (MACs) employing FIPS 140-3 validated cryptographic hash algorithms to protect the confidentiality of SSH client connections. | |
| RHEL-07-040180 | V3R9 | The Red Hat Enterprise Linux operating system must implement cryptography to protect the integrity of Lightweight Directory Access Protocol (LDAP) authentication communications. | |
| RHEL-07-040190 | V3R9 | The Red Hat Enterprise Linux operating system must implement cryptography to protect the integrity of Lightweight Directory Access Protocol (LDAP) communications. | |
| RHEL-07-040200 | V3R9 | The Red Hat Enterprise Linux operating system must implement cryptography to protect the integrity of Lightweight Directory Access Protocol (LDAP) communications. | |
| RHEL-07-040400 | V3R9 | The Red Hat Enterprise Linux operating system must be configured so that the SSH daemon is configured to only use Message Authentication Codes (MACs) employing FIPS 140-2 approved cryptographic hash algorithms. | |
| RHEL-08-010290 | V2R3 | The RHEL 8 SSH server must be configured to use only Message Authentication Codes (MACs) employing FIPS 140-3 validated cryptographic hash algorithms. | |
| RHEL-08-010291 | V2R3 | The RHEL 8 operating system must implement DOD-approved encryption to protect the confidentiality of SSH server connections. | |
| RHEL-08-010293 | V2R3 | The RHEL 8 operating system must implement DoD-approved encryption in the OpenSSL package. | |
| RHEL-08-010294 | V2R3 | The RHEL 8 operating system must implement DoD-approved TLS encryption in the OpenSSL package. | |
| RHEL-08-010295 | V2R3 | The RHEL 8 operating system must implement DoD-approved TLS encryption in the GnuTLS package. | |
| RHEL-08-010287 | V2R3 | The RHEL 8 SSH daemon must be configured to use system-wide crypto policies. | |
| RHEL-08-040342 | V2R3 | RHEL 8 SSH server must be configured to use only FIPS-validated key exchange algorithms. | |
| RHEL-08-010296 | V2R3 | RHEL 8 SSH client must be configured to use only Message Authentication Codes (MACs) employing FIPS 140-3 validated cryptographic hash algorithms. | |
| RHEL-08-010297 | V2R3 | RHEL 8 SSH client must be configured to use only ciphers employing FIPS 140-3 validated cryptographic hash algorithms. | |
| RHEL-09-255055 | V2R4 | RHEL 9 SSH daemon must be configured to use system-wide crypto policies. | |
| RHEL-09-255060 | V2R4 | RHEL 9 must implement DOD-approved encryption ciphers to protect the confidentiality of SSH connections. | |
| RHEL-09-255065 | V2R4 | The RHEL 9 SSH server must be configured to use only DOD-approved encryption ciphers employing FIPS 140-3 validated cryptographic hash algorithms to protect the confidentiality of SSH server connections. | |
| RHEL-09-255075 | V2R4 | The RHEL 9 SSH server must be configured to use only Message Authentication Codes (MACs) employing FIPS 140-3 validated cryptographic hash algorithms to protect the confidentiality of SSH server connections. | |
| RHEL-09-255064 | V2R4 | The RHEL 9 SSH client must be configured to use only DOD-approved encryption ciphers employing FIPS 140-3 validated cryptographic hash algorithms to protect the confidentiality of SSH client connections. | |
| RHEL-09-255070 | V2R4 | The RHEL 9 SSH client must be configured to use only DOD-approved Message Authentication Codes (MACs) employing FIPS 140-3 validated cryptographic hash algorithms to protect the confidentiality of SSH client connections. | |
| SLES-12-030270 | V3R2 | The SUSE operating system SSH server must be configured to use only FIPS-validated key exchange algorithms. | |
| SLES-15-040450 | V2R4 | The SUSE operating system SSH server must be configured to use only FIPS-validated key exchange algorithms. | |
| UBTU-18-010417 | V2R15 | The Ubuntu operating system must configure the SSH daemon to only use Message Authentication Codes (MACs) employing FIPS 140-2 approved cryptographic hash algorithms to protect the integrity of nonlocal maintenance and diagnostic communications. | |
| UBTU-18-010421 | V2R15 | The Ubuntu operating system SSH server must be configured to use only FIPS-validated key exchange algorithms. | |
| UBTU-20-010045 | V2R1 | The Ubuntu operating system SSH server must be configured to use only FIPS-validated key exchange algorithms. | |
| UBTU-22-255055 | V2R4 | Ubuntu 22.04 LTS must configure the SSH daemon to use Message Authentication Codes (MACs) employing FIPS 140-3-approved cryptographic hashes to prevent the unauthorized disclosure of information and/or detect changes to information during transmission. | |
| UBTU-24-100830 | V1R1 | Ubuntu 24.04 LTS must configure the SSH daemon to use Message Authentication Codes (MACs) employing FIPS 140-3 approved cryptographic hashes to prevent the unauthorized disclosure of information and/or detect changes to information during transmission. | |
| UBTU-24-100850 | V1R1 | Ubuntu 24.04 LTS must configure the SSH client to use FIPS 140-3 approved ciphers to prevent the unauthorized disclosure of information and/or detect changes to information during transmission. | |
| UBTU-24-100860 | V1R1 | Ubuntu 24.04 LTS SSH client must be configured to use only Message Authentication Codes (MACs) employing FIPS 140-3 validated cryptographic hash algorithms. | |
| WN10-CC-000285 | V3R4 | The Remote Desktop Session Host must require secure RPC communications. | |
| WN11-CC-000285 | V2R3 | The Remote Desktop Session Host must require secure RPC communications. | |
| WN16-CC-000400 | V2R9 | The Remote Desktop Session Host must require secure Remote Procedure Call (RPC) communications. | |
| WN16-CC-000410 | V2R9 | Remote Desktop Services must be configured with the client connection encryption set to High Level. | |