182
submitted 7 months ago by [email protected] to c/[email protected]

As the title says, I want to know the most paranoid security measures you've implemented in your homelab. I can think of SDN solutions with firewalls covering every interface, ACLs, locked-down/hardened OSes etc but not much beyond that. I'm wondering how deep this paranoia can go (and maybe even go down my own route too!).

Thanks!

you are viewing a single comment's thread
view the rest of the comments
[-] [email protected] 2 points 7 months ago

I'm a Nixos user, I wouldn't be much help unless you do Nixos. But it's a whole new rabbit hole which would take you months/years to learn and setup 😅

What I can say, you can do "access from home network", "access from VPN network", "1fa/2fa from the internet" OR "access for / and /api, but 1fa/2fa for stuff like /admin, /admin-settings, or just /login or /logged-in"

Fail2ban is fun, also maybe have a look at crowdsec

[-] [email protected] 1 points 7 months ago

Ah, yeah, I'm running Proxmox. And I'm definitely seeing I have a lot of research to do before I open up to the internet!

[-] [email protected] 1 points 7 months ago

I'm actually not from the "close everything, don't open ports, always sit behind cloudflare" camp

We selfhost so we can use and share our services

There are other things we can practice instead of just isolationism and keeping everything as simple as possible

this post was submitted on 06 Feb 2024
182 points (99.5% liked)

Selfhosted

39257 readers
209 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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. 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.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

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

Questions? DM the mods!

founded 1 year ago
MODERATORS