The HIPAA concerns are very alarming. And I agree with the spirit if the article. However, I’m not sure the article is correct when it says Recall cannot be disabled. I’ve already seen other articles telling you how to turn it off. The fact that it’s opt-out and not opt-in is a huge issue, though.
Actually it is more than a local problem. Since Recall shipped with opt-out, means every computer will have this enabled. Even if you truned it off, the computer on the other end may still capture your data.
Say you said something here, regret about and delete it, but right before a user have Recall enabled see it and can just dig out your now deleted comment. Not good. This applies to HIPAA data or not.
This is essentailly a local search engine that index everything you see and others said in near real time, without repecting robots.txt.
Yes, that is also a big problem. In general you should be very aware in online meetings / screen sharing to be very cautious and deliberate with what you show. That problem has burned a streamer or two. :) Having a boring vanilla “work machine” for that sort of thing is always a good idea. Windows Recall definitely makes this problem worse! You could be doing 100% legit professional ‘work stuff’ and it could still grab things that it shouldn’t (HIPAA and many other potentially sensitive bits of corporate data).
If you disable it, make sure to check on it regularly, as MS loves to turn things back on “for you” after Windows updates run. I’ve already seen some sysadmins saying they will run a scheduled task to make sure it stays dead.
The problem with it isn’t that MS says it can be disabled, because like everything MS does it breaks its own rules constantly. I have worked in HIPAA environments and making systems block potential MS systems is a constant cat and mouse game only accomplished by firewall appliances that don’t have MS software in them
Who the fuck is making a Firewall appliance with windows software on it. Some *nix or BSD or custom bare metal kernel is what a firewall should be. You have to have very low level access to properly secure traffic on a network. Microsoft often breaks the OSINT Framework ffs, I’d never trust them as a firewall.
I’m referring to Fortigate inside of azure, basically it’s a Fortigate but it is a VM on the azure hosts in your virtual space inside the azure cloud. The MS global network that is the Azure cloud systems is pretty cool in lots of ways. Just MS is an evil empire and it sucks that they drive the world
The HIPAA concerns are very alarming. And I agree with the spirit if the article. However, I’m not sure the article is correct when it says Recall cannot be disabled. I’ve already seen other articles telling you how to turn it off. The fact that it’s opt-out and not opt-in is a huge issue, though.
Actually it is more than a local problem. Since Recall shipped with opt-out, means every computer will have this enabled. Even if you truned it off, the computer on the other end may still capture your data.
Say you said something here, regret about and delete it, but right before a user have Recall enabled see it and can just dig out your now deleted comment. Not good. This applies to HIPAA data or not.
This is essentailly a local search engine that index everything you see and others said in near real time, without repecting
robots.txt.Yes, that is also a big problem. In general you should be very aware in online meetings / screen sharing to be very cautious and deliberate with what you show. That problem has burned a streamer or two. :) Having a boring vanilla “work machine” for that sort of thing is always a good idea. Windows Recall definitely makes this problem worse! You could be doing 100% legit professional ‘work stuff’ and it could still grab things that it shouldn’t (HIPAA and many other potentially sensitive bits of corporate data).
If you disable it, make sure to check on it regularly, as MS loves to turn things back on “for you” after Windows updates run. I’ve already seen some sysadmins saying they will run a scheduled task to make sure it stays dead.
The problem with it isn’t that MS says it can be disabled, because like everything MS does it breaks its own rules constantly. I have worked in HIPAA environments and making systems block potential MS systems is a constant cat and mouse game only accomplished by firewall appliances that don’t have MS software in them
Who the fuck is making a Firewall appliance with windows software on it. Some *nix or BSD or custom bare metal kernel is what a firewall should be. You have to have very low level access to properly secure traffic on a network. Microsoft often breaks the OSINT Framework ffs, I’d never trust them as a firewall.
I guess you haven’t used Azure much?
Hopefully not
I’m referring to Fortigate inside of azure, basically it’s a Fortigate but it is a VM on the azure hosts in your virtual space inside the azure cloud. The MS global network that is the Azure cloud systems is pretty cool in lots of ways. Just MS is an evil empire and it sucks that they drive the world
Fortigate is not a windows kernel