Item Search

NameAudit NamePluginCategory
1.28 UBTU-24-100860CIS Ubuntu Linux 24.04 LTS STIG v1.0.0 CAT IIUnix

ACCESS CONTROL

1.81 RHEL-10-300040CIS Red Hat Enterprise Linux 10 STIG v1.0.0 CAT IUnix

ACCESS CONTROL, MAINTENANCE

1.82 RHEL-10-300050CIS Red Hat Enterprise Linux 10 STIG v1.0.0 CAT IUnix

ACCESS CONTROL, MAINTENANCE

1.83 RHEL-10-300060CIS Red Hat Enterprise Linux 10 STIG v1.0.0 CAT IUnix

ACCESS CONTROL, MAINTENANCE

1.135 WN22-CC-000380CIS Microsoft Windows Server 2022 STIG v4.0.0 MS CAT IIWindows

ACCESS CONTROL

2.2.26 Ensure ldap_tls_cacert is set for LDAP.CIS Amazon Linux 2 STIG v2.0.1 STIGUnix

ACCESS CONTROL

2.2.27 Ensure ldap_id_use_start_tls is set for LDAP.CIS Amazon Linux 2 STIG v2.0.1 STIGUnix

ACCESS CONTROL

2.2.28 Ensure ldap_tls_reqcert is set for LDAPCIS Amazon Linux 2 STIG v2.0.1 STIGUnix

ACCESS CONTROL

5.3.17 Ensure only strong MAC algorithms are usedCIS Amazon Linux 2 STIG v2.0.1 L1 ServerUnix

ACCESS CONTROL

ARBA-NT-000100 - AOS must use Transport Layer Security (TLS) 1.2, at a minimum, to protect the confidentiality of sensitive data during electronic dissemination using remote access.DISA HPE Aruba Networking AOS Wireless STIG v1r2ArubaOS

ACCESS CONTROL

DKER-EE-006280 - Docker Enterprise Universal Control Plane (UCP) must be configured to use TLS 1.2.DISA STIG Docker Enterprise 2.x Linux/Unix UCP v2r2Unix

ACCESS CONTROL

GEN005306 - SNMP must require the use of a FIPS 140-2 cryptographic hash algorithm as part of its authentication and integrity methods.DISA STIG for Red Hat Enterprise Linux 5 v1r18 AuditUnix

ACCESS CONTROL

GEN005306 - SNMP service must require a FIPS 140-2 approved hash algorithm as part of its authentication and integrity methodsDISA STIG AIX 6.1 v1r14Unix

ACCESS CONTROL

GEN005306 - The SNMP service must require the use of a FIPS 140-2 approved cryptographic hash algorithm as part of its authentication and integrity methods.DISA STIG for Oracle Linux 5 v2r1Unix

ACCESS CONTROL

GEN005507 - SSH daemon must be configured to only use MACs employing FIPS 140-2 approved cryptographic hash algorithmsDISA STIG AIX 6.1 v1r14Unix

ACCESS CONTROL

GEN005507 - The SSH daemon must be configured to only use Message Authentication Codes (MACs) employing FIPS 140-2 approved cryptographic hash algorithms - MACs that employ FIPS 140-2 cryptographic hash algorithms.DISA STIG for Oracle Linux 5 v2r1Unix

ACCESS CONTROL

GEN005507 - The SSH daemon must be configured to only use Message Authentication Codes (MACs) employing FIPS 140-2 approved cryptographic hash algorithms.DISA STIG Solaris 10 X86 v2r4Unix

ACCESS CONTROL

GEN005507 - The SSH daemon must be configured to only use Message Authentication Codes (MACs) employing FIPS 140-2 approved cryptographic hash algorithms.DISA STIG Solaris 10 SPARC v2r4Unix

ACCESS CONTROL

GEN005507 - The SSH daemon must only use message authentication codes (MACs) that employ FIPS 140-2 cryptographic hash algorithms.DISA STIG for Red Hat Enterprise Linux 5 v1r18 AuditUnix

ACCESS CONTROL

GEN005512 - The SSH client must be configured to only use Message Authentication Codes (MACs) employing FIPS 140-2 approved cryptographic hash algorithms - MACs that employ FIPS 140-2 cryptographic hash algorithms.DISA STIG for Oracle Linux 5 v2r1Unix

ACCESS CONTROL

GEN005512 - The SSH client must be configured to only use Message Authentication Codes (MACs) employing FIPS 140-2 approved cryptographic hash algorithms.DISA STIG Solaris 10 SPARC v2r4Unix

ACCESS CONTROL

GEN005512 - The SSH client must be configured to only use Message Authentication Codes (MACs) employing FIPS 140-2 approved cryptographic hash algorithms.DISA STIG Solaris 10 X86 v2r4Unix

ACCESS CONTROL

GEN005512 - The SSH client must only use MACs employing FIPS 140-2 approved cryptographic hash algorithmsDISA STIG AIX 6.1 v1r14Unix

ACCESS CONTROL

GEN005512 - The SSH client must only use message authentication codes (MACs) that employ FIPS 140-2 cryptographic hash algorithms.DISA STIG for Red Hat Enterprise Linux 5 v1r18 AuditUnix

ACCESS CONTROL

GEN007980 - If the system is using LDAP for authentication or account information, the system must use a TLS connection using FIPS 140-2 approved cryptographic algorithms - '/etc/ldap.conf'DISA STIG for Oracle Linux 5 v2r1Unix

ACCESS CONTROL

GEN007980 - If the system is using LDAP for authentication or account information, the system must use a TLS connection using FIPS 140-2 approved cryptographic algorithms - 'ssl start_tls'DISA STIG for Oracle Linux 5 v2r1Unix

ACCESS CONTROL

GEN007980 - If the system is using LDAP for authentication or account information, the system must use a TLS connection using FIPS 140-2 approved cryptographic algorithms - 'tls_ciphers'DISA STIG for Oracle Linux 5 v2r1Unix

ACCESS CONTROL

GEN007980 - If the system is using LDAP for authentication or account information, the system must use a TLS connection using FIPS 140-2 approved cryptographic algorithms - configuredDISA STIG Solaris 10 X86 v2r4Unix

ACCESS CONTROL

GEN007980 - If the system is using LDAP for authentication or account information, the system must use a TLS connection using FIPS 140-2 approved cryptographic algorithms - configuredDISA STIG Solaris 10 SPARC v2r4Unix

ACCESS CONTROL

GEN007980 - If the system is using LDAP for authentication or account information, the system must use a TLS connection using FIPS 140-2 approved cryptographic algorithms - serversDISA STIG Solaris 10 X86 v2r4Unix

ACCESS CONTROL

GEN007980 - If the system is using LDAP for authentication or account information, the system must use a TLS connection using FIPS 140-2 approved cryptographic algorithms - serversDISA STIG Solaris 10 SPARC v2r4Unix

ACCESS CONTROL

GEN007980 - If using LDAP for auth or account information, must use a TLS connection using FIPS 140-2 algorithms - '/etc/ldap.conf'DISA STIG for Red Hat Enterprise Linux 5 v1r18 AuditUnix

ACCESS CONTROL

GEN007980 - If using LDAP for auth or account information, must use a TLS connection using FIPS 140-2 algorithms - 'ssl start_tls'DISA STIG for Red Hat Enterprise Linux 5 v1r18 AuditUnix

ACCESS CONTROL

GEN007980 - If using LDAP for auth or account information, must use a TLS connection using FIPS 140-2 approved algorithms - 'tls_ciphers'DISA STIG for Red Hat Enterprise Linux 5 v1r18 AuditUnix

ACCESS CONTROL

OL08-00-010290 - The OL 8 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.DISA Oracle Linux 8 STIG v2r9Unix

ACCESS CONTROL, MAINTENANCE

OL08-00-010291 - The OL 8 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.DISA Oracle Linux 8 STIG v2r9Unix

ACCESS CONTROL, MAINTENANCE

RHEL-10-300040 - RHEL 10 must be configured so that Secure Shell (SSH) servers use only DoW-approved encryption ciphers employing FIPS 140-3-validated cryptographic hash algorithms to protect the confidentiality of SSH server connections.DISA Red Hat Enterprise Linux 10 STIG v1r3Unix

ACCESS CONTROL, MAINTENANCE

RHEL-10-300050 - RHEL 10 must be configured so that Secure Shell (SSH) clients use only DoW-approved Message Authentication Codes (MACs) employing FIPS 140-3-validated cryptographic hash algorithms to protect the confidentiality of SSH client connections.DISA Red Hat Enterprise Linux 10 STIG v1r3Unix

ACCESS CONTROL, MAINTENANCE

RHEL-10-300060 - RHEL 10 must be configured so that Secure Shell (SSH) servers use only DoW-approved Message Authentication Codes (MACs) employing FIPS 140-3-validated cryptographic hash algorithms to protect the confidentiality of SSH server connections.DISA Red Hat Enterprise Linux 10 STIG v1r3Unix

ACCESS CONTROL, MAINTENANCE

WBLC-01-000010 - Oracle WebLogic must use cryptography to protect the integrity of the remote access session - SSL Listen PortOracle WebLogic Server 12c Linux v2r2Unix

ACCESS CONTROL

WBLC-01-000010 - Oracle WebLogic must use cryptography to protect the integrity of the remote access session - SSL Listen PortOracle WebLogic Server 12c Windows v2r2Windows

ACCESS CONTROL

WBLC-01-000010 - Oracle WebLogic must use cryptography to protect the integrity of the remote access session - Unsecure Listen PortOracle WebLogic Server 12c Windows v2r2Windows

ACCESS CONTROL

WN22-CC-000370 - Windows Server 2022 Remote Desktop Services must require secure Remote Procedure Call (RPC) communications.DISA Microsoft Windows Server 2022 STIG v2r11Windows

ACCESS CONTROL

WN22-CC-000370 - Windows Server 2022 Remote Desktop Services must require secure Remote Procedure Call (RPC) communications.DISA Microsoft Windows Server 2022 STIG v2r8Windows

ACCESS CONTROL

WN22-CC-000380 - Windows Server 2022 Remote Desktop Services must be configured with the client connection encryption set to High Level.DISA Microsoft Windows Server 2022 STIG v2r8Windows

ACCESS CONTROL

WN22-CC-000380 - Windows Server 2022 Remote Desktop Services must be configured with the client connection encryption set to High Level.DISA Microsoft Windows Server 2022 STIG v2r11Windows

ACCESS CONTROL

WN25-CC-000370 - Windows Server 2025 Remote Desktop Services must require secure Remote Procedure Call (RPC) communications.DISA Microsoft Windows Server 2025 STIG v1r4Windows

ACCESS CONTROL

WN25-CC-000370 - Windows Server 2025 Remote Desktop Services must require secure Remote Procedure Call (RPC) communications.DISA Microsoft Windows Server 2025 STIG v1r1Windows

ACCESS CONTROL

WN25-CC-000380 - Windows Server 2025 Remote Desktop Services must be configured with the client connection encryption set to High Level.DISA Microsoft Windows Server 2025 STIG v1r1Windows

ACCESS CONTROL

WN25-CC-000380 - Windows Server 2025 Remote Desktop Services must be configured with the client connection encryption set to High Level.DISA Microsoft Windows Server 2025 STIG v1r4Windows

ACCESS CONTROL