At least with AWS they're clear that this is the only type of proactive scanning they do on their ZDR AI endpoints. With Azure it's actually unclear exactly how much more falls into the synchronous scanning pipeline, though I may be missing some docs.
The way this was explained to me is although there is no legal requirement to do this, vendors are concerned that AI processing constitutes "actual knowledge" of the content unlike a lot of traditional cloud-based workloads, which would expose them to legal liability. Seems like a weird argument in a ZDR context, but anyway, there's also a public optics element too I'm sure.
This whole thing kind of puts the industry in a bind. On one hand, the big labs do have an incentive to get this kind of thing rolled out so as to avoid open weight on-prem AI gaining traction, and to remove remaining roadblocks to corporate adoption in regulated industries. But rolling it out risks attracting even stronger regulatory responses for them as well (that's even setting aside likely national security/law enforcement pushback), as well as likely being strongly opposed by the AI safety people. There's no one way to square the circle that will please everyone. My guess is the labs will take a third route: continue to lobby against open weight models, thus killing the possibility of on-prem, and then drag their heels on E2EE/secure enclave models except perhaps for military customers.
Because of economies of scale with batch inference as seen with DS4.1 Flash, this is the only avenue for true privacy from frontier models at scale/cost.
In terms of policy, I agree it's looking dire. There's unfortunately just more money/lobbying/mindshare on the 'safety at all costs' camp but I'm still advocating and educating where I can.
"ZDR, except for _______" is not ZDR.