Now for the last 7 years I've been more on the dev side of devops, but I can't remember seeing any network appliances being sold for "enterprise" that didn't ha

Now for the last 7 years I've been more on the dev side of devops, but I can't remember seeing any network appliances being sold for "enterprise" that didn't have an option to enter a proxy for updates, or cloud services, or whatever it needed to phone home for. This could also be that for the last 15 years I've been working for very large non-tech companies that just wouldn't budge on giving a random network appliance direct access to the internet. So the vendors either added the feature for us, or those features didn't work, and maybe we didn't buy it at all. I just did some quick searches and found proxy settings for F5, juniper, cisco, infoblox, and tufin appliances. Now if the problem is that they have an option to configure a proxy, but don't trust your internal cert for the proxy itself, then the answer is to use a publicly signed cert on your internal proxy server. Even if it's just a let's encrypt one. It does feel dirty using public namespace for something that is only ever internal, but it works fine.