Deep Edge closes HTTPS security loopholes by decrypting and
inspecting all encrypted traffic. administrators can allow clients to access all HTTPS
traffic
for specified URL categories or source IP addresses by adding them to the HTTPS
Inspection exception list. While decrypted, data is treated the same way as HTTP
traffic to which URL filtering and scanning rules are applied. Decrypted data
remains completely secure in the Deep Edge server's memory. Before leaving the Deep Edge server, data is encrypted for
secure passage to the client's browser.
For traffic filtering, Deep Edge first queries URL categories
according to the hostname from the local pattern or local cache. If the category is
not in the local pattern or local cache, then this connection is not decrypted. To
determine whether or not to decrypt traffic, another thread will issue a Trend Micro
URL Filtering Engine (TMUFE) query at the same time and put the result into local
cache. When a user accesses the same site in the future, Deep Edge matches the decryption policy
with the category queried to the local cache.