Custom List

The Custom Lists section allows you to configure custom whitelists and blacklists.

Configure Blacklist and Whitelist – Allows you to define strings for matching common names in SSL certificates. Entries are case-insensitive and are used in pattern-matching fashion, as shown in Blacklist and Whitelist: pattern matching:

• 67.115.118.87 is currently the IP address to which sslvpn.demo.sonicwall.com resolves, and that site uses a certificate issued to sslvpn.demo.sonicwall.com. This results in a match to “sonicwall.com” as matching occurs based on the common name in the certificate.
• This is the decimal notation for the IP address 63.208.219.44, whose certificate is issued to www.megaproxy.com.
• www.freeproxy.ru will not match “prox” as the common name on the certificate that is currently presented by this site is a self-signed certificate issued to “-“. This can, however, easily be blocked by enabling control of self-signed or Untrusted CA certificates.

To configure the Blacklist

1. Navigate to Network > Firewall > SSL Control > Custom List > Blacklist.

2. Click + icon. The Add Blacklist dialog displays.

   

3. Enter the certificate’s name in the Certificate Common Name field.

   List matching is based on the subject common name in the certificate presented in the SSL exchange, not in the URL (resource) requested by the client.

4. Click Add.

   Changes to any of the SSL Control settings do not affect currently established connections; only new SSL exchanges that occur after the change is committed are inspected and affected.

To configure the Whitelist

1. Navigate to Network > Firewall > SSL Control > Custom List > Whitelist.

2. Click + icon. The Add Whitelist dialog displays.

   

3. Enter the certificate’s name in the Certificate Common Name field.

   List matching is based on the subject common name in the certificate presented in the SSL exchange, not in the URL (resource) requested by the client.

4. Click Add.

   Changes to any of the SSL Control settings do not affect currently established connections; only new SSL exchanges that occur after the change is committed are inspected and affected.