<?xml version="1.0"?>
<rss version="2.0">
<channel>
<title>Thycotic Community - Secret Server - Best Practices - Organizing Secrets - Messages</title>
<link>http://www.thycotic.com/forums/messages.aspx?TopicID=534</link>
<description>Thycotic Community - Secret Server - Best Practices - Organizing Secrets - Messages</description>
<language>en-us</language>
<docs>http://blogs.law.harvard.edu/tech/rss</docs>
<generator>Jitbit AspNetForum</generator>
<pubDate>Wed, 02 Jan 2013 08:42:34 GMT</pubDate>
<lastBuildDate>Wed, 02 Jan 2013 08:42:34 GMT</lastBuildDate>
<item>
<link>http://www.thycotic.com/forums/messages.aspx?TopicID=534</link>
<title>Message from Nick D</title>
<description><![CDATA[The best way to structure personal secrets is to NOT allow (encourage) them. This opens a very nasty can of worms if (when) someones personal password is obtained from Secret Server (i.e. mis-ACLed, Unlimited Admin Mode...etc).<br/><br/>There needs to be separation of corporate secrets and personal secrets, as such, separation of technologies. I would encourage users to use personal password vaults such as LastPass. <br/><br/>There are also some past discussions on the forum that we all discussed folder/permission structures that scale well for a large user-base. I'll see if i can dig them up, but for example we stay away from folders that are for specific teams because there is no need for them (accept if using inherit folder permissions, which we find causes more trouble than its worth). We do single departments and environments within them.]]></description>
<pubDate>Wed, 02 Jan 2013 08:42:34 GMT</pubDate>
</item>
<item>
<link>http://www.thycotic.com/forums/messages.aspx?TopicID=534</link>
<title>Message from Ray V</title>
<description><![CDATA[Sorry -- formatting looks correct (with bulleted list) in the preview, don't know why it didn't translate properly in the message.]]></description>
<pubDate>Wed, 02 Jan 2013 01:25:05 GMT</pubDate>
</item>
<item>
<link>http://www.thycotic.com/forums/messages.aspx?TopicID=534</link>
<title>Message from Ray V</title>
<description><![CDATA[How do others structure and organize their secrets?  Control access?<br/><br/>Am considering doing it in several different ways:<br/><ul><li>Team Secrets - Access based on departmental or team ACL's.  Up to a group manager to organized secrets and grant access as they see fit (example: Database Team, Security Team)<br/></li><li>Application / Environment Secrets - Similar to the above but based on individual applications or environments (example: Active Directory Administrators, Web Application XYZ Team)<br/></li><li>Personal Secrets - Each user can store their own secrets</li></ul>Thoughts on the above?  Lessons learned?  I'm trying to think how I structure the Personal secrets.  Is there the concept of a "Home Directory" folder for users?  Or could everyone's personal secrets just go in one top level folder and permissions are set automatically?  I'm thinking it makes more sense to have a Personal/Home folder with subfolder per user so permissions can be inherited more easily...<br/>Curious to hear how others out there have done this.  We have around 3000 users who may eventually have access to the system so getting this right/scalable from the get-go is important.<br/>Thanks!<br/>Ray]]></description>
<pubDate>Wed, 02 Jan 2013 01:23:45 GMT</pubDate>
</item>
</channel>
</rss>
