I’m strongly considering adding another backup location in the form of an old Raspberry Pi and a USB HDD.
I want the Pi to exclusively use the available network to connect to my Wireguard Server, so other devices (local to the Wireguard Server and remote connected to the server) can use it as a secondary backup location.
I’m kind of worried about a scenario, where my network is compromised and, through the VPN connection of the Pi in the external network, the external network is as well.
What are the best practices to secure such a setup?
You must log in or register to comment.
I just did this over the weekend, I’ll try to remember to come back after work and add in my steps. It can be really confusing to parse over a bunch of tutorials
I’d appreciate it very much!
This is a exercise in network DMZ planning. Assume the NAS will be compromised, so you limit its access to the rest of the network.
put the NAS on its own VLAN in both locations, setup firewall rules so that only select protocols are allowed to/from the NAS.
That’d be the gold standard. Unfortunately, the external network utilizes infrastructure that doesn’t support specifying firewall rules on the existing separate VLAN, so all rules would have to be applied on the Pi itself or on yet another device between, which is something I’d like to avoid. Great general advice, though!
so all rules would have to be applied on the Pi itself
Sounds like you’ll want to setup IPTables
Go the other way. Have the backup server connect in to the rest of the network.
I think you can have password auth in Samba.
That being said, the more important thing is to protect your VPN network.
Use object storage and enable immutability for the backups. If they compromise your site they shouldn’t be able to delete your backups unless they have the NAS password too.
Great suggestion to secure the backups themselfes, but I’m more concerned about the impact an attacker on my network might have on the external network and vice versa.
