3 ms·
I think you’re right. Fifteen years ago would have been the right time to disable macros by default. Now, we have the technology to sandbox everything to largel
by jimbob45 5y ago
I think you’re right. Fifteen years ago would have been the right time to disable macros by default. Now, we have the technology to sandbox everything to largely mitigate security concerns.
However, sandboxing is a much higher investment from MS’ POV. This feels like they’re making this move specifically to distract from the fact that they should have made the tech investment into sandboxing today.
- jodrellblank 5y ago> "This feels like they’re making this move specifically to distract from the fact that they should have made the tech investment into sandboxing today." cough https://docs.microsoft.com/en-us/windows/security/threat-protection/windows-sandbox/windows-sandbox-overview https://docs.microsoft.com/en-us/windows/security/threat-pro... That's been built into Windows 10 Pro since Dec 2018.
- iancarroll 5y agoI don’t think any platform, either Linux or Windows, has successfully implemented secure sandboxing aside from true virtualization, if that. The isolation provided by kernel-level sandboxing like cgroups has proven to be a thin layer of protection in practice; it will just shift the problem to fixing sandboxing issues.
- kritr 5y agoI think https://gvisor.dev/ https://gvisor.dev/ might be the closest thing I can think of to container level sandboxing that tries to add meaningful security guarantees.
- kritr 5y agohttps://docs.microsoft.com/en-us/windows/security/threat-protection/microsoft-defender-application-guard/md-app-guard-overview https://docs.microsoft.com/en-us/windows/security/threat-pro... Office “Sandboxing” is a thing today.