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

Selfhosted

39435 readers
8 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
 

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] 11 points 9 months ago* (last edited 9 months ago) (3 children)

I'm an enterprise guy, so that's the explanation for non home use things.

  • VPN for anything not my web or certificate revocation distribution point
  • Sophos IPS
  • sophos utm for web application firewall
  • transparent inline web proxy, sophos is doing https inspection. I have internal CA and all clients trust it. I don't inspect medical or banking, other common sense stuff.
  • heavily vlan segmented with firewall between
  • my windows clients are managed by active directory with heavy handed GPOs.
  • least priv accounts, different accounts for workstation admin, server, domain, network devices
  • security Onion IDS
  • separate red forest that has admin accounts for my management access and accounts on devices
  • trellix antivirus and global reputation based file monitoring
  • I've started applying disa STIGs on servers
  • site to site VPN with other family member household. They get managed trellix av also.
  • my public identity accounts like MS,.Google, etc all need 2fa, token, etc.

I bet this can still get exploited, just would take effort hopefully none does for a home network.

I'm still one shitty windows zero day click away from getting my workstation or browser tokens owned though, I can feel it.

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

I'm still one shitty windows zero day click away from getting my workstation or browser tokens owned though, I can feel it.

As somebody taking like 0% of all that measures and not having any problem, luck was involved for sure, unless they have a good reason to attack you in particular... I feel like you will be fine...

[–] [email protected] 2 points 9 months ago

Ha, probably. It's fun to learn stuff though.

Working in this field, almost every company has been beached, IP stolen, etc.

Sometimes your home IP gets hit in an automated scan for a vulnerability and then auto exploited by automation. I'm hoping not to get random chance added to a botnet.

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

You seem to have a great setup. Since this comment touches on slightly advanced topics, I'll ask this here:

  1. What use do you have for a WAF?
  2. How did you get your Android clients to trust your certificate? Do you use an MDM? Did you root your devices to access the trusted root store?
  3. Segmenting stuff with VLANs, subnetting and ACLs is a great idea, but do you also make sure that the firmware of the device is somewhat robust? Although I suppose you don't have to worry about it if Sophos sends out regular updates, however I hate the idea of my switches and routers having to connect to the Internet, pass along credentials and the sort to be able to get updates.

Your measures seem to be focussed more on security than privacy - which is great! It's my fault for not specifying it in the post, but I'd definitely like to know if you have done anything specific to keep your network private as well as secure.

Thanks for your wonderful comment - saved!

[–] [email protected] 1 points 9 months ago (1 children)
  1. Exchange on prem 😳
  2. Both mdm,.Ms intune, and just installing the root cert manually in trusted store. You don't have to root Android for that. It presents some warnings, appropriate.
  3. My Sophos is self contained. It does radius against active directory. It wants IPS and other updates though.

I guess the firmware is as good as possible. All network devices are just computers and can be exploited. I use a Cisco router as my actual gateway. Sophos is inline after that.

Privacy. 🤔

Not much. I have certain traffic go through a VPN to the Internet, but that's split tunneled.

I use incognito? That doesn't really do anything, ha.

I'm slowly killing web browser tracking and cookie stuff that group policy allows.

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

I didn't know MS exchange could be used as a WAF. Will need to read more about that.

Can I host Intune completely on-prem?

What do you mean by "My Sophos is self-contained"?

Does your Cisco router get updates? My problem with these companies is that they build backdoors in their firmware for agencies to use. Are you monitoring the network usage of your Cisco gateway?

Using AD/RADIUS on-prem is an intriguing idea. I didn't consider it because if my AD server goes down I'm essentially locked out of my services. I need to think more on this. Thanks.

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

Sorry for confusion. I use Sophos utm as a WAF for exchange. Basically reverse proxy that is specifically programmed for exchange attacks. It allows OWA to keep working.

I put the exchange admin URL behind authentication, so you try to go to /ecp, it Sophos intercepts and make you authenticate to Sophos utm first, which is passing to ad with radius.

MS got rid of intune on prem. It's only Azure service now. I think.

My router is my biggest vuln. Oddly the most important. It's an enterprise ISR. It's updated as far as possible. My paranoia ends with the US gov/NSA. I don't care if they want back door oddly. I don't want China using me for attack relay however.

Loads of monitoring. You do a span/mirror port to your IDS like security Onion. Let it analyze all your traffic. Apparently there are some state sponsored exploits that allow them to owe a router at kernel level and hide their activities from you and monitoring, but that's a level I can't deal with.

As far as lock out, you create a break glass on everything. Emergency account with non rememberable ridiculous password, saved in a safe place.

[–] [email protected] 2 points 9 months ago

As far as lock out, you create a break glass on everything. Emergency account with non rememberable ridiculous password, saved in a safe place.

This is such a great and a simple idea. Thanks.

I think I followed your setup at a high level, but because I don't have hands-on experience with AD I didn't quite catch the scope of it. Thanks for letting me know, I'll get some reading done when I get the time!

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

I have the older Sophos utm, which doesn't use the Sophos cloud central manager.

I think their new firewall utm can work disconnected, but I don't know.

Sophos has a home use license that's free for non business use.

I love companies that do community edition or free home use.

Sophos, Veeam has nfr, Elastiflow has community edition, which is a netflow.

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

This is the first time I've come across Elastiflow, thanks for mentioning it. Seems like an intriguing service to add.

I was considering using Suricata/installing Security Onion to do IDS from the certificate from a private CA. Sophos firewall seems pretty good too.