• 1 Post
  • 16 Comments
Joined 4 years ago
cake
Cake day: May 30th, 2021

help-circle


  • Thank you for taking the time to answer throughly! I noted your advice and chunked up my goals into “mini-projects”, once I have all the configurations set and all devices connected to the new router. I did check what I bought is a router, not a switch (I find the naming of the device acting as the gateway between the LAN and WAN to be a bit ambigous: switch, router, gateway…).

    As for the IDS capability, this is something that would be done by a raspberry pi being fed packets from the router. I don’t know if I will ever undertake that task, but I keep it in mind if I’ll feel adventorous 🙃

    (for those wondering: Linux Magazine #279 has a guide on how to accomplish this with a Fritz!Box 7583).


  • Thank you for all the questions to help me clarify my use case 🙂

    At the very basic, I’d like to:

    1. achieve better security through segmentation by isolating cloud-connected devices, guest devices from trusted devices.
    2. Being able to “pin” a Mac address to an IP, and being able to use internal network name resolution to reach those devices.
    3. a blocklist for known ad-domains / malicious domains.

    Once the basics are in place, I’d like to elevate my netsec game and implement:

    • a high level monitoring capability to seen what devices are communicating with what domains / IPs
    • An IDS capability of some sort to be able to detect anomalies in my LAN.

    The NAS part is just for convince, it would be nice to have a samba / NFS with my files available when I need them.



  • Welcome to the deep rabbit hole :-) how much do you know about how computers work? In general, you’re going to need to understand some basic networking and general Linux administration, but if you already have a grasp on that then I’d say you just need to start small (simple service, aim to have a resilience goal with backups and restoration) and other metrics that motivates you. Perhaps you want to learn something new with every service you host? You decide, this is your hobby :-)







  • I’ve tried different approaches with fail2ban, crowdsec, VPNs, etc. What I settled on is to divide the data of my services in two categories: confidential and “I can live with it leaking”.

    The ones that host confidential data is behind a VPN and has some basic monitoring on them.

    The ones that are out in the public are behind a WAF from cloudflare with pretty restrictive rules.

    Yes, cloudflare suck etc., but the value of stopping potential attacks before they reach your services is hard to match.

    Just keep in mind: you need layers of different security measures to protect your services (such as backups, control of network traffic, monitoring and detection, and so on).



  • I like this thread :-)

    I have just checked off a long standing item in my backlog: implementing OIDC on at least two apps. I’ve used a remote keycloak instance for authention for my household and so far so good. Now I’ll try to understand the configurations a little better before take on other items on my backlog.