Treat UTM Proxies as Network Protocols
When adding a new 'Service Definition', we need to be able to pick one of the proxy services as the 'Type of definition' so that we can enable tighter security on non-standard ports.
An example of this would be to define a new service named "HTTP.8080" of type "HTTP" source port "1:65535" and destination port "8080" to allow 8080 traffic to still be scanned by the Web Security HTTP proxy.
Another example of this would be to make a new service named "HTTPS.444" of type "HTTPS" source port "1:65535" and destination port "444" to allow 444 traffic to still be scanned by the Web Security HTTPS proxy.
This is similar to many other suggestions for non-standard ports for web or email protection; but this feature REALLY needs to exist so I may as well throw my $0.02 in from a fresh perspective.