|
Like his counterparts at many universities, Bill Jiminez, systems architect at the University of the Pacific, has to balance security with the desire of faculty and students for openness. How he did that while rolling out NAC and password-management systems provides some key lessons for dealing with reluctant users.
Bill Jiminez
University networks are notoriously open and accessible. Why did you want to implement a password management system?
Was there much resistance from the students, faculty and other users? |
Requires Free Membership to View
SearchSecurity.com members gain immediate and unlimited access to breaking industry news, virus alerts, new hacker threats, highly focused security newsletters, and more -- all at no cost. Join me on SearchSecurity.com today!
Michael S. Mimoso, Editorial Director| key was that it was easy for the users and for us. We didn't need a separate database. Everything is stored in our LDAP directory and the users can do password resets themselves.
How do you handle the problem of access control, which can be tricky on a large, diverse network?
We had lots of discussions with the students and faculty about it. But the integration on the wired network was fairly transparent. And so we released it and we had a thousand users within a month, without any notifications about it. I started broadcasting it to more lists on campus and adoption has kept growing. Working with the user base ahead of time was really important in the whole process. It wouldn't have worked otherwise.
Would that same strategy apply in an enterprise?
|
This was first published in September 2008