4 ms·
> They didn't secure their database with auth/access control True, although they had reason to believe that that was safe. > they misconfigured docker. Ah, n
by yjftsjthsd-h 4y ago
> They didn't secure their database with auth/access control
True, although they had reason to believe that that was safe.
> they misconfigured docker.
Ah, no, that's where we disagree. They didn't configure it, docker shipped an insane default that bypasses existing security measures. There is absolutely no reason to expect that running a program in docker magically makes it ignore the system firewall.
- DistractionRect 4y agoThe sysadmin is responsible for what they install and how it's configured. Docker didn't specify what ports to open, what container to run, volume mounts, image etc. That's part of the config the sysadmin supplies when they spin it up. No matter how you slice it, it down to them not understanding what they were pushing to prod. By the same token having an unsecured database is a bad default, so we can keep passing the buck around.
- xboxnolifes 4y ago> True, although they had reason to believe that that was safe. That's like the antithesis of layered security. There would be no point in layers if you assume a single layer will protect you.