Home Theater Server User Manual
Table Of Contents
- Contents
- About This Document
- Network Security
- TCP SYN attacks
- IP TCP syn-proxy
- Granular application of syn-proxy feature
- Syn-def
- No response to non-SYN first packet of a TCP flow
- Prioritizing management traffic
- Peak BP utilization with TRAP
- Transaction Rate Limit (TRL)
- Understanding transaction rate limit
- Configuring transaction rate limit
- Configuring the maximum number of rules
- Saving a TRL configuration
- Transaction rate limit command reference
- Global TRL
- TRL plus security ACL-ID
- security acl-id
- Transaction rate limit hold-down value
- Displaying TRL rules statistics
- Displaying TRL rules in a policy
- Displaying IP address with held down traffic
- Refusing new connections from a specified IP address
- HTTP TRL
- Overview of HTTP TRL
- Configuring HTTP TRL
- Displaying HTTP TRL
- Display all HTTP TRL policies
- Display HTTP TRL policy from index
- Display HTTP TRL policy client
- Display HTTP TRL policy starting from index
- Display HTTP TRL policy matching a regular expression
- Display HTTP TRL policy client index (MP)
- Display HTTP TRL policy client index (BP)
- Display HTTP TRL policy for all client entries (BP)
- Downloading an HTTP TRL policy through TFTP
- HTTP TRL policy commands
- Logging for DoS Attacks
- Maximum connections
- clear statistics dos-attack
- Maximum concurrent connection limit per client
- Firewall load balancing enhancements
- Syn-cookie threshhold trap
- Service port attack protection in hardware
- Traffic segmentation
- DNS attack protection
- Access Control List
- How ServerIron processes ACLs
- Default ACL action
- Types of IP ACLs
- ACL IDs and entries
- ACL entries and the Layer 4 CAM
- Configuring numbered and named ACLs
- Modifying ACLs
- Displaying a list of ACL entries
- Applying an ACLs to interfaces
- ACL logging
- Dropping all fragments that exactly match a flow-based ACL
- Enabling ACL filtering of fragmented packets
- Enabling hardware filtering for packets denied by flow-based ACLs
- Enabling strict TCP or UDP mode for flow-based ACLs
- ACLs and ICMP
- Using ACLs and NAT on the same interface (flow-based ACLs)
- Displaying ACL bindings
- Troubleshooting rule-based ACLs
- IPv6 Access Control Lists
- Network Address Translation
- Syn-Proxy and DoS Protection
- Understanding Syn-Proxy
- Configuring Syn-Proxy
- DDoS protection
- Configuring a security filter
- Configuring a Generic Rule
- Configuring a rule for common attack types
- Configuring a rule for ip-option attack types
- Configuring a rule for icmp-type options
- Configuring a rule for IPv6 ICMP types
- Configuring a rule for IPv6 ext header types
- Binding the filter to an interface
- Clearing DOS attack statistics
- Clearing all DDOS Filter & Attack Counters
- Logging for DoS attacks
- Displaying security filter statistics
- Address-sweep and port-scan logging
- Secure Socket Layer (SSL) Acceleration
- SSL overview
- SSL acceleration on the ServerIron ADX
- Configuring SSL on a ServerIron ADX
- Basic SSL profile configuration
- Advanced SSL profile configuration
- Configuring Real and Virtual Servers for SSL Termination and Proxy Mode
- Configuration Examples for SSL Termination and Proxy Modes
- SSL debug and troubleshooting commands
- Displaying socket information

ServerIron ADX Security Guide 127
53-1002440-03
DDoS protection
5
Configuring a rule for common attack types
As described in “Configuring a Generic Rule” on page 125, you can create a custom rule to manage
DDoS attacks. In addition, ServerIron ADX has built-in rules to manage common attack types. In
this case, the rule command is used with a <rule-name> variable specified in Table 13.
The following example configures a the "filter1" security filter with a rule to drop packets that are
associated with a "xmas tree" attack.
ServerIronADX(config)# security filter filter1
ServerIronADX(config-sec-filter1)#rule xmas-tree drop
Syntax: [no] rule <rule-name> [log | no-log] [drop | no-drop]
The <rule-name> variable is specified as one of the options described in Table 13.
The log parameter directs the ServerIron ADX to log traffic on the bound interface that matches the
rule specified by the configured <rule-name>. The no-log parameter disables this function.
The drop parameter directs the ServerIron ADX to drop traffic on the bound interface that matches
the rule specified by the configured <rule-name>. The no-drop parameter disables this function.
TABLE 13 Rules for common attack types and descriptions
Attack Type Description
syn-fragments A SYN-fragment attack floods the target host with SYN-packet fragments.
The host stores the fragments, in order to reassemble them. By not
completing the connection, and flooding the server or host with such
fragmented SYN packets, the host’s memory buffer would eventually fill up.
A SYN packet need not be fragmented. It is very small. Use syn-fragments to
drop any SYN packet with the more-fragments bit on.
syn-and-fin-set Attacker sends a packet with both SYN and FIN bits set to see what kind of
system reply is returned, and then use the system information for further
attacks using known system vulnerabilities.
Use syn-and-fin-set to drop packets having both the SYN and FIN bits set in
the flags field
tcp-no-flags TCP packets are normally sent with at least one bit set in the flags field.
Use tcp-no-flags to drop TCP packet with a missing or malformed flags field.
icmp-fragments ICMP fragments can be used to exploit the vulnerabilities in the packet
reassembly code. Enabling icmp-fragments allows you to create a rule that
can be configured to drop or log fragmented ICMP packets.
deny-all-fragments IP fragments can be used to exploit the vulnerabilities in the packet
reassembly code of specific IP stack implementations. When you enable
deny-all-fragments, the ServerIron ADX drops all IP fragments.
land-attack Attacker sends spoofed SYN packets containing the destination IP as the
source-IP address. Flooding a system with such empty connections can
overwhelm the system, causing DoS.
Use land-attack to drop packets containing the same IP address as both the
source and destination IP addresses.
ping-of-death If the sum of "Fragment Offset" and "Total length" fields in the IP header of
each IP fragment is larger than 65,535, then the packet is invalid, and such
packet will be dropped.










