
20
McAfee
®
IntruShield
®
IPS System IntruShield Best Practices
Special Topics: Best Practices Sensor performance with HTTP Response processing
1
TLS_RSA_WITH_NULL_MD5
TLS_RSA_WITH_NULL_SHA
TLS_RSA_WITH_RC4_128_MD5
TLS_RSA_WITH_RC4_128_SHA
TLS_RSA_WITH_DES_CBC_SHA
TLS_RSA_WITH_3DES_EDE_CBC_SHA
TLS_RSA_WITH_AES_128_CBC_SHA
TLS_RSA_WITH_AES_256_CBC_SHA
Unsupported SSL functionality
The following SSL functionalities are not supported:
iPlanet Web servers
Diffie-Hellman ciphers (McAfee recommends that you disable acceptance of
Diffie-Hellman requests on the SSL Web server to ensure that IntruShield is able to
decrypt the traffic)
Compression in the SSL records (a negotiable option in SSLv3 and TLS)
PCT (Microsoft's extension to SSLv2)
Sensor performance with HTTP Response processing
HTTP response processing is disabled by default. You can enable it for each traffic
direction on an interface pair. To minimize the potential performance impact on the
sensor, we recommend that you enable HTTP response processing on the minimum
number of ports and in only the required directions to achieve your protection goals.
Some examples of HTTP response processing deployment:
You want to protect a bunch of clients on your internal network -- enable HTTP
response processing for inbound traffic only.
You are serving Web content and do not wish to serve attacks embedded in HTTP
response traffic -- enable HTTP response processing for outbound traffic only.
You want to protect both clients internally and content you’re serving. Enable HTTP
response processing in both directions.
HTTP Response processing enabled for both inbound and
outbound traffic
The following table shows sensor performance with HTTP response processing
enabled in both directions:
5 HTTP 1.1 get page requests per TCP connection with a 5K response each sent in
both directions
Comentarios a estos manuales