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
36 ServerIron ADX Security Guide
53-1002440-03
Traffic segmentation
1
NOTE
VIP protection works for IPv4 VIPs alone and cannot be enabled for IPv6 VIPs.
You can enable this feature globally by entering the following command.
ServerIronADX(config)# server vip-protection
Syntax: [no] server vip-protection
Once enabled, the VIP protection applies to all existing and new VIP configurations.
If you want to enable the feature on individual VIPs, enter the following command.
ServerIronADX(config)# server virtual-name-or-ip v1
ServerIronADX(config-vs-v1)# vip-protection
NOTE
A reload is required for VIP protection to take effect when enabled on a global level using the server
vip-protection command.
Syntax: [no] vip-protection
VIP protection adds CAM entries for each defined virtual port associated with each VIP. An
additional CAM entry is defined for ICMP traffic destined to each VIP. An entry to drop the traffic is
also added in the CAM for each VIP, which makes sure that traffic destined to any destination port
other than the virtual ports is dropped by hardware.
NOTES:
• VIP protection does not support complex protocols such as FTP, TFTP, MMS, RTSP, SIP, that
establish data connections based on the information exchanged on control channel.
• VIP protection cannot be enabled on a VIP that is part of a dynamic NAT address pool.
• VIP protection cannot be used along with features that require binding of virtual default port to
real server default port.
Traffic segmentation
The traffic segmentation feature allows you to create segmentation among multiple L4-7 SLB
domains of a single ServerIron ADX. The purpose of this feature is to ensure that traffic from one
SLB domain to another SLB domain goes through the upstream firewall and does not get switched
locally. This can be accomplished using either of the following methods:
• VLAN bridging
• Using the server use-session-for-vip-mac
These features help meet some of the security requirements for PCI compliance.
VLAN bridging
The VLAN bridging feature allows you to bridge together two VLANs so that packets will be layer-2
switched from one VLAN to the other. When two VLANs are bridged together, all packets received
on one VLAN are translated to the other VLAN and switched.