There are 2 ways to do https filtering:
- You can do reverse dns. For example if a host is going to an ip address on port 443, you can do reverse dns and see the domain of that ip and allow it or not. Devices like that are filtering devices that the ASA supports. Sch methods don't proxy as a man in the middle.
- You can be a man in the middle as you are saying. One of the first devices that introduced this functionality is the Ironport WSA. Of course having the mad in the middle introduces the concerns that you mention. But if you trust the certificate of the device that proxies then you can trust the transaction also.
I hope it helps.
PK