SSL-Interception

notempty

Dieser Artikel bezieht sich auf eine nicht mehr aktuelle Version!

notempty

Der Artikel für die neueste Version steht hier

notempty

Zu diesem Artikel gibt es bereits eine neuere Version, die sich allerdings auf eine Reseller-Preview bezieht

Configuration of the SSL interception in the HTTP proxy

Last adaptation to the version: 12.5.2

New:

• SNI validation without webfilter

notempty

This article refers to a Resellerpreview

12.2 11.7

Access: UTM-IP:Port or UTM-URL:Port
Port as configured at Network / Appliance Settings / Webserver
Default-Port: 11115
i.e.: https://utm.ttt-point.de:11115
Default: https://192.168.175.1:11115 → Applications →HTTP-ProxyTab SSL-Interception

Part of the HTTP-Proxy

SSL-Interception

SSL-Interception

Caption	Value	Description	SSL Interception tab
SSL-Interception:	On	Activates the SSL interception		SSL Interception tab </includeonly>
Webfilter based:	No	When enabled, only connections blocked by the web filter are intercepted. This avoids the problem that there are sites that do not tolerate an interruption of the encryption (e.g. banking software) without having to define an exception for it.
Validate SNI Only available when "Webfilter-based" is active.	No	Bei Aktivierung Yes wird eine sich ggf. im ClientHello des TLS-Handshake befindliche SNI geprüft. Dabei wird der enthaltene Hostname aufgelöst und die Adressen im Ergebnis mit der Zieladresse des abgefangenen Requests abgeglichen. Bei Nichtübereinstimmung wird die Verbindung geschlossen. Without Server Name Indication validation, clients can manipulate SNI arbitrarily to bypass the web filter. This setting should only be considered as a last resort when it seems impossible to standardize the DNS settings between the HTTP proxy and the UTM clients. Verwenden Client und UTM unterschiedliche DNS-Server, kann es dabei zu false-positives kommen.
SNI in den Ausnahmen validieren:notempty New as of v12.5.2 Nur verfügbar, wenn Webfilter basiert nicht aktiv ist	No	Wendet die Server Name Indication Validierung nur auf aktivierte Yes  Ausnahmen für SSL-Interception  an
Allow non identified protocols:	Yes	If this switch is deactivated, unrecognized protocols are blocked
CA-Certificate:	CA-SSL-Interception	Here, a CA must be selected that can re-encrypt the connection after decryption (and scanning). The public key of the CA must be installed on all client computers that are to use SSL Interception. Download can be done here directly with  ⬇Download public key .
	Download public key	The public key should be installed on the clients that are going to use SSL interception to avoid certificate errors.
Peer verification:	Off	This should definitely be enabled With this, the HTTP proxy checks whether the certificate of the called page is trustworthy. Since the browser only sees the local certificate, a check by the browser is no longer possible.
Exceptions for SSL-Interception	On	It is possible to define exceptions in the format of Regular Expressions. However, since only https can arrive here, it is not filtered for protocols, unlike the virus scanner. With + Regex new exceptions are added. So an exception for www.securepoint.de would be: .*\.securepoint\.de"    Regex exceptions do not apply to transparent mode!
Peer verification exceptions	Aus	Here exceptions for certificate verification in regex format can be added.