Update: Secrets Management Cheat Sheet #1289
Assignees
Labels
ACK_OBTAINED
Issue acknowledged from core team so work can be done to fix it.
HELP_WANTED
Issue for which help is wanted to do the job.
UPDATE_CS
Issue about the update/refactoring of a existing cheat sheet.
Comments
garthoid
added
ACK_WAITING
|
@garthoid Yes this is definitely worth having more guidance on. Do you want to submit a PR? I'm happy to help as well since secrets management is one of my areas of expertise, but I don't have the bandwidth to lead the effort at this time. |
szh
added
ACK_OBTAINED
|
@garthoid do you want to work on PR for this? It can be a draft to have a starting point. |
rohitg00
added a commit
to rohitg00/CheatSheetSeries
that referenced
this issue
Nov 2, 2024
Fixes OWASP#1289 Add a new section on secrets management in a multi-cloud environment to the `cheatsheets/Secrets_Management_Cheat_Sheet.md` file. * **Introduction**: Discuss the unique challenges of managing secrets in a multi-cloud environment. * **Challenges**: List the challenges such as diverse APIs, inconsistent security policies, key rotation, access control, and auditing and monitoring. * **Best Practices**: Provide best practices including using a centralized secrets management solution, standardizing security policies, automating key rotation, implementing fine-grained access control, and enabling comprehensive auditing and monitoring. * **References**: Add references to tools and resources like HashiCorp Vault, CyberArk Conjur, AWS Secrets Manager, Azure Key Vault, and Google Cloud Secret Manager. --- For more details, open the [Copilot Workspace session](https://copilot-workspace.githubnext.com/OWASP/CheatSheetSeries/issues/1289?shareId=XXXX-XXXX-XXXX-XXXX).
mackowski
pushed a commit
that referenced
this issue
Nov 12, 2024
* Update: Secrets Management Cheat Sheet Fixes #1289 Add a new section on secrets management in a multi-cloud environment to the `cheatsheets/Secrets_Management_Cheat_Sheet.md` file. * **Introduction**: Discuss the unique challenges of managing secrets in a multi-cloud environment. * **Challenges**: List the challenges such as diverse APIs, inconsistent security policies, key rotation, access control, and auditing and monitoring. * **Best Practices**: Provide best practices including using a centralized secrets management solution, standardizing security policies, automating key rotation, implementing fine-grained access control, and enabling comprehensive auditing and monitoring. * **References**: Add references to tools and resources like HashiCorp Vault, CyberArk Conjur, AWS Secrets Manager, Azure Key Vault, and Google Cloud Secret Manager. --- For more details, open the [Copilot Workspace session](https://copilot-workspace.githubnext.com/OWASP/CheatSheetSeries/issues/1289?shareId=XXXX-XXXX-XXXX-XXXX). * Update Secrets_Management_Cheat_Sheet.md * Update Secrets_Management_Cheat_Sheet.md
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What is missing or needs to be updated?
Discussion of secrets management in a multi-cloud environment.
How should this be resolved?
Investigation and discussion of issues. I am sure this is an evolving field and I am learning myself. It affects more than Dev and CI/CD. References to existing art.
The text was updated successfully, but these errors were encountered: