Question for IT departments using LastPass

[David Curry <david.curry () NEWSCHOOL EDU>]

We're just beginning our move off of Thycotic Secret Server and onto
LastPass Enterprise for our IT department, to manage all the server,
database, application, etc. passwords. In our Thycotic environment, we took
a very hierarchical approach to storing things, with permissions set
generally along the org charge structure. The different "silos" of the
department had access to different areas of the vault, and there wasn't
much cross-silo access. That worked for a while, but as the organization
started changing, it started getting in the way of getting things done.

Now we're thinking, partly because our organization has changed and there's
much more cooperation and working together than there used to be, but also
because LastPass doesn't support the same hierarchical storage model, that
we should be organizing things more simply. But while we have some
high-level ideas on how we might want to do this, we're not quite sure of
the details. So we're hoping to learn from others who've already done it.

If your IT department is using LastPass internally to manage the
department's passwords and share them with staff, how have you chosen to
organize things storage-wise in LastPass (i.e., how have you named the
folders and what have you put into them)? And how have you set up your user
groups for sharing purposes?

Thanks,
--Dave

--

DAVID A. CURRY, CISSP
*DIRECTOR • INFORMATION SECURITY & PRIVACY*
THE NEW SCHOOL • INFORMATION TECHNOLOGY

71 FIFTH AVE., 9TH FL., NEW YORK, NY 10003
+1 646 909-4728 • david.curry () newschool edu

**********
Replies to EDUCAUSE Community Group emails are sent to the entire community list. If you want to reply only to the 
person who sent the message, copy and paste their email address and forward the email reply. Additional participation 
and subscription information can be found at https://www.educause.edu/community