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 167
53-1002440-03
Advanced SSL profile configuration
6
Enabling certificate verification
The ServerIronADX can be optionally configured to enforce client certificate verification. When
client certificate verification is configured, the ServerIronADX requires all clients to present their
signed certificates. The certificates are compared against trusted CAs and a connection is allowed
or denied.
You can enable client certificate verification on a per-ssl-handshake or per-connection basis in one
of two modes:
• Request mode
• Require mode
In request mode, a client-certificate is requested. The connection is allowed if the client presents a
valid certificate, or if a certificate is not presented at all. The connection is denied if a client
presents an invalid, revoked, or expired certificate.
In require mode, a client-certificate is always required.
Client-authentication can be used in the following four combinations:
• Per-connection request
• Per-connection require
• Per-ssl-handshake request
• Per-ssl-handshake require
Syntax: verify-client-cert <per-ssl-handshake/per-ssl-connection> <request/require>
• per-ssl-handshake - Requests a client certificate for every new SSL handshake.
• per-connection - Requests a client certificate for every new SSL connection.
The difference between the two modes is apparent if SSL session caching is enabled. When this is
the case, multiple SSL connections share the same SSL session, without performing a full SSL
handshake for each connection.
Client certificate verification in SSL Proxy Mode
SSL Proxy mode has two traffic segments: from the client to the ServerIronADX and from the
ServerIronADX to the server.
In the first segment, the ServerIronADX acts a server to a browser-based client. In the second
segment, ServerIronADX acts as a client to the real server.
In some cases the real server is configured so that only clients with valid certificates can connect to
it. Because the ServerIronADX is also a client, it must have a valid client certificate to connect to
the real server. A client certificate can be obtained from a CA, and uploaded to the ServerIronADX.
Once uploaded, the client certificate should be configured in the server ssl profile using the
following commands:
• keypair-file - To configure client-certificate key
• certificate file - To configure client-certificate
Client certificate verification in the second traffic segment (from the ServerIronADX to the server)
can also be enabled. In this configuration, the real server allows a connection only from the
ServerIronADX. No other device is allowed. To connect to the real server, the ServerIronADX must
present a client certificate issued by a CA and trusted by the server.
To successfully complete this process, the ServerIronADX requires the following items: