3 ms·
They seem to be betting the farm on the containerization will contain (heh) whatever security issues that come up. This in the sense, i guess, that if they hav
by digi_owl 11y ago
They seem to be betting the farm on the containerization will contain (heh) whatever security issues that come up.
This in the sense, i guess, that if they have a security flaw in their php that gives disk access, all the attacker will see is the content of the php container as the database will be on the next container over.
Then again the containerization seems to have come alongside devops, where the mantra seems to be "update early, update often, to hell with stable branches".
- jfoster 11y agoI've heard of that approach (breaches being limited to a container), but I don't think it makes sense. If a security flaw exists in one container due to the stack not being updated, isn't there a pretty good chance that it also exists in the other containers? Also, for any given container, there probably still is a way for an attacker to do immense amounts of damage. With the database container you can steal customer data. With the PHP container you can remotely instruct the database to do whatever you want, or just point the code at your own database.
- u02sgb 11y agoDepends what the security flaw is. If it's (as discussed above) a php error, it's unlikely to be in your database container.