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 165
53-1002440-03
Basic SSL profile configuration
6
Specifying a keypair file
Each SSL profile must be associated with an RSA key-pair file that was previously defined using the
genrsa command. The following example uses the keypair-file command to associate the key pair
file named "rsakey" with the "profile1" SSL profile.
ServerIronADX(config)# ssl profile profile1
ServerIronADX(config-ssl-profile-profile1)# keypair-file rsakey
Syntax: keypair-file <keypair-file-name>
The <keypair-file-name> variable is an ASCII string a keypair file that was generated using the
genrsa command.
Specifying a cipher suite
By specifying cipher suites under an SSL profile, you can control the security strength of the SSL
handshakes. The ServerIronADX can accept a new SSL handshake from the client only if the list of
cipher suites presented by the client includes a cipher suite configured under the SSL profile.
The following example specifies that all cipher suites are configured under the "profile1" SSL
profile.
ServerIronADX(config)# ssl profile profile1
ServerIronADX(config-ssl-profile-profile1)# cipher-suite all-cipher-profiles
Syntax: cipher-suite rsa-export-with-des40-cbc-sha | rsa-export-with-rc4-40-md5 |
rsa-with-3des-ede-cbc-sha | rsa-with-aes-128-sha | rsa-with-aes-256-sha |
rsa-with-des-cbc-sha | rsa-with-rc4-128-md5 | rsa-with-rc4-128-sha | all-cipher-suites
Use the rsa-export-with-des40-cbc-sha parameter to specify that cipher suite.
Use the rsa-export-with-rc4-40-md5 parameter to specify that cipher suite.
Use the rsa-with-3des-ede-cbc-sha parameter to specify that cipher suite.
Use the rsa-with-aes-128-sha parameter to specify that cipher suite.
Use the rsa-with-aes-256-sha parameter to specify that cipher suite.
Use the rsa-with-des-cbc-sha parameter to specify that cipher suite.
Use the rsa-with-rc4-128-md5 parameter to specify that cipher suite.
Use the rsa-with-rc4-128-sha parameter to specify that cipher suite.
Use the all-cipher-suites parameter to specify all cipher suites including the other parameters used
in this command.
NOTE
The export cipher suites work only if the asymmetric key pair strength is less than or equal to 512
bits. This is consistent with the export rules. If the RSA key pair strength is greater than 512 bits,
then SSL handshake requests that contain export cipher suites do not work.
Configuring Multiple Cipher Suites
Among the cipher suite options, is one that specifies all cipher suites. You can also specify more
than one cipher inside an SSL profile without specifying all options. This is shown in the following
example.










