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
170 ServerIron ADX Security Guide
53-1002440-03
Advanced SSL profile configuration
6
NOTE
All intermediate CA certificates need to be uploaded to the ServerIronADX.
Configuring certificate chain depth
You can configure certificate chain depth up to which certificate verification can be done by a
ServerIronADX. The default value is 4 and it can be configured up to 10 as shown in the following.
ServerIronADX(config)#ssl profile profile1
ServerIronADX(config-ssl-profile-ssl-profile1)# verify-cert-depth 10
Syntax: [no] verify-cert-depth <chain-depth>
The <chain-depth> variable specifies the maximum certificate chain depth verified. The accepted
values are 4 - 10. The default value is 4.
Enabling session caching
Session caching or session reuse is a mode of operation in SSL where multiple SSL connections
can share the same SSL session. A complete SSL handshake is done only for the first connection.
All subsequent connections use the parameters negotiated in the first connection, for as long as
the SSL session is cached.
By default, session caching is turned off on the ServerIronADX.
The following example enables session caching for the SSL client in the SSL profile "profile1".
ServerIronADX(config)# ssl profile profile1
ServerIronADX(config-ssl-profile-profile1)# session-cache on
Syntax: [no] session-cache { on| off }
The on parameter enables session caching for the SSL client.
The off parameter disables session caching. This is the default state.
NOTE
Please note that SSL session caching will not work with the server source-port-hash command
because that command will redirect traffic (from the same client IP) with different TCP source ports
to different BPs.
Configuring session cache size
You can specify the maximum number of session-cache entries per profile, as shown in the
following example:
ServerIronADX(config-ssl-profile-ssl1)# session-cache max-entries 512
Syntax: [no] session-cache max-entries <num-max-entries>
The <num-max-entries> can have a value between 512 and 8192.
The default value is 1024.