You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Support secret files encrypted with SOPS (Secrets Operations). Basically, the idea is to let users work with encrypted files directly, so stuff like API keys, credentials, and sensitive configs stay secure. Nuclei would handle the decryption part on the fly, making things way safer and easier to manage.
Describe the use case of the feature
Encrypt any sensitive data, store it in repo, and never worry about exposing plaintext secrets.
Just point Nuclei to a SOPS-encrypted file, and it handles the rest. No extra steps like decrypting manually.
Makes it easier to follow security policies that require encryption while reducing the risk of leaks.
Describe alternatives you've considered
Store secrets as env vars. This is okay for small setups, but it gets messy with lots of secrets.
Describe your feature request
Support secret files encrypted with SOPS (Secrets Operations). Basically, the idea is to let users work with encrypted files directly, so stuff like API keys, credentials, and sensitive configs stay secure. Nuclei would handle the decryption part on the fly, making things way safer and easier to manage.
Describe the use case of the feature
Describe alternatives you've considered
Store secrets as env vars. This is okay for small setups, but it gets messy with lots of secrets.
Ref:
env
helper function dsl#192Additional context
SOPS is super handy for encrypting files and works with backends like GCP KMS, AWS KMS, Azure Key Vault, HashiCorp Vault, and even age.
The text was updated successfully, but these errors were encountered: