Item Search

NameAudit NamePluginCategory
2.3.11.4 (L1) Ensure 'Network security: Configure encryption types allowed for Kerberos' is set to 'AES128_HMAC_SHA1, AES256_HMAC_SHA1, Future encryption types'CIS Microsoft Windows 10 EMS Gateway v3.0.0 L1Windows

ACCESS CONTROL, IDENTIFICATION AND AUTHENTICATION, SYSTEM AND COMMUNICATIONS PROTECTION

2.3.11.4 (L1) Ensure 'Network security: Configure encryption types allowed for Kerberos' is set to 'AES128_HMAC_SHA1, AES256_HMAC_SHA1, Future encryption types'CIS Microsoft Windows 10 Enterprise v3.0.0 L1 + BLWindows

ACCESS CONTROL, IDENTIFICATION AND AUTHENTICATION, SYSTEM AND COMMUNICATIONS PROTECTION

2.3.11.4 (L1) Ensure 'Network security: Configure encryption types allowed for Kerberos' is set to 'AES128_HMAC_SHA1, AES256_HMAC_SHA1, Future encryption types'CIS Microsoft Windows 11 Stand-alone v3.0.0 L1Windows

ACCESS CONTROL, IDENTIFICATION AND AUTHENTICATION, SYSTEM AND COMMUNICATIONS PROTECTION

2.3.11.4 (L1) Ensure 'Network security: Configure encryption types allowed for Kerberos' is set to 'AES128_HMAC_SHA1, AES256_HMAC_SHA1, Future encryption types'CIS Microsoft Windows Server 2019 v3.0.1 L1 DCWindows

ACCESS CONTROL, IDENTIFICATION AND AUTHENTICATION, SYSTEM AND COMMUNICATIONS PROTECTION

2.3.11.4 (L1) Ensure 'Network security: Configure encryption types allowed for Kerberos' is set to 'AES128_HMAC_SHA1, AES256_HMAC_SHA1, Future encryption types'CIS Microsoft Windows Server 2022 v3.0.0 L1 Member ServerWindows

ACCESS CONTROL, IDENTIFICATION AND AUTHENTICATION, SYSTEM AND COMMUNICATIONS PROTECTION

2.3.11.4 Ensure 'Network security: Configure encryption types allowed for Kerberos' is set to 'AES128_HMAC_SHA1, AES256_HMAC_SHA1, Future encryption types'CIS Microsoft Windows Server 2016 STIG v3.0.0 L1 MSWindows

ACCESS CONTROL, IDENTIFICATION AND AUTHENTICATION, SYSTEM AND COMMUNICATIONS PROTECTION

4.2.14 Ensure sshd MACs are configuredCIS Oracle Linux 8 Workstation L1 v3.0.0Unix

ACCESS CONTROL, IDENTIFICATION AND AUTHENTICATION, SYSTEM AND COMMUNICATIONS PROTECTION

4.4 Ensure Federal Information Processing Standard (FIPS) is enabledCIS MongoDB 7 v1.1.0 L2 MongoDBUnix

ACCESS CONTROL, IDENTIFICATION AND AUTHENTICATION, SYSTEM AND COMMUNICATIONS PROTECTION

4.4 Ensure Federal Information Processing Standard (FIPS) is enabledCIS MongoDB 7 v1.1.0 L2 MongoDBWindows

ACCESS CONTROL, IDENTIFICATION AND AUTHENTICATION, SYSTEM AND COMMUNICATIONS PROTECTION

4.10 Ensure That App Engine Applications Enforce HTTPS ConnectionsCIS Google Cloud Platform v3.0.0 L2GCP

ACCESS CONTROL, IDENTIFICATION AND AUTHENTICATION, SYSTEM AND SERVICES ACQUISITION, SYSTEM AND COMMUNICATIONS PROTECTION

5.1.6 Ensure sshd MACs are configuredCIS Oracle Linux 9 v2.0.0 L1 WorkstationUnix

ACCESS CONTROL, IDENTIFICATION AND AUTHENTICATION, SYSTEM AND COMMUNICATIONS PROTECTION

5.1.6 Ensure sshd MACs are configuredCIS Red Hat Enterprise Linux 9 v2.0.0 L1 ServerUnix

ACCESS CONTROL, IDENTIFICATION AND AUTHENTICATION, SYSTEM AND COMMUNICATIONS PROTECTION

5.1.6 Ensure sshd MACs are configuredCIS Rocky Linux 9 v2.0.0 L1 WorkstationUnix

ACCESS CONTROL, IDENTIFICATION AND AUTHENTICATION, SYSTEM AND COMMUNICATIONS PROTECTION

5.2.14 Ensure only strong MAC algorithms are usedCIS Debian 8 Workstation L1 v2.0.2Unix

ACCESS CONTROL, IDENTIFICATION AND AUTHENTICATION, SYSTEM AND COMMUNICATIONS PROTECTION

5.2.14 Ensure only strong MAC algorithms are usedCIS Debian 8 Server L1 v2.0.2Unix

ACCESS CONTROL, IDENTIFICATION AND AUTHENTICATION, SYSTEM AND COMMUNICATIONS PROTECTION

5.043 - Terminal Services is not configured with the client connection encryption set to the required level.DISA Windows Vista STIG v6r41Windows

ACCESS CONTROL, MAINTENANCE

8.1 Ensure 'SSL Forward Proxy Policy' for traffic destined to the Internet is configured - Invalid CategoriesCIS Palo Alto Firewall 9 v1.1.0 L1Palo_Alto

ACCESS CONTROL, IDENTIFICATION AND AUTHENTICATION, SYSTEM AND COMMUNICATIONS PROTECTION

8.2 Ensure 'SSL Inbound Inspection' is required for all untrusted traffic destined for servers using SSL or TLSCIS Palo Alto Firewall 10 v1.2.0 L1Palo_Alto

ACCESS CONTROL, IDENTIFICATION AND AUTHENTICATION, SYSTEM AND COMMUNICATIONS PROTECTION

GEN003820 - The rsh daemon must not be running.DISA STIG for Oracle Linux 5 v2r1Unix

ACCESS CONTROL

GEN003820 - The rsh daemon must not be running.DISA STIG Solaris 10 SPARC v2r4Unix

ACCESS CONTROL

GEN003820 - The rsh daemon must not be running.DISA STIG Solaris 10 X86 v2r4Unix

ACCESS CONTROL

GEN003820 - The rsh daemon must not be running.DISA STIG for Red Hat Enterprise Linux 5 v1r18 AuditUnix

ACCESS CONTROL

GEN003830 - The rlogind service must not be running.DISA STIG Solaris 10 X86 v2r4Unix

ACCESS CONTROL

GEN003830 - The rlogind service must not be running.DISA STIG for Oracle Linux 5 v2r1Unix

ACCESS CONTROL

GEN003830 - The rlogind service must not be running.DISA STIG for Red Hat Enterprise Linux 5 v1r18 AuditUnix

ACCESS CONTROL

GEN003830 - The rlogind service must not be running.DISA STIG Solaris 10 SPARC v2r4Unix

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

GEN005307 - The SNMP service must require the use of a FIPS 140-2 approved encryption algorithm for protecting the privacy of SNMP messages.DISA STIG for Oracle Linux 5 v2r1Unix

ACCESS CONTROL

GEN005505 - The operating system must implement DoD-approved encryption to protect the confidentiality of SSH connections.DISA STIG for Oracle Linux 5 v2r1Unix

ACCESS CONTROL

GEN005505 - The operating system must implement DoD-approved encryption to protect the confidentiality of SSH connections.DISA STIG Solaris 10 SPARC v2r4Unix

ACCESS CONTROL

GEN005505 - The operating system must implement DoD-approved encryption to protect the confidentiality of SSH connections.DISA STIG Solaris 10 X86 v2r4Unix

ACCESS CONTROL

GEN005505 - The SSH daemon must be configured to only use FIPS 140-2 approved ciphers.DISA STIG for Red Hat Enterprise Linux 5 v1r18 AuditUnix

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

GEN005510 - The SSH client must be configured to only use FIPS 140-2 approved ciphers.DISA STIG Solaris 10 SPARC v2r4Unix

ACCESS CONTROL

GEN005510 - The SSH client must be configured to only use FIPS 140-2 approved ciphers.DISA STIG for Oracle Linux 5 v2r1Unix

ACCESS CONTROL

GEN005510 - The SSH client must be configured to only use FIPS 140-2 approved ciphers.DISA STIG Solaris 10 X86 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 - 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 X86 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 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 - '/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 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 - 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 - 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

RHEL-09-672030 - RHEL 9 must implement DOD-approved TLS encryption in the GnuTLS package.DISA Red Hat Enterprise Linux 9 STIG v2r2Unix

ACCESS CONTROL, SYSTEM AND COMMUNICATIONS PROTECTION

VCFL-67-000005 - vSphere Client must be configured with FIPS 140-2 compliant ciphers for HTTPS connections.DISA STIG VMware vSphere 6.7 Virgo Client v1r2Unix

ACCESS CONTROL, SYSTEM AND COMMUNICATIONS PROTECTION