01.01.2013 Views

Web Gateway 7.1.5 Product Guide - McAfee

Web Gateway 7.1.5 Product Guide - McAfee

Web Gateway 7.1.5 Product Guide - McAfee

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

<strong>Web</strong> filtering<br />

SSL scanning 6<br />

SSL Client Context engine settings<br />

You can configure the SSL Client Context engine settings. These are the settings for the module that<br />

deals with the certificates the appliance sends to its clients.<br />

Note: These settings can be configured on the Settings tab of the Policy top-level menu.<br />

Default CA<br />

Settings for the SSL Client Context module when it uses a certificate issued by the default root<br />

certificate authority (root CA)<br />

Define SSL Client Context<br />

Settings for the SSL Client Context module<br />

(Current root certificate authority) — Parameters and values of the root certificate authority (root CA)<br />

that is currently in use on the appliance<br />

After the initial setup, a default root CA is implemented on the appliance. For further administration, it<br />

is recommended that you create your own root CA. Use the Generate New button to create this<br />

certificate authority.<br />

Send certificate chain — When selected, the appliance sends information on the chain of<br />

certificates that are involved in the process of validating the certificate the appliance sends to its<br />

clients<br />

The certificate the appliance sends as a server to its clients is considered to exist on level 0. When a<br />

certificate authority (CA) signs this server certificate to validate it, it is done on level 1. When an<br />

additional certificate authority validates the first certificate authority, it is done on level 2. With each<br />

additional certificate authority that is involved, the level increases by one.<br />

When a certificate authority validates another certificate authority, it issues and signs a certificate for<br />

this authority. However, instead of being validated by another certificate authority, a certificate<br />

authority can also validate itself by issuing and signing a certificate. This certificate is then called a<br />

self-signed certificate.<br />

The certificates involved in the validating process are said to form a certificate chain. In the simplest<br />

case, a certificate chain has only two members: the certificate the appliance sends as a server to its<br />

clients and the self-signed certificate of the certificate authority that signed the server certificate on<br />

level 1. The certificate authority that stands at the beginning of the validating process is known as the<br />

root certificate authority (root CA).<br />

Information on a certificate chain includes data on all the certificate authorities involved. The appliance<br />

needs to send this information to its clients if not all of these certificate authorities are known and<br />

trusted by the clients.<br />

Certificate chain — Input field for entering information on a certificate chain<br />

After importing an existing certificate authority (CA) that is involved in a certificate chain, the<br />

information on this certificate chain appears in the field.<br />

Perform insecure renegotations — When selected, the module renegotiates the parameters for<br />

the SSL-secured communication even if this is insecure to do<br />

Client cipher list — String of Open SSL symbols used for decrypting client data<br />

SSL session cache TTL — Time (in seconds) for keeping the parameter values of a session in<br />

SSL-secured communication stored in the cache<br />

SSL protocol version — Version of the protocol the SSL Scanner module follows when it performs a<br />

handshake<br />

• TLS 1.0 — When selected, TLS (Transport Layer Security) version 1.0 is used<br />

• SSL 3.0 — When selected, SSL version 3.0 is used<br />

For more information on how to create a new certificate authority or import an existing certificate<br />

authority for use instead of the default one, see Create your own certificate authority and Import a<br />

certificate authority.<br />

<strong>McAfee</strong> <strong>Web</strong> <strong>Gateway</strong> <strong>7.1.5</strong> <strong>Product</strong> <strong>Guide</strong> 225

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!