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 153
53-1002440-03
Configuring SSL on a ServerIron ADX
6
Chained Certificate Verification
When the server certificate is not signed directly by the root CA, but signed by an intermediate CA,
as shown in the following example, there are two possible scenarios.
• CA ----> intermediate CA ----> server certificate
Client Already Has Intermediate CA's Certificate
In the first scenario, there are NO additional requirements. When the server sends a certificate that
is signed by the intermediate CA, the client browser will be able to process it successfully.
Client Does NOT Have Intermediate CA's Certificate
In the second scenario, the server sends a certificate that is signed by intermediate CA. However
since the end-client has no knowledge of the intermediate CA, it denies the certificate and the
process is unsuccessful.
To resolve this issue, the server must send not only its own certificate, but also the intermediate
CA's certificate that is signed the root CA. In other words, the server sends a chain of certificates.
NOTE
The server sends only its own certificate and the intermediate CA's certificate. It does NOT send the
root CA’s certificate.
Example
Your server certificate is signed by VeriSign International Server CA - Class 3. This is an
intermediate CA, whose certificate is signed by VeriSign Class 3 Public Primary CA.
Figure 12 shows the certificate hierarchy, with "L47.brocade.com" at the third level. The first level
certificate is also labeled as "built-in object token" by Firefox. This is an example of chaining. The
server sends a two-level chain containing its own certificate and the certificate of the intermediate
CA.
The certificate chain sent by the server must be correct: server-> intermediate CA. The
intermediate CA certificate must also be signed by a CA whose certificate is present with the client.
Figure 12 shows the certificate fields.