We're looking at our Sierra logins from a security perspective and trying to make some changes in the interest of better security.
We have 8 locations with anywhere from 2 to 15 shared circulation terminals at each. Each terminal has its own login (we track circulation by stat group/terminal). These terminals use a shared Sierra password. We change this shared password every 6 months, in compliance with our internal password policy.
Staff with a dedicated workstation/office (managers, supervisors, tech services) have individual logins for which they create their own password.
Our public and staff networks come from one external IP address. By opening our (hosted) Sierra server up to these networks, we're opening it to our staff and public machines and our staff and public wi-fi. Anyone with knowledge of our Sierra Web URL and shared login credentials (or the ability to guess either) can access Sierra from our parking lot on the public wi-fi. We have turned off Sierra Web for all the logins that have a shared password, but with Innovative on track to move Sierra entirely to the web client we're going to have to grapple with it eventually.
Turnover with frontline staff is constant. I can't imagine changing the shared password for all of them each time someone leaves.
We're considering context users with individual credentials for each staff person. This would be much easier if Innovative permitted us to push credentials from Active Directory. In lieu of that, we're considering a username/password OR username/PIN approach.
--What is everyone else doing about logins and security? Did you draw a line somewhere for the sake of your staff?
--If you use individual logins, how has this been for your hourly/part time staff? For your less technically-inclined staff? We're concerned about putting another stressor on staff--Type in your complicated password correctly while this patron is breathing down your neck about fines!
--What if staff forget a password? We may have as few as 2 people working on a weekend. If one forgets the password, that leaves one person with access to Sierra.
--Do you lock Sierra after a set number of incorrect entries? How do your staff reset their passwords?
--How do you manage a large amount of logins (onboarding, termination, forgotten passwords) without being able to integrate with something like Active Directory?
--Are you waiting for Sierra to permit you to push domain credentials before you take this plunge? Do you feel that it will be easier for staff to use their domain credentials in Sierra after every timeout, or a shorter/simpler password or PIN? We have a lot of debate on this topic!
--If you’re using a timeout in Sierra, what is your inactivity period?
We’re looking in all different directions and have staff with an argument on every side of this issue. It would be nice to share some outside perspectives and feedback with my team.