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

128 ServerIron ADX Security Guide
53-1002440-03
DDoS protection
5
fin-with-no-ack TCP packets with a FIN flag normally have an ACK bit set.
Use fin-with-no-ack to drop TCP packet where FIN flag is set, but the ACK bit
is not set.
large icmp ICMP packets greater than 1500 bytes.
unknown-ip-protocol <value> Protocol 101 and above are currently reserved and undefined. Attackers
sometimes use protocol values that are not valid protocols.
Use unknown-ip-protocol <value> to drop packets where protocol field is set
to 101 or greater. Replace the <value> with the actual protocol number. If
the ServerIron ADX gets an IP protocol packet matching that number, the
packet will be dropped.
address-sweep <dest-ip>
<hold-down-interval>
Attacker scans the network for information behind the ServerIron ADX,
uncovering an address to target. For example, sending ping requests to
10.1.1.1 through 100. A reply from any device indicates a server exists.
Use address-sweep <dest-ip> <hold-down-interval> to log the number of
different addresses being accessed from one remote source. If the same
client sends a request to different IP addresses, then the ServerIron ADX
keeps track of the number of IP address the client is trying to access. If the
number exceeds the configured <dest-ip> limit within a 5-second timer, then
all the packets from that client will start being dropped (reset) for the
specified <hold-down-interval>. The timer is internal to the ServerIron ADX,
and it does not start when the client accesses the first IP address.
For example, consider the command address-sweep 2 8. A client can access
only a maximum of two IP addresses. As soon as it accesses the third IP
within a 5-second interval, the ServerIron ADX will hold the client down for 8
minutes. Accessing two IP addresses within 5 seconds is permissible in this
example.
Use security net-scan-mon-interval <seconds> to change the timer default
(5 seconds).
port-scan <dest-ip-or-port-pair>
<hold-down-interval>
Attacker sends traffic using the same source IP to different ports on the
same destination IP, with the intent of identifying a service to target.
The ServerIron ADX tracks the number of IP destination and port pairs. For
example, if a client accessed IP 1 and port 0, that counts as one
<dest-ip-or-port-pair>.
Use port-scan to internally log the number of different ports scanned from
one source. If the number exceeds a configured <dest-ip-or-port-pair> value
(for example, 10 ports in 5 seconds), the ServerIron ADX will flag it as an
attack and reject all traffic from that source for the <hold-down-interval>.
The default internal timer value is 5 seconds. Use security
net-scan-mon-interval <seconds> to change the timer default.
xmas-tree A Xmas tree attack is detected when a packet with the URG,PSH & FIN flags
set is detected.
icmp-type Different types and subtypes of ICMP can be used to attack or to gain
knowledge about the host or network, which would then be used for an
attack. For example, ICMP timestamp (type 13) will elicit a timestamp reply
from Unix systems, but Microsoft Windows would not do so. A hacker can
then attack known vulnerabilities of the system.
Use icmp-type to configure an ICMP software rule to drop specific ICMP
types and subtypes.
TABLE 13 Rules for common attack types and descriptions










