Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create a best practices document for secrets with running checks #94

Open
majormoses opened this issue Dec 29, 2017 · 1 comment
Open

Comments

@majormoses
Copy link
Member

I see a lot of folks accidentally expose secrets in sensu by providing them directly in the command parameters. We should Talk about the dangers of such and how to properly use token substitution and redaction to prevent the leakage.

@majormoses
Copy link
Member Author

ping @absolutejam.

My thoughts on an outline:

  • what this is all about?
  • what are the real dangers?
  • what are the solutions?
  • if there are good and bad try to illustrate both and why they might be a good/bad idea.
    There are definitely similarities lending a similar format to best practices on installing plugins #89

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants