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 169
53-1002440-03
Advanced SSL profile configuration
6
The ServerIronADX supports configuration of up to ten CRL records. For each CRL record, the size is
up to 255K.
Syntax: ssl crl-record <local-name> <url> der | pem <refresh-interval-in-hours>
The <local-name> variable specifies a name for the CRL entry. The value of this entry is an ASCII
string.
The <url> variable specifies the location where the CRL is located. This value can be either an IP
address or a domain name.
The pem parameter directs the CRL to be downloaded in the PEM format.
The der parameter directs the CRL to be downloaded in the DER format.
The <refresh-interval-in-hours> variable specifies the number of hours to wait before updating the
CRL.
NOTE
Limiting the maximum number of connections from all client-ip’s is supported only via the max-conn
default <num> command. The max-conn 0.0.0.0/0 <num> command is no longer supported.
NOTE
To avoid “man-in-the-middle” attacks, where the CRL may be compromised while on the network,
CRLs are digitally signed by the issuing CAs. For this reason, it is essential that the certificate of the
CA that issues the CRL is present on the ServerIronADX when a client certificate is being checked
for revocation.
Allowing Self Signed Certificates
By default, the a ServerIronADX does not accept certificates that have been issued by a CA that is
not trusted. A ServerIronADX only accepts certificates which have been signed by a CA that is
configured under the SSL profile. For testing purposes, customers may want to use self-signed
certificates (generated using the Open SSL utilities or by the ServerIron cert gen utility) on the SSL
client.
The following example configures a ServerIronADX to accept self signed certificates.
ServerIronADX(config)# ssl profile profile1
ServerIronADX(config-ssl-profile-profile1)#allow-self-signed-cert
Syntax: [no] allow-self-signed-cert
Enabling a certificate chain
By default, for CA signed certificates, the ServerIronADX does not send the entire certificate chain
when presenting the certificate to the client.
To enable the ServerIronADX to send the entire certificate chain (including the root CA certificate
and any intermediate CA certificates), enter the following commands in the SSL profile
configuration mode:
ServerIronADX(config)#ssl profile profile1
Syntax: ssl profile <profile-name>
ServerIronADX(config-ssl-profile-ssl-profile1)# enable-certificate-chaining
Syntax: enable-certificate-chaining