Item Search

NameAudit NamePluginCategory
1.53 AZLX-23-001225CIS Amazon Linux 2023 STIG v1.0.0 CAT IUnix

ACCESS CONTROL, SYSTEM AND COMMUNICATIONS PROTECTION

1.220 RHEL-09-255090CIS Red Hat Enterprise Linux 9 STIG v1.0.0 CAT IIUnix

ACCESS CONTROL, SYSTEM AND COMMUNICATIONS PROTECTION

7.8 Ensure Medium Strength SSL/TLS Ciphers Are DisabledCIS Apache HTTP Server 2.4 v2.3.0 L1Unix

ACCESS CONTROL, CONFIGURATION MANAGEMENT, IDENTIFICATION AND AUTHENTICATION, SYSTEM AND COMMUNICATIONS PROTECTION

AIX7-00-002097 - AIX must protect the confidentiality and integrity of transmitted information during preparation for transmission and maintain the confidentiality and integrity of information during reception and disable all non-encryption network access methods.DISA IBM AIX 7.x STIG v3r3Unix

MAINTENANCE, SYSTEM AND COMMUNICATIONS PROTECTION

AOSX-14-000011 - The macOS system must implement DoD-approved encryption to protect the confidentiality and integrity of remote access sessions including transmitted data and data during preparation for transmission - SSHD currently runningDISA STIG Apple Mac OSX 10.14 v2r6Unix

ACCESS CONTROL, SYSTEM AND COMMUNICATIONS PROTECTION

AZLX-23-001225 - Amazon Linux 2023 must force a frequent session key renegotiation for SSH connections to the server.DISA Amazon Linux 2023 STIG v1r4Unix

ACCESS CONTROL, SYSTEM AND COMMUNICATIONS PROTECTION

OL09-00-002342 - OL 9 must force a frequent session key renegotiation for SSH connections to the server.DISA Oracle Linux 9 STIG v1r6Unix

ACCESS CONTROL, SYSTEM AND COMMUNICATIONS PROTECTION

RHEL-09-255090 - RHEL 9 must force a frequent session key renegotiation for SSH connections to the server.DISA Red Hat Enterprise Linux 9 STIG v2r9Unix

ACCESS CONTROL, SYSTEM AND COMMUNICATIONS PROTECTION

RHEL-10-700650 - RHEL 10 must force a frequent session key renegotiation for Secure Shell (SSH) connections to the server.DISA Red Hat Enterprise Linux 10 STIG v1r2Unix

ACCESS CONTROL, SYSTEM AND COMMUNICATIONS PROTECTION

WBSP-AS-001770 - The WebSphere Application Server must use FIPS 140-3-approved encryption modules when authenticating users and processes.DISA IBM WebSphere Traditional 9 STIG v2r1 MiddlewareUnix

IDENTIFICATION AND AUTHENTICATION, SYSTEM AND COMMUNICATIONS PROTECTION

WN10-SO-000035 - Outgoing secure channel traffic must be encrypted or signed.DISA Microsoft Windows 10 STIG v3r6Windows

SYSTEM AND COMMUNICATIONS PROTECTION

WN10-SO-000040 - Outgoing secure channel traffic must be encrypted when possible.DISA Microsoft Windows 10 STIG v3r6Windows

SYSTEM AND COMMUNICATIONS PROTECTION

WN10-SO-000045 - Outgoing secure channel traffic must be signed when possible.DISA Microsoft Windows 10 STIG v3r6Windows

SYSTEM AND COMMUNICATIONS PROTECTION

WN10-SO-000100 - The Windows SMB client must be configured to always perform SMB packet signing.DISA Microsoft Windows 10 STIG v3r6Windows

SYSTEM AND COMMUNICATIONS PROTECTION

WN10-SO-000120 - The Windows SMB server must be configured to always perform SMB packet signing.DISA Microsoft Windows 10 STIG v3r6Windows

SYSTEM AND COMMUNICATIONS PROTECTION

WN12-SO-000012 - Outgoing secure channel traffic must be encrypted or signed.DISA Windows Server 2012 and 2012 R2 MS STIG v3r7Windows

SYSTEM AND COMMUNICATIONS PROTECTION

WN12-SO-000012 - Outgoing secure channel traffic must be encrypted or signed.DISA Windows Server 2012 and 2012 R2 DC STIG v3r7Windows

SYSTEM AND COMMUNICATIONS PROTECTION

WN12-SO-000013 - Outgoing secure channel traffic must be encrypted when possible.DISA Windows Server 2012 and 2012 R2 DC STIG v3r7Windows

SYSTEM AND COMMUNICATIONS PROTECTION

WN12-SO-000013 - Outgoing secure channel traffic must be encrypted when possible.DISA Windows Server 2012 and 2012 R2 MS STIG v3r7Windows

SYSTEM AND COMMUNICATIONS PROTECTION

WN12-SO-000014 - Outgoing secure channel traffic must be signed when possible.DISA Windows Server 2012 and 2012 R2 MS STIG v3r7Windows

SYSTEM AND COMMUNICATIONS PROTECTION

WN12-SO-000014 - Outgoing secure channel traffic must be signed when possible.DISA Windows Server 2012 and 2012 R2 DC STIG v3r7Windows

SYSTEM AND COMMUNICATIONS PROTECTION

WN12-SO-000017 - The system must be configured to require a strong session key.DISA Windows Server 2012 and 2012 R2 DC STIG v3r7Windows

SYSTEM AND COMMUNICATIONS PROTECTION

WN12-SO-000017 - The system must be configured to require a strong session key.DISA Windows Server 2012 and 2012 R2 MS STIG v3r7Windows

SYSTEM AND COMMUNICATIONS PROTECTION

WN12-SO-000028 - The Windows SMB client must be configured to always perform SMB packet signing.DISA Windows Server 2012 and 2012 R2 DC STIG v3r7Windows

SYSTEM AND COMMUNICATIONS PROTECTION

WN12-SO-000028 - The Windows SMB client must be configured to always perform SMB packet signing.DISA Windows Server 2012 and 2012 R2 MS STIG v3r7Windows

SYSTEM AND COMMUNICATIONS PROTECTION

WN12-SO-000029 - The Windows SMB client must be enabled to perform SMB packet signing when possible.DISA Windows Server 2012 and 2012 R2 DC STIG v3r7Windows

SYSTEM AND COMMUNICATIONS PROTECTION

WN12-SO-000029 - The Windows SMB client must be enabled to perform SMB packet signing when possible.DISA Windows Server 2012 and 2012 R2 MS STIG v3r7Windows

SYSTEM AND COMMUNICATIONS PROTECTION

WN12-SO-000032 - The Windows SMB server must be configured to always perform SMB packet signing.DISA Windows Server 2012 and 2012 R2 MS STIG v3r7Windows

SYSTEM AND COMMUNICATIONS PROTECTION

WN12-SO-000032 - The Windows SMB server must be configured to always perform SMB packet signing.DISA Windows Server 2012 and 2012 R2 DC STIG v3r7Windows

SYSTEM AND COMMUNICATIONS PROTECTION

WN12-SO-000033 - The Windows SMB server must perform SMB packet signing when possible.DISA Windows Server 2012 and 2012 R2 DC STIG v3r7Windows

SYSTEM AND COMMUNICATIONS PROTECTION

WN12-SO-000033 - The Windows SMB server must perform SMB packet signing when possible.DISA Windows Server 2012 and 2012 R2 MS STIG v3r7Windows

SYSTEM AND COMMUNICATIONS PROTECTION

WN16-DC-000320 - Domain controllers must require LDAP access signing.DISA Microsoft Windows Server 2016 STIG v2r10Windows

SYSTEM AND COMMUNICATIONS PROTECTION

WN16-SO-000080 - The setting Domain member: Digitally encrypt or sign secure channel data (always) must be configured to Enabled.DISA Microsoft Windows Server 2016 STIG v2r10Windows

SYSTEM AND COMMUNICATIONS PROTECTION

WN16-SO-000090 - The setting Domain member: Digitally encrypt secure channel data (when possible) must be configured to enabled.DISA Microsoft Windows Server 2016 STIG v2r10Windows

SYSTEM AND COMMUNICATIONS PROTECTION

WN16-SO-000100 - The setting Domain member: Digitally sign secure channel data (when possible) must be configured to Enabled.DISA Microsoft Windows Server 2016 STIG v2r10Windows

SYSTEM AND COMMUNICATIONS PROTECTION

WN16-SO-000130 - Windows Server 2016 must be configured to require a strong session key.DISA Microsoft Windows Server 2016 STIG v2r10Windows

SYSTEM AND COMMUNICATIONS PROTECTION

WN16-SO-000190 - The setting Microsoft network client: Digitally sign communications (always) must be configured to Enabled.DISA Microsoft Windows Server 2016 STIG v2r10Windows

SYSTEM AND COMMUNICATIONS PROTECTION

WN16-SO-000200 - The setting Microsoft network client: Digitally sign communications (if server agrees) must be configured to Enabled.DISA Microsoft Windows Server 2016 STIG v2r10Windows

SYSTEM AND COMMUNICATIONS PROTECTION

WN16-SO-000230 - The setting Microsoft network server: Digitally sign communications (always) must be configured to Enabled.DISA Microsoft Windows Server 2016 STIG v2r10Windows

SYSTEM AND COMMUNICATIONS PROTECTION

WN16-SO-000240 - The setting Microsoft network server: Digitally sign communications (if client agrees) must be configured to Enabled.DISA Microsoft Windows Server 2016 STIG v2r10Windows

SYSTEM AND COMMUNICATIONS PROTECTION

WN19-DC-000320 - Windows Server 2019 domain controllers must require LDAP access signing.DISA Microsoft Windows Server 2019 STIG v3r9Windows

SYSTEM AND COMMUNICATIONS PROTECTION

WN19-SO-000060 - Windows Server 2019 setting Domain member: Digitally encrypt or sign secure channel data (always) must be configured to Enabled.DISA Microsoft Windows Server 2019 STIG v3r9Windows

SYSTEM AND COMMUNICATIONS PROTECTION

WN19-SO-000070 - Windows Server 2019 setting Domain member: Digitally encrypt secure channel data (when possible) must be configured to enabled.DISA Microsoft Windows Server 2019 STIG v3r9Windows

SYSTEM AND COMMUNICATIONS PROTECTION

WN19-SO-000080 - Windows Server 2019 setting Domain member: Digitally sign secure channel data (when possible) must be configured to Enabled.DISA Microsoft Windows Server 2019 STIG v3r9Windows

SYSTEM AND COMMUNICATIONS PROTECTION

WN19-SO-000110 - Windows Server 2019 must be configured to require a strong session key.DISA Microsoft Windows Server 2019 STIG v3r9Windows

SYSTEM AND COMMUNICATIONS PROTECTION

WN19-SO-000160 - Windows Server 2019 setting Microsoft network client: Digitally sign communications (always) must be configured to Enabled.DISA Microsoft Windows Server 2019 STIG v3r9Windows

SYSTEM AND COMMUNICATIONS PROTECTION

WN19-SO-000170 - Windows Server 2019 setting Microsoft network client: Digitally sign communications (if server agrees) must be configured to Enabled.DISA Microsoft Windows Server 2019 STIG v3r9Windows

SYSTEM AND COMMUNICATIONS PROTECTION

WN19-SO-000190 - Windows Server 2019 setting Microsoft network server: Digitally sign communications (always) must be configured to Enabled.DISA Microsoft Windows Server 2019 STIG v3r9Windows

SYSTEM AND COMMUNICATIONS PROTECTION

WN19-SO-000200 - Windows Server 2019 setting Microsoft network server: Digitally sign communications (if client agrees) must be configured to Enabled.DISA Microsoft Windows Server 2019 STIG v3r9Windows

SYSTEM AND COMMUNICATIONS PROTECTION

WN25-SH-000050 - Windows Server 2025 OpenSSH must force a frequent session key renegotiation for SSH connections to the server.DISA Microsoft Windows Server 2025 STIG v1r3Windows

ACCESS CONTROL, SYSTEM AND COMMUNICATIONS PROTECTION