DevOps

830 readers

2 users here now

Development & operations

founded 5 years ago

MODERATORS

cat_programmer@lemmy.ml

How do you store database secrets for an application in your source code management system? (lemmy.eco.br)

submitted 1 year ago by silas@lemmy.eco.br to c/devops@lemmy.ml

11 comments fedilink hide all child comments

Hi. We successfully store secrets in ansible variables files with either ansible-vault or sops. It is a good approach when Ansible itself configures something that requires a secret, such as configuring a database admin password.

But I'd like to ask you about how you store secrets meant to be used by applications. Example: we have a an application in PHP with a config.php file with all credentials needed by the application. Developers have a config.php setup to work with the test environment, while we maintain a different config.php for production in production machines. Nowadays this config.php file is stored in ansible repository, encrypted by ansible-vault or sops. We thought about moving the config.php production file to the application repository, so we could get advantage of the CI/CD pipeline.

It doesn't smell right, because it would require to encrypt it somehow, and store keys to decrypt it in CI/CD, but I decided to ask you anyway what do you think of that and how you solved it yourselves.

Thanks!

top 9 comments

sorted by: hot top controversial new old

[–] steph@lemmy.clueware.org 2 points 1 year ago* (last edited 1 year ago)

Secrets don't belong anywhere inside an application code. They're related to the runtime environnement - 'cause you don't use the same password for production and integration, right? - and should come from an external configuration source. That might be as simple as environment variables.

Application deployment should never require modification of a file that resides inside the application itself. PHP and other interpreted languages has a tendancy to promote laziness when it comes to proper release management.

And don't start with "but it makes development complicated": fix your onboarding and then tooling instead of putting the security of your users and customers at risk.

[–] MariaRomanov@lemmy.sdf.org 1 points 1 year ago (1 children)

Depends where you are deploying. If you're deploying to AWS or Azure you can use their secret manager and replace the secret text in the config.php file with the path to the secret, then write a simple utility file to read the secret. If you are deploying to a Windows Server you can store an encrypted value in the registry and write a class to decrypt/read from the registry.

[–] silas@lemmy.eco.br 1 points 1 year ago (2 children)

Thanks for the answer. I'm actually deploying to a local Linux server. Is there any tool I could use?

[–] thejml@lemm.ee 1 points 1 year ago (1 children)

We use Hashicorp Vault to do this. A local Agent on the box can get the secret for you on your behalf and either you can use that in your app launch process, or have the app call the agent or the vault server itself.

[–] silas@lemmy.eco.br 3 points 1 year ago (1 children)

That is exactly what I'm looking now! Thanks! I'm actually new to this paradigm. How is it more secure than storing password in plain text? I mean, in your application, you'll have to store a token or something, so you can query Vault server, right? If an attacker have access to the server, it can query the Vault server with the token, retrieving relevant secrets, no?

[–] thejml@lemm.ee 2 points 1 year ago

One of our apps have vault write it to a file, but rotate it regularly (like every hour or so) and have their app watch the file for updates.

Other apps query vault directly and thus it never gets written to disk. As our apps are all containerized, the password for each instance is unique and only that ephemeral container can use that password.

In fact, when the vault agent requests a password for something like a database, the agent doesn’t just share what’s in vault, but uses what’s in vault to generate a password and username that is unique to only that container and expires previous ones on a rotation.

In truth, if you had low level access to a compromised box, you could probably still sniff it out of ram or off disk, but the rotation means it’s only good for a small amount of time, and the fact that only that machine and username can use it, combined with the Least Privilege, means it’s fairly secure.

[–] MariaRomanov@lemmy.sdf.org 0 points 1 year ago (1 children)

You can probably write a utility in your PHP that just pulls the value from Ansible Vault and decrypts at runtime. Still not 100% secure but better than having the value in plaintext in your config.php.

[–] silas@lemmy.eco.br 2 points 1 year ago (1 children)

Thanks. I would still have to store ansible-vault password locally or something like that, no?

[–] MariaRomanov@lemmy.sdf.org 2 points 1 year ago

Yeah, or just continue to have two separate config files.

My team is in a bit of a different situation as we are cloud hosted but I suspect it's a similar approach. We have secrets hosted in AWS and our config file just references the secret name. We then have a SecretReader utility in our code which we reference to pull the secret from AWS at runtime, that way it doesn't show up as plaintext in our code. Our CI/CD doesn't touch the secret at all in that use case -- we only use secrets in our CI/CD if there is a step such as connecting to a DB that is part of our pipeline.

load more comments