Re:New ‘Meow’ attack has deleted almost 4k unsecured databases
by gerdesj on Sunday July 26, 2020 @02:41PM
(#23959146)
"and long iptables rulesets are almost comically difficult to validate sometimes."
Use nmap to evaluate your policy from the outside, don't try to validate it in your head by inspection.
Re:New ‘Meow’ attack has deleted almost 4k unsecured databases
by acdha on Sunday July 26, 2020 @06:05PM
(#23960541)
Use Shodan.io’s monitor feature and you’ll get alerting, too.
Re:New ‘Meow’ attack has deleted almost 4k unsecured databases
by gavinray on Sunday July 26, 2020 @03:28PM
(#23959497)
Friendly FYI, "EXPOSE" is a no-op that is only meant as visual documentation to end-users.
"The EXPOSE instruction does not actually publish the port. It functions as a type of documentation between the person who builds the image and the person who runs the container, about which ports are intended to be published."
Second paragraph:
Re:New ‘Meow’ attack has deleted almost 4k unsecured databases
by jcrawfordor on Sunday July 26, 2020 @03:50PM
(#23959652)
I'm referring to docker-compose, where 'port' and 'expose' are container configuration options that behave differently from the Dockerfile keyword.
Although the similar words with different meanings no doubt contribute to confusion.
In general I would recommend putting some kind of protection between machines running Docker (and especially orchestrators) and the internet. This could be cloud provider mechanisms (security groups, ACLs, etc), a firewall appliance, NAT gateway configuration, etc. depending on the situation. It's not necessary, but it makes the situation easier to audit/validate, and more layers of protection seldom hurt. If nothing else it means that much of the time you'll need to make a mistake in two places instead of one, in order to have an unintended exposure.