Google loves to mix traffic types (ad, telemetry, biz app) across protocols basically creating their own overlay which is a huge pain.
For Apple, we basically have to exempt the entire 17.0.0.0/8 as that is theirs and they pin everything.
Microsoft at least has several dynamic lists but I have my own list of their stuff that ISN'T on their lists (a few hundred IPs).
At this point I don't think there's any way to secure a network. You can't trust or verify much of the traffic.
Maybe using a synthetic NIC at the endpoint that is directly tied to the policy system is the only way forward.
You mean hardware products, right? In this case putting them in a separate VLAN would help. I you mean software running on your machine, you can set up a proxy and block all traffic not coming through it.
So I still believe "High Entropy" is a better description than "Fully Encrypted Traffic".
I mean, you can pack the entire data stream in Base64 after sending them through a SHA256 pipeline, and it will still be "Fully Encrypted", but the entropy (in terms of traffic classification by content scanning) is not the same compare to doing it without the Base64 step.
I wonder if you can run this in observe only mode to analyze/log that traffic.
You have no idea how much time I've wasted trying to block some products from pinging their home server with curious data stream, but failed to do so because I can't be bothered to sit my ass in front of Wireshark to sniff out all their DoH servers.
With this project, it's hopeful that in the future I can just not putting their domains in the TLS whitelist, even when they use DoH.
---
Off topic but BTW: "Fully Encrypted Traffic" is really a confusing term that can only be understood correctly if the context is correct too. How about calling those protocols "High Entropy" (HighE)? Which IMO is more specific than calling it "Fully Encrypted". It's just my two-cents suggestion.