I think there are more prominent questions to ask.
Even if a remote share isn't mapped on a workstation, that wouldn't necessarily mean it's protected from being infiltrated by other network scanning tools. Personally, I've not seen the need to axe mapped drives in the networks I manage. In a sense, every service or bit of connectivity we deploy introduces some sort of surface area that could be utilized in an attack. In one sense it's an unanswerable question of what ransomware you'll get hit with when or if that actually happens. I saw this post about having to restore Google Drive data after being hit with ransomware: SW Ransomware & Google Drive This got me thinking, if my machine were to get hit with ransomware / cryptoware would this make it easier to encrypt my entire Google Drive content? Or would it have been easier to encrypt content before? What best practices should be followed to reduce the likelihood of a Google Drive being encrypted - besides not syncing to it. The new Drive for Desktop now uses a mapped drive letter instead of just a folder on the PC. Alas now I must choose to sync everything from My Drive to my local hard drive or stream files from the cloud to my PC (with some option to have certain files available offline). Everything seemed to go smoothly and I gained about 150 GB of free hard disk space after deleting the old Google Drive folder. So yesterday I updated my Google Drive sync client from Google's backup and sync to Google Drive for Desktop.
0 kommentar(er)
