sͧb̴ͫƸ̴gͬᵉ<p>I think <a href="https://infosec.exchange/tags/Microsoft" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Microsoft</span></a> have given themselves enough rope with <a href="https://infosec.exchange/tags/Recall" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Recall</span></a>. For Reasons, running anything like it would be flat out, no discussion, illegal in my org. As <a href="https://infosec.exchange/tags/CISO" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>CISO</span></a> I’m sensitive to such things… :) </p><p>Sure we run a MSFT shop, and sure they theoretically have access to all that data anyhow - can’t [viably yet] process ciphertext, they see all the cleartext at some point.</p><p>The rope part is that argument. If MSFT argues that they see all data *anyway* so why not Recall, they burst our collective hallucination that various <a href="https://infosec.exchange/tags/GDPR" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>GDPR</span></a> agreements are actually worth a damn [Narrator: They’re not].</p><p>And then, my <a href="https://infosec.exchange/tags/infosec" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>infosec</span></a> friends, I get to eject Microsoft - and coincidentally all other <a href="https://infosec.exchange/tags/US" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>US</span></a> <a href="https://infosec.exchange/tags/cloud" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>cloud</span></a> services as well as collateral damage - and finally build a full scale Linux/FOSS environment.</p><p>It’ll be more fun than I can <a href="https://infosec.exchange/tags/recall" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>recall</span></a>!</p>