I’m having trouble staying on top of updates for my self hosted applications and infrastructure. Not everything has auto updates baked in and some things you may not want to auto update. How do y’all handle this? How do you keep track of vulnerabilities? Are there e.g. feeds for specific applications I can subscribe to via RSS or email?

  • bigDottee@geekroom.tech
    link
    fedilink
    English
    arrow-up
    1
    ·
    4 days ago

    I’ve just started to delve into Wazuh… but I’m super new to vulnerability management on a home lab level. I don’t do it for work so 🤷🏼‍♂️

    Anyways, best suggestion is to keep all your containers, vms, and hosts updated best you can to remediate vulnerabilities that are discovered by others.

    Otherwise, Wazuh is a good place to start, but there’s a learning curve for sure.

  • lambalicious@lemmy.sdf.org
    link
    fedilink
    English
    arrow-up
    3
    ·
    7 days ago

    I don’t.

    Yeah, hot take, but basically there’s no point to me having to keep track of all that stuff and excessively worry about the dangers of modernity and sacrifice the spare time I have on watching update counter go brrrr of all things, when there’s entire peoples and agencies in charge of it.

    I just run unattended-upgrades (on Debian), pin container image tags to only the major version number where available, run rebuild of containers twice a week, and go enjoy the data and media I built the containers and installed for software for.

  • F04118F@feddit.nl
    link
    fedilink
    English
    arrow-up
    1
    ·
    6 days ago

    GitOps + Renovate.

    Tools that allow you to work GitOps (everything is defined in text files in Git) are:

    • Kubernetes
    • NixOS
    • to a lesser degree, Ansible

    Here’s a nice starter template for running your own Kubernetes cluster via GitOps with Renovate pre-configured: https://github.com/onedr0p/cluster-template