Thycotic Community Forum

12/6/2011 8:45:48 AM Nick D Posts: 58

I don't know how other companies handle this, but the biggest drawback to Secret Server we have found is redundant secrets because someone created a secret that already exists because they didn't know it already existed or they don't have access to it. Secret Server can get messy quickly. We were thinking of a way to help resolve that. The first thing which we can do as a business process is to have a naming standard for all secrets. This can be monitored by a team that gets alerts when new secrets are created and if they dont conform to the naming standard we put in place they inform the creator to change the name. The next thing (feature request) would be if Secret server could do some sort of validation of the secret name against all other secrets. If another secret exists with the same name they get an error that it already exists. This would be a huge win for us. Thoughts? or maybe people can tell me how they handle redundant secrets in secret server when using many ACL's and AD users/groups?

0 • link

---