Configure firewalld To Rate Limit Connections
Configure Kernel to Rate Limit Sending of Duplicate TCP Acknowledgments
Configure Firewalld to Use the Nftables Backend
Enable DoS Protections in SuSEfirewall2
ufw Must rate-limit network interfaces
The A10 Networks ADC must protect against TCP and UDP Denial of Service (DoS) attacks by employing Source-IP based connection-rate limiting.
The A10 Networks ADC must implement load balancing to limit the effects of known and unknown types of Denial of Service (DoS) attacks.
The A10 Networks ADC must enable DDoS filters.
The A10 Networks ADC must protect against ICMP-based Denial of Service (DoS) attacks by employing ICMP Rate Limiting.
Kona Site Defender providing content filtering must protect against known and unknown types of denial-of-service (DoS) attacks by employing rate-based attack prevention behavior analysis.
Kona Site Defender providing content filtering must protect against known types of denial-of-service (DoS) attacks by employing signatures.
The Apache web server must be tuned to handle the operational requirements of the hosted application.
The Apache web server must be protected from being stopped by a non-privileged user.
The Arista Multilayer Switch must ensure all Exterior Border Gateway Protocol (eBGP) routers are configured to use Generalized TTL Security Mechanism (GTSM) or are configured to meet RFC3682.
The ALG must implement load balancing to limit the effects of known and unknown types of Denial of Service (DoS) attacks.
The ALG providing content filtering must protect against known and unknown types of Denial of Service (DoS) attacks by employing rate-based attack prevention behavior analysis.
The ALG providing content filtering must protect against or limit the effects of known and unknown types of Denial of Service (DoS) attacks by employing pattern recognition pre-processors.
The ALG providing content filtering must protect against known types of Denial of Service (DoS) attacks by employing signatures.
The application server, when a MAC I system, must be in a high-availability (HA) cluster.
The application server must protect against or limit the effects of all types of Denial of Service (DoS) attacks by employing organization-defined security safeguards.
The Arista MLS layer 2 switch must be configured for Storm Control to limit the effects of packet flooding types of denial-of-service (DoS) attacks.
The Arista MLS switch must have Root Guard enabled on all switch ports connecting to access layer switches and hosts.
The Arista MLS layer 2 switch must have BPDU Guard enabled on all switch ports connecting to access layer switches and hosts.
The Arista MLS switch must have STP Loop Guard enabled on all nondesignated STP switch ports.
The Arista MLS layer 2 switch must have DHCP snooping for all user VLANs to validate DHCP messages from untrusted sources.
The Arista MLS layer 2 switch must have IP Source Guard enabled on all user-facing or untrusted access switch ports.
The Arista MLS layer 2 switch must have Dynamic Address Resolution Protocol (ARP) Inspection (DAI) enabled on all user VLANs.
The Arista router must not be configured to have any zero-touch deployment feature enabled when connected to an operational network.
The Arista router must be configured to have gratuitous ARP disabled on all external interfaces.
The Arista router must be configured to have IP directed broadcast disabled on all interfaces.
The Arista router must be configured to have Internet Control Message Protocol (ICMP) unreachable notifications disabled on all external interfaces.
The Arista router must be configured to have Internet Control Message Protocol (ICMP) mask replies disabled on all external interfaces.
The Arista router must be configured to have Internet Control Message Protocol (ICMP) redirects disabled on all external interfaces.
The Arista BGP router must be configured to use the maximum prefixes feature to protect against route table flooding and prefix de-aggregation attacks.
The Arista BGP router must be configured to limit the prefix size on any inbound route advertisement to /24 or the least significant prefixes issued to the customer.
The multicast Rendezvous Point (RP) Arista router must be configured to limit the multicast forwarding cache so that its resources are not saturated by managing an overwhelming number of Protocol Independent Multicast (PIM) and Multicast Source Discovery Protocol (MSDP) source-active entries.
The Arista multicast Designated Router (DR) must be configured to increase the shortest-path tree (SPT) threshold or set it to infinity to minimalize source-group (S, G) state within the multicast topology where Any Source Multicast (ASM) is deployed.
The Arista BGP router must be configured to enable the Generalized TTL Security Mechanism (GTSM).
XML-based applications must mitigate DoS attacks by using XML filters, parser options, or gateways.
The CA API Gateway must protect against or limit the effects of all known types of Denial of Service (DoS) attacks on the CA API Gateway management network by employing organization-defined security safeguards.
The CA API Gateway providing content filtering must protect against known and unknown types of Denial of Service (DoS) attacks by employing rate-based attack prevention behavior analysis.
The CA API Gateway must implement load balancing to limit the effects of known and unknown types of Denial of Service (DoS) attacks.
The on-failure container restart policy must be is set to 5 in Docker Enterprise.
The Docker Enterprise default ulimit must not be overwritten at runtime unless approved in the System Security Plan (SSP).
The firewall must employ filters that prevent or limit the effects of all types of commonly known denial-of-service (DoS) attacks, including flooding, packet sweeps, and unauthorized port scanning.
The FortiGate device must protect against known types of denial-of-service (DoS) attacks by employing organization-defined security safeguards.
The FortiGate firewall must employ filters that prevent or limit the effects of all types of commonly known denial-of-service (DoS) attacks, including flooding, packet sweeps, and unauthorized port scanning.
The HP FlexFabric Switch must have Root Guard enabled on all ports where the root bridge should not appear.
The HP FlexFabric Switch must have BPDU Guard enabled on all user-facing access ports.
The HP FlexFabric Switch must have STP Loop Protection enabled all non-designated STP switch ports.
The HP FlexFabric Switch must have unknown storm-constrain enabled.
The HP FlexFabric Switch must have DHCP snooping for all user VLANs to validate DHCP messages from untrusted sources as well as rate-limit DHCP traffic.
The HP FlexFabric Switch must have IP Source Guard enabled on all user-facing or untrusted access switch ports.
The HP FlexFabric Switch must have Dynamic ARP Inspection (DAI) enabled on all user VLANs.
The HP FlexFabric Switch must protect against or limit the effects of all known types of Denial of Service (DoS) attacks on the HP FlexFabric Switch management network by employing organization-defined security safeguards.
The HP FlexFabric Switch must protect against or limit the effects of denial of service (DoS) attacks by employing control plane protection.
The HP FlexFabric Switch must ensure all Exterior Border Gateway Protocol (eBGP) HP FlexFabric Switches are configured to use Generalized TTL Security Mechanism (GTSM).
The DataPower Gateway providing content filtering must protect against known and unknown types of Denial of Service (DoS) attacks by employing rate-based attack prevention behavior analysis (traffic thresholds).
The DataPower Gateway must implement load balancing to limit the effects of known and unknown types of Denial of Service (DoS) attacks.
The DataPower Gateway providing content filtering must protect against known types of Denial of Service (DoS) attacks by employing signatures.
The DataPower Gateway providing content filtering must protect against or limit the effects of known and unknown types of Denial of Service (DoS) attacks by employing pattern recognition pre-processors.
The MQ Appliance messaging server, when categorized as a high level system, must be in a high-availability (HA) cluster.
The MQ Appliance messaging server must protect against or limit the effects of all types of Denial of Service (DoS) attacks by employing operationally-defined security safeguards.
The WebSphere Application servers with an RMF categorization of high must be in a high-availability (HA) cluster.
The WebSphere Application Server high availability applications must be installed on a cluster.
The WebSphere Application Server memory session settings must be defined according to application load requirements.
The WebSphere Application Server thread pool size must be defined according to application load requirements.
The IDPS must protect against or limit the effects of known and unknown types of Denial of Service (DoS) attacks by employing rate-based attack prevention behavior analysis.
The IDPS must protect against or limit the effects of known and unknown types of Denial of Service (DoS) attacks by employing anomaly-based attack detection.
The IDPS must protect against or limit the effects of known types of Denial of Service (DoS) attacks by employing signatures.
The Sentry must implement load balancing to limit the effects of known and unknown types of Denial-of-Service (DoS) attacks.
The JBoss server, when hosting mission critical applications, must be in a high-availability (HA) cluster.
The Juniper router must be configured to protect against known types of Denial of Service (DoS) attacks by employing organization-defined security safeguards.
The Juniper router must be configured to protect against or limit the effects of denial-of-service (DoS) attacks by employing control plane protection.
The Juniper router must be configured to have Gratuitous ARP disabled on all external interfaces.
The Juniper router must be configured to have Internet Control Message Protocol (ICMP) unreachable messages disabled on all external interfaces.
The Juniper router must be configured to have Internet Control Message Protocol (ICMP) mask reply messages disabled on all external interfaces.
The Juniper router must be configured to have Internet Control Message Protocol (ICMP) redirect messages disabled on all external interfaces.
The Juniper BGP router must be configured to enable the Generalized TTL Security Mechanism (GTSM).
The Juniper SRX Services Gateway Firewall providing content filtering must protect against known and unknown types of Denial of Service (DoS) attacks by implementing statistics-based screens.
The Juniper SRX Services Gateway Firewall must implement load balancing on the perimeter firewall, at a minimum, to limit the effects of known and unknown types of Denial of Service (DoS) attacks on the network.
The Juniper SRX Services Gateway Firewall must protect against known types of Denial of Service (DoS) attacks by implementing signature-based screens.
The Juniper BGP router must be configured to use the maximum prefixes feature to protect against route table flooding and prefix de-aggregation attacks.
The Juniper BGP router must be configured to limit the prefix size on any inbound route advertisement to /24 or the least significant prefixes issued to the customer.
The Juniper PE router must be configured to implement Protocol Independent Multicast (PIM) snooping for each Virtual Private LAN Services (VPLS) bridge domain.
The Juniper multicast Rendezvous Point (RP) router must be configured to limit the multicast forwarding cache so that its resources are not saturated by managing an overwhelming number of Protocol Independent Multicast (PIM) and Multicast Source Discovery Protocol (MSDP) source-active entries.
The Juniper multicast Rendezvous Point (RP) must be configured to rate limit the number of Protocol Independent Multicast (PIM) Register messages.
The Juniper multicast Designated Router (DR) must be configured to limit the number of mroute states resulting from Internet Group Management Protocol (IGMP) and Multicast Listener Discovery (MLD) Host Membership Reports.
The Juniper multicast Designated Router (DR) must be configured to set the shortest-path tree (SPT) threshold to infinity to minimalize source-group (S, G) state within the multicast topology where Any Source Multicast (ASM) is deployed.
The Juniper Networks SRX Series Gateway IDPS must protect against or limit the effects of known and unknown types of Denial of Service (DoS) attacks by employing rate-based attack prevention behavior analysis.
The Juniper Networks SRX Series Gateway IDPS must protect against or limit the effects of known and unknown types of Denial of Service (DoS) attacks by employing anomaly-based detection.
The Juniper Networks SRX Series Gateway IDPS must protect against or limit the effects of known types of Denial of Service (DoS) attacks by employing signatures.
The Juniper SRX Services Gateway must configure the control plane to protect against or limit the effects of common types of Denial of Service (DoS) attacks on the device itself by configuring applicable system options and internet-options.
The Juniper SRX Services Gateway must limit the number of sessions per minute to an organization-defined number for SSH to protect remote access management from unauthorized access.
The Juniper SRX Services Gateway must implement service redundancy to protect against or limit the effects of common types of Denial of Service (DoS) attacks on the device itself.
The layer 2 switch must have Root Guard enabled on all switch ports connecting to access layer switches and hosts.
The layer 2 switch must have BPDU Guard enabled on all user-facing or untrusted access switch ports.
The layer 2 switch must have STP Loop Guard enabled on all non-designated STP switch ports.
The layer 2 switch must have Unknown Unicast Flood Blocking (UUFB) enabled.
The layer 2 switch must have DHCP snooping for all user VLANs to validate DHCP messages from untrusted sources.
The layer 2 switch must have IP Source Guard enabled on all user-facing or untrusted access switch ports.
The layer 2 switch must have Dynamic Address Resolution Protocol (ARP) Inspection (DAI) enabled on all user VLANs.
Exchange must provide redundancy.
Exchange must not send delivery reports to remote domains.
Exchange must not send nondelivery reports to remote domains.
The Exchange SMTP automated banner response must not reveal server details.
Exchange must provide Mailbox databases in a highly available and redundant configuration.
Exchange internal Send connectors must use an authentication level.
A host-based firewall must be configured on the SCOM management servers.
ONTAP must be configured to prohibit the use of all unnecessary and/or nonsecure functions, ports, protocols, and/or services.
The network device must be configured to protect against known types of denial-of-service (DoS) attacks by employing organization-defined security safeguards.
Nutanix AOS must protect against or limit the effects of denial-of-service (DoS) attacks by ensuring the operating system is implementing rate-limiting measures on impacted network interfaces.
OHS must be tuned to handle the operational requirements of the hosted application.
Oracle WebLogic must protect the integrity and availability of publicly available information and applications.
The configuration integrity of the container platform must be ensured and compliance policies must be configured.
Oracle WebLogic must protect against or limit the effects of HTTP types of Denial of Service (DoS) attacks.
Oracle WebLogic must limit the use of resources by priority and not impede the host from servicing processes designated as a higher-priority.
The Riverbed NetProfiler must be configured to protect against known types of denial-of-service (DOS) attacks by restricting web and SSH access to the appliance.
The router must not be configured to have any zero-touch deployment feature enabled when connected to an operational network.
The router must be configured to protect against or limit the effects of denial-of-service (DoS) attacks by employing control plane protection.
The router must be configured to have Gratuitous ARP disabled on all external interfaces.
The router must be configured to have IP directed broadcast disabled on all interfaces.
The router must be configured to have Internet Control Message Protocol (ICMP) unreachable notifications disabled on all external interfaces.
The router must be configured to have Internet Control Message Protocol (ICMP) mask replies disabled on all external interfaces.
The router must be configured to have Internet Control Message Protocol (ICMP) redirects disabled on all external interfaces.
The BGP router must be configured to use the maximum prefixes feature to protect against route table flooding and prefix de-aggregation attacks.
The BGP router must be configured to limit the prefix size on any inbound route advertisement to /24 or the least significant prefixes issued to the customer.
The PE router must be configured to implement Internet Group Management Protocol (IGMP) or Multicast Listener Discovery (MLD) snooping for each Virtual Private LAN Services (VPLS) bridge domain.
The multicast Rendezvous Point (RP) router must be configured to limit the multicast forwarding cache so that its resources are not saturated by managing an overwhelming number of Protocol Independent Multicast (PIM) and Multicast Source Discovery Protocol (MSDP) source-active entries.
The multicast Rendezvous Point (RP) must be configured to rate limit the number of Protocol Independent Multicast (PIM) Register messages.
The multicast Designated Router (DR) must be configured to limit the number of mroute states resulting from Internet Group Management Protocol (IGMP) and Multicast Listener Discovery (MLD) Host Membership Reports.
The BGP router must be configured to enable the Generalized TTL Security Mechanism (GTSM).
Riverbed Optimization System (RiOS) must protect against or limit the effects of all known types of Denial of Service (DoS) attacks on the network device management network by employing organization-defined security safeguards.
The SDN controller must be configured to protect against or limit the effects of denial-of-service (DoS) attacks by rate-limiting control-plane communications.
The SEL-2740S must be configured to prevent packet flooding and bandwidth saturation.
SEL-2740S flow rules must include the host IP addresses that are bound to designated SEL-2740S ports for ensuring trusted host access.
The SEL-2740S must be configured with ARP flow rules that are statically created with valid IP-to-MAC address bindings.
The SEL-2740S must be configured to permit the maintenance and diagnostics communications to specified OTSDN Controller(s).
Symantec ProxySG providing content filtering must protect against known and unknown types of denial-of-service (DoS) attacks by employing rate-based attack prevention behavior analysis.
Symantec ProxySG must implement load balancing to limit the effects of known and unknown types of denial-of-service (DoS) attacks.
Tanium must limit the bandwidth used in communicating with endpoints to prevent a denial-of-service (DoS) condition at the server.
Tanium service must be protected from being stopped by a non-privileged user.
The Tanium web server must be tuned to handle the operational requirements of the hosted application.
Symantec ProxySG must enable Attack Detection.
The Tanium application must limit the bandwidth used in communicating with endpoints to prevent a Denial of Service (DoS) condition at the server.
The Tanium application service must be protected from being stopped by a non-privileged user.
The Tanium application must limit the bandwidth used in communicating with endpoints to prevent a denial of service (DoS) condition at the server.
The Tanium application must limit the bandwidth used in communicating with endpoints to prevent a denial-of-service (DoS) condition at the server.
The Tanium application service must be protected from being stopped by a nonprivileged user.
The TPS must protect against or limit the effects of known types of Denial of Service (DoS) attacks by employing signatures.
The TippingPoint SMS must be configured to protect against known types of denial-of-service (DoS) attacks by employing organization-defined security safeguards.
The Tanium Operating System (TanOS) must protect against or limit the effects of denial of service (DoS) attacks by employing organization-defined security safeguards.
The NSX-T Distributed Firewall must employ filters that prevent or limit the effects of all types of commonly known denial-of-service (DoS) attacks, including flooding, packet sweeps, and unauthorized port scanning.
The NSX-T Manager must be configured to protect against known types of denial-of-service (DoS) attacks by employing organization-defined security safeguards.
The NSX-T Tier-1 Gateway Firewall must employ filters that prevent or limit the effects of all types of commonly known denial-of-service (DoS) attacks, including flooding, packet sweeps, and unauthorized port scanning.
The NSX-T Tier-0 Gateway Firewall must employ filters that prevent or limit the effects of all types of commonly known denial-of-service (DoS) attacks, including flooding, packet sweeps, and unauthorized port scanning.
The NSX-T Tier-0 Gateway must be configured to have Internet Control Message Protocol (ICMP) unreachable notifications disabled on all external interfaces.
The NSX-T Tier-0 Gateway must be configured to have Internet Control Message Protocol (ICMP) mask replies disabled on all external interfaces.
The NSX-T Tier-0 Gateway must be configured to have Internet Control Message Protocol (ICMP) redirects disabled on all external interfaces.
The NSX-T Tier-0 Gateway must be configured to use the BGP maximum prefixes feature to protect against route table flooding and prefix de-aggregation attacks.
The application server, when categorized as a high availability system within RMF, must be in a high-availability (HA) cluster.
Tomcat server must be patched for security vulnerabilities.
The Ubuntu operating system must configure the uncomplicated firewall to rate-limit impacted network interfaces.
The Cisco ASA must be configured to implement scanning threat detection.
The Cisco router must not be configured to have any zero-touch deployment feature enabled when connected to an operational network.
The Cisco router must be configured to protect against or limit the effects of denial-of-service (DoS) attacks by employing control plane protection.
The Cisco router must be configured to have Gratuitous ARP disabled on all external interfaces.
The Cisco router must be configured to have IP directed broadcast disabled on all interfaces.
The Cisco router must be configured to have Internet Control Message Protocol (ICMP) unreachable messages disabled on all external interfaces.
The Cisco router must be configured to have Internet Control Message Protocol (ICMP) mask reply messages disabled on all external interfaces.
The Cisco router must be configured to have Internet Control Message Protocol (ICMP) redirect messages disabled on all external interfaces.
The Cisco BGP router must be configured to use the maximum prefixes feature to protect against route table flooding and prefix de-aggregation attacks.
The Cisco BGP router must be configured to limit the prefix size on any inbound route advertisement to /24 or the least significant prefixes issued to the customer.
The Cisco multicast Rendezvous Point (RP) router must be configured to limit the multicast forwarding cache so that its resources are not saturated by managing an overwhelming number of Protocol Independent Multicast (PIM) and Multicast Source Discovery Protocol (MSDP) source-active entries.
The Cisco multicast Rendezvous Point (RP) must be configured to rate limit the number of Protocol Independent Multicast (PIM) Register messages.
The Cisco multicast Designated Router (DR) must be configured to limit the number of mroute states resulting from Internet Group Management Protocol (IGMP) and Multicast Listener Discovery (MLD) Host Membership Reports.
The Cisco multicast Designated Router (DR) must be configured to set the shortest-path tree (SPT) threshold to infinity to minimalize source-group (S, G) state within the multicast topology where Any Source Multicast (ASM) is deployed.
The Cisco ASA must be configured to protect against known types of denial-of-service (DoS) attacks by enabling the Threat Detection feature.
The Cisco router must be configured to protect against known types of denial-of-service (DoS) attacks by employing organization-defined security safeguards.
The Cisco BGP router must be configured to enable the Generalized TTL Security Mechanism (GTSM).
The Cisco switch must have Root Guard enabled on all switch ports connecting to access layer switches.
The Cisco switch must have Bridge Protocol Data Unit (BPDU) Guard enabled on all user-facing or untrusted access switch ports.
The Cisco switch must have Spanning Tree Protocol (STP) Loop Guard enabled.
The Cisco switch must have Unknown Unicast Flood Blocking (UUFB) enabled.
The Cisco switch must have DHCP snooping for all user VLANs to validate DHCP messages from untrusted sources.
The Cisco switch must have IP Source Guard enabled on all user-facing or untrusted access switch ports.
The Cisco switch must have Dynamic Address Resolution Protocol (ARP) Inspection (DAI) enabled on all user VLANs.
The Cisco switch must not be configured to have any zero-touch deployment feature enabled when connected to an operational network.
The Cisco switch must be configured to protect against or limit the effects of denial-of-service (DoS) attacks by employing control plane protection.
The Cisco switch must be configured to have gratuitous ARP disabled on all external interfaces.
The Cisco switch must be configured to have IP directed broadcast disabled on all interfaces.
The Cisco switch must be configured to have Internet Control Message Protocol (ICMP) unreachable messages disabled on all external interfaces.
The Cisco switch must be configured to have Internet Control Message Protocol (ICMP) mask reply messages disabled on all external interfaces.
The Cisco switch must be configured to have Internet Control Message Protocol (ICMP) redirect messages disabled on all external interfaces.
The Cisco multicast Designated switch (DR) must be configured to limit the number of mroute states resulting from Internet Group Management Protocol (IGMP) and Multicast Listener Discovery (MLD) Host Membership Reports.
The Cisco multicast Designated switch (DR) must be configured to set the shortest-path tree (SPT) threshold to infinity to minimalize source-group (S, G) state within the multicast topology where Any Source Multicast (ASM) is deployed.
The Cisco switch must have BPDU Guard enabled on all user-facing or untrusted access switch ports.
The Cisco switch must have STP Loop Guard enabled.
The Cisco switch must be configured to protect against known types of denial-of-service (DoS) attacks by employing organization-defined security safeguards.
The Cisco router must be configured to protect against or limit the effects of denial of service (DoS) attacks by employing control plane protection.
The Cisco BGP router must be configured to limit the prefix size on any inbound route advertisement to /24, or the least significant prefixes issued to the customer.
The Cisco PE router must be configured to implement Internet Group Management Protocol (IGMP) or Multicast Listener Discovery (MLD) snooping for each Virtual Private LAN Services (VPLS) bridge domain.
The Cisco switch must be configured to have Gratuitous ARP disabled on all external interfaces.
The Cisco BGP switch must be configured to enable the Generalized TTL Security Mechanism (GTSM).
The Cisco BGP switch must be configured to use the maximum prefixes feature to protect against route table flooding and prefix de-aggregation attacks.
The Cisco BGP switch must be configured to limit the prefix size on any inbound route advertisement to /24, or the least significant prefixes issued to the customer.
The Cisco PE switch must be configured to implement Internet Group Management Protocol (IGMP) or Multicast Listener Discovery (MLD) snooping for each Virtual Private LAN Services (VPLS) bridge domain.
The Cisco multicast Rendezvous Point (RP) switch must be configured to limit the multicast forwarding cache so that its resources are not saturated by managing an overwhelming number of Protocol Independent Multicast (PIM) and Multicast Source Discovery Protocol (MSDP) source-active entries.
The Cisco multicast Rendezvous Point (RP) router must be configured to filter Protocol Independent Multicast (PIM) Join messages received from the Designated Router (DR) for any undesirable multicast groups.
The Cisco switch must have Root Guard enabled on all switch ports connecting to access layer switches and hosts.
The Cisco ISE must configure the control plane to protect against or limit the effects of common types of Denial of Service (DoS) attacks on the device itself by configuring applicable system options and internet-options.
The Cisco switch must be configured to protect against or limit the effects of denial-of-service (DoS) attacks by employing control plane protection.
The Cisco BGP switch must be configured to check whether a single-hop eBGP peer is directly connected.
The container platform must protect against or limit the effects of all types of denial-of-service (DoS) attacks by employing organization-defined security safeguards.
The operating system must protect against or limit the effects of Denial of Service (DoS) attacks by ensuring the operating system is implementing rate-limiting measures on impacted network interfaces.
AIX must protect against or limit the effects of Denial of Service (DoS) attacks by ensuring AIX is implementing rate-limiting measures on impacted network interfaces.
IBM z/OS Policy agent must contain a policy that protects against or limits the effects of Denial of Service (DoS) attacks by ensuring the operating system is implementing rate-limiting measures on impacted network interfaces.
The IBM z/OS Policy Agent must contain a policy that protects against or limits the effects of denial-of-service (DoS) attacks by ensuring IBM z/OS is implementing rate-limiting measures on impacted network interfaces.
The IBM z/OS Policy Agent must contain a policy that protects against or limits the effects of denial-of-service (DoS) attacks by ensuring the operating system is implementing rate-limiting measures on impacted network interfaces.
The Juniper EX switch must be configured to enable Root Protection on all interfaces connecting to access layer switches and hosts.
The Juniper EX switch must be configured to enable BPDU Protection on all user-facing or untrusted access switch ports.
The Juniper EX switch must be configured to enable STP Loop Protection on all non-designated STP switch ports.
The Juniper EX switch must be configured not to forward unknown unicast traffic to access interfaces.
The Juniper EX switch must be configured to enable DHCP snooping for all user VLANs to validate DHCP messages from untrusted sources.
The Juniper EX switch must be configured to enable IP Source Guard on all user-facing or untrusted access VLANs.
The Juniper EX switch must be configured to enable Dynamic Address Resolution Protocol (ARP) Inspection (DAI) on all user VLANs.
The ICS must be configured to audit the execution of privileged functions such as accounts additions and changes.
The Juniper EX switch must be configured to protect against known types of denial-of-service (DoS) attacks by employing organization-defined security safeguards.
The Juniper router must not be configured to have any zero-touch deployment feature enabled when connected to an operational network.
The Juniper router must be configured to have IP directed broadcast disabled on all interfaces.
The Juniper router must be configured to have Internet Control Message Protocol (ICMP) unreachable notifications disabled on all external interfaces.
The Juniper router must be configured to have Internet Control Message Protocol (ICMP) mask replies disabled on all external interfaces.
The Juniper router must be configured to have Internet Control Message Protocol (ICMP) redirects disabled on all external interfaces.
The Juniper BGP router must be configured to use the prefix limit feature to protect against route table flooding and prefix deaggregation attacks.
The Juniper PE router must be configured to implement Internet Group Management Protocol (IGMP) or Multicast Listener Discovery (MLD) snooping for each Virtual Private LAN Services (VPLS) bridge domain.
The Juniper multicast RP router must be configured to limit the multicast forwarding cache so that its resources are not saturated by managing an overwhelming number of PIM and MSDP source-active entries.
The Juniper multicast Designated Router (DR) must be configured to increase the shortest-path tree (SPT) threshold or set it to infinity to minimalize source-group (S, G) state within the multicast topology where Any Source Multicast (ASM) is deployed.
Exchange Internal Send connectors must use an authentication level.
Exchange internal send connectors must use an authentication level.
Exchange must provide mailbox databases in a highly available and redundant configuration.
Access to web administration tools must be restricted to the web manager and the web managers designees.
The IIS 10.0 web server must be tuned to handle the operational requirements of the hosted application.
The system must be configured to ignore NetBIOS name release requests except from WINS servers.
Turning off File Explorer heap termination on corruption must be disabled.
File Explorer heap termination on corruption must be disabled.
Windows Server 2016 must be configured to ignore NetBIOS name release requests except from WINS servers.
Windows Server 2019 must be configured to ignore NetBIOS name release requests except from WINS servers.
Windows Server 2022 must be configured to ignore NetBIOS name release requests except from WINS servers.
Multicast register messages must be rate limited per each source-group (S, G) entry.
The number of mroute states resulting from Internet Group Management Protocol (IGMP) or Multicast Listener Discovery (MLD) membership reports must be limited.
The number of source-group (SG) states must be limited within the multicast topology where Any Source Multicast (ASM) is deployed.
Internet Group Management Protocol (IGMP) or Multicast Listener Discovery (MLD) snooping must be implemented within the network access layer.
The DBMS must protect against or limit the effects of organization-defined types of Denial of Service (DoS) attacks.
The Oracle Linux operating system must protect against or limit the effects of Denial of Service (DoS) attacks by validating the operating system is implementing rate-limiting measures on impacted network interfaces.
A firewall must be able to protect against or limit the effects of denial-of-service (DoS) attacks by ensuring OL 8 can implement rate-limiting measures on impacted network interfaces.
The Palo Alto Networks security platform must protect against Denial of Service (DoS) attacks from external sources.
The Palo Alto Networks security platform must use a Vulnerability Protection Profile that blocks any critical, high, or medium threats.
The Palo Alto Networks security platform must protect against or limit the effects of known and unknown types of Denial of Service (DoS) attacks by employing rate-based attack prevention behavior analysis (traffic thresholds).
Automation Controller must be configured to fail over to another system in the event of log subsystem failure.
OpenShift must protect against or limit the effects of all types of Denial-of-Service (DoS) attacks by employing organization-defined security safeguards by including a default resource quota.
OpenShift must protect against or limit the effects of all types of Denial-of-Service (DoS) attacks by defining resource quotas on a namespace.
The Automation Controller NGINX web server must be protected from being stopped by a nonprivileged user.
A firewall must be able to protect against or limit the effects of Denial of Service (DoS) attacks by ensuring RHEL 8 can implement rate-limiting measures on impacted network interfaces.
RHEL 9 must protect against or limit the effects of denial-of-service (DoS) attacks by ensuring rate-limiting measures on impacted network interfaces are implemented.
RHEL 9 must be configured to use TCP syncookies.
SuSEfirewall2 must protect against or limit the effects of Denial-of-Service (DoS) attacks on the SUSE operating system by implementing rate-limiting measures on impacted network interfaces.
The VMM must protect against or limit the effects of Denial of Service (DoS) attacks by ensuring the VMM is implementing rate-limiting measures on impacted network interfaces.
VAMI must be protected from being stopped by a nonprivileged user.
Performance Charts must disable the shutdown port.
ESX Agent Manager must disable the shutdown port.
Lookup Service must disable the shutdown port.
The Photon operating system must use Transmission Control Protocol (TCP) syncookies.
The vCenter ESX Agent Manager service must limit the number of maximum concurrent connections permitted.
The Security Token Service must disable the shutdown port.
The vCenter Lookup service must limit the number of maximum concurrent connections permitted.
vSphere UI must disable the shutdown port.
The Photon operating system must be configured to use TCP syncookies.
The web server must be protected from being stopped by a non-privileged user.
The web server must be tuned to handle the operational requirements of the hosted application.
The BIG-IP appliance must be configured to protect against or limit the effects of all known types of Denial of Service (DoS) attacks on the BIG-IP appliance management network by limiting the number of concurrent sessions.
If the BIG-IP appliance is being used to authenticate users for web applications, the HTTPOnly flag must be set.
The F5 BIG-IP appliance must be configured to restrict a consistent inbound IP for the entire management session.
The BIG-IP Core implementation must be configured to protect against known and unknown types of Denial of Service (DoS) attacks by employing rate-based attack prevention behavior analysis when providing content filtering to virtual servers.
The BIG-IP Core implementation must be configured to implement load balancing to limit the effects of known and unknown types of Denial of Service (DoS) attacks to virtual servers.
The BIG-IP Core implementation must be configured to protect against known types of Denial of Service (DoS) attacks by employing signatures when providing content filtering to virtual servers.
The BIG-IP Core implementation must be configured to protect against or limit the effects of known and unknown types of Denial of Service (DoS) attacks by employing pattern recognition pre-processors when providing content filtering to virtual servers.
Ubuntu 22.04 LTS must configure the Uncomplicated Firewall (ufw) to rate-limit impacted network interfaces.
The F5 BIG-IP appliance providing content filtering must employ rate-based attack prevention behavior analysis.
The F5 BIG-IP appliance providing content filtering must protect against or limit the effects of known and unknown types of denial-of-service (DoS) attacks by employing pattern recognition pre-processors.
The Enterprise Voice, Video, and Messaging Session Manager must be configured to protect against or limit the effects of all types of denial-of-service (DoS) attacks by employing organizationally defined security safeguards.
The F5 BIG-IP appliance must employ filters that prevent or limit the effects of all types of commonly known denial-of-service (DoS) attacks, including flooding, packet sweeps, and unauthorized port scanning.
The F5 BIG-IP appliance must be configured to limit the number of concurrent sessions to the Configuration Utility to 10 or an organization-defined number.
The ICS must be configured to protect against known types of denial-of-service (DoS) attacks by enabling JITC mode.
The Juniper EX switch must be configured to enable Root Protection on STP switch ports connecting to access layer switches.
The Juniper SRX Services Gateway Firewall providing content filtering must protect against known and unknown types of denial-of-service (DoS) attacks by implementing statistics-based screens.
The Juniper SRX Services Gateway Firewall must implement load balancing on the perimeter firewall, at a minimum, to limit the effects of known and unknown types of denial-of-service (DoS) attacks on the network.
The Juniper SRX Services Gateway Firewall must protect against known types of denial-of-service (DoS) attacks by implementing signature-based screens.
Least privilege access and need to know must be required to access MKE runtime and instantiate container images.
The Palo Alto Networks security platform must block outbound traffic containing denial-of-service (DoS) attacks to protect against the use of internal information systems to launch any DoS attacks against other networks or endpoints.
The Palo Alto Networks security platform must protect against or limit the effects of known and unknown types of denial-of-service (DoS) attacks by employing rate-based attack prevention behavior analysis (traffic thresholds).
The multicast Designated Router (DR) must be configured to increase the shortest-path tree (SPT) threshold or set it to infinity to minimalize source-group (S, G) state within the multicast topology where Any Source Multicast (ASM) is deployed.
The TPS must protect against or limit the effects of known types of denial-of-service (DoS) attacks by employing signatures.
The NSX Distributed Firewall must limit the effects of packet flooding types of denial-of-service (DoS) attacks.
The NSX Manager must be configured to protect against denial-of-service (DoS) attacks by limit the number of concurrent sessions to an organization-defined number.
The NSX Tier-0 Gateway Firewall must manage excess bandwidth to limit the effects of packet flooding types of denial-of-service (DoS) attacks.
The NSX Tier-0 Gateway router must be configured to have Internet Control Message Protocol (ICMP) unreachable notifications disabled on all external interfaces.
The NSX Tier-0 Gateway router must be configured to have Internet Control Message Protocol (ICMP) mask replies disabled on all external interfaces.
The NSX Tier-0 Gateway router must be configured to have Internet Control Message Protocol (ICMP) redirects disabled on all external interfaces.
The NSX Tier-0 Gateway router must be configured to use the Border Gateway Protocol (BGP) maximum prefixes feature to protect against route table flooding and prefix de-aggregation attacks.
A firewall must be able to protect against or limit the effects of Denial of Service (DoS) attacks by ensuring TOSS can implement rate-limiting measures on impacted network interfaces.
The NSX Tier-1 Gateway firewall must manage excess bandwidth to limit the effects of packet flooding types of denial-of-service (DoS) attacks.