0

So say you are developing multiple different projects for different clients and want your developers to use postgres on their development machine (i.e. localhost connection in the development environment). Does one add much/anything, from a security point of view, by requiring that each project use a different postgres username and password?

I am asking because, although more security is (of course) always more secure, it also adds complexity to the development environment and I'm wondering if the trade-off is worth it. In particular, the passwords for each postgres will probably be stored in plaintext (e.g. in some yaml or .env file). If some other code was truly malicious, it could just read that file and get the password and gain access no matter what. Also, the data is usually dummy data and low sensitivity.

  • Not really. Just make sure the DB is only reachable via localhost and you're pretty secure. –  Apr 25 '22 at 14:26
  • To add to MechMK1's comment as an extra security measure I would also add it into a Docker container. – Sir Muffington Apr 25 '22 at 19:44

0 Answers0