Ruby Rogues
Secrets Management Best Practices and Tools - RUBY 655
Brian Vallelunga
And that way you have robust audit logs of like, okay, the secret was taken by X developer at this time or read by this time. And we, we can, we have this auditor of what happened. Um, so you don't want to basically create one master. I am credential and just share it with your entire team because then you lose a lot of your auditing story along with it. Um,
0
💬
0
Comments
Log in to comment.
There are no comments yet.