Or a CloudHSM if you trust the certification: https://aws.amazon.com/cloudhsm/. - Source: Hacker News / over 2 years ago

Data at rest is precisely what it sounds like - static data persisted to storage. Other than securing access to your data with proper controls we have already mentioned, it may be necessary to encrypt it as well. You can choose to encrypt it before committing it to storage (Client Side Encryption) or you can let AWS help you, using S3 bucket encryption, AWS Key Management System (KMS) or if you're operating in a... - Source: dev.to / almost 3 years ago

And you're still commenting like you've never heard of HSM: Https://aws.amazon.com/cloudhsm/. Source: about 3 years ago

AWS KMS with a KMS custom key store key management backed by CloudHSM. - Source: dev.to / about 3 years ago

Have you considered something like CloudHSM? Source: over 3 years ago

Git Secret is an essential bash tool for developers and DevOps professionals, offering a robust solution for secret management within a Git repository. This open-source tool effectively encrypts sensitive files and data, ensuring that confidential information like passwords, keys, and credentials are securely stored in the repository. - Source: dev.to / over 1 year ago

Secrets inside the repo. All the credentials, ssh keys, VPN configs can be stored directly in the repo with support of the git secret. Gpg key is optional: config works fine if it is not provided and secrets are not decrypted. Source: over 1 year ago

You might notice that some of the environmental variables have funky values that look more like template placeholders. For example "SESSION_STORAGE_SECRET=${SESSION_STORAGE_SECRET}". That's because there's a .env file that contains those (you can see it in the root of the GitHub repository page. As a good practice I try to isolate anything that needs to be secret right off the top. So even though this is a... - Source: dev.to / almost 2 years ago

There are a number of possible solutions: https://github.com/spwhitton/git-remote-gcrypt https://github.com/AGWA/git-crypt https://github.com/sobolevn/git-secret Most people who self-host a Git repository are fine with just transport-level encryption (TLS). - Source: Hacker News / almost 3 years ago

Hey guys, So I'm using git-secret as of now. Just stumbled across Mozilla SOPS today and finding it interesting. Which one you guys recommend and why? Advantages and disadvantages of each? I think SOPS is more robust and stable since it is being maintained by a large organization? Please correct me if I'm wrong. Help is appreciated. Source: almost 3 years ago