• anteaters@feddit.de
    link
    fedilink
    English
    arrow-up
    10
    arrow-down
    6
    ·
    edit-2
    1 year ago

    It is becoming an important threat to you. Managing servers, applications and data is very complex, and the problem is that you cannot do it on your own: how do you know that the server application where you store your family photos has a secure code? it was never audited.

    How do they fix this? Do they audit and approve all source code? Do they submit security patches to the apps they have in their repo?

    In fact, the recent LastPass leak happened because a LastPass employee had a Plex server that wasn’t updated to the last version and was missing an important security patch!

    How do they fix this? Auto updates? Those are going to bite you in the ass extremely hard at some point.

    Things like this are completely untrue:

    Additionally, because every new self-hosted applications re-implement crucial systems such as authentication from scratch everytime, the large majority of them are very succeptible to being hacked without too much trouble. This is very bad because not only Docker containers are not isolated, but they also run as root by default, which means it can easily be used to offer access to your entire server or even infrastructure.

    Most tools currently used to self-host not specifically designed to be secure for your scenario. Entreprise tools such as Traefik, NGinx, etc… Are designed for different use-cases that assume that the code you are running behind them is trustworthy. But who knows what server apps you might be running? On top of that, a lot of reverse-proxies and security tools lock important security features behind 3 to 4 figures business subscriptions that are not realistic for selfhosting.

    Scaremongering and lies.