Selfhosted

39435 readers

4 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago

MODERATORS

[email protected]

Security considerations for accessing NAS in external network (slrpnk.net)

submitted 3 months ago by [email protected] to c/[email protected]

10 comments fedilink hide all child comments

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?

top 10 comments

sorted by: hot top controversial new old

[–] [email protected] 9 points 3 months ago (1 children)

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

[–] [email protected] 1 points 3 months ago

I'd appreciate it very much!

[–] [email protected] 6 points 3 months ago (1 children)

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.

[–] [email protected] 1 points 3 months ago (1 children)

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!

[–] [email protected] 5 points 3 months ago

so all rules would have to be applied on the Pi itself

Sounds like you'll want to setup IPTables

[–] [email protected] 4 points 3 months ago (1 children)

Go the other way. Have the backup server connect in to the rest of the network.

[–] [email protected] 1 points 3 months ago

I was considering doing something similar to OP, but I also think it's better to do it the other way around, having the backup server connect to the network when it's time to do a backup. Then you can just use the trusty ssh/rsync combo for backup.

[–] [email protected] 3 points 3 months ago

I think you can have password auth in Samba.

That being said, the more important thing is to protect your VPN network.

[–] [email protected] 2 points 3 months ago* (last edited 3 months ago) (1 children)

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.

[–] [email protected] 0 points 3 months ago

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.