4 ms·
Would be interested in hearing other things that HN'ers do to limit risk. Mostly the same basics as you. The document you linked is a good starting point. I'd
by Silhouette 4y ago
Would be interested in hearing other things that HN'ers do to limit risk.
Mostly the same basics as you. The document you linked is a good starting point.
I'd add extensive use of virtualisation and sandboxing. I run less and less software as native, installed applications on any device I use personally or professionally. Instead it tends to run inside things like VMs or Docker containers or cloud-hosted platforms now.
My basic policy is to try and make every device and installed application expendable/replaceable in case anything breaks or gets compromised and then focus on the data. I apply the principle of least privilege for access to any sensitive data, try to keep all important data in standardised formats and avoid lock-in effects as much as reasonably possible, and keep good back-ups under my own control with the ability to redeploy/restore anything quickly and as automatically as possible.
- BLKNSLVR 4y ago100% with you on the entirety of your last paragraph. I generally use a device as an access mechanism; a configured window into the data. This configuration is the only thing lost when a device is lost. No data, no function, no service. Configure the replacement device and continue as you were. Virtualisation and Docker-isation makes backups and restores almost enjoyable.
- amelius 4y agoHow do you deal with leaking of data?
- BLKNSLVR 4y agoNot sure I fully understand the context of the question, but for a device to gain access it needs to be allowed into the local network by being in wifi range or authorised on the VPN, plus have username/password access to the service/data. If, however, there's a backdoor I don't know about, then I'm pwned.