3 ms·
The risk is not completely unmitigated in that they generate random database, user, and passwords automatically. These are not the 'appname' password your secur
by rietta 8y ago
The risk is not completely unmitigated in that they generate random database, user, and passwords automatically. These are not the 'appname' password your security-clueless developer chose. The question is what is the risk that PostgreSQL has an authentication bypass vulnerability. Compared to the risk that your web app developers got authentication and authorization at the web app layer wrong, this is very unlikely. And given such a web application vector, your database behind the firewall is just as vulnerable to attack through the web app.
- koolba 8y ago> The question is what is the risk that PostgreSQL has an authentication bypass vulnerability. Well there was the whole OpenSSL Heartbleed issue that would only be an issue if the DB is network accessible: https://blog.hagander.net/postgresql-and-the-openssl-heartbleed-vulnerability-219/ https://blog.hagander.net/postgresql-and-the-openssl-heartbl... > Compared to the risk that your web app developers got authentication and authorization at the web app layer wrong, this is very unlikely. And given such a web application vector, your database behind the firewall is just as vulnerable to attack through the web app. More layers and defense in depth is always a win for security. If nothing else, it limits your attack surface and gives you time to respond to an issue in one your layers.
- rietta 8y agoOh I agree on the layers. I'm all about the defense in depth.